Skip to main content

Legal

Subprocessors

Every third party that processes data to run Nexus Ledger: what it does, which data it touches and where it processes it.

Amazon: Nexus Ledger connects to your Amazon account read-only, within Amazon's Finance and Accounting role. No buyer personal data is requested.

Last updated: 5 November 2026

The register

Filter by purpose or search by vendor, activity, data or location. Every vendor that processes data is listed, whether or not a feature is part of your plan.

Filter by purpose
Showing 18 of 18
  • Supabase Inc.Primary subprocessor

    Activity
    Managed Postgres, authentication, object storage
    Data category
    All Customer Data and account data
    Location
    EU region — Stockholm, Sweden (eu-north-1). All tenant data is processed here; transfer from KSA relies on the SCC-equivalent clauses in the DPA plus the SDAIA Transfer Regulations.
  • Vercel Inc.Primary subprocessor

    Activity
    Web application hosting (Next.js), edge serving, static assets
    Data category
    Account data, page-render telemetry; Customer Data passes through during requests but is not persisted
    Location
    Global edge network; Customer documents are stored only in the EU database/storage
  • Hetzner Online GmbHPrimary subprocessor

    Activity
    Extraction-worker host — polls queued voucher batches and runs the OCR + AI extraction pipeline
    Data category
    Customer Data in flight during extraction; not persisted long-term
    Location
    European Union
  • Anthropic PBCPrimary subprocessor

    Activity
    Large-language-model inference for document classification, field extraction, journal-entry drafting, and plain-language narratives and answers
    Data category
    Document text and extracted fields submitted as model prompts; responses returned for processing
    Location
    Provider US/EU regions per their API; Customer Data is not used for model training under our agreement
  • Mistral AI SASPrimary subprocessor

    Activity
    Optical character recognition (OCR) and layout extraction on uploaded PDFs
    Data category
    Page-image submissions; OCR text returned for downstream processing
    Location
    France (EU) · Customer Data is not used for model training under our agreement
  • Speechmatics LtdPrimary subprocessor

    Activity
    Speech-to-text transcription for the voice assistant. Not part of the seller plans; used only for an account where the voice feature is enabled, and only when voice is used
    Data category
    Microphone audio of the user's spoken query; transcript returned for processing
    Location
    United Kingdom
  • ElevenLabs Inc.Primary subprocessor

    Activity
    Text-to-speech synthesis and conversational-voice transport for the voice assistant. Not part of the seller plans; used only for an account where the voice feature is enabled, and only when voice is used
    Data category
    AI assistant reply text submitted for audio synthesis; voice-session audio. No documents.
    Location
    United States
  • Resend, Inc.Primary subprocessor

    Activity
    Transactional email delivery (account, billing, trial-end notifications)
    Data category
    Recipient email address, subject and body of transactional emails
    Location
    EU region
  • Paddle.com Market Ltd.Secondary subprocessor

    Activity
    Merchant of record: subscription billing, payment processing, invoicing and sales-tax/VAT determination and remittance
    Data category
    Billing contact name and email, billing address and country, payment-method metadata (card last-four, brand), tax identifiers, invoice and subscription records
    Location
    United Kingdom / EU, with card processing via Paddle payment partners
  • Sentry GmbH (Functional Software, Inc.)Secondary subprocessor

    Activity
    Error monitoring and performance traces for the application
    Data category
    Error stack traces, request URLs (with PII redaction at source), user ID hash
    Location
    EU region
  • Better Stack (BetterStack Ltd.)Secondary subprocessor

    Activity
    Application logs aggregation and alerting
    Data category
    Application log lines; Customer Data fields are scrubbed before shipping
    Location
    EU region
  • PostHog Inc.Secondary subprocessor

    Activity
    Product analytics — pseudonymised event-level usage data (opt-out per workspace)
    Data category
    Pseudonymised user ID, event name, timestamp, page path; no document content, no keystrokes
    Location
    EU region (EU ingestion endpoint)
  • Cloudflare, Inc.Secondary subprocessor

    Activity
    Bot-challenge verification (Turnstile) on sign-in and public form endpoints
    Data category
    IP address, challenge token, request headers; no Customer Data
    Location
    Global edge
  • Upstash, Inc.Secondary subprocessor

    Activity
    Serverless Redis used as a shared counter store for API rate limiting and sign-up abuse detection
    Data category
    Rate-limit counters keyed by user ID, hashed IP address or network prefix, and a truncated hash of the sign-up email address; no Customer documents or ledger data
    Location
    Region set per deployment of the database; counter data only
  • Slack Technologies, LLC (Salesforce, Inc.)Secondary subprocessor

    Activity
    Operational alerting — posts to an internal operations channel when a scheduled job fails or a threshold trips; optionally a period-close summary when a close-pack delivery to Slack is requested
    Data category
    Job names, counts, status and pseudonymised identifiers; for a close-pack delivery, the period and posted-entry totals. No documents, no bank or buyer details
    Location
    Not applicable (metadata only)
  • Twilio Inc.Secondary subprocessor

    Activity
    Operational alerting by WhatsApp message to the operator — used only when this channel is configured in place of Slack
    Data category
    The same operational alert text as above; the recipient is the operator, not a Customer
    Location
    Not applicable (metadata only)
  • Amazon Services LLC (Selling Partner API)Customer-authorised integration

    Activity
    Read-only retrieval of settlement, fee, refund and reserve records (the Finances endpoints) from a connected Amazon seller account, within Amazon's Finance and Accounting role. Connected only when the Customer authorises it; revocable by the Customer in Seller Central
    Data category
    Amazon seller ID, marketplace ID, settlement and financial-event records. No buyer personal data is requested
    Location
    Amazon regions per marketplace; retrieved records are stored in the EU database (Stockholm)
  • Wise (Wise Payments Limited and Wise group companies)Customer-authorised integration

    Activity
    Read-only retrieval of balance statements from a connected Wise business account, used to reconcile bank deposits against Amazon settlements. Connected only when the Customer provides a Wise API token; revocable by the Customer in Wise
    Data category
    Wise profile and balance identifiers; statement transactions (date, amount, currency, fees, running balance, payment reference and counterparty name where Wise provides it)
    Location
    Wise's own processing locations for the Customer's Wise account; retrieved statements are stored in the EU database (Stockholm)

