Privacy Policy

Effective October 27, 2026

1. The short version

ZeroParse Statements is built around not having your financial data to lose. CSV and Excel files are parsed entirely in your browser and never uploaded anywhere. PDF files are uploaded for text extraction, processed in memory, and destroyed immediately after — never written to disk, never retained. We store the minimum needed to run your account: your email, credit balance, and plan. The one place we hold statement files is client upload links, a Firm feature that is off unless the account turns it on: files a client sends are encrypted on the client's device first, we can't read them, and we delete them when they're collected or after 72 hours (Section 3b). The other is saved client workspaces, also a Firm feature that is off unless the account turns it on: the transactions of statements the firm chooses to save, encrypted in its browser so we can't read them, kept for as long as the firm chooses and deleted when it says (Section 3c).

2. What we collect

  • Account data: your email address and password (password is hashed by our authentication provider, Supabase Auth — we never see or store it in plain text).
  • Billing data: your subscription tier, credit balance, and Stripe customer/subscription IDs. Card numbers are handled entirely by Stripe — we never receive or store them.
  • Processing metadata: for each PDF you process, we log the file type, page count, timestamps, whether it was read from its text or by OCR and how long that took, how the attempt ended (converted, nothing found, or failed), and whether the result matched the statement's own printed figures — a single word such as “reconciled” or “suspect”. Never the file's contents, a figure from it, or a description.
  • Operational telemetry: server logs and (for administrators) an operations console record response times, error codes, and an account identifier — either our internal account ID or a non-reversible identifier derived by one-way hashing your email address — never the email itself, and never statement contents. When something fails, a technical error report goes to our error-monitoring provider, Sentry (Section 6). This exists to debug incidents and detect abuse, not to profile you.
  • Failed sign-in attempts: to protect your account from password-guessing, we record the email address used in a failed sign-in and the time it happened. No password data is ever recorded. These records are deleted automatically after 24 hours.
  • Email preferences: whether you've chosen to receive product emails, and a record of which ones we've sent you (the kind and the date) so you never get the same one twice.
  • Feedback you send us: the message text, and — only if you're signed in and explicitly check the box to include one — a file you choose to attach to a support request. This is one of two deliberate exceptions to everything below; see Section 3a.
  • Client upload links (Firm accounts that turn them on): the account's firm name, its encryption public key and its passphrase-locked private key, each link's label, and, for each file a client sends, its encrypted contents, size and upload time. See Section 3b.
  • Saved client workspaces (Firm accounts that turn them on): the account's encryption public key and passphrase-locked private key, the version of the terms it agreed to and when, how long it chose to keep saved statements, and, for each statement it saves, its encrypted contents, size, the time it was saved and when it will be deleted. See Section 3c.

3. What we never collect, and the technical reason why

  • Transaction descriptions, amounts, dates, or any other statement contents.
  • Bank account numbers, routing numbers, or balances.
  • The contents of any CSV, Excel, or PDF file you process — with two narrow, opt-in exceptions, described in Sections 3a and 3b.
  • Your payment card details.

CSV and Excel files never leave your browser — they are parsed by JavaScript running on your own device, so there is nothing for us to collect even if we wanted to. PDF files are different in kind but not in outcome: the file is held in server RAM strictly for the duration of the OCR/extraction run needed to answer your request, is never written to disk at any point, and every reference to it (and to the text extracted from it) is dropped from memory before the response is returned — whether extraction succeeds or fails. What survives that request is exclusively non-content operational telemetry: which account made the request, how many pages, how long it took, and whether it succeeded — never what the statement said.

3a. Feedback attachments — the one exception, and only if you choose it

