Every subscriber gets its own server instance. Your statements, balances and positions live on that instance and nowhere else. We do not sell them, we do not share them with other users or with advertisers, and we keep no copy of them outside your server. The public website is measured for advertising; your server is not. Section 06 draws that line.
Effective 31 August 2026
01
Your account runs on a server provisioned for you alone. Statements, transactions, balances, positions, reports and knowledge pages are stored in that instance's own database and file system. There is no shared database, no pooled search index, and no copy of your records held elsewhere.
02
On your server: the documents you upload and everything derived from them. Centrally, and only what running the business requires: your email address, subscription and payment status (handled by our payment processor — we never see your card number), and minimal operational logs such as errors and uptime. Those logs are not your financial records.
03
We do not sell your data. Your statements, balances and positions are not shared with other users, not shared with advertisers, and not used to train models — ours or anyone else's. Nothing derived from a document you upload is used for advertising, and no advertising profile is built from your financial records. What does reach advertising companies is the public website itself: which pages a visitor opened and whether they subscribed. Section 06 says exactly what that means.
04
This is the one exception to everything above. Reading a statement, writing a review or answering a question requires a model, and those models run at third-party cloud providers. Your server sends the relevant content — statement text, an extracted page, the question and the context it needs — and nothing that identifies you: no name, no account, no credentials. We use providers under agreements that prohibit training on the content we send, but once content leaves your server it is handled under that provider's terms as well as ours. Statement arithmetic, caps, due dates and recommendations are computed in code on your server, not by a model.
05
Besides the AI providers we use a hosting provider for the servers, a payment processor for billing, and an email provider for account mail. If you choose to connect accounts through a bank-connection provider, that connection is read-only and its access URL is stored on your server. We also disclose data where the law compels it.
06
This public website uses Google Analytics to count visits: which pages were opened, roughly where in the world the visit came from, the device and browser, and whether the Start free month button was clicked. We use it to learn which explanations of the product land.
The website also carries Meta's advertising pixel, so that we can tell which advertisements bring subscriptions. Being plain about what that is: Meta receives the fact of the visit, recognises you if you have an account there, may use it to show you our advertisements elsewhere, and builds its own audiences from it. That is what an advertising pixel does, and switching it on is a choice we made rather than a detail. Google Signals and ad personalisation are switched off on the analytics side, so that half adds no cross-device profile.
No financial data is involved, because none exists yet. Analytics runs on these public pages, before there is a server, an account or a statement. Neither tool carries an identifier that could be matched to your instance, neither runs on your server, and nothing in this section reaches the documents described in sections 01 and 02. The line is the same one the product is built on: the public website is measured, your server is not.
Payment happens on our payment processor's own pages under its own policy, and we pass it a reference so we can tell which advertisement a subscription came from. If you would rather not be counted at all, your browser's tracking protection will stop both, and the website works exactly the same. Google's own opt-out add-on covers only the analytics half; Meta's ad preferences are managed in your Meta account.
07
Your data stays on your server for as long as your subscription lasts. Delete a statement or an account inside the app and it is removed there. Cancel and delete your subscription and the whole instance is destroyed, backups included, within 30 days. Billing records are kept as long as tax and accounting law requires.
08
Instances are isolated from one another, traffic is encrypted in transit, and secrets are stored with restricted permissions on your server. Our staff do not read your financial data; access for support happens only with your explicit request. No system is perfectly secure, and we will notify you promptly if a breach affects your instance.
09
You can see, export, correct and delete your data from inside the app at any time, since it all sits on your instance. For anything held centrally — your email address and billing record — write to us and we will provide, correct or delete it as the applicable law requires.
10
Material changes to this policy will be announced in the app or by email before they take effect. Questions about privacy: contact@bytefuture.com