Privacy Policy

SOKEN is a food-scanning app. You photograph what you eat, SOKEN analyses the photo, and the app shows you how your eating is tracking over time.

This policy explains what happens to your information: what stays on your phone, what leaves it, who else sees it, how long it is kept, and how to get rid of it. It covers the SOKEN mobile app and this website.

SOKEN is published by SOKEN LLC, a Nevada limited liability company. In GDPR terms, SOKEN LLC is the data controller. Where this policy says “we”, it means that company.

Questions, requests, or complaints: info@sokenhealth.com.

1. What stays on your device

Some things stay on your phone and nowhere else, and it is worth stating precisely which. SOKEN keeps each of them in the app’s own storage on your phone. None of it is uploaded, and there is no copy of it on any server, including ours.

• Your profile photo.
• The photos of your saved meals (the meals themselves are kept with your account, section 2.12).
• What SOKEN reads from Apple Health or Health Connect, and the scores the app works out from it. Section 2.9 sets out the exceptions.
• The nights your phone estimates for you, if you turn that on: bedtime, wake time and minutes slept (2.14).

So if you delete the app, these are gone — we cannot restore them, because we never had them. Deleting your account clears them from the phone too. Logging out sets the photos aside on the phone for you: they come back if you log in again on that phone, and are deleted if a different account logs in there. Your Health data itself stays in Apple Health or Health Connect, which SOKEN never changes. You would set a new photo on your next phone.

What you log by hand (sleep, workouts, steps, weight and waist), the body scans you add, your goals, your saved meals, your reminders and the rest of what you keep in the app are on your phone and also saved to your account, so that they come back when you log in again, reinstall the app or move to a new phone. That is 2.12.

The rest of your profile is saved to your account as well as your phone, so that it follows you when you sign in somewhere else. That is 2.7, and it covers your name, your date of birth, your gender, your country, your units, your height and weight and goal weight, your answers about your body fat and how often you strength train, your goals, anything you have said you avoid eating, and your answers to the onboarding questions.

Correction, September 9, 2026. Until this date this section listed all of the above as staying on your phone, and said that none of it was uploaded and that no copy existed on any server. That was wrong: those answers have been saved to your account since the feature that carries your profile between phones was added. Nothing new is being collected here — this corrects a description that did not match what the app was already doing, and section 2.7 now sets out where that information goes and why.

2. What leaves your device

Here is everything that does, item by item, with why it is needed. Nothing outside this section leaves your phone, unless you send it yourself — for example by sharing a file from the app through your phone’s share sheet.

Correction, October 15, 2026. Until this date this section left out four things the app already did: reading a body-scan report you photograph or upload (2.10), saving to your account some setup answers filled in from Apple Health (2.9), the suggestions you can post (2.11), and the Cloudflare check on the email sign-in screen (2.1). It also named Anthropic, Google and OpenAI as the AI companies a photo could go to; the AI company is now named as OpenAI, reached through OpenRouter (2.3). And the short version at the top still said your name, your body and your goals never leave your phone, after section 1 was corrected on September 9, 2026. Nothing new is being collected here — this corrects descriptions that did not match what the app was already doing.

Correction, October 18, 2026. Until this date this policy named OpenAI, reached through OpenRouter, as the AI company that analyses your photos. The analysis was performed by Google’s Gemini models, reached through OpenRouter. From this date your photos, descriptions and reports go to Google directly, and OpenRouter no longer receives them; sections 2.3, 2.10, 4 and 5 now say so. Nothing new is being collected.

Change, October 22, 2026. Logging out no longer deletes what you log by hand and the body scans you add from your phone. They are set aside on the phone and come back when you log in again there, and are deleted if a different account logs in. Deleting your account or the app still removes them. Section 1 and the retention table in section 5 say so. This starts with the next version of the app.

Change, October 28, 2026. Your goals, what you log by hand (weigh-ins, waist, sleep, workouts and steps), the body scans you add, your saved meals, your reminders, which parts of the app you have unlocked, your trial and your settings are now kept with your account as well as on your phone, so they come back after you log out, reinstall the app or move to a new phone. The photos of your saved meals and your profile photo will follow in a later version; until then they stay on your phone. Deleting your account erases all of it. Sections 1, 2.3, 2.9 and 2.10, the new section 2.12 and the retention table in section 5 say so. This starts with the next version of the app.