If you report a problem while signed in, you can optionally attach the file the problem is actually about (PDF, CSV, or Excel, up to 3MB) so we can diagnose it. This is off by default and requires an explicit, separate checkbox — it never happens as a side effect of using the Service or sending ordinary feedback.

  • It is stored, not processed-and-discarded. The file is emailed, as an attachment, to our support inbox via Resend (the same provider used for other account emails). Unlike every other file this product touches, it is not held in memory and dropped — it sits in that inbox.
  • Retention is manual, not automatic. We aim to review and delete it within about a week, but that is an operational commitment, not a system control — no software here enforces an expiry. If that matters for your situation, don't check the box.
  • Who can see it: whoever on the ZeroParse Statements team investigates the report, via that inbox — the same access any of our support email already has.
  • Only signed-in accounts can attach a file, so there's a traceable owner for every attachment we hold.

“Fix this bank for me” works the same way. When you ask us to fix how a statement is read, you tick a separate consent for that one PDF, and it is emailed to our support inbox, used only to fix reading that layout, and deleted once that is done or we decline it. With your account we keep the request's status, page count, what went wrong and the bank name if you gave one, never the file or its name, until you delete your account.

3b. Client upload links — only for Firm accounts that turn them on

A Firm account can turn on client upload links: its clients then send statements to it through a link, without an account. This is off unless the account holder turns it on, and it changes nothing about files you process yourself.

  • Encrypted before it reaches us. Each file is encrypted in the client's browser, with a key only the account holder can unlock, using a passphrase we never receive. We hold no key that can decrypt these files, so we can't read them. The file's name and type are encrypted with it.
  • Stored, briefly, and deleted automatically. The encrypted file is stored with Supabase until the account holder collects it, and deleted then, or 72 hours after it was uploaded, whichever comes first. A link accepts files for 7 days. Closing a link deletes anything still waiting on it.
  • What we can see. Each file's size and upload time, the label the account holder gave the link, and the firm name shown to the client. To limit abuse, we keep a one-way hash of the uploading device's IP address, never the address itself, for up to a day; and the upload form may run Cloudflare's bot check (Section 6).
  • A forgotten passphrase can't be recovered by anyone, including us. Files waiting under it can then never be opened, and are deleted.
  • Whose data it is. The account holder decides to collect these files and what to do with them; we process them on the account holder's behalf under our Data Processing Agreement. A client with a question about their files should ask the firm that sent them the link.
  • One limit, stated plainly: the page that does the encrypting is served by us. Our claim is that we hold no key that opens these files, not that it is impossible for anyone to.

3c. Saved client workspaces — only for Firm accounts that turn them on

A Firm account can choose to keep the statements it converts, client by client, so it can check one month's balances against the next and build the year from what it has kept. This is off unless the account holder turns it on, after agreeing to each of the points below separately, and it changes nothing for anyone else.

  • What is kept. The transactions and figures read from each statement the firm saves (dates, descriptions, amounts, balances, whether it adds up), with the client and account names the firm gives them. Never the PDF or spreadsheet itself.
  • Encrypted before it reaches us. Each saved statement is encrypted in the firm's browser, with a key only its passphrase unlocks. We never receive the passphrase and hold no key that can decrypt what is saved, so we can't read it: not the transactions, and not which client, account or month it is.
  • What we can see. That the account has saved workspaces, how many statements, each one's size, when it was saved and when it will be deleted. The account holder can see exactly this list in their account.
  • How long, and who decides. Each saved statement is deleted automatically after the period the account holder chooses (13 months, 25 months or 5 years), or kept until they delete it. They can delete one statement, one client, or everything at any time; turning the feature off deletes everything at once, including the key. Deleting an account deletes all of it too.
  • A forgotten passphrase can't be recovered by anyone, including us. What was saved under it can then never be opened.
  • Whose data it is. The account holder decides what to save about their clients and confirms they have their clients' authority to; we process it on their behalf under our Data Processing Agreement.
  • The same limit as client links, stated plainly: the page that does the encrypting is served by us. Our claim is that we hold no key that opens what is saved, not that it is impossible for anyone to.

4. How we use your data

