Privacy Policy

Food Moments estimates the nutritional value of your meals from photos and your own words. It was built so that your data stays yours: no advertising, no tracking, and no name — your account is nothing more than your email address. Everything you record is stored in that account, on our own servers in the European Union, with the recent days kept on your iPhone or iPad; that is what lets a new device bring everything back, and it comes with two buttons that keep the data yours in practice: one that downloads everything, one that deletes everything. What is sent where is described precisely below — and all of it stays in the European Union; the AI analysis and dictation each begin only after you have agreed in the app, and we look at your meals themselves only if you invite us to (§11).

1. Who is responsible

The data controller is Smart Backoffice Solutions B.V., Saal van Zwanenbergweg 11, 5026 RM Tilburg, Netherlands, registered with the Dutch Chamber of Commerce under number 90141482. Contact: info@smart-backoffice.nl.

2. What the app processes, and where it stays

Stored in your account, on our servers in the European Union:

• Your meal photos, notes, corrections and edit history
• The nutritional estimates, the model's own notes on how it reached them, and your timeline
• Your nutrition profile (birth year, sex, weight, height, activity, calorie goal)
• Your daily targets, day by day — for days based on Apple Health, including the burned-energy figure the target was computed from (see below)
• Your timeline background photos, if you picked your own
• Which of your meal photos and scanned products you have marked as favorites, so they come first when you use one again
• Your app settings: the appearance, when your day starts, whether your activity data comes from Apple Health, and how you like to eat — the protein, fibre, fruit and vegetables, free sugars, fat and salt levels you chose for your daily targets
• Sizes you have told the app about, in your own words — how wide your dinner plate is, what a slice of your bread weighs — kept so the app does not have to guess them again
• The size measurement of each photo your iPhone or iPad could measure (see below), together with technical details of how it was made — how steadily the device was tracking, which surface it found and how sure it was; and, since 24 September 2026, for a few hundred points inside the picture, how far from the camera each one was — so the size of what you photographed can be read later even when it was in your hand rather than on a table. Nothing outside the picture is kept
• A record of each analysis and dictation request for fair use: when it was made, what kind it was, which AI model answered, how long it took, how much data and computing it used, which meal it belonged to and whether it succeeded, and if not, a short code for why (such as "timed out") — never its content (§3)
• Whether you have switched on Help improve Food Moments, and since when (§11), and whether you have switched off occasional questions by email (§12)
• Your subscription, as Apple reports it (see below)
• The day you last used the app with your account, so that an account nobody uses any more can be deleted (§6)

This storage runs on Microsoft Azure in West Europe (§4). Your iPhone or iPad keeps roughly the last two weeks ready to show and fetches older days when you scroll back to them; signing in on a new device restores everything. Deleting the app therefore no longer deletes your data — deleting your account does, completely and in the app (§6, §8).

Your account is deliberately minimal: your email address, and nothing else — no name, no password. You sign in with a one-time six-digit code we email you; each iPhone or iPad you sign in on gets its own session, and signing out ends it. Legal basis for the account and for storing your meal data in it: the performance of our contract with you (Art. 6(1)(b) GDPR) — this storage is the service — and, because meals can say something about your health, your explicit consent, which you give when you create the account (Art. 9(2)(a) GDPR). Deleting the account withdraws it.

Apple Health, if you enable "Take activity data from Apple Health": the app reads your resting and active energy on this iPhone or iPad to set the day's energy target. The readings stay in Apple Health — they are never sent to the AI model, never used for advertising, and the app never writes to Health. What your account stores is the result: each day's energy target, together with the burned-energy total it was computed from, kept with your daily targets so a past day keeps its true target on a new device.

Your subscription. The subscription is bought and paid for through Apple (§4). So that the app knows whether analysis is available to you, we receive from Apple — through the app, and directly from Apple's servers when a subscription renews, ends or is refunded — and store with your account: the subscription's transaction numbers, the product, whether it was a real or a test purchase, when the current period ends, when Apple signed the information, whether it was refunded or revoked, any grace period for a failed payment, whether the period is the free trial, and when we last updated it. We receive no payment details — no card, no bank account, no billing address — and no Apple ID. Legal basis: the performance of our contract with you (Art. 6(1)(b) GDPR). This information is deleted with your account; Apple keeps its own record of the purchase under its own terms.

