Privacy Policy for Poops & Foods
Last updated: 15 September 2026
The short version: your logs stay on your phone.
Poops & Foods keeps everything you enter — your meals, your poop entries, your symptoms and any photos you attach — in a database stored only on your own Android device. There is no account, no login and no cloud copy of your diary. We (Innerbloom Network LLC) cannot see or retrieve what you wrote. It stays on your device unless you choose to send it somewhere yourself.
One thing is optional and off unless you turn it on. In Preferences you can choose to share anonymous usage data with us: daily counts of how much you logged and which screens you opened, under a random number that stands for your copy of the app. It never includes anything you typed or your photos. It is described in full under Anonymous usage data below, and you can switch it off at any time.
This policy explains all of that, and covers the legal rights you have.
Who we are
Poops & Foods is published by Innerbloom Network LLC (“we”, “us”, “our”), a limited liability company formed in California, United States.
Contact: support@innerbloomnetwork.com
This policy lives at: poopsandfoods.com/privacy
What Poops & Foods is, and is not
Poops & Foods is a food and bowel movement diary made for amusement and personal curiosity. You log meals by tapping the foods that were in them, log poops using the Bristol Stool Scale, and the app shows you patterns it spots in your own entries.
Poops & Foods is not a medical or health-care product. It does not diagnose, treat, cure or prevent any condition, it gives no medical advice, and it is not a substitute for a doctor. For anything concerning your health, talk to a qualified professional.
What the app stores, and where it lives
Everything you enter is written to a database (SQLite) stored locally on your device:
- Meals — the food groups and items you tap, which meal it was (breakfast, lunch, dinner, supper, snack, dessert), when it happened, and optionally a dish name and a note, both of which are free text you type yourself.
- Poops — the Bristol Stool Scale types you pick (more than one if it was mixed), roughly how much, and when.
- Symptoms — urgency, straining, pain and gas, plus a yes/no for blood. All five are optional, each one can be switched off in Preferences, and nothing is recorded for the ones you turn off.
- Photos — any image you attach to a meal, together with the quarter-turn you asked for if you straightened it.
- Places — the names you type or pick for where a meal was eaten, such as home or a restaurant, and how many meals you have logged at each.
- Dishes you teach the app — a dish name and the foods you said it is made of, so the app proposes them next time.
- Experiments and findings — which food you are currently watching or skipping, and any finding you have told the app you already understand.
- Achievements — which badges you have earned. A few badges can only be spotted as they happen rather than worked out afterwards, such as editing an entry or undoing something, so the app keeps a small record of those actions in order to award them. Nothing else in the app reads that record, and it is never used to analyse you or your health.
- Settings — your theme, which day your week starts on, whether you use a 12- or 24-hour clock, and which symptom sliders you have switched on.
We do not collect any of this. Under Google Play’s definition, data is only “collected” when it is transmitted off your device. None of the entries above is transmitted off your device — not the dish names, notes and place names you type, not your photos, and not your individual poop or meal records. There is no advertising, no trackers and no cookies in the app. If you switch on anonymous usage data, and only then, a crash sends the lines of code it happened in — never anything that was on the screen at the time. That is described under Anonymous usage data.
What can be transmitted, if you switch it on, is a daily count derived from these entries — and, if the app falls over, a report of where in its own code that happened. Those are the subject of the next section, and they are the only things this app sends anywhere.
The app never asks for your location and does not record where you are. A place is a name you typed or picked from a list, not a coordinate.
Permissions the app asks for
- Camera — only if you choose to take a photo of a meal. Any photo you take is stored locally with your log. We do not upload it.
- Photos — only so you can attach a picture you already have. The app uses the Android system photo picker, so it can see only the specific images you choose, not your whole library.
- Notifications — only if you ask for a reminder on a day you have written nothing. Off unless you turn it on.
- Screen lock or fingerprint — only if you turn on the lock that keeps the app shut until you unlock it. The check is done by Android; the app is told yes or no and never sees your fingerprint or your PIN.
All of these are optional. The app works without any of them, and you can decline or revoke them in Android settings.
What can leave your device, and only if you choose
Three things can, and each takes a deliberate action from you:
- Anonymous usage data — off unless you turn it on. Described in full in the next section.
- The summary on Your record — a plain-text list of your counts for a recent stretch of days, sent through Android’s share sheet to whatever app you pick. It is counts only: no individual entries, no photos.
- An export — a copy of your own entries, which you save or send wherever you want.
Once you send data somewhere else yourself, this policy no longer controls it. The privacy terms of wherever you sent it apply instead, and protecting that copy is up to you.
Anonymous usage data
It is off until you turn it on. The app asks once, on a screen that lists what would be sent and what would not, and dismissing that screen is a no. Nothing is collected — nothing is even counted on your device — unless you tap to accept. You can turn it off again at any time in Preferences → Usage data.
We use it for one purpose: to see which parts of the app get used, so we know what to build and what to fix. We do not sell it, we do not share it with anyone else, and we do not use it for advertising or profiling of any kind.
What is sent
Once a day, if it is switched on, the app adds up that day and sends the totals:
- Counts of what you logged — how many poop entries and meals, which Bristol types, which symptom levels, whether a colour was answered, which food groups and which of the app’s own food tiles you tapped, and which cuisine if you picked one. All of these are choices from lists the app ships, not words you wrote.
- Where you ate, in three buckets — at home, somewhere you typed, or one of the restaurant chains in the list the app ships. A place you typed yourself is counted and never named.
- Which screens you opened, how many times, and roughly how long they were on screen.
- Which achievement badges you hold, so a badge nobody can reach shows up as a mistake in the catalogue.
- The app version, and a random number generated on your device the first time you switch this on.
- A crash report, if the app falls over — the function names, files and line numbers the failure came from, which screen it happened on, the app version and the time. Those lines come out of the app’s own code, not out of anything you wrote. The error’s message is never included, deliberately: a message often quotes the thing it complained about, which could be a dish or a place name you typed, so the app keeps the stack and discards the rest.
What is never sent
- Anything you typed. Dish names, custom meal names, notes and place names you entered yourself are counted on your device and the words stay there.
- Your photos, and no file name or path from them.
- Your name, email address, phone number, account or location — the app has none of these to send. It asks for no location permission at all.
- Your device’s identifiers. We do not read the advertising ID, the Android ID, the IMEI or anything similar, and we do not record the IP address the data arrives from.
Crash reports
If the app falls over, it writes down where in its own code that happened and sends it the next time you open it — but only if anonymous usage data is switched on. With the setting off, nothing is written down and nothing is sent.
A report is the list of function names, files and line numbers the failure came from, which screen you were on, the app version, and the time. The error’s message is never included, and that is deliberate. An error message often quotes the thing it was complaining about, which could be a dish name, a note or a place you typed — so the app keeps only the lines that describe its own code and throws the rest away before anything is stored. Those lines come out of the app as we built it, not out of anything you wrote.
We use them for one thing: to find and fix what is breaking. A report is filed under the same random number as your daily counts, and switching the setting off deletes it along with everything else under that number.
The random number, and what “anonymous” means here
So that two days of counts can be recognised as coming from the same copy of the app, a randomly generated number is sent with them. It is created on your device, it is not derived from your phone or from anything about you, and it is not connected to any account — because there are no accounts. We have no way to work out who a number belongs to, and we do not try. Switching the setting off deletes it; switching it on again generates a new one, which arrives as a new copy of the app rather than as a continuation of the old.
We are describing it plainly rather than simply calling it anonymous, because a number that persists between days is the one part of this that is worth understanding.
How we look at it
The data is combined across everybody before we see it, and our dashboard shows those combined totals only. Nothing in it identifies you. There is no screen anywhere in it that shows a single device, no way to search it for a person, and no way to work back from a total to the copy of the app that contributed to it — the counts arrive carrying no name, no account, no contact detail, no location, no device identifier and nothing you typed, so there is nothing in them to work back to.
Where it goes, and how long it is kept
It is sent over an encrypted connection (HTTPS) to a service we run on Cloudflare, which processes and stores it on our behalf and is our only processor for it. Cloudflare operates a global network, so it may be processed outside your country. Individual daily counts and crash reports are kept while the setting is on, and deleted when you switch it off — that is the deletion this policy offers, and it is under your hand rather than on a timer. The combined totals are kept indefinitely, and by then they describe everybody at once rather than anybody in particular.
Turning it off
Switch it off in Preferences → Usage data. Three things happen: the app stops counting, we are asked to delete everything filed under your random number — every daily count and every crash report — and the number itself is discarded. What cannot be undone is the combined totals — once a count has been added into a figure describing thousands of days, there is no thread from that figure back to the phone it came from. That is a consequence of the design that makes this anonymous in the first place, and we would rather say so than imply a deletion that reaches further than it can.
If cloud sync arrives later
There is no cloud in this version of the app. We may add an optional sync in future, so that your entries can move between your own devices. If we do, it will be something you choose to turn on — nothing will sync unless you switch it on — and we will update this policy and our Google Play Data Safety disclosure before that ships, not after.
Deleting your data
Your entries are only on your device, so you are in full control of them. You can delete any entry in the app, and it disappears from the app immediately. The row stays in the local database, marked as deleted, until you clear the app’s storage or uninstall Poops & Foods — either of which removes the database and the photos with it. We hold no copy of your entries, so there is nothing for you to ask us to delete.
If you switched on anonymous usage data, the daily counts we hold are deleted by switching it off — see above. Uninstalling the app has the same effect on future collection but cannot send us the deletion request, so if you want the counts removed, turn the setting off before you uninstall. You can also email support@innerbloomnetwork.com and we will delete them, though we will need the random number from Preferences to find them — without it we have no way to tell which counts are yours.
Children
Poops & Foods is not directed to children and is not intended for anyone under 13, or the minimum digital-consent age where you live, which can be higher. We do not knowingly collect data from children, and the only thing the app can collect from anybody is the anonymous usage data described above, which is off unless it is switched on. Do not let a child use the app if that conflicts with the rules where you live.
Health-type data and your legal rights
Some privacy laws treat records about digestion or bodily functions as “health data” or “consumer health data” no matter how an app is marketed. Poops & Foods is built for fun, but your symptom entries — and the blood flag in particular — are exactly the kind of record those laws are written about. We take that classification seriously, and have designed the app so your individual entries are only ever handled on your own device.
The anonymous usage data described above does include counts derived from those entries — how many poop entries carried each Bristol type, how many carried each symptom level. We treat it with that in mind:
- We do not and will not sell it, and we do not “share” it for targeted advertising. We run no advertising and no profiling.
- It is optional and off by default, and it is deleted on request by switching the setting off.
- It reaches us as totals, not as records. No individual entry, no date of birth, no name, no contact detail and nothing you typed is in it, and we do not attempt to re-identify anybody from it.
- Apart from your individual entries — which we never receive — we have nothing of yours to disclose, correct or delete beyond those counts.
US state privacy rights
Residents of states with consumer privacy laws — including California, Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Florida, Delaware, Iowa, Nebraska, New Hampshire, New Jersey, Tennessee, Minnesota, Maryland, Indiana, Kentucky and Rhode Island — generally have rights to access, delete, correct and port personal information a business holds, and to opt out of sale, targeted advertising and certain profiling. These rights attach to personal information a business actually holds. We hold none of your entries, so there is nothing for us to produce, correct, delete or stop selling from those — you exercise those rights directly on your device by viewing, editing, exporting or deleting them in the app. The anonymous usage data we do hold, if you switched it on, is not linked to you by name, account or contact detail and cannot be searched for you; it is deleted by switching the setting off, or on request if you can give us the random number from Preferences. We do not sell it and we do not use it for targeted advertising or profiling. If you have a question about any of this, email support@innerbloomnetwork.com and we will respond.
California
We do not sell or share personal information under the CCPA/CPRA, and we do not use it for cross-context behavioural advertising. We do not collect your entries at all. The anonymous usage data described above is collected only with your opt-in and is not linked to an identified or identifiable person, so we do not treat it as personal information — but we have described it here in full rather than leaving you to take our word for that classification.
Washington, Nevada, and other consumer-health-data laws
A separate Consumer Health Data Privacy Policy covers Washington’s My Health My Data Act, and is linked separately from our homepage. Nevada residents: the same document addresses Nevada’s SB 370.
If you are in the EU, EEA, UK or Switzerland
Poops & Foods stores your entries only on your device. We do not receive or process those entries on our systems.
Where data protection law (the GDPR and UK GDPR) applies, the on-device data you enter is under your own control. If any of your entries are treated as special category data — for example, data concerning health — you are the one creating and holding it on your device; we are not processing it on our servers. You have rights of access, rectification, erasure, restriction, portability and objection, and for your on-device data you exercise them directly by viewing, editing, exporting and deleting entries in the app.
The anonymous usage data is the one thing we do receive, and only if you switch it on. Our lawful basis is your consent (Article 6(1)(a)), given by the in-app screen that lists what is sent before anything is; you can withdraw it at any time in Preferences, and doing so stops the collection and deletes what we hold. It is processed on Cloudflare’s global network and may therefore be processed outside the UK and EEA, under Cloudflare’s standard contractual clauses. We consider this data not to identify you, but we have set out above exactly what it contains so you can judge that for yourself. Because we do not otherwise process personal data on our own infrastructure, we have not appointed an Article 27 representative for this version of the app. If that changes, this policy will be updated with the representative’s details.
Security
Your data sits inside the app’s private storage area on your device, which Android isolates from other apps. Its security also depends on your device: a screen lock and keeping Android up to date protect it. If you export data off the device, protecting the exported copy is up to you.
Changes to this policy
If we change how the app handles data — for example, when we add features that send data off your device — we will update this policy and the “last updated” date before that change ships, and we will update our Google Play Data Safety disclosure to match.
Contact
Questions about privacy: support@innerbloomnetwork.com