Change, October 19, 2026. If you have corrected earlier scans with the pencil, a short list of those corrections (what SOKEN read, and what you said it was) is now sent to Google with each new photo, so the model can recognise your foods better. The list is kept on your phone only. Section 2.3 has the detail. This starts with the next version of the app; until then nothing changes.

Change, October 30, 2026. You can now describe a meal by voice: a microphone button in the “What did you eat?” box turns what you say into text, which you can edit before you tap Analyze. The app asks for Microphone and Speech Recognition permission the first time. Where your phone can turn speech into text itself, it does. Where it cannot, Apple’s or Google’s online speech service does it, and your speech audio goes to Apple or Google under their terms, never to SOKEN. SOKEN receives and stores only the resulting words, as it does for a meal you type. Section 2.13 has the detail, and sections 3, 4, 5 and 8 say so. This starts with the next version of the app.

Change, October 31, 2026. If you do not wear a sleep tracker, you can now turn on “Track sleep with this phone”, an opt-in switch on the Sleep screen and in Settings › Connected Sources (“This phone”). On an iPhone, SOKEN reads the motion history your iPhone keeps (or, if you have connected Apple Health, the “In Bed” time it recorded) and works out your time in bed. On an Android phone, Google Play services works out your sleep on the phone and hands SOKEN the start and end times. The app asks for Motion & Fitness permission on iPhone or Physical activity permission on Android. SOKEN keeps only the resulting nights, on your phone; they are not sent to our server, not saved with your account and not sent to analytics. Section 2.14 has the detail, and sections 1, 2.8, 3 and 5 say so. This starts with the next version of the app.

2.1 Your email address

When you create an account, your email address is sent to Supabase, which runs our authentication, database, and file storage. It is used for two things: sending you the sign-in link that gets you into the app, and identifying which account is yours.

That is all. We do not send marketing email, and we do not give your address to anyone who does.

When you sign in with your email address, the sign-in screen also runs Cloudflare Turnstile, a check that a person rather than an automated script is signing in. It is Cloudflare’s own code, loaded from Cloudflare into the app, and like any request over the internet it reaches Cloudflare from your IP address. Your email address is not sent to Cloudflare: the check hands back a one-time pass, and that pass goes to Supabase with your sign-in request. Cloudflare handles what it receives under its own privacy terms — cloudflare.com/privacypolicy.

2.2 Your food photos, stored

When you scan a meal, the photo is uploaded to a private storage bucket at Supabase. Private means exactly that: the files are not served at a public address, and there is no URL anyone can guess or share.

When the app needs to show you one of your own photos, our server creates a temporary signed link for it. Those links expire after six hours. The database stores only the file’s internal path, never a link.

2.3 Your food photos, analysed

To analyse a photo, we send it to an AI company in the United States. Our server hands the photo to a Google Gemini model, and that model returns the analysis that becomes your verdict. The photo goes straight to Google, so Google receives it. Your data is never used to train AI models. There is no way to use SOKEN’s scanning without this happening — it is how the product works, and you should know it before you photograph your dinner. From version 1.0.1 of the app, SOKEN asks for your permission before it sends your first photo, description or report.

Which AI company that is can change. We choose the model that reads food most accurately, and when a better one appears we move to it. Today that is Google, whose Gemini models we reach through Google’s own Gemini API. If we ever send photos to a different company, we will update this policy first, not afterwards.

What is sent is the photo and the analysis instructions. If you have corrected earlier scans with the pencil, a short list of those corrections is sent with the photo as well: for each one, what SOKEN read and what you said it was, the five most recent from the last 90 days. It lets the model recognise your foods better. The list is kept on your phone and with your account (2.12), so it is not lost when you change phones. Your email address, your account identifier, your name, your profile photo, and your profile answers (sections 1 and 2.7) are not sent. What arrives at the other end is a picture of food and the words you used for your own foods, with no idea whose they are.

SOKEN reviews corrections, without names, to improve how it recognises food. SOKEN’s team also reviews scans and their results (the photo, the foods read, the verdict, and the Body Scan result), without names, to check and improve accuracy.

If you describe a meal in words instead of photographing it, typed or spoken (2.13), that text is sent the same way, for the same reason. When you scan a barcode, the product details found for it (2.5) can be sent the same way, so the model can score the product. When you open healthier swaps for a scan, the food’s name and its result can be sent the same way too, so the model can suggest and score alternatives; your allergies and diet are not sent, because the app filters the suggestions on your phone. A body-scan report you ask SOKEN to read also goes the same way — see 2.10.

