Privacy policy · 12 October 2026

Digestly Privacy Policy

Digestly is a food, symptom, and exposure diary for families. Privacy is the product: your diary belongs to you, stays with you, and is never seen by us or anyone else.

This is the policy the app links to from Settings. It is generated from the same text the developers keep under version control, so the page and the app never disagree. This website has a short section of its own at the end.

What Digestly collects

Nothing about you. Digestly has no user accounts, no tracking, and no third-party SDKs, and nothing you log ever reaches us. The app can send us two things, and only when you choose to: a daily count of how many times each of its features was used, as numbers with nothing attached that could identify you, if you switch that on ("Feature counts, specifically" below; it is off until you say otherwise); and a message you write yourself and send from Settings → Help & feedback ("Feedback you send us, specifically" below).

Digestly makes three kinds of network request, all only at your choice: scanning a barcode looks that barcode up in a public food database, sending the barcode and nothing else ("Barcode scanning, specifically"); if you have opted in, the daily feature counts just mentioned ("Feature counts, specifically"); and, when you tap Send, a feedback message ("Feedback you send us, specifically").

Apple shows developers aggregate, anonymous statistics about their apps in App Store Connect — download counts, crash reports, how many people open the app — collected by Apple only from people who opted in under Settings → Privacy & Security → Analytics & Improvements. We read those numbers. They come from Apple, not from the app, they cannot identify you, and nothing you log is part of them.

Where your data lives

  • Everything you log (profiles, meals, symptoms, exposures, notes, photos, and anything you add to an emergency card) is stored on your device, inside the app's private storage.
  • If you enable iCloud sync (optional, on by default when signed in), your data is also stored in your personal iCloud account using Apple's CloudKit, encrypted in transit and at rest by Apple. We have no access to it. You can turn sync off at any time in Settings.
  • Digestly also remembers a few small things about the app itself rather than about you: which language you chose, whether you turned iCloud sync on, and which of the app's hint bubbles you have already dismissed. These live on your device only. They are never synced, never exported and never sent anywhere, and Settings → Tips → Show tips again clears the last of them.

Photos, specifically

Photos you attach to a symptom — a rash, for example — or to a meal are treated like the rest of your log: on your device, and in your own iCloud if sync is on. They are not stored separately or handled specially, and we never see them.

You can take a photo back off. Open the entry and tap Remove photo, then save. The picture is deleted from the entry along with everything else that save writes, and from your iCloud copy the next time it syncs. You do not have to delete the whole entry to undo an attachment you did not mean to make.

Being straight with you about one detail: iCloud data is encrypted, but unless you have Advanced Data Protection switched on in your iPhone's iCloud settings, the encryption keys are held by Apple rather than only by you. That means Apple could in principle be compelled to hand over iCloud contents, including these photos. This is true of everything in iCloud, not just Digestly — but photos of a child's skin deserve a plain warning rather than a footnote. If that matters to you, either turn on Advanced Data Protection, or turn Digestly's iCloud sync off and keep your log on the device only.

Reading a meal photo, specifically

If you attach a photo to a meal, Digestly can offer to read it and suggest which foods are in it, so there is less for you to type. On iPhones that support it, that reading is done by Apple Intelligence, on your own device.

  • The photo does not leave your iPhone. It is not uploaded, not sent to us, and not sent to Apple's servers. Apple's on-device model has a cloud counterpart that apps can use instead — Private Cloud Compute — and Digestly deliberately does not use it, so there is no version of this feature that sends your picture anywhere.
  • Nothing extra is stored. The only copy of the photo is the one you attached to the meal yourself. Reading it creates no request, no cache and no identifier of any kind.
  • The suggestions start unticked, and stay suggestions. Nothing reaches your diary until you tick it and tap Add. What comes back is a guess from a picture, sometimes a wrong one, which is exactly why you confirm it rather than the app filling the meal in for you.
  • It is asked to name only what it can see. Digestly instructs the model not to guess at ingredients hidden inside a cooked dish, so the app does not put foods into your diary that nobody could see on the plate.
  • If your iPhone can't do it, the button isn't there. On an older iPhone or an older iOS version, or with Apple Intelligence switched off, the feature is simply absent rather than present and failing. Typing ingredients by hand works exactly as it always has.