When you last used the app. When the app talks to our server while you are signed in, the server notes the day — at most once a day — on your account. It records nothing about what you did. It is what lets us delete an account nobody has used for 18 months and that has no running subscription (§6) rather than keep it forever. Legal basis: our legitimate interest in not keeping data longer than it is used (Art. 6(1)(f) GDPR).

We also run a gateway that every analysis and dictation request passes through, described in §3. It keeps none of your meal content — photos, notes and recordings travel through it and are gone as soon as the answer comes back. What it does keep is a technical identifier for your device and a record of each request for fair use, both explained in §3.

Sent for a meal analysis (only with your consent, see §3):

• The photos of the meal being analyzed
• Your note and any later corrections for that meal
• Text of nutrition labels and barcode product information found in the photos
• Your meals of the last two weeks in short form — at most 30, each with its time, title and dishes with their portions and calories — so portions stay consistent across days; and the date, time and language of the meal being analyzed
• Once, for each of your meals of the last two weeks that was analyzed before 19 September 2026: its title and dishes with their portions, sugars and weight, in short form, so the app can add free sugars and fruit and vegetables without analyzing the meal again
• For a meal that is only scanned products: their names, pack sizes and the product database's values per 100 g, a moment after the scan, so the app can add the vitamins and minerals product databases rarely list — without a photo
• Once, after the update of 29 September 2026: each meal on your iPhone or iPad — about the last two weeks, and older days once you scroll back to them — is analyzed again as described here, so that it has vitamins and minerals too. Your device hands these requests to our gateway, which runs them while the app is closed — using the photos already stored in your account — and keeps each answer only until your device collects it, then deletes it; deleting your account deletes waiting requests and answers with it
• The sizes you have told the app about (above), so portions are measured against your own plates rather than average ones
• A size measurement of each photo, where your iPhone or iPad could make one: how many centimetres across the picture covers at the surface the food is resting on, how far away and at what angle the camera was held, and the size of the shapes on that surface. Your device works this out by itself while you are framing the shot, from the small movements of your hand — or, if you choose, the little movement around your food the viewfinder invites — and, on models that have one, the depth sensor. No extra pictures are taken, and nothing outside the picture is mapped or kept; the depth readings the app keeps for points inside it are listed under stored data above. Whenever it found a surface, the app also sends a copy of that photo with a centimetre grid drawn on the surface, together with how reliable that measurement is, so the model can read sizes off it or set it aside. Photos you pick from your library carry no measurement; a meal someone shares with you keeps the measurement their device made

Sent when you dictate a note (only with your consent, see §3):

• The audio recording of your dictation, to be transcribed into text, together with the last few sentences of the note written so far — typed or dictated — so that words and names stay consistent. Like a meal analysis, it is processed on our own Azure deployment in the European Union (§3)

Kept only on your iPhone or iPad, while something is unfinished:

• A meal you have started but not yet analyzed — its photos, scanned barcodes and typed note — so that the capture screen opens again where you left off if the app is closed, crashes or is ended by the system; the same goes for a correction you have started on a meal but not yet applied. It stays until you press Analyze or Apply, when it becomes your meal or your correction and is stored in your account as described above, or Cancel, when it is deleted. It is also deleted when you log out or delete your account, and nothing in it is sent for analysis before you press Analyze or Apply
• The recording of a dictation, from the moment it is complete — when you let go of the mic button, or about every minute during a long note — until its text has arrived, normally a second or two, after which it is deleted. If it cannot be sent yet, because there is no network or the service is unavailable, it waits on your device and is sent automatically when the connection returns or you open the app again, and your note fills itself in. A waiting recording is also deleted when you cancel the meal or correction it belongs to, log out or delete your account, and it is never sent without your dictation consent

Both are kept in the app's private storage on your iPhone or iPad, protected by the system's encryption and left out of device backups; neither is ever uploaded to your account.

Sent when you scan a barcode, or one is found in a photo:

• The barcode number, looked up in the public Open Food Facts database (§4). The product's name, pack size, nutrition values and photograph come back to your iPhone or iPad and are kept there; the photograph is never uploaded to us, never sent for analysis and never travels in a meal you share — your device fetches its own copy from Open Food Facts. Legal basis: our legitimate interest in basing the estimate on the product's own printed values (Art. 6(1)(f) GDPR); the lookup only happens once you have agreed to meal analysis

