Privacy policy
Ghost AP reads the vendor bills you send us and delivers the extracted data into your accounting platform. That means we handle two very different kinds of information, and we treat them differently.
This notice describes how Ghost Ledger Inc. (Ghost Ledger, we, us) handles personal data when we decide what happens to it. It applies to Ghost AP. Ghost AP is not currently offered to customers in the European Economic Area, the United Kingdom, or Quebec.
The short version
Your customers’ bills belong to your customers. When you use Ghost AP to process bills, you decide what we do with that data. We act on your instructions, we don’t use it for anything else, and we don’t sell it or let anyone train general-purpose AI models on it. Those commitments are contractual and they sit in our data processing agreement, referenced from section 9 of our terms of service.
Your account belongs to you. Your name, your work email, your billing details, your support conversations — that’s data we hold for our own purposes, and this document explains what we do with it.
Our own infrastructure runs in Canada, but two things leave it: document images sometimes go to a provider in the United States for a second reading, and your billing and account data goes to our payment processor in the United States, which may in turn pass it to its own affiliates elsewhere. Section 7 explains when, why, and what we do and don’t control about each.
1. Who we are and what this document covers
Ghost Ledger Inc. operates Ghost AP, a vendor bill extraction service.
This privacy policy describes how we handle personal data where Ghost Ledger decides what happens to it — in data protection language, where we are the controller. That covers:
- visitors to our marketing website
- people who sign up for product updates
- the personnel of our customers who hold Ghost AP accounts
- billing contacts
- anyone who contacts our support or privacy teams
It does not cover the bill data our customers send us. For that data our customer decides what happens, and we act on their instructions. Our obligations there are set out in our data processing agreement, referenced from section 9 of our terms of service. If your name appears on an invoice one of our customers uploaded, see section 10.
| Contact | Address |
|---|---|
| Privacy questions and requests | [email protected] |
| General support | [email protected] |
| Postal | Suite 750, 1095 W Pender St, Vancouver BC, Canada V6E 2M6 |
| Accountable individual | Judy Kalyan, Chief Privacy Officer. Accountable for Ghost Ledger’s compliance with this notice and with applicable privacy law, including questions about how our service providers outside Canada handle personal data. |
2. Our two roles
| Data | Who decides what happens to it | Where the rules live |
|---|---|---|
| Marketing site server logs, update-list subscriptions | Ghost Ledger | This document |
| Account data for our customers’ personnel | Ghost Ledger | This document |
| Billing and payment data | Ghost Ledger, with Stripe also acting on its own behalf — see section 6 | This document |
| Support correspondence | Ghost Ledger | This document |
| Uploaded bills and everything extracted from them | Our customer | Data processing agreement |
| Imported accounting history | Our customer | Data processing agreement |
| Vendor coding rules, matching memory, trained reading models | Our customer | Data processing agreement |
3. What we collect, and why
3.1 Marketing website
Our marketing site is statically hosted on our own AWS infrastructure. There are no third-party embeds, no advertising pixels and no advertising cookies. We do not currently use any website analytics tool. If we adopt one it will be cookieless and privacy-preserving, and we will update this notice before turning it on.
| What | Why | Retention |
|---|---|---|
| Server access logs, including IP address, user agent, requested page | Security, abuse prevention, keeping the site working | 365 days |
| Email address, if you subscribe to product updates | Sending you those updates | Until you unsubscribe, plus the consent record below |
| Proof of your consent: the address, a timestamp, and a copy of the terms you agreed to with their publication date | Demonstrating compliance with anti-spam law | 3 years after you unsubscribe |
We do not collect location data beyond what an IP address implies, we do not build behavioural profiles, and we do not use any of this for advertising.
3.2 Ghost AP accounts
| What | Why | Retention |
|---|---|---|
| Name, work email, company name | Creating and securing the account | Duration of the agreement, plus 30 days |
| Authentication records held by Auth0 | Logging you in, managing roles and organisation membership | Duration of the agreement, plus 30 days |
| Application activity, device data, error logs | Keeping the service secure and working | 365 days, with personal data redacted as it is written |
3.3 Billing
| What | Why | Retention |
|---|---|---|
| Billing contact details, subscription status | Charging the correct amount to the right person | 7 years from the end of the fiscal year. Tax law requires this and it overrides a deletion request. |
| Payment card details | Taking payment | Held by Stripe, not by us. We never see or store full card numbers. |
| Volume of bills processed per billing period | Calculating usage charges | 7 years, as part of the billing record |
3.4 Support
| What | Why | Retention |
|---|---|---|
| Correspondence with our support and privacy teams | Answering you, and keeping a record that we did | 2 years |
Two clocks, and how long deletion takes
Retention is how long data lives while your account is open — the periods above.
Deletion runs from a trigger: you close your account, you ask us to delete something, or a retention period expires. From that trigger:
- Data is removed from our live systems within 30 days.
- Backups age out on rotation. We have set a target of 90 days. We do not delete individual records from backups; they expire on rotation. While a backup exists it is encrypted and is not read in the ordinary course.
We also keep a record of every security breach for 24 months, whether or not it was reportable, because Canadian law requires it.
If you disconnect your accounting platform without closing your account. Your imported accounting history is deleted immediately. Everything we have derived from it — coding rules, vendor matching memory, and reading models trained on your documents — is kept for up to 90 days, so a temporary disconnection does not cost you work you would otherwise have to redo. If you reconnect within that window, it is there waiting for you. If you don’t, it is deleted at the end of the window.
4. Consent and our basis for processing
Under Canadian privacy law we rely on consent, as PIPEDA defines it, including implied consent where the purpose is obvious from the circumstances.
| Processing | How consent works |
|---|---|
| Providing Ghost AP to an account holder | Implied by holding an account and using the Service, and set out in the terms |
| Securing the service, preventing abuse, keeping logs | Implied — a reasonable person expects a service to protect itself |
| Taking payment and keeping financial records | Implied for payment. The retention period is a legal obligation and consent does not override it. |
| Sending product update emails | Express, opt-in, with a record kept as anti-spam law requires |
| Responding to support requests | Implied by contacting us |
You can withdraw consent for marketing emails at any time without affecting your use of Ghost AP. Where withdrawing consent would prevent us providing part of the Service, we will tell you that before acting on it.
5. Where your data is stored and processed
Our own infrastructure runs in Canada, in the AWS ca-central-1 region.
| System | Purpose | Location |
|---|---|---|
| AWS (S3, SES, SNS, SQS, ECS on Fargate, and other compute and hosting) | Storage, email intake and delivery, queues, application hosting | Canada |
| MongoDB Atlas, running on AWS | Application database | Canada |
| Azure AI Document Intelligence | Reading documents | Canada |
| Azure Blob Storage | Storing training examples for per-customer reading models | Canada |
| Auth0 | Authentication and identity | Canada (see note below) |
| Backups and snapshots | Disaster recovery | Canada |
Two exceptions, both described in section 7. A subset of documents is sent to Anthropic in the United States for a second reading. Separately, your billing and account data is sent to Stripe, our payment processor, in the United States — and Stripe’s own terms permit it to move that data on to its own affiliates and sub-processors in other jurisdictions, which we don’t control.
This table states where each service is configured to run, based on our own account and infrastructure settings. For AWS and Azure that is independently confirmed by the provider’s region-scoped service. For Auth0, “Canada” describes the region our tenant is configured to use.
Customers with formal data residency requirements should contact [email protected] before onboarding.
6. Service providers
Providers that handle bill data on your instructions
| Provider | What they do | Location |
|---|---|---|
| Amazon Web Services | Hosting, storage, queues, email intake and delivery | Canada |
| MongoDB Atlas | Application database, running on AWS in Canada | Canada |
| Microsoft Azure AI Document Intelligence | Reads uploaded documents and extracts fields | Canada |
| Microsoft Azure Blob Storage | Stores training examples for per-customer reading models | Canada |
| Anthropic | Re-reads a document image when our primary reader fails or returns a low-confidence result | United States — see section 7 |
We will give customers at least 30 days’ notice before adding a provider to this list, and an opportunity to object on reasonable data-protection grounds. If an objection cannot be resolved, the customer may terminate. Write to [email protected] to be notified of changes.
Providers that handle our own data, not your bill data
| Provider | What they do | Location | Relationship |
|---|---|---|---|
| Auth0 (Okta) | Authentication, roles, organisation membership | Canada | Processes account and login data on our instructions, including individual login records for our customers’ personnel. It receives no bill data. Okta separately acts on its own behalf for its customer relationship with us and for its own service security and telemetry; we do not control that part. |
| Stripe | Payment processing, subscription billing | United States. Stripe’s own data processing agreement states: “User transfers Personal Data to Stripe, LLC in the United States.” The specific data center or sub-region within the US is not disclosed. Stripe’s own terms also permit it to move data on to its affiliates and sub-processors in other jurisdictions — see section 7. | Processes payments on our instructions, and separately acts on its own behalf for fraud prevention, risk modelling and its own regulatory compliance. It receives billing details and the number of bills processed. It receives no bill content. |
Intuit and QuickBooks are deliberately not on either list. You connect your own accounting platform using your own credentials, and we act inside your existing relationship with that provider. We are not sending your data to a provider of ours; we are putting it where you told us to put it. Section 10 of the terms of service covers what that means for responsibility.
Corporate transactions
We may disclose the account, billing and marketing data described in this notice — the data we hold as controller — to a prospective or actual acquirer, investor, or successor, and to their professional advisers, in connection with a proposed or completed merger, financing, reorganization, or sale of assets, under confidentiality obligations. If your data is transferred as part of such a transaction, we will tell you before it becomes subject to a different privacy notice.
This does not extend to bill data. Bill data is Customer Data under our data processing agreement. A successor in a merger or acquisition takes on our agreement with you, including the data processing agreement and every restriction in it, by assignment (terms of service section 19). It does not gain separate access to your bill data through this clause.
7. Where data leaves Canada
There are two transfers outside Canada. Bill content never goes to Stripe, and billing or account data never goes to Anthropic.
The Anthropic transfer (bill content)
Ghost AP reads every document with Azure Document Intelligence, in Canada. When that reader fails outright, or returns a low-confidence result on a field that matters — the invoice total, the date, the vendor name — we send the original document image to Anthropic’s Claude API for an independent second reading. This happens for a minority of documents, but when it does, the whole image goes, not just the failed field.
Anthropic processes this in the United States. What that means:
- No model training. Anthropic’s commercial terms prohibit training models on data submitted through the API.
- 30-day deletion. Anthropic deletes API inputs and outputs from its systems within 30 days.
- A longer tail if content is flagged. If Anthropic’s automated trust and safety systems flag content as violating its usage policy, inputs and outputs may be retained for up to two years, and classification scores for up to seven. Vendor invoices are unlikely to trigger this, but we would rather you knew the rule than discovered it.
- Zero data retention is available and we have not taken it. We will not route this step through one of Anthropic’s “Covered Models” — a category that carries a 30-day minimum retention with no zero-retention option — without updating this notice and telling customers first.
Because this transfer leaves Canada, PIPEDA treats your data as subject to the laws of the United States while it is there, including lawful access by US authorities. If you would prefer that no document of yours leaves Canada, contact [email protected] before onboarding and we will discuss what is possible.
The Stripe transfer (billing and account data)
Stripe is contracted through Stripe, LLC, a United States company. Stripe’s own data processing agreement states: “User transfers Personal Data to Stripe, LLC in the United States.” This is billing contact details and the volume of bills you process — never bill content.
Stripe’s own data processing agreement also states that Stripe and its affiliates may transfer personal data on a global basis as necessary to provide the services, including to affiliates and sub-processors in other jurisdictions. We disclose what we control and what Stripe has told us; we do not represent that the United States is the only country your billing data can ever reach downstream of Stripe.
Stripe also acts on its own behalf for fraud prevention, risk modelling and its own regulatory compliance. We do not control that second capacity.
Written information about foreign service providers
This section, together with sections 5 and 6, is our written statement of the countries in which personal data is collected, used, disclosed or stored on our behalf and the purposes we have authorised. Two authorised purposes send data outside Canada: Anthropic’s second reading of a document image, in the United States; and Stripe’s payment processing, contracted with Stripe, LLC in the United States and potentially reaching Stripe’s own affiliates and sub-processors elsewhere.
Judy Kalyan, our Chief Privacy Officer, can answer questions about how service providers outside Canada handle personal data, at [email protected].
When you create a Ghost AP account we also tell you, at that point:
Some of your data is handled outside Canada by our payment processor and, for some documents, a secondary reading provider — see our Privacy Policy, Section 7, or contact our Chief Privacy Officer, Judy Kalyan, at [email protected].
8. How we protect data
- Encryption in transit and at rest. Accounting platform OAuth tokens are encrypted with AES-256 before storage.
- Tenant isolation enforced in code, not by convention. Ghost AP hosts many customers in one database. There is exactly one sanctioned path to the data layer, and it cannot query or write outside the customer it was created for.
- Access to customer data is restricted internally on a need-to-know basis.
- Automated dependency and vulnerability scanning on every build, plus continuous monitoring and a weekly scan of application packages, build tooling, and container base images. Multi-factor authentication is enabled and enforced for our own administrative access.
- We have not yet completed a third-party penetration test. One is planned before general availability.
We hold no third-party security certification. We can provide a written security summary and a review call on request, and, under our data processing agreement, a right to a third-party or on-site audit at your own cost.
If something goes wrong
Where we are the controller, we will notify affected individuals as PIPEDA’s real-risk-of-significant-harm standard requires, and we will notify the Office of the Privacy Commissioner of Canada where that federal standard is met.
British Columbia. Current BC PIPA does not impose a mandatory duty to notify BC’s Office of the Information and Privacy Commissioner of a breach. We will notify that office voluntarily, alongside any notification we make to the federal Office of the Privacy Commissioner.
Alberta. Alberta’s Personal Information Protection Act requires an organization to notify Alberta’s Office of the Information and Privacy Commissioner without unreasonable delay where a reasonable person would consider there is a real risk of significant harm to an individual. This applies to the account, billing and marketing data we hold as controller, including the account data of any Alberta-based personnel of our customers. We treat this as binding.
Where we are acting on your instructions, we notify you without undue delay and support your response. We do not notify regulators on a customer’s behalf — whether a breach is reportable is your assessment to make, not ours.
9. Data delivered into your accounting platform
Ghost AP’s job ends when extracted data lands in your connected platform. Once it arrives there, that platform’s own terms, privacy policy and security practices govern it, and those are outside our control.
We remain responsible for performing the delivery correctly and securely. We are not responsible for how Intuit, or any accounting platform we support in future, subsequently stores, secures, uses, discloses or retains that data.
10. Your rights
If you hold a Ghost AP account, or subscribe to our updates
You can ask us to:
| Right | What it means |
|---|---|
| Access | Tell you what personal data we hold about you |
| Correction | Fix data that’s wrong |
| Deletion | Delete your data, where no legal obligation requires us to keep it |
| Withdraw consent | For anything based on consent, including marketing email |
| Explanation | Tell you how we are using it and who we have given it to |
Send requests to [email protected]. We respond within 30 days, and will tell you if we need longer. We may ask you to verify your identity before acting on a request.
Complaints. You can complain to the Office of the Privacy Commissioner of Canada, to BC’s Office of the Information and Privacy Commissioner, or, if you are in Alberta, to Alberta’s Office of the Information and Privacy Commissioner. You do not have to come to us first.
If your details appear on a bill someone else uploaded
You are almost certainly a vendor, or someone who works for one. We hold that data on our customer’s instructions, not our own. If you contact us, we aim to identify the relevant customer and forward your request to them within five business days, support them in responding, and tell you that this was done. We will not act on it unilaterally.
The customer who uploaded the bill is responsible for telling you they did so, and for having a lawful basis to collect and share it.
11. Marketing email
We send product updates only to people who asked for them.
When you subscribe we record your address, the time you subscribed, and a copy of the terms you agreed to along with their publication date. We keep that record as proof of consent, as Canada’s anti-spam legislation requires.
Every message identifies Ghost Ledger Inc., gives our postal address, and carries a working unsubscribe link. Unsubscribe requests are honoured within 10 business days, usually immediately. Unsubscribing from updates does not affect service messages about your account, billing or security.
12. Cookies and similar technologies
We use only what is strictly necessary to run the application securely — principally keeping you signed in. No advertising cookies, no third-party trackers, no cross-site tracking, and no analytics cookies.
Server access logs record IP addresses. Section 3.1 covers those.
13. Automated processing
Ghost AP reads documents automatically and applies rules learned from a customer’s own bookkeeping history. That is the product.
This processing categorises expenses in a business’s books. It produces no legal or similarly significant effect on any individual. A person always reviews anything the system is not confident about, and every automated posting can be reviewed and reversed inside the customer’s accounting platform.
We do not profile individuals, score them, or make decisions about them.
14. Children
Ghost AP is business software. It is not directed at children and we do not knowingly collect data from anyone under 16.
15. Changes to this notice
We will tell account holders about material changes at least 30 days before they take effect, by email or in-app notice.
This notice is a statement of our practices, and we can update it. The contractual terms that govern your bill data are in our data processing agreement, referenced from section 9 of the terms of service, and we cannot change those unilaterally.
16. Accessibility
We are building Ghost AP toward WCAG 2.2 Level AA. We have not yet completed a formal assessment, so we are not claiming conformance.
If you hit a barrier, tell us at [email protected] and we will treat it as a defect rather than a request.
17. Contact
| Purpose | Contact |
|---|---|
| Privacy questions and rights requests | [email protected] |
| Chief Privacy Officer | Judy Kalyan, via [email protected] |
| Legal and compliance | [email protected] |
| Support | [email protected] |
| Postal | Suite 750, 1095 W Pender St, Vancouver BC, Canada V6E 2M6 |
| Office of the Privacy Commissioner of Canada | priv.gc.ca (opens in a new tab) |
| BC Office of the Information and Privacy Commissioner | oipc.bc.ca (opens in a new tab) |
| Alberta Office of the Information and Privacy Commissioner | oipc.ab.ca (opens in a new tab) |