Skip to main content

Privacy

Last updated: October 2026 (beta)

This page explains how FinScope handles your information in plain language. It isn’t a claim of certification against every privacy law, and it isn’t legal advice. Where local privacy law says something different, that law applies.

What we store

The documents you upload, the transactions we extract from them, the reports you generate, and, if you reach out for help, your support conversation and any files you attach. Messages sent through the public Contact form are kept separate from your signed-in support history.

How your files are kept

Your files are stored privately, not in a public location. Every request for your data goes through FinScope’s own servers first, and nothing is served straight from storage. Support attachments are shared using links that expire, never a permanent public address.

How documents are read

To turn a document into transactions, FinScope sends it to an AI document-reading service. The reader proposes rows; they only count once they pass FinScope’s own checks against the balances printed on the statement.

Where we are today

FinScope is in a free beta while we finish hardening sign-in and account security ahead of general availability. Please don’t upload documents you’re not comfortable testing with.

Beta: how your data may be used to improve the reader

During the beta, the AI document-reading service we use runs on a free tier. Under free-tier terms, the provider may keep and use the content we send it, which includes the documents you upload and what is read from them, to improve its own products and models. FinScope also looks at how documents were read (for example which kinds of document fail, and how often) so we can improve the reader. That review uses reasons, counts and dates, not the text of your documents.

So please upload only documents you are comfortable using for testing. If you can, remove names and full account numbers first. We do not sell your documents or use them for advertising.

Before the beta ends we plan to move document reading to a paid service tier whose terms do not allow customer content to be used for model training, and we will update this page when that happens. Signing in during the beta means you accept this.

Retention and deletion

Deleting a source document removes the file. The transactions that came from it stay in your Library, clearly marked as having a deleted source, unless you also choose to remove them. We don’t pretend they never existed, and we don’t silently rewrite your history. Deleting your whole account is not self-service yet: ask us through Support and we will help. Contact-form submissions are kept for 24 months after your request is closed, then deleted.

Cookies, analytics and outside services

Essential cookies. FinScope sets a cookie to keep you signed in and to protect your session. These are needed for the service to work and are always on. We also remember your cookie choice in a small setting on your device (it holds no identifier).

Our own visit measurement (always on). We measure basic visit information with our own cookieless tool: which pages are viewed, approximate device type (phone, tablet or desktop), time on page, country, and the site that referred you. It sets no cookie, uses no browser storage and no persistent identifier, and does not store your IP address or browser details: they are mixed into a one-way code that changes every day and the originals are thrown away. For signed-in users we record our internal account ID with visits, to understand how the service is used; it is never shown next to your name or email address. This data stays on our own systems (our database in Singapore), is kept for 60 days and then reduced to daily totals. We skip visits that send a “Do Not Track” or Global Privacy Control signal.

Product analytics (optional). With your permission we use product analytics (PostHog, EU region) to understand how people find and use FinScope: which pages are visited, where people stop, and whether uploads and reports work. You choose on the cookie notice when you first visit. If you have not made a choice, signing in counts as accepting it, as stated on the sign-in page; a choice you made on the notice is never overridden. “Essential only” means nothing is sent to PostHog and nothing from PostHog is stored on your device. You can change your mind at any time with “Cookie settings” in the page footer.

What analytics never see. Neither tool receives your documents, your transactions, descriptions or amounts, file names, account numbers, your name or email address, or anything you type into a form. Events are fixed labels and counts (for example “upload finished”, with a size range). Web addresses are cut down to the page name and a short list of campaign tags before they are sent. We do not record sessions or screens.

How product analytics data is handled. PostHog counts visits with a random identifier stored on your device. When you sign in, it is linked to our internal account ID only. Like most analytics tools, PostHog receives your IP address and browser details to count visits; we ask it to discard the IP address and do not use it to identify you. Data reaches PostHog through FinScope’s own web address.

The outside services we rely on are limited to hosting, file storage, email delivery, AI document reading and the two analytics tools above. We don’t store IP addresses from public Contact submissions.

Changes to this notice

This notice will keep evolving as FinScope moves toward general availability, and we will update this page when it does.

Questions about this page? Use the contact page.