Sent automatically if the app crashes, freezes or uses too much processor or storage:

• A technical diagnostic report from Apple's own on-device crash detection (MetricKit) — what kind of failure happened, which part of the app was involved, your iPhone or iPad model and iOS or iPadOS version, and the app version, so we can find and fix the problem. It carries none of your photos, notes, or anything you typed, and it is stored with this device's installation rather than with your account. Legal basis: our legitimate interest in an app that works (Art. 6(1)(f) GDPR).

Looked at to make the app work better — technical details, never what you ate:

• To find out where the app fails and whether a change fixed it, we look at technical details of how it worked, which are already kept with your meals or on our gateway: for each photo, whether and how well your iPhone or iPad could measure it (the measurement's quality, the reason it could not measure, the distance and angle, how steadily the device was tracking, and whether the surfaces it found agreed with each other); where a photo came from — the camera, your library, or an earlier meal; for each analysis, which AI model answered, how long it took, how many rounds it needed, how much data it carried and whether it succeeded, and if not, why; and the crash reports above. We look at them without your photos, notes, corrections, meal names or nutritional values, and report on them only as totals that do not point to you ("the camera could measure 44 % of photos"). Nothing new is collected for this: these details exist anyway, for the purposes described in this section. Legal basis: our legitimate interest in an app that works and gets better (Art. 6(1)(f) GDPR). You can object at any time by writing to the address in §1; we then leave your account out.

Shared by you, from your iPhone or iPad straight to another (nothing passes through us):

• When you share a meal with someone who ate it with you, the meal — its photos and their size measurements, your note, the estimate, its history and the model's notes — goes from your device directly to the recipient you choose, over AirDrop, Messages or whichever app you pick. It does not pass through our servers: we never see it and keep no copy of it. A meal someone shares with you appears in your timeline and is then stored in your account like a meal you photographed yourself.

3. Meal analysis by AI — your consent

To compute an estimate, the app sends the data listed above to an AI model (OpenAI GPT) running on Microsoft Azure servers in the European Union, on our own deployment. What the app sends is used to compute your nutritional estimate — and, only if you have switched on Help improve Food Moments, to improve the app as §11 describes. It is not used to train AI models. Your account carries no name, and the AI model sees nothing of it: what reaches the model is the meal, not who you are.

Every request first passes through our own gateway. This is a small server we operate on Microsoft Azure in the European Union. It exists so that the credentials for the AI service are not inside the app, where anyone could extract them from the downloaded file and run up costs on our account. The gateway checks that a request really comes from an unmodified copy of Food Moments on a genuine Apple device — using Apple's App Attest — and that it belongs to a signed-in account, so that the fair-use limits are counted per account rather than per device, and then passes it on. For an analysis it inserts your photos from your account's storage into the request; it does not otherwise read what you send, and keeps no copy of it. For fair use and cost control it records, per account, a line for each request: when, what kind, which model, how long it took, how much data and computing it used, which meal it concerned and whether it succeeded — and if it failed, a short code for why, such as "timed out", never an error message or content. Your photos, notes and recordings never appear in these records or in its logs, and the records are deleted with your account.

For that check your iPhone or iPad creates a cryptographic key that never leaves the device, and the gateway stores the key's identifier together with a counter that stops a captured request from being replayed. The identifier is a random value created by this installation of the app: it contains no name, no email address and no device serial number. While you are signed in, our records link it to your account's session, so we treat it as personal data. It is created the first time the app talks to our server — when you sign in — and deleting the app makes it useless. Legal basis for this one technical record: our legitimate interest in protecting the service against abuse (Art. 6(1)(f) GDPR).

The app asks for your explicit consent before the first analysis (legal basis: Art. 6(1)(a) GDPR, and Art. 9(2)(a) GDPR because meals can say something about your health). You can withdraw consent at any time in Settings → Privacy; analysis then stays off until you agree again, and the rest of the app keeps working.

Dictation has its own consent. A spoken note is turned into text by speech models on our own Microsoft Azure deployments in the European Union — Azure Speech in North Europe (Ireland), and, for app versions before 1.2 only, Azure OpenAI in Sweden Central — so a dictation recording is processed in the European Union too. (Until 1 October 2026 dictation ran on a worldwide deployment and a recording could be processed outside the EU; that is no longer the case.) The app asks before your first dictation (Art. 6(1)(a) GDPR as well) and you can withdraw that consent in the same place; dictation then stays off, and a note can always be typed instead.

Meal photos and notes can incidentally reveal things about you — a diet, an allergy, a fasting practice. We minimize this by sending only the meal being analyzed, keeping the results in your own account where only you can reach them, and storing none of it on our gateway.

4. Service providers

• Microsoft Ireland Operations Ltd. (Azure) provides the infrastructure and processes analysis requests and dictation recordings as our processor, under Microsoft's Data Protection Addendum. This covers the AI deployments, the gateway described in §3 — which runs on Azure Functions in West Europe, with its device identifiers and the crash diagnostics from §2 in Azure Table Storage in the same region — and the storage behind your account (§2): your meals, photos and profile live in Azure storage in West Europe, inside the European Union. The emails we send — login codes, export links and the others described in §12 — are sent through Azure Communication Services, configured with its data location in the European Union, from noreply@smart-backoffice.nl. Meal analysis runs in Azure's EU Data Zone, and dictation on Azure Speech in North Europe (Ireland) — app versions before 1.2 on Azure OpenAI in Sweden Central — so photos, notes, corrections and dictation recordings are processed in the European Union. Microsoft's abuse monitoring checks requests automatically at the time of processing without storing them; only requests flagged as potentially abusive may be stored temporarily for review under Microsoft's standard published procedure — for EU deployments stored and reviewed within the EU — and are deleted afterwards. Microsoft does not use your data to train models.
• Open Food Facts (a French non-profit) receives only the digits of a scanned barcode to return public product information, and your iPhone or iPad then fetches that product's photograph from them. As with any internet request, their servers technically see your IP address. Their product data is published under the Open Database License and their photographs under Creative Commons Attribution-ShareAlike 3.0; the app credits their contributors where it shows them.
• Apple distributes the app and sells the subscription: payment, renewal, cancellation and refunds are Apple's, as an independent controller under its own terms. Apple tells us the subscription details listed in §2, so that the app knows whether analysis is available. When you subscribe in the app, the purchase carries your account's random identifier, so that Apple's later messages about it can be matched to your account; it contains no name and no email address, and Apple learns nothing about your meals. Label reading and barcode detection run entirely on your iPhone or iPad using Apple's on-device frameworks — no data leaves the device for these.

We share no data with anyone else. We sell no data. There are no analytics or advertising SDKs in the app. This policy covers the app; the website smart-backoffice.nl has its own privacy statement, and uses Google Analytics only after you accept its cookie banner.

5. International transfers

Meal analysis is pinned to Azure's EU Data Zone and dictation to Azure regions in the European Union (North Europe and Sweden Central); both are processed in the European Union. The gateway they pass through (§3), the storage behind your account (§2) and the service that sends our emails (§4) run in the European Union as well, so none of them adds a transfer: nothing the app sends leaves the EU. (Until 1 October 2026 a dictation recording could be processed outside the EEA under Microsoft's standard contractual clauses; dictation has since moved to the EU.)