The emergency card, specifically

Digestly can hold an emergency card for each person: the allergy action plan your doctor gave you (a PDF or a photo of the paper form), the phone numbers you want to hand in a hurry, your clinician's details, and the expiry dates of adrenaline auto-injectors.

  • Stored exactly as you provide it. Digestly saves the document as-is. It does not read the file, extract text from it, summarise it, or send it anywhere. Nothing in the app interprets what your doctor wrote, and nothing in the app adds medical instructions of its own.
  • Same place as the rest of your log — on your device, and in your own iCloud if sync is on. The Advanced Data Protection caveat above applies to these documents too, and applies more sharply: an action plan usually carries a child's name and their diagnoses on the same page. If that concerns you, turn on Advanced Data Protection or turn sync off.
  • Phone numbers are typed by you. Digestly never reads your address book. It has no access to your Contacts, and asks for none.
  • Expiry reminders are local. If you switch on a reminder for an auto-injector, it is scheduled by your own iPhone as a local notification. Nothing is sent to us or to anyone else. If you have "Discreet reminders" switched on in Settings, the reminder omits the person's name, the brand and the location, so a lock screen shows only that an auto-injector is expiring.
  • Deleted with everything else. Removing a person removes their emergency card, and "Erase all data" removes all of it, documents included.

Linking a breastfed baby to the parent who feeds them, specifically

If you say in a profile that a baby is breastfed by someone, Digestly can show that parent's logged meals alongside the baby's symptoms, and can list what the parent ate in the hours before a feed you are logging.

  • Nothing new is collected or sent. This shows meals the parent had already logged on their own profile. It creates no record of its own and makes no request.
  • Both profiles are already yours. They are two people in one family diary on one device, so this moves nothing between accounts — there is only ever one account, which is yours.
  • You set it up and you can undo it. The link is off unless you choose it in the profile editor, and clearing it stops the sharing immediately. Past meals keep whatever you logged about them; nothing is rewritten.
  • It is not a conclusion. The app says what was logged and when, and says plainly that it cannot tell what actually reached the baby.

What leaves your device

Only what you choose to share:

  • Doctor reports (PDF) and CSV exports are generated on your device and leave it only through the iOS share sheet, to a destination you pick.
  • Backup files (Settings → Backup & sharing) are generated on your device and leave it only through the iOS share sheet, to a destination you pick. A backup contains everything — profiles, the diary, photos, emergency cards — and is not encrypted, so anyone who has the file can read it; the app says so where the file is made. Keep it as carefully as you would any medical document. The prepared file is removed from the app's own storage when you leave the screen, and "Erase all data" clears any staged exports it finds.
  • Shared profiles (Settings → Backup & sharing) are for a co-parent's phone. The file is encrypted on your device before it leaves, and it leaves only through the share channel you pick (AirDrop, for example). It can only be opened with the code Digestly shows you, which you pass on yourself — the code is never stored in or sent with the file, and Digestly transmits nothing anywhere in the process. The file's name is generic and includes nobody's name. Be aware of what rides along: so the receiving phone can name everything, the share also carries the household's own catalog additions — custom foods, symptoms and medicines, and saved meal templates — even when they were made for another profile.
  • iCloud sync, if enabled, moves data only between your own devices via your own iCloud account.
  • A barcode, and only when you scan one — see below.
  • Feature counts, and only if you have switched them on — see below.
  • A feedback message you write, and only when you tap Send — see below.
  • A symptom you log on an Apple Watch, which travels to your own iPhone and no further — see below.
  • Nothing from Digestly when you install it from one of our ads. Apple itself may tell the ad platform that an install happened — see "Installs from our ads, specifically" below.

Barcode scanning, specifically

If you scan the barcode on a packet, Digestly asks the public Open Food Facts database what that product is, so it can offer you the ingredient list instead of making you type it.