We use the data described above to:

  • Authenticate you and maintain your session.
  • Track and enforce your credit balance.
  • Process payments and manage your subscription.
  • Respond to support requests you send us.
  • Send you the occasional product email: a reminder to try your first statement if you haven't yet, or a note when your credits are running low. Every one has a one-click unsubscribe link, and you can turn them off at any time under Account → Your data. Emails about your account and billing, such as password resets, are sent regardless.
  • Detect abuse and debug incidents, using the operational telemetry described above.

We do not sell your data, use it for advertising, or send it to third-party AI models for training.

5. Legal basis & international transfers (GDPR)

For users in the EU/EEA and UK, we process personal data under the following legal bases (GDPR Article 6):

  • Contractual necessity — account data, billing data, and processing metadata, because we can't run your account, deduct credits, or bill your subscription without them.
  • Legitimate interests — operational telemetry and failed sign-in records, for security, fraud prevention, and keeping the Service running, balanced against your privacy by keeping this data non-content, short-lived (failed sign-ins), or already non-reversible (the hashed account identifier).

Cross-border transfers. We are based in Singapore and our infrastructure providers — Vercel, Render, and Supabase — operate cloud infrastructure across multiple regions, which may include regions outside your own. Error reports sent to Sentry are stored in its United States region, and Cloudflare's bot check is answered from its global network. Where that involves transferring personal data out of the EU/EEA, UK, or Singapore, we rely on the standard contractual clauses or equivalent transfer safeguards those providers make available under their own terms, rather than maintaining separate transfer agreements of our own. If you need copies of the specific mechanisms in place for your account, email support@getzeroparse.com.

If you're in Singapore, we handle personal data consistent with the Personal Data Protection Act (PDPA); if you're in California, see the CCPA note in Section 8 below.

6. Who we share data with

We use a small number of infrastructure providers to run the Service, each of whom only sees what they need to do their job:

  • Supabase — authentication and database hosting (email, credit balance, plan), and, for Firm accounts that turn on client upload links, storage of the encrypted files clients send, which it can't read, for at most 72 hours (Section 3b), and, for Firm accounts that turn on saved client workspaces, storage of the encrypted statements they save, which it can't read, for as long as the account chooses (Section 3c).
  • Stripe — payment processing (billing details, never your card number).
  • Vercel — hosts the web application, and provides aggregated, cookieless traffic analytics (see Cookies & Analytics below).
  • Render — hosts the PDF extraction backend; sees PDF contents only transiently, in memory, during processing.
  • Resend — delivers account, administrative and product emails. If you choose to attach a file to a support request (Section 3a), Resend is where it's actually stored, as an email attachment, until we delete it.
  • Sentry — error monitoring for the web application and the PDF extraction backend. When something fails, it receives a technical report: the error and where in our code it happened, the page or endpoint involved (without any query string), and log messages from just before it, which identify an account only by our internal account ID or the one-way hash described in Section 2. It never receives statement contents, passwords, payment details, request bodies, or session cookies. Reports are stored in Sentry's United States region.
  • Cloudflare — runs a bot check (Turnstile) on the sign-in, sign-up, password-reset and resend-confirmation forms, and on the client upload form (Section 3b). When you use one of those forms, Cloudflare receives your IP address, your browser's user-agent and a TLS fingerprint, which it uses to tell a person from an automated sign-up. It doesn't see your password or anything else you type into the form. Cloudflare describes what it does with these signals in its Turnstile privacy notice, including using them to improve Turnstile itself.

We don't share your data with anyone else, except where required by law. If you're an accounting firm or other organization processing client data through ZeroParse Statements, our Data Processing Addendum sets out these same providers as pre-approved subprocessors, with a process for notifying you before we add or change one.

7. Cookies & analytics

When you first visit, we ask which cookies you allow, with two equal choices: Necessary only or Accept all. Nothing optional is set before you answer. You can change your answer at any time from Cookie settings at the foot of every page; choosing Necessary only deletes the optional cookies straight away.