Where Microsoft as a global company could in exceptional cases process support or telemetry data outside the EEA, Microsoft's EU Data Boundary commitments and the same standard contractual clauses apply as safeguards.

6. Retention

Your account's data is kept until you delete it — that is the point of an account. A single meal is deleted by swiping it away, on our servers as well as on the device; Settings → Account → Delete account erases everything we hold at once — meals, photos, profile, sessions and any export file still waiting. Deleting the app no longer deletes anything: sign in again and everything is back; delete the account when you want it gone.

An account nobody uses is not kept forever. If an account has not been used for 18 months — the app not opened with it, nothing synced — we delete it, with everything in it. An account with a running subscription — in its free trial, paid, or in a grace period after a failed payment — is never deleted for not being used. 30 days before, we email its address to say so, with the way to download everything first; opening the app once with the account is enough to keep it. The end of a subscription deletes nothing by itself: you can still look at your meals, download them and come back.

Your subscription details (§2) are kept with your account and deleted with it — also when it is deleted for not being used. A subscription itself runs on at Apple until you cancel it in your Apple account.

Everything around the account is short-lived. A login code works once and expires after about ten minutes. The zip made by Download all my data is deleted from our server a few days after it was made (its download link stops working after 24 hours), and like any deleted file it then stays recoverable in our backup for up to 35 days. Nothing you send for an analysis or a dictation is stored on our gateway — it is forwarded and then gone — and Microsoft's transient retention is described in §4.

