Last updated 30 August 2026
Every family gets its own server instance. Your records and knowledge pages live on that instance and nowhere else. We do not sell your data. Your records are not shared with other families and not shared with advertisers, and we keep no copy of them outside your server. The public website is measured for advertising; your instance is not. Section 5 draws that line.
One important exception: to analyse documents and answer questions, the service sends the relevant content to third-party cloud AI providers. Section 4 explains exactly what that means.
Your subscription provisions a server instance dedicated to your family: a virtual private server we set up for you, or a physical computer you keep at home. It is not a shared account on a shared system. Medical records, uploaded documents, everyday log entries and knowledge pages are stored on that instance. Other families run on their own instances and cannot reach yours.
We do not sell or rent your health information. We do not use it for advertising. We do not pool it with other families' data, and we do not use it to build or train our own models. We do not retain your records beyond your private server: there is no central database of family health records at our end.
To run the service we hold account and billing details: the subscriber's name, email address, and the subscription status. Payments are processed by our payment provider, and we never see your full card details. We also hold operational information needed to keep your instance running, such as server status and error logs. Where those logs could contain fragments of your content, we keep them only as long as needed to fix the problem.
The service depends on large language models that do not run on your instance. To read a document, structure a lab report, interpret something you have typed, revise a knowledge page, or answer a question, the service sends the relevant content to third-party cloud AI providers over an encrypted connection. That content can include medical records, test results, log entries, and the questions you ask.
Those providers process the content to return a result. We use them under commercial terms rather than consumer ones, and we select providers that state they do not use business API content to train their models. Their retention windows, security practices and legal obligations are theirs, not ours, and they may change. We cannot guarantee how a third party handles data on its own systems.
If you are not comfortable with health information leaving your instance for this purpose, this service is not the right fit, because the analysis cannot be performed without it.
This public website uses Google Analytics to count visits. It records which pages were opened, roughly where in the world the visit came from, the kind of device and browser used, and whether the Start free trial button was clicked. We use it to understand which explanations of the product land and which do not.
The website also carries Meta's advertising pixel, so 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 was a choice we made rather than a detail. On the analytics side Google Signals and ad personalisation stay switched off, so that half adds no cross-device profile. What either one measures is whether an advertisement led to a subscription — that it worked. Neither is told anything about your health, because at this point there is nothing to tell.
No health information is involved, because none exists at this point: analytics runs on these public pages, before there is an instance, an account or a record. Neither tool is connected to your instance, neither runs on it, and neither carries an identifier that could be matched to one. The line is the one this product is built on: the public website is measured, your instance is not. Your records are covered by sections 1 to 4, and nothing in this section reaches them.
Payment happens on our payment provider’s own pages, under its own privacy 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 either way. Google's own opt-out add-on covers only the analytics half; Meta's ad preferences are managed in your Meta account.
You decide who is invited to your instance and what is shared with them. Anyone you invite can see the records shared with them. When you add another person's health information, you confirm you have the right to do so and their consent where consent is required. Removing a member removes their access, not the records themselves.
Access to your instance requires authentication, and traffic to and from it is encrypted in transit. If your instance is a computer in your home, its physical security is yours to manage. No system is perfectly secure, and we cannot promise that a determined attacker will never succeed.
Your data stays on your instance for as long as your subscription is active. You can export your records and knowledge pages at any time. If you cancel, you may ask us to decommission the instance, which destroys the data on it, or you may keep the machine and the data on it. We retain billing records for as long as tax and accounting law requires.
The subscriber must be an adult. A caregiver may keep records about a child in their care. Children should not be given accounts of their own.
We cannot hand over records we do not hold. If we receive a lawful demand for account or billing information, we will comply where required, and will tell you unless we are prohibited from doing so.
We are not a healthcare provider and the service is not medical advice. See the Terms of Service for what that means, including what to do in an emergency.
We may update this policy. If a change materially affects how your data is handled, we will tell subscribers before it takes effect.
Privacy questions and data requests: contact@bytefuture.com