This policy covers the One L1fe app and, in section 13, this website. To delete your account, see section 8.
One L1fe is operated by One L1fe ApS (CVR 46866193), Nørrebro Vænge 2, 1. th, 2200 Copenhagen N, Denmark. We are the data controller for the personal data described in this policy. Questions or requests, including anything about privacy: privacy@one-l1fe.com.
Age. One L1fe is for people aged 18 and over. We do not knowingly collect data from anyone younger. If we learn that an account belongs to someone under 18, we delete it.
You give us:
| Category | Examples |
|---|---|
| Account | Email address and password. The app asks you to sign in before you use it. You need these to use the app; everything else you give us is optional. |
| Profile | Birth date or year, sex, height, country, units and date format, and the coaching style you choose |
| What you log | Entries in the hubs, such as training sessions, meals, supplements, sleep, weight, body composition and lab markers, your priorities, plans and goals, and notes you write |
| Health record | What you choose to note about yourself, such as conditions, medication, allergies, diet, blood type, organ donor status, vitals, fitness tests and notes |
| Coach conversations | Messages you send an AI coach, what you attach (a photo, a file or a voice note) and its replies. The history is kept on your phone; to answer, each message goes to our AI provider (section 6). If you switch on personalized coaching (section 3), conversations are also kept in our database and used to personalize your coaching (section 4). |
| Feedback and reports | A message you send from the Feedback screen, or an AI reply you report. Each is sent to us when you tap Agree and send on the form, whether or not you have allowed storage, and kept in our database in Frankfurt (section 4). |
| Support | Emails you send us and our replies |
You connect or hand in: nothing is imported unless you allow it, and you can withdraw that permission at any time in your phone's settings.
| Source | Data imported |
|---|---|
| Health Connect (Android) and Apple Health (iPhone) | Read only: steps, sleep, heart rate, resting heart rate, heart-rate variability, workouts, weight, aerobic fitness (VO2 max), active and total calories, distance, blood oxygen and breathing rate. The app never writes to them. The first sync reads the last 90 days where the phone allows it. Data from your watch or other apps arrives through them. |
| Garmin, if you connect your Garmin account | The data you allow in Garmin Connect, such as activities, sleep, heart rate, heart-rate variability, stress and body composition. What we do with it, who processes it and its limits: section 12. |
| Files and photos you add | A lab report, a microbiome or genomic test report, a meal photo, a supplement label, a workout export file or another file you hand to a coach or add to a hub, and the values read from it |
On your phone only: if you allow it, the app uses the camera and your photos to take or pick an image, the microphone for voice notes and dictation, and your calendar to add a session you asked it to add. Nothing from your calendar is sent to us. Dictation runs on the phone where it can; otherwise your phone passes the audio to the speech service of its operating system.
We collect automatically: only what the update check needs (our app update service, section 6), and nothing else unless you switch on usage statistics and crash reports (section 3). The app uses no advertising identifiers and no tracking pixels and sets no cookies. It keeps your sign-in on your phone so that you stay signed in. The providers described in section 6 see what any server sees in a request, such as your IP address and the app version.
Usage statistics and crash reports (optional, off until you switch them on): which screens and features you open and where you stop, as event names with the time, never what you typed or any health value; the app version, phone model, OS version and language; and a random installation number that is not linked to your account or name. For a crash: the error and the place in the code where it happened. No names, messages, photos or health data.
Most of what makes One L1fe useful is data about your body, including health and genetic data such as lab and genomic test reports. Under Article 9 GDPR this is a special category and gets stronger protection. The app asks for two separate consents, each with its own switch and neither as part of accepting any terms, and offers two optional ones: personalized coaching from your conversations, and usage statistics and crash reports.
What we never do with health data, including data from your phone's health service or any other service you connect:
We use it only to show it to you, to give you the insight and coaching you ask for, and to keep that working. Nobody at One L1fe reads your health data unless you have explicitly agreed (for example by sending us a report or a support email that contains it), where it is needed for security or required by law, or in aggregated form to run the service. Data the app receives from Health Connect is used in line with the Health Connect permissions policy, including its Limited Use requirements. Where a connected service's own terms do not allow its data to go to an AI model, that data is left out of every AI request. Health Connect data goes to our AI provider only with your AI consent (section 6) and within those Limited Use requirements.
What you log is kept on your phone. The app processes it there, on your device; we have no access to it unless it is copied as described below. While you are signed in and have allowed storage, a copy of your hubs, health record, plans and profile is also kept in our database, so a new phone can have it back. That database is hosted by our database provider in Frankfurt, Germany.
Some records are kept in that database whether or not you have allowed storage, because the service cannot work or prove its own conduct without them: your sign-in details, a record of which consents you gave or withdrew and which version of the Terms of Service you accepted, each with the time, and a daily count of how many AI requests your account made. Feedback and a reported AI reply are stored there when you send them, whether or not you have allowed storage, because you send them to us on purpose. Tapping Agree and send, under the sentence that says so, is your consent to us reading any health details in them.
Coach conversations are kept on your phone. A new phone or a reinstall starts with none unless you use personalized coaching, and you can delete a conversation in the app. On Android the history is not included in the phone's cloud backup. To answer, each message and what you attach go to our AI provider, which keeps them as described in section 6. With personalized coaching (section 3), your conversations and the facts drawn from them are also kept in our database in Frankfurt; deleting a conversation in the app deletes it there too, together with the facts drawn only from it.
| Purpose | Legal basis |
|---|---|
| Create and run your account | Contract, Art. 6(1)(b) |
| Copy your hubs, health record, plans and profile to your account | Explicit consent, Art. 6(1)(a) and 9(2)(a) |
| Keep your conversations and draw facts from them to personalize your coaching (optional) | Explicit consent, Art. 6(1)(a) and 9(2)(a) |
| Send coach questions, attachments and readings to our AI provider for an answer | Explicit consent, Art. 6(1)(a) and 9(2)(a) |
| Keep a record of your consents and of the terms version you accepted, so we can show what you agreed to | Legitimate interests, Art. 6(1)(f), in meeting Art. 7(1) |
| Provide support, read feedback and reports you send | Contract, Art. 6(1)(b); for health details in what you send, your explicit consent given by tapping Agree and send, Art. 9(2)(a) |
| Deliver app fixes without a store update (our app update service) | Legitimate interests, Art. 6(1)(f) |
| Learn from usage statistics and crash reports, to fix faults and improve the app (optional) | Consent, Art. 6(1)(a) |
| Look up a product when you scan its barcode (a public food database) | Contract, Art. 6(1)(b), because you asked for the lookup |
| Keep the service secure and working, including a daily limit on AI requests | Legitimate interests, Art. 6(1)(f) |
Where we rely on legitimate interests, we have weighed our interest against your rights, and you can object (section 9).
We do not sell your data and do not share it with advertisers. These providers process data for us, under a data processing agreement or the provider's own data terms. Every provider that receives your health data (our database provider, our AI provider and the provider of our connection server, section 12) is bound by contract to protect it to the standard of this policy, and every other provider in this section that processes data for us is bound to protect it at least to that standard. A list of the providers we use, by name, is available on request at privacy@one-l1fe.com. The providers that receive data from Garmin are named in section 12.
| Provider | What it does | Where |
|---|---|---|
| Our database provider | Database, sign-in, account deletion, usage statistics (with your consent) and the server function that passes AI requests on to our AI provider | Frankfurt, Germany; support staff may reach it from outside the EU (section 7) |
| Our email provider | Our email, including privacy@ and support mail you send us | Can be outside the EU/EEA (section 7) |
| Our website hosting provider | Serves our website, including the page that opens the links in account emails | Global network (section 7) |
| Our crash reporting provider | Crash reports, only with your consent: the error, the place in the code, app version, phone model and OS version | Frankfurt, Germany; US staff may reach it for support (section 7) |
| Our AI provider | Processes what the app sends it (below) to write the answer, and may keep it for a limited period (currently up to 55 days) only to detect misuse and meet legal duties | Can be outside the EU/EEA (section 7) |
Our app update service delivers app fixes without a store update. When the app checks for one, the service sees your device's IP address, the app version and platform, and a random installation number, and acts as our processor under that provider's own terms of service, which include the Standard Contractual Clauses. It receives no health data. That provider is in the United States (section 7).
An on-device text recognition component is built into the app to read text on your phone. What it reads stays on the phone. The component may send its provider technical data, such as the device model and how the feature performed, which that provider handles as an independent controller under its own privacy policy. We rely on our legitimate interest in a working text scanner, Art. 6(1)(f).
A public food database, run independently from France, receives the barcode when you scan a product and, like any server, your IP address. It receives nothing else about you.
We may also disclose data to public authorities where legally required. In a merger or acquisition we notify you in advance, and health data moves to the new owner only with your explicit consent; if you do not give it, we delete that data before the transfer, or you can delete your account.
The AI coach. When you use it, you are interacting with an AI system, not a person. Only after you have given the AI consent does the app ask our server to send our AI provider:
Apart from the conversations and facts kept for personalized coaching, our server keeps no copy of these requests or answers. We use our AI provider's paid service, under whose terms our AI provider processes them for us and does not use them to improve its products or train its models, apart from the models it uses only to enforce its usage policies on flagged requests (below). Our AI provider may keep them for up to 55 days, only to detect misuse and meet legal duties. If its systems flag a request as possible misuse, authorized staff of our AI provider may read it, and our AI provider may use it only for the models that enforce its usage policies, not its general models. We do not make solely automated decisions with legal or similarly significant effects under Article 22; the coach suggests, you decide.
Our AI provider, our email provider, our app update service, our website hosting provider and our crash reporting provider may process data outside the EU/EEA, including in the United States. Our crash reporting provider is a US company: it stores crash reports in Frankfurt, and its staff may reach them from the US under the Standard Contractual Clauses in its data processing agreement. Our database provider is one of the established cloud database services; its staff may reach the database from outside the EU/EEA. Those transfers are covered by the European Commission's Standard Contractual Clauses in our database provider's data processing agreement. Our AI provider, our email provider, our app update service and our website hosting provider state that they are certified under the EU/US Data Privacy Framework and rely on it for these transfers. The data processing terms of our AI provider and our email provider add the Standard Contractual Clauses for any case the framework does not cover. Ask us at privacy@one-l1fe.com for a copy of the Standard Contractual Clauses.
In the app: Settings, Account, Delete account. That deletes your account and everything stored with it in our database at once, and clears the app's data on that phone. Calendar entries you asked the app to add stay in your calendar until you remove them.
Without the app: email privacy@one-l1fe.com from the address you signed up with and ask us to delete your account. We delete it within 30 days and confirm by email.
What is kept afterwards:
Nothing else.
You have the right to access your data, have it corrected or deleted, restrict or object to processing, receive it in a portable format, and withdraw consent at any time.
To get a copy of your data, email us and we send it. We respond to every request within one month, and will tell you within that month if a complex request needs longer. It is free. We may need to verify your identity first. Data on your phone is yours to delete in the app or by uninstalling it.
You can also complain to Datatilsynet, or to the supervisory authority where you live.
Traffic between the app and our server is encrypted, data in our database is encrypted at rest by our hosting provider, and the database only lets an account read its own rows. The key to our AI provider is held on our server, never in the app. No system is perfectly secure.
| Data | Retention |
|---|---|
| Account, profile, health record and copied hub data on our server | While your account is open, and only while it serves the purposes above; deleted at once when you delete your account in the app, or within 30 days of a request by email (section 8) |
| Consent records, Terms acceptance, daily count of AI requests, feedback and reported replies | While your account is open; deleted with it |
| Coach conversation history | On your phone until you delete it or uninstall the app; with personalized coaching also in our database until you delete the conversation, switch the feature off or delete your account |
| Facts drawn from your conversations | While personalized coaching is on and your account is open; deleted when you switch it off or delete your account |
| Requests sent to our AI provider | Up to 55 days at our AI provider; none on our server |
| Usage statistics | 12 months, then deleted; not linked to your account |
| Crash reports | 30 days at our crash reporting provider, then deleted |
| Support correspondence | 24 months after the case closes |
If you connect your Garmin account in the app, Garmin sends us the data you allow in Garmin Connect: activities and workouts, sleep, heart rate and heart rate variability, stress, body composition and similar daily health values. This section covers what Garmin sends us through that connection. Readings that Garmin Connect writes to your phone's health service reach us as Health Connect or Apple Health data and are covered in sections 2 and 3. You connect it yourself, and we store what Garmin sends only with your storage consent (section 3; Art. 6(1)(a) and 9(2)(a) GDPR), which you can withdraw in Settings, under Account. You can disconnect at any time in the app or in Garmin Connect; from then on we receive nothing new.
How we use it. Only to show you your own data in the app and to track your trends over time. We do not sell Garmin data, do not use it for advertising and do not pass it to anyone except the two providers named here.
Who processes it for us.
Support staff of both providers may reach the data from outside the EU/EEA under the Standard Contractual Clauses in their data processing terms (section 7). We keep Garmin data as long as your account exists and delete it with your account (section 8), or earlier on request at privacy@one-l1fe.com; withdrawing storage consent deletes the copy in our database as described in section 3.
No AI processing. Garmin data is not sent to our AI provider. The coach does not read it, and neither we nor anyone else use Garmin data, or anything derived from it, to train, evaluate or improve an AI model.
Your rights. You can access, correct, export and delete your data and withdraw any consent as described in section 9.
This section covers the website one-l1fe.com.
The form collects your email address and an optional message. After you sign up it asks one optional question about what you train for. We use this to send you the launch announcement, product updates and early access invites, and your answer helps decide the order of invites. Messages are read internally and not published. Joining the list does not create an app account.
We also record the date and time of your consent, your IP address, the exact consent wording you ticked, the technical name of your browser, the country it reports, the page that referred you and any campaign tags in the link you opened. We keep this with your entry to show that your consent was real and to see which links bring people to the list. The legal basis for the list is your consent, Article 6(1)(a) GDPR, together with section 10 of the Danish Marketing Practices Act for the messages. The legal basis for the record is our legitimate interest in being able to show your consent and in knowing where sign-ups come from, Article 6(1)(f) with Article 7(1).
We do not send a confirmation email. We write to you when access opens. Signing up again with the same address changes nothing. Entries are stored with our database provider on its servers in Frankfurt, Germany, as a processor under Article 28 GDPR; where its staff reach them from outside the EU, the Standard Contractual Clauses apply. Your details go only to the processors described on this page, and there is no advertising.
We keep your entry until you withdraw your consent, or at the latest 18 months after you signed up if One L1fe has not launched by then. After that it is deleted. You can withdraw at any time, free of charge, by writing to hello@one-l1fe.com. Withdrawing does not affect how lawful the processing was before it. Entries made before 27 October 2026 may also hold a phone number given for text messages; it stays with the entry under the same limit and is not used.
This site sets no cookies and writes nothing to browser storage. It has no analytics, no advertising, no social media buttons and no embedded video, and its fonts are hosted on the site itself. That is why there is no cookie banner. The /account page also sends what you type there to the app's sign-in service, see below.
The page /account only serves the links in the app's emails, such as choosing a new password. What you type there goes straight to the app's sign-in service, run for us by our database provider on servers in Frankfurt, Germany, and is not stored on this site. The legal basis is the contract for your app account, Article 6(1)(b) GDPR. Where its staff reach that service from outside the EU, the European Commission's Standard Contractual Clauses apply.
The site is hosted by our website hosting provider, a company based in the United States, as a processor under Article 28 GDPR. To deliver a page, the hosting provider processes the IP address of your device, the time of the request, the page requested, the browser and system your device reports, and the referring page if your browser sends one. This keeps the site working and protects it against attacks and abuse. The legal basis is our legitimate interest in a working and secure website, Article 6(1)(f) GDPR. The data is not used for profiling or passed on, and the hosting provider keeps it briefly and then discards it.
Our hosting provider serves requests from a global network, so this data may be processed outside the EU, including in the United States. It states that it is certified under the EU-US Data Privacy Framework and also relies on the standard contractual clauses adopted by the European Commission. Until we delete them, earlier copies of waiting-list entries also remain in our hosting provider's key value storage on that global network and may be held outside the EU on the same terms. Ask us at hello@one-l1fe.com for a copy of the standard contractual clauses.
Email you send us arrives in our hello@one-l1fe.com mailbox, which our email provider, through its company in Ireland, hosts for us as a processor under Article 28 GDPR. It may process it outside the EU under the standard contractual clauses and the Data Privacy Framework. We keep such emails for 24 months after your request is closed, based on our legitimate interest in answering you, Article 6(1)(f) GDPR.
We may update this policy as the product develops; the date at the top shows the current version. We update it before any data goes to a new service or provider. For a new purpose or a change of controller, we notify you by email or in the app before it takes effect. Where a change needs your consent, we ask for it separately rather than treating continued use as agreement.