On your iPhone or iPad, an unfinished meal or correction, and a dictation recording still waiting for its text, are kept only as long as §2 describes: until you finish or cancel it, or until its text has arrived — and never past logging out or deleting your account.

The device identifier described in §3 is kept because it is what a request is checked against; it is not yet deleted automatically when an installation stops using the service, so we delete it on request — write to the address in §1 and mention that you want your device registration removed. Its link to your account ends when you sign out or delete the account. It tells us nothing about what you eat.

The fair-use records of §3 — the line per request and the counts per week and month — are kept with your account and deleted with it.

Crash diagnostics (§2) are kept for 90 days and then deleted automatically — long enough to notice and fix a problem, not a permanent record.

Email delivery records. For each email we send, our email service (§4) records the address, the time and whether the email was delivered, bounced or held back by the receiving server. We keep this record for 90 days — so that when a login code does not arrive we can see why — and it is then deleted automatically. It contains no code, link or other content of the email.

Help improve Food Moments (§11) adds no storage of its own: your meals stay in your account. A working copy made for a comparison is deleted when the comparison is done, and in any case within 30 days of you switching the setting off.

We keep backups. Your account is the only complete copy of your meals — your iPhone or iPad keeps only the recent days — so we back it up. Photos and files can be restored to any moment in the last 30 days, and the rest of your account is written to a dated file every night and kept for the same 30 days. A file that has been deleted — a photo, or a nightly file that has aged out — stays recoverable for up to 35 days more before it is gone for good. All of it stays with the rest of your data in the European Union and is used for nothing else. One consequence, plainly: deleting your account erases everything we hold in service immediately, but what sits in those backups disappears as it ages out — photos within about five weeks, the nightly copies of your account within 66 days at the latest — rather than in the same instant.

7. Security

Everything sent leaves your device over encrypted connections (TLS), and on the device your data is protected by the system's built-in encryption and your device passcode. Your account's data also lives on our servers now, so it is protected there rather than by not existing: it is stored on Microsoft Azure in the European Union and encrypted at rest; it can be reached only through the app itself, because every request must prove — via Apple's App Attest (§3) — that it comes from an unmodified copy of Food Moments and must carry a valid session for your account; sessions are per device and end when you sign out; and the server stores session tokens only as hashes, so a stolen copy of our records could not be used to sign in as you. There are no passwords to steal: a login code arrives by email, works once, and dies after minutes.

8. Your rights

Under the GDPR you have the right of access, rectification, erasure, restriction, data portability and objection, and the right to withdraw consent at any time without affecting the lawfulness of processing before the withdrawal. The app is built so that you exercise them directly, without writing to anyone:

• Access: the app shows you your meals, profile and settings, and the download below contains all of it, including what the app does not show, such as the photo measurements, your subscription details and the day you last used the app. For the rest — the fair-use records of §3, crash reports, the device identifier — write to us and we send you a copy.
• Rectification: correct any meal in the app; change your profile in Settings.
• Portability: Settings → Account → Download all my data has the server pack everything — every photo, a set of pages you can browse on any computer, a table a spreadsheet can read, and one data file with everything your account holds, corrections, profile, settings and daily targets included — and email you a download link.
• Erasure: swipe a meal away, or delete everything at once with Settings → Account → Delete account.
• Withdrawing consent: analysis and dictation in Settings → Privacy, Help improve Food Moments with its own switch (§11).
• Objection: to our use of technical details (§2), by writing to us; we then leave your account out. To our occasional questions by email (§12), with the switch in Settings → Privacy.

For anything else, or questions, contact info@smart-backoffice.nl — we answer within one month. You also have the right to lodge a complaint with a supervisory authority; in the Netherlands this is the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl), but you may contact the authority of your own country.

9. Children

Food Moments is for people aged 16 and over. If someone enters a birth year that makes them younger, the account waits: nothing is analyzed and no new meals or photos are added until a parent or guardian has emailed info@smart-backoffice.nl and we have confirmed their consent by email. If the year was entered by mistake, correcting it in Settings opens the account again. We keep that email as the record of the consent while the account exists. A parent or guardian can withdraw the consent by email at any time, and the account then waits again. Changing the year does not end that wait. Exporting and deleting the account always work, and an App Store subscription keeps running until it is cancelled in the Apple account. Without that consent we knowingly process nothing of anyone under 16 beyond what the account holds at that moment. If you believe a child has created an account by giving a wrong year, write to the address in §1 and we will delete it.