Apart from the optional feature counts and any feedback you choose to send, both described below, this is the only request Digestly ever makes to anyone. Precisely what is sent:

  • The barcode digits, and nothing else. No profile, no name, no age, nothing you have logged, no device or installation identifier, no advertising identifier, no location, and no timestamp beyond the unavoidable fact that the request happens when you make it.
  • The same request for everybody. Digestly asks for the product's details in all five of its languages every time and picks the right one on your device. It could have asked only for yours, which would have been a smaller request — and would have told Open Food Facts which language you read. It does not.
  • A version line identifying the app (Digestly/1.0) and the developer's own contact address, which Open Food Facts requires of every app that uses it. This is our contact detail, not yours.
  • No cookies. The connection is made fresh each time and stores nothing, so nobody can set an identifier that survives from one scan to the next.

Other things worth stating plainly:

  • Nothing about you is sent, so nothing about you can be stored at the other end. Open Food Facts can see that somebody looked up a barcode, from an IP address, as they can for any website. They cannot see who, and they cannot connect two scans to the same person through anything Digestly sends.
  • Results are cached on your device so scanning the same product again needs no request at all.
  • No photograph is taken or kept. The camera reads the barcode live and the image is never saved.
  • Scanning is entirely optional and never required. You can type ingredients by hand exactly as before, and everything works with no network at all.
  • The camera is only used while the scanner is open, and only if you allow it. Decline, and Digestly offers a field to type the barcode digits instead.

We receive nothing from any of this. We have no server involved in it and no way to see that it happened.

Feature counts, specifically

If you switch on Share feature counts (Settings → Privacy & about → Feature counts; it is off until you do, and Digestly asks you once, on the second time you open the app), then once a day the app sends us how many times each of its features was used the day before. This is how we learn which parts of Digestly people actually use and which they do not, so we know what to keep working on.

Here is the whole of one such message, exactly as the app builds it:

{ "schema": 1, "day": "2026-11-03", "app": "1.0 (8)", "lang": "de", "counts": { "app_opened": 6, "quick_log": 9, "barcode_scanned": 1, "report_exported": 0, … } }

  • Numbers only. Each feature — quick log, barcode scan, the emergency card, the doctor report, and so on — has one counter, and the message is those counters for one calendar day. Every feature is listed every time, with a zero if it was not used, so the message does not reveal which features you never use either.
  • Nothing that identifies you or your phone. No name, no account, no device or installation identifier, no advertising identifier, no location, no phone model or system version. The message has five parts — a format number, the day, the app version, the app language, and the counts — and there is no field for anything else. Our server rejects any message with a sixth.
  • Nothing you logged. No meals, symptoms, exposures, medicines, notes or photos, no names or ages, not even how many people you log for. No counter is named after a symptom, a food or a trigger.
  • Only the day, not the time. The message says which day the counts describe and is sent at a random moment in the hours after it, so nothing about when you use the app is recorded.
  • What we keep is a total. The message is added to a running total for that day, app version and language, and then discarded. We do not keep the messages, and we do not record the internet address they came from.
  • You can see it before it goes. The Settings page shows the exact message built from your own counters, and a button that switches sharing off and sets every counter to zero. Turning the switch off does the same. "Erase all data" forgets the counters and your answer.

The counts go to a small service we run on Cloudflare (digestly-counts.os-0fa.workers.dev). Nothing else is sent there, and nothing is sent at all while the switch is off.

Feedback you send us, specifically

Settings → Help & feedback → Send feedback is a text box that comes straight to us. Nothing is sent until you tap Send, and nothing is sent at all if you never use it.

Here is the whole of one such message, exactly as the app builds it:

