Data processing agreement
This data processing agreement (DPA) forms part of the terms of service between Ghost Ledger Inc. (Processor) and the customer identified in the account or order form (Controller). It is incorporated by reference into the terms of service and is the authoritative statement of Ghost Ledger’s data-protection commitments for Customer Data. Terms of service section 9 summarizes it. This DPA controls if the two ever conflict on a data-protection matter.
It governs Ghost Ledger’s processing of personal data on the Controller’s behalf.
Unlike the terms of service, this document cannot be amended unilaterally. Changes require agreement, except where required to comply with a legal obligation, in which case Ghost Ledger gives notice and the Controller may terminate if it objects.
1. How this agreement fits
This DPA takes effect when the terms of service do and continues for as long as Ghost Ledger processes Customer Data.
2. Definitions
Customer Data — all personal data submitted to, or generated by, Ghost AP in the course of the Controller’s use of the Service. This includes:
- the content of vendor bills the Controller submits, whether uploaded or received by email, including documents, images, PDFs and email bodies
- every field extracted from those bills
- accounting history imported from the Controller’s connected platform
- data derived from the above: coding rules, vendor matching memory, confirmed vendor identities, training examples and trained reading models
- any personal data contained within bills, including names, signatures, contact details, business numbers, tax identifiers and banking information belonging to the Controller’s vendors or their personnel
We do not split Customer Data by whose name appears in it. A vendor contact’s name printed on an invoice is treated under exactly the same rules as anything else in that invoice.
Customer Data does not include the Controller’s own account, billing, support and marketing data, for which Ghost Ledger is the controller and the privacy policy applies. That carve-out covers authentication and account records belonging to the Controller’s individual personnel — the people who hold logins — and not only a single top-level record for the Controller entity.
Process / Processing — any operation performed on Customer Data: collection, extraction, storage, use, transmission, derivation or deletion.
Subprocessor — a third party engaged by Ghost Ledger to process Customer Data on its behalf.
Data Protection Law — whichever of the following apply: PIPEDA; BC PIPA; Alberta PIPA; Quebec’s Law 25; the EU GDPR; the UK GDPR and Data Protection Act 2018; and any other applicable privacy or data protection legislation.
3. Roles
The Controller determines the purposes and means of processing Customer Data. Ghost Ledger processes it on the Controller’s behalf, as a processor (or, under Canadian law, a service provider).
The Controller is responsible, as between the parties, for having a lawful basis for the Customer Data it submits and for giving the notices its own personnel and vendors are entitled to.
4. Processing on documented instructions
Ghost Ledger processes Customer Data only:
- to provide, maintain, secure and support Ghost AP
- on the Controller’s documented instructions, which include instructions given through ordinary use of the product’s features — connecting an accounting platform, configuring an intake address, approving a document, teaching a coding rule
- as required by applicable law, in which case Ghost Ledger notifies the Controller before processing unless the law forbids it
- with the Controller’s separate written authorisation
Ghost Ledger will tell the Controller if, in its opinion, an instruction infringes Data Protection Law.
Ghost Ledger will not: sell Customer Data; use it for advertising or marketing; use it to build behavioural profiles; use it to train general-purpose AI models; use it for any purpose other than providing the Service to that Controller; or create aggregated or de-identified datasets from it for any purpose beyond providing the Service to that Controller, absent that Controller’s separate written agreement.
5. Confidentiality
Ghost Ledger ensures that personnel authorised to process Customer Data are bound by confidentiality obligations, contractual or statutory, that survive the end of their engagement. Access is granted on a need-to-know basis and reviewed.
6. Security
Ghost Ledger implements and maintains the technical and organisational measures described in Annex II, taking account of the state of the art, implementation cost, and the nature, scope, context and risks of the processing.
Ghost Ledger may update these measures provided the level of protection is not reduced.
7. Subprocessors
The Controller gives general authorisation for Ghost Ledger to engage the subprocessors listed in Annex III.
Ghost Ledger will:
- impose data protection obligations on each subprocessor that are no less protective than those in this DPA
- remain fully liable to the Controller for each subprocessor’s performance
- give the Controller at least 30 days’ notice before adding or replacing a subprocessor that will process Customer Data
The current list of subprocessors is Annex III. Write to [email protected] to be notified of changes.
If the Controller objects on reasonable data-protection grounds within the notice period, the parties will discuss in good faith. If the objection cannot be resolved within 30 days, the Controller may terminate the affected part of the Service, or the agreement, without penalty and with a pro-rata refund of prepaid fees.
Intuit and other connected accounting platforms
The Controller’s accounting platform is not a Ghost Ledger subprocessor. The Controller connects it using the Controller’s own credentials and its own relationship with that provider. Ghost Ledger acts on the Controller’s instruction to deliver data into a system the Controller already controls.
Ghost Ledger is responsible for performing that delivery accurately and securely. Once data has been correctly delivered, the platform provider’s own terms govern it. This is described further in section 10 of the terms of service.
8. Data subject rights
Ghost Ledger will assist the Controller, by appropriate technical and organisational measures and so far as is reasonably possible, in responding to requests from data subjects exercising rights of access, correction, erasure, restriction, portability or objection.
Ghost Ledger will not respond to such a request itself unless the Controller instructs it to or the law requires it.
Where a request comes from someone whose data appears on a bill — a vendor, or a vendor’s employee — Ghost Ledger will identify the relevant Controller, pass the request on promptly (targeting five business days), support the Controller in responding, and tell the requester that it has done so. It will not act unilaterally.
The notice obligation to a vendor or vendor employee named on a bill rests with the Controller, consistent with the Controller’s warranty in terms of service section 12 and with privacy policy section 10.
9. Assistance with the Controller’s own obligations
Taking into account the nature of processing and the information available to it, Ghost Ledger will assist the Controller with:
- maintaining the security of processing
- notifying personal data breaches to supervisory authorities and data subjects
- carrying out data protection impact assessments
- prior consultation with supervisory authorities
- equivalent obligations under Canadian law
10. Personal data breaches
Ghost Ledger will notify the Controller without undue delay after becoming aware of a personal data breach affecting Customer Data. There is no harm threshold on this obligation — the Controller is told, and the Controller assesses.
The notification will describe, so far as known: the nature of the breach, the categories and approximate number of data subjects and records affected, likely consequences, measures taken or proposed, and a contact point. Where full information is not immediately available, Ghost Ledger provides it in phases rather than delaying the initial notice.
Ghost Ledger will not notify a supervisory authority or any data subject on the Controller’s behalf for a breach affecting Customer Data. Whether a breach is reportable is the Controller’s assessment. Ghost Ledger will cooperate reasonably with whatever the Controller decides.
Where Ghost Ledger is itself the controller — for account, billing or marketing data — it notifies regulators and individuals directly as the law requires, as described in the privacy policy.
11. Return and deletion
On termination of the agreement, at the Controller’s choice and within 30 days, Ghost Ledger will either return all Customer Data in a reasonably accessible format, or securely delete it.
Deletion reaches derived data. Deletion covers, at minimum:
| Category | Covered |
|---|---|
| Raw emails and original documents in object storage | Yes |
| Extracted fields, coding verdicts, rule results, audit records | Yes |
| Imported accounting history and reference lists | Yes |
| Coding memory, vendor links, vendor coding rules, expensing overrides | Yes |
| Training examples held in blob storage | Yes |
| Trained per-vendor reading models and their retained prior versions | Yes |
| Encrypted accounting platform credentials | Yes — revoked and deleted |
| Backups and snapshots | Aged out on rotation, on a 90-day target, and protected under this DPA throughout |
The exception is data Ghost Ledger must keep by law, which remains protected under this DPA for as long as it is retained.
What “return” means for trained models
The Controller owns the reading models trained on its documents (terms of service, section 7). A trained model is not a portable file — outside Azure Document Intelligence it has no function. In practice, ownership and return mean:
- the model is built from the Controller’s documents and used only for the Controller
- it never processes another customer’s documents
- the training examples behind it are returnable in their original form
- the model is deleted on termination
12. Audit and information
Ghost Ledger will make available to the Controller the information reasonably necessary to demonstrate compliance with this DPA.
On reasonable written request, no more than once in any 12-month period — or more often following a personal data breach or at a supervisory authority’s direction — Ghost Ledger will provide:
- a written summary of its technical and organisational security measures
- responses to a reasonable security questionnaire
- a review call with someone who can answer technical questions
- any third-party audit reports or certifications it holds at the time
Ghost Ledger currently holds no third-party security certification. In its place, Ghost Ledger will also allow the Controller to conduct, or engage an independent third party to conduct, an audit of the technical and organisational measures described in Annex II — no more than once in any 12-month period (or more often following a breach or at a supervisory authority’s direction), at the Controller’s own cost, on at least 30 days’ written notice, and subject to a mutual confidentiality agreement and reasonable limits on scope and timing to protect Ghost Ledger’s operations and other customers’ service.
13. International transfers
Customer Data is stored and processed in Canada, in the ca-central-1 region, across all systems listed in Annex III except as set out below.
Canada to the United States. One processing step transfers Customer Data to Anthropic in the United States: where the primary document reader fails, or returns low confidence on a critical field, the original document image is sent for an independent second reading. Anthropic does not train models on API data and deletes inputs and outputs within 30 days, except where content is flagged by its automated trust and safety systems, in which case inputs and outputs may be retained for up to two years and classification scores for up to seven.
Ghost Ledger will not designate this fallback step to one of Anthropic’s Covered Models — which carry a 30-day minimum retention and no zero-data-retention option — without first updating the privacy policy and giving customers notice.
Ghost AP is not currently offered to customers in the European Economic Area, the United Kingdom, or Quebec. Standard Contractual Clauses, a UK International Data Transfer Addendum, and a transfer impact assessment covering US government access are therefore not in place. They will be completed, or this United States fallback will be disabled for that customer, before any EEA or UK customer is onboarded.
Stripe’s processing of billing and account data is not a transfer of Customer Data under this DPA. It is described in the privacy policy.
14. Liability
Liability under this DPA is subject to the limitations in section 15 of the terms of service, including the higher aggregate cap for claims arising from a data breach involving Customer Data or a breach of confidentiality obligations. Nothing in this DPA restricts any right an individual has to compensation under applicable privacy or data protection law.
15. Term
This DPA takes effect when the terms of service do and continues for as long as Ghost Ledger processes Customer Data.
Sections 5 (confidentiality), 10 (breaches), 11 (return and deletion), 13 (transfers) and 14 (liability) survive termination for as long as Ghost Ledger retains any Customer Data.
Annex I — Details of processing
Subject matter. Extraction of structured data from vendor bills and delivery of that data into the Controller’s connected accounting platform.
Duration. The term of the terms of service, plus the retention periods below.
Nature and purpose. Receipt of documents by email or upload; optical character recognition and machine reading; identification of the vendor; derivation of expense coding from the Controller’s own accounting history; automated safety checks; human review where flagged; posting into the Controller’s accounting platform; storage and retrieval to support all of the above.
Categories of data subject.
- the Controller’s personnel who use Ghost AP
- the Controller’s vendors, where they are sole proprietors or individuals
- personnel of the Controller’s vendors whose details appear on bills
- individuals named in imported accounting history
Types of personal data. Names; business and personal contact details; email addresses and sender domains; postal addresses; signatures; tax and business identification numbers, including numbers that identify individuals where a vendor is a sole proprietor; banking and payment details printed on invoices; amounts, dates and descriptions of goods and services; free text in email bodies and invoice line items.
Special category data. Not intentionally processed. Ghost AP does not require it and does not extract it. Because bills are free-form documents, special category data could appear incidentally — for example in the line-item description of a medical or legal invoice. Ghost AP does not seek, tag, or make any decision based on the sensitive nature of bill content. The general controls in Annex II apply regardless of what a given invoice happens to describe. Customers whose own client base predictably and routinely generates invoices naming clinical services or legal matters should discuss their use case with Ghost Ledger before onboarding.
Frequency. Continuous, as bills arrive.
Retention
| Data | Retention | Deleted at termination |
|---|---|---|
| Raw emails in object storage | 30 days after extraction completes | Yes |
| Quarantined emails that failed intake screening | 30 days | Yes |
| Email records | Duration of the agreement; message body content removed at 30 days | Yes |
| Unrecognised placeholders | Duration of the agreement | Yes |
| Original document images | 24 months rolling | Yes |
| Duplicate-detection records | Duration of the agreement | Yes |
| Extractions, coding verdicts, rule results | Duration of the agreement | Yes |
| Reviewer corrections | Duration of the agreement | Yes |
| Audit records | Duration of the agreement, then de-identified and held 24 months | De-identified |
| Posted bill records | Duration of the agreement | Yes |
| Imported accounting history | Duration of the platform connection | Yes |
| Accounting platform reference lists | Duration of the platform connection | Yes |
| Encrypted platform credentials | Revoked and deleted immediately on disconnection | Yes |
| Coding memory, vendor links, coding rules, expensing overrides | Duration of the agreement, or 90 days after disconnection without reconnection, whichever comes first | Yes |
| Training examples | Duration of the agreement, or 90 days after disconnection without reconnection, whichever comes first | Yes |
| Trained reading models, including retained prior versions | Duration of the agreement, or 90 days after disconnection without reconnection, whichever comes first | Yes |
| Dead-letter queue contents | 14 days | Yes |
| Application logs | 365 days, with personal data redacted at the point of writing | Yes |
| Backups and snapshots | 90-day rotation target | On rotation |
Deletion timing. Two clocks, and they are not the same:
- Retention is the period above, during normal operation.
- Deletion runs from a trigger — termination, account closure, or a deletion instruction. Customer Data is deleted from Ghost Ledger’s live systems within 30 days of the trigger.
Backups. Backups are not deleted surgically. They age out on rotation, configured to a 90-day target. While a backup exists it is encrypted, access is restricted, and it is not read in the ordinary course.
Subprocessor copies expire on their own cycles: Azure Document Intelligence at 24 hours; Anthropic within 30 days, or up to two years where content is flagged by Anthropic’s automated trust and safety systems.
Annex II — Technical and organisational measures
Tenant isolation. Ghost AP hosts many customers in a single database. There is exactly one sanctioned path to the data layer, and it cannot query or write outside the customer it was created for. Every filter is wrapped with the customer identifier before it reaches the database, and attempts to override that identifier are detected and rejected rather than ignored.
Encryption. TLS in transit. Encryption at rest across object storage, database and backups. Accounting platform OAuth credentials are encrypted with AES-256 before storage and never logged.
Access control. Authentication through Auth0 with role-based access and one organisation per customer. Internal access to Customer Data is need-to-know and reviewed. Administrative operations use a separate machine-to-machine authentication path from user access.
Input validation. Schema validation at every system boundary, in and out.
Intake screening. Inbound email passes five checks before it becomes a document: notification signature verification, recipient resolution, sender authentication (SPF, DKIM, DMARC, spam and virus verdicts), duplicate detection, and per-attachment type, size and encryption checks. Each has a deliberate failure direction — reject what is unsafe, quarantine what is merely unusual, and never discard silently.
Processing integrity. Every queue consumer tolerates redelivery. Side effects are idempotent or compare-and-swap gated, retries are capped so failures surface rather than loop, and sweepers recover work stranded between states. Coding decisions are deterministic: the same inputs always produce the same result.
Safety checks before posting. Independent rules run before any document posts automatically, covering extraction confidence, cross-reader disagreement, arithmetic integrity, duplicates, vendor match certainty, coding completeness, connection health and sender authentication. Any single failure routes the document to human review instead of posting it.
Audit logging. A full timeline is recorded per document: what was read, by which reader, what was decided, which rules fired, what a reviewer changed, and what was posted.
Resilience. The web and worker processes communicate only through queues with dead-letter queues, so either can fail and restart without losing work.
Certifications. None at this time. A written security summary and a review call are available on request, and a right to a third-party or on-site audit under section 12.
Annex III — Approved subprocessors
| Subprocessor | Purpose | Data processed | Location |
|---|---|---|---|
| Amazon Web Services, Inc. | Email intake and delivery, object storage, message queues, compute, application hosting | All Customer Data | Canada (ca-central-1) |
| MongoDB, Inc. (Atlas, hosted on AWS) | Application database | All Customer Data | Canada (ca-central-1) |
| Microsoft Corporation (Azure AI Document Intelligence) | Primary document reading, and per-vendor custom reading models trained on Controller data | Bill content and extracted fields | Canada |
| Microsoft Corporation (Azure Blob Storage) | Storage of training examples for per-vendor reading models | Bill content and labelled extracts | Canada |
| Anthropic, PBC | Second-opinion reading of the original document image where the primary reader fails or returns low confidence | Original document images and extracted fields | United States |
Listed for transparency — not subprocessors
These providers handle Ghost Ledger’s own controller-role data, or act inside the Controller’s existing relationship with them. They do not process Customer Data on Ghost Ledger’s behalf under this DPA.
| Provider | What it does | Data | Location |
|---|---|---|---|
| Okta, Inc. (Auth0) | Authentication, roles, organisation membership | Account identifiers and authentication records, including individual login records for the Controller’s personnel. No Customer Data. | Canada — the region our tenant is configured to use |
| Stripe, LLC | Payment processing and subscription billing | Billing contact details and usage volume. No bill content. | United States, per Stripe’s own data processing agreement. Stripe’s terms also permit onward transfer to its affiliates and sub-processors in other jurisdictions. See privacy policy section 7. |
| Intuit Inc. (QuickBooks Online) | The Controller’s accounting platform | Data the Controller instructs Ghost Ledger to deliver there | Per the Controller’s own Intuit relationship |
Why Auth0 and Stripe are not subprocessors. Section 2 defines a Subprocessor as a third party engaged to process Customer Data, and excludes the Controller’s own account, billing, support and marketing data from that definition. Auth0 handles only account and login data. Stripe handles only billing contact details and usage volume. Neither receives bill content, extractions or imported history.
Okta and Stripe each also act as independent controllers for their own customer relationship with Ghost Ledger and for their own service security, fraud prevention, risk modelling or telemetry, under their own terms.
Because Auth0 is not a Customer Data subprocessor, replacing it does not trigger notice under section 7. Ghost Ledger will nonetheless give customers reasonable advance notice, targeting 30 days where feasible, before replacing its authentication provider.
Microsoft. Ghost AP uses both the prebuilt invoice model and per-vendor custom models trained on the Controller’s own documents. Submitted input data and analysis results are stored by Azure Document Intelligence for 24 hours after the operation completes and are then deleted automatically. Training data for custom models is held in Ghost Ledger’s own Azure blob storage in Canada.
Stripe. Stripe acts as a processor for payment processing on Ghost Ledger’s instructions, and separately as an independent controller for fraud prevention, risk modelling and its own regulatory compliance. Ghost Ledger does not control that second category.