10. Changes

If the app's data flows change, this policy is updated before the change ships, with the effective date above.

Every change is published on the support page. Small ones — wording, grammar, a typo, a clarification that does not change what happens to your data — are announced there and nowhere else.

A change with substantial implications for your data is announced in the app as well, before it takes effect. And a genuinely new data flow that processes what you photograph, write or say — the kind analysis and dictation are — needs more than an announcement: it does not start until you have agreed to it. A new technical signal about the app itself, like the crash diagnostics in §2, changes nothing about how your meals or account are handled; it is disclosed rather than gated, the same way the device identifier in §3 already is.

11. Helping improve Food Moments — only if you switch it on

Food Moments gets better by seeing where its estimates go wrong, and the amount on the plate is where they go wrong most. Under Settings → Help improve Food Moments there is a switch that lets us use your meals for exactly that. It is off unless you switch it on.

What you allow when you switch it on. We — the people at Smart Backoffice Solutions B.V. who make Food Moments, and nobody else — may look at the meals in your account: the photos, your notes and corrections, the estimates and their history, and the size measurements that come with the photos. We use them for one purpose: to find out where the app's estimates go wrong and why, and to check whether a change to the app makes them better. To check a change, we may send a meal through the analysis again with the improved instructions, on the same Microsoft Azure deployment in the European Union that analyzes your meals (§4); the answer is compared with the original and never changes the meal in your timeline. Meals can say something about your health — a diet, an allergy, how much you eat — so this needs your explicit consent (Art. 9(2)(a) and Art. 6(1)(a) GDPR). The switch is that consent: its label says what you agree to, switching it on is agreeing, and the app shows the date you did.

What it never allows. Your meals are not used to train AI models, ours or anyone else's. They are not shared with anyone, not sold, not published and not used for advertising. What we learn is kept as general findings and totals ("the first estimate was 15 % off on average") that do not point to you. Nobody will contact you because of it.

Where your meals stay. In your account, in the European Union, as before. When a comparison needs a working copy — a photo next to its old and new estimate — that copy is kept only on our own encrypted computers, for as long as the comparison runs, and deleted afterwards.

Switching it off. You can switch it off in the same place at any time, as easily as you switched it on; your other devices follow within minutes. From then on we no longer look at your meals, and we delete any working copy of them without delay, at the latest within 30 days. Withdrawing does not undo what was done before it (Art. 7(3) GDPR), and general findings that no longer point to you stay. Nothing else in the app changes either way. Deleting your account switches it off too, and signing in with another account starts with it off.

12. Emails from us

We write only to the email address you sign in with, and only for two kinds of reason.

Emails that are part of the service: your login codes, the link to your download, notice 30 days before an account nobody uses any more is deleted (§6), changes to this policy or to the terms that we must tell you about, and the end of the service. Legal basis: the performance of our contract with you (Art. 6(1)(b) GDPR).

Occasional questions. Beyond those, we write rarely — only about something important, or to ask your opinion: what works for you, what does not, what you would like. We send no advertising and no newsletter. Legal basis: our legitimate interest in hearing from the people who use Food Moments (Art. 6(1)(f) GDPR). You can object at any time (Art. 21 GDPR) with Settings → Privacy → Occasional questions by email: switched off, we send you no more questions. It is on unless you switch it off, it follows your account to your other devices, and each such email says in one line at its end where to switch it off. Answering is always up to you.

13. Research with universities

We may work with universities and research institutes on studies or field experiments about nutrition and the app. Your data is used for a study only if you have given your separate, informed consent to that particular study. Before you decide, you are told who carries it out, what it involves, which of your data it would use, for how long, and how to stop. Every study is reviewed by an ethics committee before it begins. Taking part is always voluntary; you can stop at any time, without giving a reason and without any disadvantage, and your consent is recorded separately for each study. If you do not consent, you never take part, and none of your data is used for the study. This is separate from Help improve Food Moments (§11): switching that on does not make you take part in a study, and consenting to a study does not switch it on.