Necessary — set whatever you choose, because the site cannot work without them:

  • Sign-in session (names beginning sb-) — keeps you signed in. Removed when you sign out; your browser keeps it for at most 400 days.
  • zp_consent — remembers your cookie choice, so we don't ask on every page. Six months, then we ask again.

Optional — set only if you choose Accept all:

  • zp_signup_arm — if you use the site without an account, whether its sign-up buttons open our sign-up form or a page about what an account adds, picked at random, so we can learn which helps more. 90 days.
  • zp_signup_recorded — notes that your use of the site without an account, a click on a sign-up button, and creating an account have already been counted, so each visitor counts once. 90 days.

No optional cookie identifies you or is shared with anyone: we keep only running totals, not a record per visitor. If you choose Necessary only, you see our standard sign-up buttons and are not counted in the test.

The sign-in, sign-up and password-reset forms also run Cloudflare's Turnstile check in your browser. It is a security measure against automated sign-ups, not analytics, and what it receives is listed in Section 6.

We use Vercel Web Analytics and Speed Insights to understand site traffic and performance. Both are cookieless: they don't track you individually or across other sites, and we never see your IP address or any personally identifying information through them — only aggregated counts (page views, referrers, approximate country, device/browser type, and page load performance). We do not collect personal demographic data (age, gender, income, etc.) — that would require far more invasive tracking than we're willing to add, and it isn't something Vercel Analytics provides. Because this analytics is cookieless and doesn't process personal data, it runs whichever cookie choice you make. If we ever add anything more invasive, we'll ask for it in the cookie choice and update this section first.

On the same terms, we keep three daily totals for visitors without an account: how many times the site read a file for one (once per page, and never the file itself), how many times one dropped a PDF, and how many times a sign-up button was clicked. Each is a single number per day. They set no cookie and record nothing about who you are, so they too run whichever cookie choice you make.

8. Your rights

From your Account page, you can:

  • Export your data — download everything we hold about your account as a JSON file.
  • Delete your account — permanently removes your profile, credit balance, and processing history. This cannot be undone.

If you're in the EU/EEA or UK, GDPR also gives you the right to access, rectify, restrict, or object to our processing of your data, and to lodge a complaint with your local data protection authority. If you're a California resident, the CCPA gives you the right to know what personal information we collect and to request its deletion — both of which the Account page above already gives you directly, since our collection is deliberately narrow enough that there's nothing extra to disclose. We do not sell personal information, so there is no opt-out to exercise. For any of the above, or any other jurisdiction's data rights, email us at support@getzeroparse.com and we'll assist directly.

9. Data retention

We keep your account data for as long as your account exists. PDF file contents are never retained at all — there is nothing to expire. Processing metadata (Section 2: file type, page count, timing, outcome and the one-word check result) and your credit history are kept until you delete your account, at which point they are permanently deleted along with everything else tied to your account. Failed sign-in records are deleted automatically after 24 hours, whether or not you have an account with us.

10. Security

All traffic is encrypted in transit (TLS). Database access is protected by row-level security so your account data is only ever readable by you. Administrative operations (billing, account deletion) use a separate, tightly-scoped service credential that is never exposed to the browser.

11. Enterprise & business use

If you're a CPA, bookkeeping firm, or other organization using ZeroParse Statements to process statements on behalf of clients or third parties, our Data Processing Addendum sets out the roles, security commitments, and subprocessor list relevant to that use. You can also request it directly by emailing support@getzeroparse.com.

12. Children's privacy

ZeroParse Statements is not directed at children under 16, and we don't knowingly collect data from them.

13. Changes to this policy

We may update this policy from time to time. Material changes will be reflected by updating the effective date above.

14. Contact

Wedgr Technologies (UEN 53532707B), which operates ZeroParse Statements, is responsible for the personal data described in this policy. Questions about this policy: support@getzeroparse.com