Google handles what it receives under its own privacy terms — policies.google.com/privacy and the Gemini API terms, ai.google.dev/gemini-api/terms. We do not control how long Google keeps an API request.

2.4 The result of the analysis

The analysis itself is saved to our database so your history survives closing the app. Each saved scan holds: the verdict, the score, the points that made up that score, the organ signals and disqualifiers the analysis found, the processing band, the name the model gave the food, a short summary, and the time you scanned it.

Every one of those records is tagged with your account. Every query the app makes filters on it, and the database has its own rules on top that stop one account reading another’s rows. You cannot see anyone else’s scans and they cannot see yours.

2.5 Barcode lookups

If you scan a barcode, our server looks that number up in two public food databases, Open Food Facts and the USDA FoodData Central database, to get the product’s name and brand. Only the barcode number is sent. Nothing that identifies you goes with it, and the request comes from our server rather than your phone.

2.6 Your subscription status

Subscriptions are handled through RevenueCat, which tells the app whether your subscription is active. The payment itself is taken by Apple or Google through your app store account, under their terms.

SOKEN never sees your card details. We do not receive your card number, your billing address, or anything else about how you paid. We only learn whether you are subscribed.

2.7 Your profile answers

When you finish onboarding, and again each time you edit your profile, your answers are saved onto your account at Supabase. That is:

• Your name and username
• Your date of birth
• Your gender
• Your country
• Whether you prefer metric or imperial units
• Your height, your weight, and your goal weight
• Your answers about your body: a body fat figure you know or chose to take from Apple Health, or the estimate made from the body shape you picked and the questions after it; and where you said you carry weight
• How many days a week you said you strength train
• The goals you picked, including any goal you typed yourself, and the goal you are working toward with its target
• Whether you told us you have a food allergy, and any foods you said you avoid
• Your answers to the other onboarding questions — for example what you find hardest, how confident you feel shopping for food, and how you rate your nutrition knowledge — including any answer you typed in yourself, and the result of the example scan during setup
• Which parts of the in-app tour you have finished, so it is not shown to you again

On iPhone, some of these can be filled in from Apple Health during setup instead of being typed: see 2.9.

Your profile photo is not included — see section 1.

It is stored for one reason: so that signing in on a new phone gives you your profile back instead of asking you every question again. It is not used to advertise to you, it is not sold, it is not shared with anyone outside the companies named in section 4, and it is not sent to the AI companies with your food photos.

Because it lives on the account, deleting your account deletes it too. Logging out clears it from the phone but leaves it on the account, which is exactly what lets it come back when you sign in again.

2.8 How you use the app

The app records usage events and sends them to PostHog, an analytics service, hosted in the United States. An event is a short record that something happened: a screen was opened, a scan started or finished, a meal was saved, a reminder was allowed, a subscription step was reached.

What an event carries:

• the name of the event and the time it happened;
• a few short details about it, such as the kind of scan (photo, barcode or typed), whether a meal was described by voice or with the keyboard, how many seconds you spoke and how many characters the text has (never the words themselves), how long it took, and the result’s category (for example “Healthy” or “Balanced”) and processing level, and how many years your SOKEN Age sits from your actual age when you open it, and whether you turned sleep estimates from your phone on or off (never the sleep times themselves);
• whether the phone is an iPhone or an Android phone;
• an identifier: your account’s internal ID once you are signed in, and before that a random ID created on your phone.

What an event never carries: your email address, your name, your photos, the names of the foods you log, the nights your phone estimates, or anything you type. The app removes those kinds of fields before anything is sent. Like any request over the internet, an event reaches PostHog from your IP address.

On iPhone and Android, the app also sends PostHog a recording of how its screens are used: where you tap and scroll, and which screen is open. The text and images on screen, including anything you type and your meal photos, are hidden on your phone before a recording is sent.

We use these events to understand how the app is used and to fix what does not work. We do not use them for advertising, and we do not sell or share them.

2.9 Apple Health and Health Connect

If you connect it, SOKEN reads health data from Apple Health on an iPhone, or from Health Connect on an Android phone. It only reads. It asks your phone for permission to read and for nothing else, and it never writes anything to Apple Health or Health Connect. You choose which of these types to share on your phone’s own permission screen and can change that there at any time; Disconnect in Profile › Connected sources stops SOKEN reading.