How to read the roles

Primary subprocessor
Required to deliver the core service. Customer Data is processed by them as part of normal operation.
Secondary subprocessor
Supports observability, billing, abuse prevention, operational alerting and product analytics. They do not host or persist Customer documents. Customers can opt out of product analytics for their entire workspace.
Customer-authorised integration
An external service a Customer chooses to connect. Each connection is read-only, is made only on the Customer's instruction, and can be revoked at the source. No Customer documents or ledger data are transmitted to them.

None of the subprocessors in this register use Customer Data to train or improve their own AI models. Where a subprocessor is listed because it has model-inference capabilities, our agreement with it expressly prohibits training on Customer Data and is a precondition to processing.

What changed

Dated changes to this register, newest first.

  1. Filled in the processing location of every vendor, stated the availability of the voice vendors, and regrouped the register by purpose. No vendor was added or removed.

  2. Added Upstash (rate limiting), Slack and Twilio (operational alerting), and the customer-authorised integrations Amazon and Wise.

  3. Corrected the Supabase activity: no Edge Functions are used. Nothing was added or removed.

  4. Added Paddle, the merchant of record.

Notification of changes

We give Customers at least 30 days' advance notice before adding or replacing a subprocessor, by email to the workspace's billing-contact address and by updating the "Last updated" date on this page. Customers with a Data Processing Addendum in place can object on reasonable grounds; if we cannot accommodate the objection, the Customer may terminate the subscription with respect to the affected service for a pro-rata refund of pre-paid fees.

To request the current Data Processing Addendum or our security questionnaire response pack, use the contact page.