Your health data is yours.
Here is how it is protected.
This page describes what BodySynk does today — the architecture, the controls and the choices you have. Plain language first, technical detail underneath.
- Your health data is private to your account
- Core health data is stored in the EU (Ireland)
- Encrypted in transit and at rest
- Two-factor login available
- We do not sell your health data
- Export or delete your data whenever you want
Your records are separated from everyone else's
BodySynk is built so that each person reaches only their own health information. That separation is enforced by the system itself, not by a promise in a policy document.
One account, one set of records
Every health record you create is tied to your account. The application only ever asks the database for your own rows, and the database enforces that rule again on its own.
Enforced by the database, not just the app
User-owned tables are protected by row-level security. Even if a request reaches the database directly, it is evaluated against who you are signed in as.
Signed-in access only
Health features live behind authentication. There is no public path to a personal record, and nothing personal is exposed on the marketing site.
Privileged functions are role-protected
Administrative and support functionality is separated from ordinary accounts and checked on the server against an explicit role. A normal account cannot reach it, and several internal views are read-only by design.
BodySynk's database and application authorization are designed to restrict each account to its own private records, and automated and internal adversarial tests check those boundaries. In that internal testing we found no reproducible way for one account to reach another account's health data.
Stored in the European Union
Core BodySynk health data at rest is hosted in EU infrastructure in Ireland.
EU hosting, Ireland
The production database and the storage that holds your uploaded medical files are hosted in the European Union, in Ireland.
Service providers
BodySynk uses service providers to run the platform, and some operational processing can take place outside the EU. We do not claim that every byte of operational data stays in Europe — only that core health data at rest is hosted in Ireland.
Encrypted in transit
Traffic between your device and BodySynk is protected with HTTPS/TLS, so your information is not readable as it travels.
Encrypted at rest
The production database and file storage use encryption at rest as provided by the underlying platform. BodySynk is not end-to-end encrypted: the service has to read your data to organise and explain it.
Details of the providers required to operate BodySynk are described in our Privacy Policy.
Add a second step to your login
BodySynk supports two-factor authentication using a standard authenticator app (TOTP), such as the one you may already use for your bank.
Authenticator-app codes
Turn on two-factor authentication in Settings and scan the code with your authenticator app. From then on, signing in to BodySynk asks for a code from your app in addition to your password.
Checked before the app opens
If you have enrolled a second factor, BodySynk's authenticated application routes require you to complete that challenge before they open. We are extending the same requirement deeper into the backend, and we do not yet claim it is enforced at every layer.
Your permissions are recorded
BodySynk keeps an auditable record of the privacy and health-data permissions you provide, so there is never a question about what you agreed to.
Terms acceptance
Recorded separately when you accept the Terms of Service.
Privacy acknowledgement
Recorded separately when you acknowledge the Privacy Policy.
Health-data consent
Your explicit permission for BodySynk to process health information is its own record, not bundled into the others.
Each record stores the account it belongs to, the type of consent, the version of the document, and the time it happened. Entries are kept as a history rather than overwritten, so an earlier decision is still visible after you make a new one.
Take your data with you, or remove it
A platform you can trust should be easy to leave. Export your data, download your reports, or delete your account whenever you choose.
Export your BodySynk data
From Settings you can export your account and health records as a single structured JSON file, together with time-limited download links for the files you uploaded. The export lists what it covers and what it leaves out, such as internal security logs and regenerable caches.
Keep your reports
Your generated health summaries and timelines are yours to download and keep, whether or not you continue using BodySynk.
Delete your account
You can delete your account from Settings. Your health records and the files you uploaded are removed from BodySynk's active systems, and your sign-in account is deleted, as part of that process.
Documented retention
What BodySynk keeps, and for how long, follows a documented retention and deletion practice mapped to the data the platform actually holds.
When you delete your BodySynk account, your health records are removed from BodySynk's active systems according to our deletion process, your uploaded files are purged from storage, and your sign-in account is deleted. We keep a pseudonymous statistical record of the closure — things like how long the account existed, how many entries it held and any reason you choose to type in — with no name, no contact details and none of your health content in it.
What happens before AI sees anything
Where a BodySynk feature works with text, direct personal identifiers are removed by our privacy layer before that text is sent onward, and the request is blocked if that step cannot complete. Some document-image and photo features have to send the uploaded image itself to our AI processor to read or classify what is in it.
- 01
Your data is structured first
BodySynk reads your records with structured health logic before any AI is involved, so the system already knows what is relevant.
- 02
Only the relevant context is selected
Instead of handing an AI everything about you, BodySynk selects the narrow slice of context needed to answer the question in front of you.
- 03
Direct identifiers are removed from text
Where a feature works with text, names, IDs, dates of birth, addresses and similar identifiers are removed by a deterministic privacy layer — rule-based, not another AI guessing.
- 04
If the text privacy step fails, the request stops
On those text paths the privacy layer is a required checkpoint. If it cannot complete, the request is blocked rather than sent onward.
AI helps explain. It does not decide, and it is not given your identity.
BodySynk does not use your health data to train AI models, and we do not sell it. Where a feature sends text, direct identifiers are stripped first, so what the AI service receives is pseudonymised rather than anonymous — an uploaded image can still contain printed details we cannot promise to remove. The prompt content from health requests is kept out of ordinary application logging. We are still completing written confirmation from our AI provider about upstream retention, training and processing regions, and we will not state those as settled until we have it.
The steps a health request passes through.
Text-based health requests are routed through the privacy checkpoint before they leave BodySynk. Image-based extraction features are a separate, narrower path: the file you uploaded is processed by the AI service so its contents can be read, and the result is then handled like the rest of your records.
- Step 01
Secure upload
Files travel over encrypted connections into your own private storage area.
- Step 02
Text extraction where the file allows it
When a document contains machine-readable text, that text is extracted inside BodySynk's own environment rather than by sending the file itself onward.
- Step 03
Identifier detection
Rule-based detection locates names, IDs, dates and addresses in extracted text. No external AI is used to find your personal details.
- Step 04
Redaction
Identifiers are replaced with neutral tokens such as [NAME] or [ID] before the text leaves the boundary.
- Step 05
Second check
The cleaned text is re-scanned. If something personal is still present, the request does not continue.
- Step 06
Image and photo workflows
Scanned documents, label photos and similar images cannot be read as text first. For those features the image itself is sent to our AI processor so its contents can be extracted or classified, over an encrypted connection and on your action.
Uploaded medical files stay private
Lab PDFs, scans and photos of reports are some of the most personal things you can upload. They are treated that way.
Non-public storage
Medical and private health uploads — lab PDFs, imaging, scans and photos — are stored in non-public buckets with controlled access. They are not published to a public address and are not listed anywhere browsable. Cosmetic assets such as a profile picture are held separately and are not treated as medical files.
Ownership boundaries
Each file is owned by the account that uploaded it, and access is checked against that ownership. One account cannot browse another account's documents.
Time-limited links
When a file needs to be shown or downloaded, BodySynk generates a short-lived signed link for you rather than leaving the file openly reachable.
We try to break it before anyone else does
BodySynk maintains automated security checks and performs internal adversarial testing across authentication, authorization, user isolation and sensitive-data boundaries. This work is done by our own team — it is not an independent audit, and we do not describe it as one.
Authorization invariants
Row-level security rules, database migration invariants and privileged endpoints are re-checked automatically, so a protected route cannot quietly become open.
Cross-account isolation tests
BodySynk maintains automated tests that sign in as two separate purpose-made accounts and check that neither can reach the other's records. These run against configured test accounts rather than continuously, and results are reviewed by our team.
Authentication coverage
Sign-in, session handling and unauthenticated access to protected endpoints are covered by automated checks. Second-factor behaviour is exercised manually and by test specs that require a purpose-made enrolled account.
Transport and header checks
Public routes and browser-security headers are tested, and scheduled/automated endpoints must present their own authentication.
Browser and transport protections
BodySynk applies modern browser and transport security protections across the web application, including a Content Security Policy, HSTS, content-type and frame protection, a strict referrer policy and a restrictive permissions policy.
Incident response
BodySynk maintains documented incident-response and personal-data-breach procedures covering how an incident is identified, contained, investigated, remediated and recorded, and how affected data is handled.
We do not monetize your health data
BodySynk earns money from people who choose to pay for BodySynk. That is the entire business model.
- No advertising business model.
- No sale of your health data.
- No advertising profiles built from your records.
- No third-party marketing use of your health information.
- No data brokers, no insurer pipelines, no analytics resale.
BodySynk does not provide your individual health information to employers, insurers, advertisers or other users unless you deliberately choose to share it yourself. The service providers required to operate BodySynk are handled under our privacy framework and described in the Privacy Policy.
If we ever changed this, you would be told plainly, before anything changed — and you would still be free to leave with all of your data.
Trust and security contact
One inbox for privacy, security, and data questions.
Security questions
Questions about how BodySynk is built, hosted, or protected.
Privacy questions
How your data is collected, used, retained, and deleted.
Data requests
Export, correct, or delete your personal data. You can also do all three from Settings inside the app.
Responsible disclosure
If you believe you have found a security issue, please contact us before publishing. We will respond and credit responsible reports.
Reach the trust and security team at [email protected].
This page is maintained by the BodySynk team and describes practices that are in place today. It is not a certification, and BodySynk is not a medical provider, laboratory or diagnostic service. See our Privacy Policy and Terms.
Your data is yours. You can see it, take it, and remove it — at any time, for any reason.