What SOKEN asks to read:

• Apple Health: sleep; steps; active and resting energy; walking and running distance; exercise minutes; workouts; heart rate, resting heart rate and heart rate variability; cardio fitness (VO2 max); respiratory rate; blood oxygen; sleeping wrist temperature; weight, body fat percentage and lean body mass; walking speed; and your height, date of birth and sex.
• Health Connect: sleep; steps; active calories burned; distance; exercise sessions; heart rate, resting heart rate and heart rate variability; VO2 max; respiratory rate; oxygen saturation; skin temperature; weight, body fat and lean body mass.

It is used on your phone: to show your sleep, activity, heart and body readings beside your meals, to work out SOKEN’s sleep and activity scores, to draw your body figure and its projection, and, while you set up the app on an iPhone, to show a short summary of what Apple Health holds and to fill in answers you would otherwise type.

The readings themselves do not leave your phone. SOKEN sends no Health or Health Connect data to our server, to the AI companies, or to anyone else, with these exceptions, both kept with your account and never sent to the AI companies:

• SOKEN can fill in your date of birth, your sex and your height from Apple Health, and offer a body fat reading from Apple Health as your answer to the body fat question. Once filled in, these are profile answers like any other and are saved to your account with the rest (2.7); the body fat answer records that it came from Apple Health. A weight read from Apple Health during setup is logged as a weigh-in, and kept with your account like the weights you log by hand (2.12).
• The record SOKEN keeps each day of the projection of your body (2.12) stores the figures it was worked out from — among them your recent average sleep, steps, heart rate and heart rate variability — and, when the projected day comes, the weight and body fat measured then. Some of those figures come from Apple Health or Health Connect. The record is kept with your account so your projection history survives a new phone. Which sources you connected is kept with it; the readings they hold are not.

Your Health data is never used for advertising or marketing, never sold, and never shared with anyone beyond what this section describes. If you use Settings › Export test data, the file it makes includes your Health readings; the app hands it to your phone’s share sheet, and where it goes from there is your choice. It is not sent to us.

2.10 Body-scan reports SOKEN reads for you

In Profile › Add a body scan you can photograph a body composition report — from a DEXA scan, a 3D scan or a smart scale, for example — or choose a photo or a PDF of one, and SOKEN reads the numbers off it for you. To do that, the photo or file goes to our server, and from there to Google, by the same route as food photos (2.3). Only the report and the reading instructions are sent: not your email address, your account identifier or your profile answers. But whatever is printed on the report goes with it, and reports often show your name, your date of birth or a clinic’s patient number — cover or crop those first if you would rather not send them.

Our server does not keep the photo or the file. It holds it only while the model reads it, and neither the report nor the numbers read from it are written to our database or our logs. The numbers come back to your phone and fill in the form; nothing is saved until you press Save, and then the scan is saved on your phone and with your account (2.12), without the photo or file. How long Google keeps the request is governed by their own policies, as with food photos.

2.11 Suggestions you post

Profile › Request a feature lets you suggest a feature and vote for other people’s suggestions. A suggestion’s title and details, and your votes, are saved to our database at Supabase, tied to your account. We read a new suggestion first; if we approve it, it appears on the board for other SOKEN users with its vote count, but without your name, your email address or anything else that says it was yours. You can withdraw a suggestion of yours at any time, and deleting your account deletes your suggestions and your votes.

2.12 What you keep in the app

Beyond your profile answers (2.7), SOKEN keeps the rest of what you set up and record in the app with your account at Supabase, tied to your account like your scans. That is:

• Your short-term goal (with the weight you started it at) and your long-term goal
• What you log by hand: sleep, workouts, steps, weight and waist
• The body scans you add, without the report itself (2.10)
• Your saved meals: their names and the result of their analysis. Their photos stay on your phone for now
• The daily record of your body’s projection (see 2.9), the tests you pin from it, and your answers to “Was that everything?”
• Your SOKEN Age reading and which parts of the app you have unlocked
• Your meal reminders, the bedtime you entered, your choice of light or dark appearance and the tiles you picked for Home
• Whether you agreed to scans being sent to an AI company, and which of Apple Health or Health Connect you connected (not what they hold)
• Your answers to “Is this your product?” for store barcodes, and the short list of your pencil corrections (2.3)
• Your trial: when it started and how long it is, and whether you said “Not now” to the subscription offer
• The temporary links that let you adjust a meal you scanned in the last day

