The short version
- Your data is stored in the EU. LabSense runs on Amazon Web Services in Frankfurt, Germany, and serves every country from there.
- Your health data is used to run LabSense for you. No ads, no third-party trackers, no data brokers. We never sell your data.
- We count how the app is used, in our own database. It shows us what works and where people get stuck. It never includes your health data, and you can turn it off in More → Settings → Share usage statistics.
- AI features ask first. Before any AI feature sends data for the first time, the app asks for your permission, and you can turn AI off at any time. Names, birth dates and ID numbers on lab reports are hidden before the AI sees them, and your email is never sent.
- You’re in control. You can edit or delete any entry, delete a profile, or delete your whole account in the app.
- Questions? Write to privacy@labsenseapp.com.
Who we are
This policy explains how LabSense (“LabSense”, “we”, “us”) handles personal data when you use the LabSense app for iOS and Android (the “app”) and this website, labsenseapp.com.
LabSense is the controller of your personal data: we decide why and how it’s processed. You can reach us about anything in this policy at privacy@labsenseapp.com. For help with the app, write to support@labsenseapp.com.
What we collect
Account and settings
- Your email address, and how you sign in: with Google, with Apple (on iPhone and iPad), or with a one-time code we email you.
- The identifier Google or Apple gives us for your sign-in. If you use Apple’s Hide My Email, we receive the relay address Apple creates, not your real address.
- If you sign in with Apple, a token Apple issues, stored encrypted, so we can revoke your Apple sign-in when you delete your account.
- Your settings: language, units, time zone, notification choices, whether original lab files are kept on our servers, and your choice about AI processing (with its date and version).
Profiles
For your own profile and each family member you add: a name (a nickname is fine), sex, year of birth and, if you choose one, an avatar or photo. An account holds up to 6 profiles, and every profile is for an adult aged 18 or over.
Health data
Health data is a special category of personal data under the EU General Data Protection Regulation (GDPR). LabSense stores:
- lab results and biomarker values, whether you enter them, upload a report or import them from Apple Health or Health Connect, with their dates, units and lab
- measurements you log, such as weight, height, blood pressure or glucose
- custom reference ranges you set
- your answers to the onboarding questions and the body-system surveys, such as conditions, symptoms, lifestyle and family history
- Health Status assessments, body-system scores, checkup lists, and the PDFs LabSense makes for you
- the food you log, your nutrition goals (such as target weight and activity level), the supplements you take, their schedules and the doses you mark
Files you upload
- Lab reports, as PDFs, photos or document scans.
- Medical documents such as ultrasound, ECG or MRI reports. They’re stored for you and never sent to an AI service.
- Food photos, and photos you add to profiles.
Things we process without storing them
- Voice descriptions of meals. The recording is sent for transcription and discarded. Only the text comes back to your phone.
- Photos of supplement labels. The photo is read and discarded.
Apple Health and Health Connect
If you turn on health data sync, LabSense reads the types you allow: weight, height, heart rate, resting heart rate, blood pressure, blood glucose, blood oxygen, body temperature, steps and sleep. The first sync imports up to the last 12 months. Heart rate, blood oxygen and continuous glucose monitor readings are saved as one average per day. See Apple Health and Health Connect below for how this data is used.
Device and security data
- For each device you sign in on: a random installation ID, the platform (iOS or Android), the operating system version, the device model, the app version, the push notification token, and session tokens (we store only their hashes).
- When you ask for a sign-in code, sign up or log in, the app includes a check from Apple App Attest or Google Play Integrity, so we can tell the request comes from the genuine app. We record the result.
- When you ask for a sign-in code, we keep the IP address the request came from for 24 hours, to stop codes being sent in bulk.
Purchases
If you buy LabSense Plus, the App Store or Google Play takes the payment. We never see your card details. Through RevenueCat we receive your plan, the store, its start, renewal and expiry dates, and purchase events such as renewals, cancellations and refunds.
Messages you send us
If you email us, we receive your address, your message and anything you attach. When you write from the app, it fills in your account ID and app version, so we can find your account.
How you use the app
To learn which parts of LabSense work and where people get stuck, the app records simple usage events:
- when it’s opened and for how long
- which screens are opened
- the steps of sign-up
- what happens on the LabSense Plus screen, such as what opened it, which plan is chosen and whether a purchase completes
- whether you allow notifications, the camera or health data sync, and the errors the app shows
Each event carries a random ID the app creates on your device, your account ID once you’re signed in, the platform, the app version and its language. Events never contain health data: no values, results, food, supplements, documents or answers to health questions. They’re stored in our own database in Frankfurt and are never shared with or sold to anyone.
We also record what the AI features cost us for each account, to keep LabSense affordable and to spot abuse.
Usage statistics are on unless you turn them off in More → Settings → Share usage statistics. Turning them off stops the app sending them from then on.
What we don’t collect
LabSense doesn’t use advertising identifiers or third-party analytics or tracking tools, and doesn’t ask for your location or contacts.
How we use your data and why
The GDPR requires a legal basis for each use of personal data. Here’s ours:
| What we do | Data used | Legal basis |
|---|---|---|
| Create your account, sign you in and keep you signed in on your devices | Account and device data | Performing our contract with you (Art. 6(1)(b) GDPR) |
| Store and show your health data: values, ranges and statuses, charts, scores, checkups, food and supplement tracking, reminders and upper-limit warnings | Health data, profiles, files | Your explicit consent (Art. 9(2)(a)) and our contract with you (Art. 6(1)(b)) |
| Run the AI features: reading lab reports, analyzing food, scanning supplement labels, transcribing voice notes and writing your Health Status | Only what each feature needs (see AI processing) | Your explicit consent, given in the app (Art. 6(1)(a) and 9(2)(a)) |
| Import data from Apple Health or Health Connect | The types you allow | Your explicit consent, given in the app and the system permission screen (Art. 9(2)(a)) |
| Send notifications about your data, such as results that are ready | Push token, notification text | Our contract with you (Art. 6(1)(b)); you can turn each kind off |
| Send tips and special offers | Your opt-in, your plan, when you last used the app | Your consent (Art. 6(1)(a)); off unless you turn it on |
| Manage subscriptions, free limits and daily fair-use limits, and keep track of what the AI features cost for each account | Purchase data, usage counts, the AI features’ token counts and cost | Our contract with you (Art. 6(1)(b)) |
| Keep LabSense secure: stop abuse and fraud, limit sign-in code requests, check that requests come from the genuine app | Device data, attestation results, the IP address of code requests | Our legitimate interest in protecting LabSense and its users (Art. 6(1)(f)) |
| Find and fix errors | Technical error reports with personal data removed | Our legitimate interest in a working service (Art. 6(1)(f)) |
| Understand how LabSense is used and improve it: which features are used, where sign-up or purchases get stuck, how long the app is open | Usage events: a random app ID, your account ID once you’re signed in, the platform, app version and language | Our legitimate interest in improving LabSense (Art. 6(1)(f)). You can object by turning off Share usage statistics |
| Improve food analysis using the problem reports you send | The report, the food’s result and a copy of its photo | Your explicit consent, given when you send the report (Art. 9(2)(a)) |
| Answer your messages | Your message, account ID | Our contract with you, or our legitimate interest in helping you (Art. 6(1)(b), (f)) |
| Meet legal obligations and handle legal claims | What the situation requires | Legal obligation (Art. 6(1)(c)); legal claims (Art. 6(1)(f) and 9(2)(f)) |
When you create your account, you agree to the Terms of Use and confirm you’ve read this policy. Before any AI feature first sends data, the app asks for your separate, explicit consent to AI processing. You can withdraw at any time: turn off AI processing in More → Settings → AI processing, turn off health data sync, or delete your data or your account. LabSense can’t work without storing health data, so withdrawing that consent means deleting your account. Withdrawing doesn’t affect processing that happened before.
LabSense doesn’t make decisions about you that have legal or similarly significant effects. Statuses, scores and the Health Status are information for you, not decisions.
AI processing
Some features use AI. How LabSense uses AI explains each one in plain language. In short:
- We ask first. Before an AI feature sends anything for the first time, the app shows Allow AI processing. You can say no and keep using everything that doesn’t need AI, including adding results by hand. Your choice is stored with your account, and our servers refuse AI work without it.
- Who gets it. Anthropic, through its Claude models, reads lab reports, titles reports, analyzes food, calculates ingredients and nutrients, reads supplement labels and writes the Health Status. OpenAI transcribes voice descriptions of meals and nothing else.
- What’s sent. Only what the feature needs: the report, photo, text or recording you add, and for the Health Status your results and answers with only your sex and age. Names, birth dates and ID numbers on lab reports are hidden first: on digital PDFs by our own redaction service running on our servers, and on photos and scans by you, painting over them in the app. Your name, email address, exact birth date and account ID are never sent.
- How they handle it. Anthropic and OpenAI process the data as our service providers under their commercial API terms. They don’t use it to train their models. They may keep it for a limited period to detect and prevent abuse, and then delete it.
Who we share data with
We share personal data only with the service providers that help us run LabSense, under contracts that require them to protect it and use it only on our instructions:
| Provider | What they do for LabSense | Data they handle | Where |
|---|---|---|---|
| Amazon Web Services | Hosting: servers, database, file storage, and our own redaction service | Everything LabSense stores | Frankfurt, Germany |
| Anthropic | AI features, with Claude models | What each AI feature sends | United States |
| OpenAI | Transcribing voice descriptions of meals | The recording | United States |
| Google (Firebase Cloud Messaging) | Delivering push notifications | Push token and the notification’s text, which can name a profile, a supplement or biomarkers | United States and other countries where Google operates |
| RevenueCat | Keeping track of subscriptions | Your LabSense account ID (a random identifier), purchase records from the stores, platform and app version | United States |
| Postmark | Sending sign-in code emails | Your email address and the code | United States |
| Sentry | Error reports | Technical details of errors. Request contents, user details, AI inputs and outputs are removed before sending. | European Union |
Our servers also read app settings, such as the minimum supported app version, from Firebase Remote Config. No user data goes there.
Apple and Google. When you sign in with Apple or Google, buy Plus in the App Store or Google Play, connect Apple Health or Health Connect, receive notifications through Apple’s push service, or the app checks itself with App Attest or Play Integrity, Apple or Google process data under their own privacy policies.
Tips and offers. If we start sending tips and offers through a messaging service, it will receive only your account ID, whether you’ve opted in, whether you have Plus and when you last used the app. We’ll name it in this policy first.
Other cases. We may disclose data when the law requires it, to protect the rights and safety of our users or others, or as part of a merger or acquisition, in which case this policy keeps applying and we’ll tell you first. We never sell personal data or share it for advertising.
International transfers
Your data is stored in the European Union, in Frankfurt, Germany, wherever you live. Some of our providers are based in the United States or process data there (see the table above). When personal data leaves the European Economic Area, we protect it with the safeguards the GDPR provides: the European Commission’s Standard Contractual Clauses, or its adequacy decision for the EU–US Data Privacy Framework where a provider is certified under it. You can ask for a copy of these safeguards at privacy@labsenseapp.com.
How long we keep data
We keep your data while your account exists, unless you delete it sooner or a shorter period below applies. When you delete something in the app, it’s removed from our database at once and from file storage within minutes.
| Data | How long we keep it |
|---|---|
| Your account, profiles, health data, and the documents and PDFs you keep | Until you delete them or your account |
| Original lab report files | While Keep original files on our servers is on (it’s on by default). Turning it off deletes the stored originals; your digitized results stay. |
| The copy of a lab report prepared for the AI (the redacted PDF, or your painted pages) | Deleted once the analysis succeeds. If it fails, kept so you can retry, until you retry or delete the upload. |
| Uploads you don’t finish | 24 hours |
| Food photos | Until their day leaves the two-week food diary, then deleted overnight. The food’s name, portion and nutrients stay. |
| Food problem reports, with a copy of the photo | 90 days |
| Voice recordings and supplement label photos | Not stored |
| Sign-in codes, and the IP address that asked for one | 24 hours |
| Sessions and device records | Until you log out, or one year after you last used the app on that device |
| Notification history | 90 days. A record that a retest or results reminder was sent stays with your account, so it isn’t sent twice. |
| Purchase events | 13 months |
| Usage events | 13 months |
| What the AI features cost for each account | 25 months. When you delete your account, these records lose any link to you. |
| Daily fair-use counters | 30 days |
| Dismissed supplement warnings | 14 days |
| Server logs, which identify you only by account ID and never contain health content | 90 days |
| Database backups | 14 days |
| Error reports | A limited period, then deleted automatically. They contain no personal data. |
| Support emails | As long as we need them to help you |
| Data sent to AI providers | A limited period under their terms, for abuse monitoring |
How we protect your data
- Encryption in transit. The app talks to our servers only over HTTPS. Our file storage refuses unencrypted connections, and our servers connect to the database over verified TLS.
- Encryption at rest. The database and file storage are encrypted on disk. Apple sign-in tokens are encrypted with a key held in AWS Key Management Service. Sign-in codes and session tokens are stored only as hashes.
- Separation. Every request is checked against your account, and automated tests confirm that one account can’t reach another’s data. Files are private, and the links the app uses to show them expire after 10 minutes.
- Limited access. There’s no admin website. Support tasks run as recorded commands that never show health data.
- Careful logging. Logs and error reports never contain document text, food descriptions, AI inputs or outputs, sign-in codes or tokens.
No system is perfectly secure. If a breach puts your data at risk, we’ll tell you and the authorities as the law requires.
Your rights
Under the GDPR you have the right to:
- access your data and get a copy of it
- correct data that’s wrong
- delete your data
- restrict how we use it
- receive your data in a portable format
- object to processing based on our legitimate interests
- withdraw your consent at any time, without affecting what happened before
- complain to a data protection authority
Many of these you can do yourself in the app:
- Edit or delete values, reports, documents, foods and supplements.
- Delete a family member’s profile from its profile page.
- Share or save your stored files and the PDFs LabSense makes. Plus members can also export their biomarkers as a PDF.
- Turn off AI processing in More → Settings → AI processing.
- Turn off usage statistics in More → Settings → Share usage statistics.
- Turn off health data sync, and remove the imported data, in More → Health data sync.
- Turn off Keep original files on our servers in More → Settings.
- Delete your account in More → Delete account (see Delete your account).
For anything else, including a full copy of your data (your usage events included), write to privacy@labsenseapp.com from the email address of your account. We may ask you to confirm it’s you. We’ll answer within one month, or tell you within that month if we need longer (up to two more months for complex requests). It’s free.
You can also complain to the data protection authority where you live or work. The European Data Protection Board lists them for the EU and EEA. We’d appreciate the chance to sort things out first, so do write to us.
Wherever you live, you can use these rights with us. If the law where you live gives you more, write to us and we’ll honor them.
Apple Health and Health Connect
- LabSense only reads data. It never writes anything to Apple Health or Health Connect.
- Imported data is used only to provide the features you use: it’s added to your biomarkers, your Health Profile and your Health Status. If you allow AI processing, it can be part of what the Health Status sends to Anthropic.
- It’s never used for advertising or marketing, never sold, never shared with data brokers, and never used for anything unrelated to the features you use.
- Only the account holder’s profile is synced. It’s your phone’s data, so it can’t go to a family member’s profile.
- You can turn sync off, or remove the imported data, in More → Health data sync. You can also withdraw the permission in the Health app on iPhone (Settings → Health → Data Access & Devices) or in the Health Connect app on Android.
LabSense’s use of information received from Health Connect adheres to the Health Connect Permissions policy, including its Limited Use requirements.
Family members
You can add profiles for adult family members, up to 6 profiles per account. Please add someone’s health data only with their permission. A family member can write to privacy@labsenseapp.com to use their rights over their own data.
Children
LabSense is for adults. You must be 18 or older to create an account, and profiles can only be created for people aged 18 or over. We don’t knowingly collect children’s data. If you believe a child’s data is in LabSense, contact us and we’ll delete it.
Notifications
- Notifications about your data, such as results that are ready, a Health Status that’s ready or a suggested retest, are sent from our servers through Google Firebase Cloud Messaging and Apple’s push service. Their text can name a profile, a supplement or biomarkers.
- Supplement and meal reminders are scheduled on your phone and don’t pass through our servers.
- Tips and special offers are off unless you turn them on.
- You choose which notifications you get in More → Settings → Notifications and in your phone’s settings.
This website
This website uses no cookies, no analytics, no tracking pixels, and no third-party scripts, fonts or embeds. Its fonts and images are served from our own domain. Our hosting provider, Amazon Web Services, processes technical data such as your IP address and browser type to deliver the pages and protect the site, and we don’t use it to identify you. Links to the App Store, Google Play or your email app take you to those services, under their own policies.
Changes to this policy
We’ll update this page and the date at the top when this policy changes. If a change is significant, for example a new purpose or a new kind of provider, we’ll tell you in the app or by email before it takes effect, and ask for your consent again where the law requires it.
Contact
- Privacy questions and requests: privacy@labsenseapp.com
- Help with the app: support@labsenseapp.com