Subprocessors
- Last updated:
- 3 May 2026
- Product:
- BuildPass Ledger / Ledger
- Provider:
- BuildPass Pty Ltd ACN 652 324 635
This page lists subprocessors and third-party services that may be used to provide BuildPass Ledger, Ledger, app.ledger.build, related websites, APIs, dashboards, integrations, support services and associated products and services (Ledger).
Ledger is built and operated by BuildPass Pty Ltd ACN 652 324 635 (BuildPass, we, us or our).
Not every provider is used for every Customer, region, feature, plan, or workflow. Some services are used only when a Customer enables a relevant feature or integration.
1. Related documents
This page should be read together with:
- the Ledger Terms of Service, available at
https://ledger.build/terms-of-service; - the Ledger Privacy Policy, available at
https://ledger.build/privacy-policy; and - the Ledger AI Policy, available at
https://ledger.build/ai-policy.
2. Infrastructure, hosting and delivery
| Provider | Purpose | Data that may be processed |
|---|---|---|
| Convex | Database, backend services and application infrastructure | Customer Data, Accounting Platform Data, Operational Data, Usage Data, technical logs |
| Vercel | Application hosting, deployment and delivery | Customer Data, Usage Data, technical logs |
| Cloud, workspace, AI, analytics, productivity or supporting services where used | Customer Data, Usage Data, communications data, technical data |
3. Identity, access and authentication
| Provider | Purpose | Data that may be processed |
|---|---|---|
| WorkOS | SSO, SAML, enterprise authentication, directory sync and access management | Account information, User information, authentication data, organisation metadata |
4. Payments and billing
| Provider | Purpose | Data that may be processed |
|---|---|---|
| Stripe | Payment processing, billing and subscription payments | Billing information, payment metadata, transaction data |
5. AI, OCR and automation
| Provider | Purpose | Data that may be processed |
|---|---|---|
| OpenAI | AI Features, classification, summarisation, extraction, recommendations and related processing | Customer Data, prompts, inputs, outputs, Usage Data |
| Anthropic | AI Features, classification, summarisation, extraction, recommendations and related processing | Customer Data, prompts, inputs, outputs, Usage Data |
| AI, OCR, document processing, extraction, automation or related services where used | Customer Data, prompts, inputs, outputs, Usage Data |
BuildPass does not use Customer Data to train its own foundation models. Unless otherwise agreed, BuildPass does not permit third-party AI providers to use Customer Data submitted through Ledger to train their general foundation models under BuildPass's applicable commercial arrangements. More detail is provided in the Ledger AI Policy at https://ledger.build/ai-policy.
6. Monitoring, analytics and product improvement
| Provider | Purpose | Data that may be processed |
|---|---|---|
| Sentry | Error tracking, monitoring and diagnostics | Usage Data, logs, error data, limited Customer Data if included in error context |
| PostHog | Product analytics, usage analytics and feature analytics | Usage Data, account metadata, event data |
7. Communications and support
| Provider | Purpose | Data that may be processed |
|---|---|---|
| Resend | Transactional email and notifications | Contact information, email metadata, notification content |
| Twilio | SMS, phone verification or notifications where used | Phone numbers, message metadata, notification content |
8. Customer-selected integrations
Ledger may exchange data with third-party platforms selected and authorised by the Customer, including accounting platforms, BuildPass products, operational systems, client portals, APIs and other integrations.
Those connected platforms are not always subprocessors of BuildPass. In many cases, they are independent third-party services that the Customer separately uses and authorises. The data exchanged depends on the Customer's configuration, platform permissions, User permissions, selected features and available API scopes.
9. Changes
BuildPass may add, replace, or remove subprocessors and third-party services from time to time. Material changes will be handled in accordance with the Ledger Terms of Service, Ledger Privacy Policy and applicable law.
Privacy requests may be sent to privacy@buildpass.com.au.
Product support requests may be sent to support@buildpass.com.au.