The app saves each item when it changes, and once more when you log out, and brings them back when you log in, on that phone or any other. It is stored for that reason only: it is not used to advertise to you, not sold, not sent to the AI companies, and not shared with anyone outside the companies named in section 4. Deleting your account erases it.

2.13 Describing a meal by voice

In the “What did you eat?” box, a microphone button lets you say what you ate instead of typing it. The first time, your phone asks for two permissions: Microphone, and Speech Recognition on iPhone. SOKEN uses them for one thing: to turn what you say about a meal into text so it can analyze it. You can change either permission in your phone’s settings at any time; the keyboard keeps working without them.

The microphone listens only while you have tapped it. It stops when you go quiet or tap it again, and it never listens in the background. It listens in your phone’s language. The words appear in the box, and nothing is sent to SOKEN until you tap Analyze; you can edit or delete them first.

Who turns your speech into text. Where your phone can do it on the phone itself, it does, and your speech does not leave the phone. Where it cannot, your phone uses Apple’s speech service on an iPhone or Google’s on an Android phone, and your speech audio is sent to Apple or Google to be turned into text. That is between you and them, under their own terms: apple.com/legal/privacy and policies.google.com/privacy.

SOKEN never receives or stores your audio. Only the resulting words reach our server, when you tap Analyze, and they are handled exactly like a meal you typed: sent to Google for analysis (2.3) and, if you save the meal, kept with your account. The usage event for a voice meal (2.8) records only that voice was used rather than the keyboard, how many seconds you spoke and how many characters the text has, never the words.

2.14 Estimating your sleep with your phone

If you do not wear a sleep tracker, you can turn on “Track sleep with this phone” on the Sleep screen, or the “This phone” switch in Settings › Connected Sources. It is off until you turn it on. When you do, your phone asks for permission: Motion & Fitness on an iPhone, Physical activity on an Android phone. SOKEN uses it for one thing: to estimate your night (your time in bed on an iPhone, your sleep on an Android phone), so the app can show a night you did not type. The nights stay on your phone; the one figure that can reflect them elsewhere is explained under “How the estimates are used”.

What is read, and where.

• iPhone. When you open the app, SOKEN reads the motion history your iPhone keeps, about the last seven days of when it was still, walking, running, driving or cycling, with times. SOKEN works out on the phone the overnight stretch when the phone lay still, and that gives an estimated bedtime and wake time. A phone cannot tell lying awake from sleeping, so the app shows this as “Time in bed”, not sleep. If you have connected Apple Health (2.9) and your iPhone recorded “In Bed” time, SOKEN uses that as the estimate instead.
• Android. Google Play services has a Sleep API. Google works out your sleep on the phone, from its motion, light and how you use it, and hands SOKEN a daily segment with a start and an end time.

What SOKEN keeps. Only the resulting nights: the bedtime, the wake time and the minutes. They are stored in the app’s own storage on your phone. They are not sent to our server, not saved with your account (so they do not come back on a new phone) and not sent to analytics. The motion history itself is never stored by SOKEN and never sent anywhere. SOKEN does not use the microphone for this, and nothing in SOKEN runs overnight.

How the estimates are used. Each one is shown as “Estimated by your phone” and is not scored. It counts the way a night you type does: it feeds your sleep ring, your sleep goal and your body forecast, which are all worked out on your phone. Because it counts like a typed night, it can feed your recent average sleep, and that average is one of the figures the daily record of your body’s projection keeps with your account (2.9, 2.12). The nights themselves are not. An estimate can be wrong; it is SOKEN presenting a guess from your phone, not a measurement.

Who handles your motion. Your phone’s own system does: Core Motion on an iPhone, Google Play services on an Android phone. SOKEN sends nothing to Apple or Google for this. Their software on your phone is under their own terms: apple.com/legal/privacy and policies.google.com/privacy.

Turning it off. Turn the “This phone” switch off in Settings › Connected Sources: SOKEN stops reading and deletes the estimated nights it stored. You can also change the permission in your phone’s settings at any time, which stops SOKEN reading your phone’s motion; to delete the estimates already stored, turn the switch off in the app. Logging out, deleting your account and deleting the app remove them too.