{ "schema": 1, "message": "What you typed", "app": "1.0.1 (9)", "os": "27.0", "lang": "en" }

  • What you typed, and three facts about the app. The app version, the iOS version and the language the app is shown in, so that a report of a problem can be understood. All three are shown on the screen above the Send button, as they will be sent. The message has five parts and there is no field for anything else; our server rejects any message with a sixth.
  • Nothing that identifies you or your phone. No name, no email address, no account, no device or installation identifier, no advertising identifier, no phone model, no location. We do not record the internet address a message came from, and we keep only the date it arrived, not the time.
  • Nothing from your diary. The app attaches nothing you have logged — no meals, symptoms, notes, photos, profiles or reports. Only the words you type are sent.
  • You agree before anything is sent. Directly above the button the screen says: "I agree that Longstop Software can read and keep this message, including any health details about me or my family that I choose to include, to improve Digestly", and the button reads Agree and send. Names and health details are not needed to tell us about a problem, and the screen says so.
  • Health details are removed once we have read them. If a message mentions anyone's health, we edit that out of the stored copy, or delete the message, as soon as we have read it. Until then it is read only by us.
  • We cannot reply. Nothing about you is attached, so there is no way for us to answer. If you want a reply, email os@longstopsoftware.com instead.
  • Kept for six months, then deleted. Messages are deleted automatically 183 days after they arrive. They are read by Longstop Software only, are never used for advertising, never sold and never shared. You can withdraw a message at any time: because it carries nothing that identifies you, we can only find yours if you tell us roughly what it said and when, so email os@longstopsoftware.com and we will delete it.
  • Nothing is kept on your phone. An unsent message stays in the text box until you leave the screen, and is then discarded. A message that fails to send is not queued or retried; you can simply tap Send again.

Messages go to a small service we run on Cloudflare (digestly-feedback.os-0fa.workers.dev) and are stored in Cloudflare's European Union jurisdiction. Nothing else is sent there. On the App Store, Digestly's privacy label lists these messages as "Customer Support" data linked to you. We attach nothing that identifies you, but what someone writes can identify them, so we declare it the cautious way.

The Apple Watch app, specifically

If you use the Apple Watch app, you can log a symptom from your wrist without taking your phone out. What moves does so directly between your own two devices, over the link your iPhone and your watch already have with each other. No server of ours is involved, and no third party's either — this is not a network request and nothing about it reaches the internet.

It also works whether or not you use iCloud sync, and that is deliberate: a symptom logged on the wrist must not go missing simply because you have chosen to keep your diary on one device only.

  • Watch to phone: one symptom. Which symptom you picked, how severe you said it was, when, and which person it is about. Nothing else — no note, no photo, and nothing else you have ever logged.
  • Phone to watch: what a list needs. The symptom names, so the watch can show them to you in your own language; a marker saying which of them involve breathing, so the emergency-care notice can appear on the watch itself instead of waiting for a phone in another room; and the names of the people you log for, so the watch can show whose entry it is.
  • If you add Digestly to your watch face, four more things travel with that: how many meals and how many symptoms you have logged today, how many days in a row you have logged at all, and the name of the person those numbers describe. They are counted on your phone, so the watch receives the totals and never the entries behind them. These are the same numbers the iPhone widget has always shown.
  • Your diary, your patterns, your insights and your reports are never sent to the watch. A watch is the screen in a household most easily read over your shoulder, so it is given the least it can work with.
  • The watch keeps no diary of its own. It holds the list above, those few numbers, and any entry not yet handed over — nothing more. Your log lives on your iPhone. Removing the watch app removes the watch's copy with it.

Lock Screen cards, specifically

Two features can put a card on your Lock Screen, and only if you turn them on: the 72-hour window you can start from a food's page, and (from version 1.0.1) a running trial, from the trial's own page.

  • Drawn by your iPhone, from what is already on it. The card is a Live Activity: iOS shows it from a few words the app hands it on the phone itself. Nothing is sent to us, to Apple's servers or to anyone else.
  • What it shows. The watch-window card shows the person's name, the food and the time left. The trial card shows the person's name, the trial as you named it, which day it is on and the length you planned, if you noted one — never anything about how the trial is going. Anyone who can see your Lock Screen can read these.
  • Discreet reminders covers the trial card. With Settings → Reminders → Discreet reminders on, the trial card names neither the person nor the food.
  • It goes when you say. Turn the switch off, end or delete the trial, or stop the window, and the card is removed. "Erase all data" removes every card too.

Installs from our ads, specifically