3. What SOKEN does not collect

This section is as important as the last one, and it is unusual enough to be worth spelling out.

• No crash reporting. The app contains no crash-reporting service. The one that came with the project template was replaced with an empty stub whose every function does nothing. When SOKEN crashes, we do not find out.
• No advertising, and no tracking. There are no advertising SDKs. We do not read your advertising identifier (IDFA on iOS, Advertising ID on Android), we do not build a profile of you, and we do not track you across other apps or websites. SOKEN has nothing to ask you for tracking permission about.
• No location. The app does not ask for your location and does not collect it.
• No contacts, and no other apps. We do not read your address book and we have no way of knowing what else is installed on your phone.
• No audio. If you describe a meal by voice, SOKEN receives only the resulting words, never a recording. The microphone is not used for anything else, and never in the background (2.13).
• No motion history, and no sleep times. If you turn on sleep estimates from your phone, your phone works them out and SOKEN keeps only the resulting nights, on your phone. We receive neither the motion history nor the nights (only the recent average sleep your body forecast keeps can reflect them), and nothing in SOKEN runs overnight (2.14).
• No push tokens. Reminders are scheduled by your own phone, locally. There is no push server, and no token is registered with one.

4. Who else sees your information

The complete list of companies that receive anything, and what each one gets:

Nobody else receives your information. We do not sell it, rent it, trade it, or hand it to advertisers, brokers, or insurers. There is no arrangement under which anyone pays us for it.

We would disclose information if the law genuinely required it — a valid court order, for example — or if it were necessary to protect someone’s safety. If SOKEN were ever sold or transferred to someone else, your information could move with it; you would be told before that happened, and this policy would keep applying until you were given a new one.

5. How long we keep it

6. Deleting your account

Email info@sokenhealth.com from the address on your account and ask us to delete it. We will do it within 30 days and confirm when it is done. We will not ask you to justify the request.

Deleting your account removes:

• Your account record, including your email address
• Every scan you have ever saved. This is enforced by the database itself: the scan records are tied to your account with a rule that deletes them along with it, so it is not a cleanup step anyone can forget
• The photo files those scans point to
• Your suggestions and votes (2.11), by the same database rule

There is also a Delete account option inside the app, and it does the whole job: everything in the list above, plus everything held on your phone — your profile, your settings, your on-device history — and what you keep in the app (2.12) — and it signs you out. If any part of it fails, the app tells you so and stops: you stay signed in, nothing on your phone is cleared, and you can try again. Email us as above if you would rather we did it, or if the button will not work for you.

Two honest caveats. First, if a temporary signed link to one of your photos was already issued before you deleted your account, it can still work until it expires — at most six hours. Second, our database provider keeps routine backups, so a deleted record can survive inside a backup until that backup rotates out of existence. In neither case is the data reachable through the app or used for anything.

7. How we protect it

• Photos live in a private storage bucket. Nothing is served publicly, and the database never stores a link — only an internal path.
• When a photo does need to be shown, it is shown through a signed link that expires after six hours.
• Every scan record carries the account that owns it. Every query filters on that, and the database enforces per-account rules of its own as a second layer.
• Everything in transit is encrypted with TLS — between the app and our server, and between our server and every company in section 4.
• The key that lets us call the AI model lives on the server only. It has never been in the app, where anyone could pull it out.

No system is perfectly secure, and it would be dishonest to claim otherwise. What we can say is that we have kept the amount of data worth stealing as small as the product allows.

If it goes wrong anyway

If your information is exposed to someone who should not have had it, we will tell you. Not eventually, and not buried in a release note — by email to the address on your account, without undue delay once we know what happened.

The notice will say, in plain words:

• what happened, and when we found out;
• which of your information was involved — your email, your photos, your scan results, or some combination;
• what we have done about it, and what we are still doing;
• anything you should do yourself, and who to reach at SOKEN for more.

We will also notify the authorities we are required to notify. In the United States, SOKEN handles health information and is not a HIPAA-covered entity, which puts us under the Federal Trade Commission’s Health Breach Notification Rule; we will follow it, including its deadlines and, where the rule requires it, notice to the media. Under the GDPR we will notify the relevant supervisory authority within 72 hours of becoming aware of a breach that requires it. State breach-notification laws apply on top of both, and we will follow those too.

Nothing in this section is a promise that a breach cannot happen. It is a promise about what we do on the day one does.

8. Where your information is processed

SOKEN is run from the United States, and every company in section 4 processes data in the United States, except that we do not control where Apple’s or Google’s speech service handles speech audio (2.13). If you use SOKEN from the UK, the EEA, or Switzerland, your information is transferred there.

The United States has not been found to offer the same level of data protection as the EEA in general terms. Where our providers offer them, we rely on the European Commission’s Standard Contractual Clauses (and the UK Addendum) as the safeguard for those transfers, alongside the technical measures in section 7.

9. Your rights in the UK and the EEA (GDPR)

If the GDPR applies to you, you have the right to:

• Access the personal data we hold about you, and get a copy of it
• Rectification — have anything inaccurate corrected
• Erasure — have it deleted (see section 6)
• Restriction — have us pause using it while a dispute is sorted out
• Portability — receive your data in a machine-readable format, or have it sent to another service
• Object to processing we carry out on the basis of legitimate interests
• Withdraw consent at any time, where consent is what we rely on. Withdrawing it does not undo what was lawful before
• Complain to a supervisory authority in the country where you live or work. In the UK that is the Information Commissioner’s Office; in the EEA it is your national data protection authority. You do not have to come to us first, though we would like the chance to fix it

To exercise any of these, email info@sokenhealth.com. We will respond within one month. There is no charge.

Legal bases

Automated decisions

SOKEN scores food automatically. That score is information about food, not a decision about you: it has no legal effect and nothing similarly significant turns on it. No automated decision-making within the meaning of Article 22 takes place.

10. Your rights in California (CCPA/CPRA)

In the last twelve months we have collected these categories of personal information:

• Identifiers — your email address and your name
• Personal characteristics and health information — your date of birth, gender, height, body answers and goals (section 2.7), some of which may be filled in from Apple Health (section 2.9)
• Content you write — suggestions you post (section 2.11)
• Visual information — your food photos, and any body-scan report you ask SOKEN to read (section 2.10)
• Commercial information — whether you have an active subscription
• Inferences — the verdicts and scores produced from your scans
• Internet or other electronic network activity — usage events from the app, described in section 2.8

Each was collected for the purposes described in section 2, from you, and disclosed only to the service providers listed in section 4.

We do not sell personal information, and we do not share it for cross-context behavioural advertising. We have not done either in the last twelve months, and we have no plan to. There is no “Do Not Sell or Share My Personal Information” link on this site because there is nothing to opt out of. A Global Privacy Control signal has nothing to act on here for the same reason.

You have the right to:

• Know what we have collected about you, where it came from, why, and who received it
• Get a copy of it
• Have it corrected
• Have it deleted
• Limit our use of sensitive personal information. Food and health information can count as sensitive. We use it only to provide the app you asked for, which is a permitted purpose; we do not use it to infer characteristics about you for anything else
• Not be treated differently for exercising any of these rights. The app works the same either way

Email info@sokenhealth.com to make a request. We will verify it by replying to the email address on the account, since that is the only way we have to reach you. You may use an authorised agent; we may ask for proof of their authority.

11. Cookies

This website sets no advertising cookies and runs no analytics scripts; the usage events described in section 2 come from the app, not from this site. If you sign in on the website, a cookie strictly necessary to keep you signed in may be set. That is the only kind used.

12. SOKEN is for adults only

SOKEN is not for anyone under 18. You must be 18 or older to create an account or use the app.

We do not knowingly collect information from anyone under 18. If we learn that we have, we will delete the account and everything attached to it. If you believe a child has given us information, email info@sokenhealth.com and we will act on it.

13. SOKEN is not medical advice

SOKEN presents published research. It is not a medical device, it does not diagnose or treat anything, and it is not a substitute for a qualified healthcare professional. Its analysis is produced by an AI model and can be wrong.

The full disclaimer is at the top of the Terms of Service, and it is the most important thing on either page. Please read it.

14. Changes to this policy

If this policy changes, the “Last updated” date at the top changes with it, and the new version appears here.

If a change is significant — a new company receiving your data, a new category of information collected, or a new purpose — we will tell you in the app before it takes effect, and give you the chance to delete your account first. We will not quietly widen what we collect and date-stamp it.

15. Contact

SOKEN LLC
info@sokenhealth.com