We advertise Digestly on Facebook and Instagram, and those ads open the App Store directly. To learn how many installs an ad campaign produced, we use Apple's own install attribution (SKAdNetwork), built into iOS. It works like this:

  • When you first open Digestly, the app tells iOS — on your phone, not over the internet — that it has been opened. That is the whole of what the app does. Digestly contains no code from Meta or from any other advertising company.
  • If, and only if, you installed Digestly after tapping one of our ads, Apple later sends Meta (the company behind Facebook and Instagram) a short, delayed message saying that the ad campaign led to an install. Apple, not Digestly, sends it, after a random delay of a day or more.
  • That message contains no identifier for you or your phone, no advertising identifier, nothing you have logged and nothing about how you use the app. It cannot be used to recognise you, and it is not tracking: there is no tracking request, because nothing here tracks you. The only value Digestly ever reports is "installed and opened"; it is never changed by anything you do in the app.
  • If you did not come from one of our ads, nothing is sent to anyone.

Apple describes the system at developer.apple.com/documentation/storekit/skadnetwork. Meta's own privacy policy covers what Meta does with the counts Apple gives it.

Apple Health (optional)

If you turn on Connect Apple Health in Settings (it is off by default), Digestly reads sleep and activity information — sleep analysis, steps, active energy, and exercise minutes — from Apple Health, as recorded by your iPhone, Apple Watch, Oura ring, or other apps that write to Apple Health.

  • Read-only. Digestly never adds, changes, or deletes anything in Apple Health.
  • On-device only. Health data read from Apple Health is processed and stored only on your device. It is never synced to iCloud, never transmitted anywhere, never included in exported reports, and never used for advertising.
  • Only for you. It is used solely to show your sleep and activity alongside your own symptom log and to look for patterns you can discuss with your doctor. Patterns are observations, not medical conclusions.
  • Reversible. Turn the switch off at any time and Digestly deletes its stored copy of the Health data. You can also revoke Digestly's read access in the Health app under Sharing → Apps. "Erase all data" removes it as well.

Health information

Digestly is a diary and pattern finder, not a medical device. It never provides medical conclusions. Information you log is health-related, so treat exported files with the same care you would any medical document.

Deleting your data

Settings → Erase all data permanently deletes everything from the device and from your iCloud (the app's CloudKit zone). Deleting the app removes all on-device data.

Children

Digestly is designed for parents logging on behalf of their children. Children's data is handled identically to all other data: on-device and in the family's own iCloud only. There are no accounts, and the app never sends us anything about a child: a feedback message contains only what you type, names and health details are not needed in it, and any health details are removed once we have read them. Apple Health data is only ever read on the device it belongs to.

Changes

If this policy changes, the updated version will be available at this address and the change will be noted in the App Store release notes.

Contact

Questions: os@longstopsoftware.com

This website

longstopsoftware.com sets no cookies, runs no analytics and includes no scripts at all. Fonts and images are served from this domain, so loading a page contacts no third party. The site's Content Security Policy forbids scripts and outside connections outright, so that is enforced by your browser rather than promised by us; you can confirm it in the browser's network tab.

Our host, Cloudflare, processes request logs — IP address, user agent, URL — as part of serving the site, as any web host does. We do not join those to anything else, and we have no other record of your visit.

Data protection

Because your diary stays on your device, we are not a data controller for it — we never receive it. Where we do hold personal data it is the ordinary minimum: emails you send us, including any TestFlight beta correspondence. Longstop Software Ltd is registered in England and Wales, company number 17359840, registered office Apartment 14, 11 Brompton Place, London SW3 1QE. You can ask us what we hold, ask for it to be corrected, or ask us to erase it, at the address above or at os@longstopsoftware.com.

TestFlight, the App Store and iCloud are operated by Apple under Apple's own privacy terms. We see only the aggregate, opt-in analytics Apple offers every developer in App Store Connect — download counts and crash reports — and nothing from inside the app.

Not medical advice

Digestly is a journal, not a medical device. It does not diagnose or treat any condition. Always consult a qualified clinician about allergies — especially for children, and urgently for any severe reaction. Call emergency services for signs of anaphylaxis.

Company

Longstop Software Ltd, a private company limited by shares, registered in England and Wales under company number 17359840. Registered office: Apartment 14, 11 Brompton Place, London SW3 1QE. os@longstopsoftware.com