← Poopier

Privacy Policy

Last updated 9 November 2026

Poopier analyses your logs on your own device. Scores are worked out in the app, on your phone. Photos are checked on this phone, and Poopier never uploads them. There is no account required, and no copy of your health record on a server that anyone but you can read. If you turn on backup, it is encrypted on your device with a key we never receive, so we cannot read it.

Who we are

Poopier is built by Kashif Mehmood. For anything in this policy, including a request to delete data, write to hello@poopier.app.

What is saved on your device

Everything you log — bowel movements, symptoms, photos, notes, foods, timings, nights of sleep you type in, and the Gut Score derived from them — is written to your phone's encrypted app storage. It is not sent to us, except inside the encrypted backup if you turn one on, which we cannot read and which leaves out photos and private notes.

Photos are checked on this phone, and Poopier never uploads them. A photograph you attach to an entry is written to the app's own storage and kept with that entry, and it is deleted when you delete the entry or erase your data. It is not sent to us, and it is not in the encrypted backup, which carries no image and no path to one.

Sleep, if you connect a health app. The Today screen can show last night's sleep beside your logs. On iPhone, Poopier asks Apple Health (HealthKit) for permission to read sleep analysis; on Android, it asks Health Connect for permission to read sleep sessions. It asks for that one thing on each platform and nothing else, and it is read-only — Poopier never writes anything to Apple Health or Health Connect. When the card loads, Poopier reads the last two days of sleep, takes your most recent night, and works out how long you were asleep, when it began, the times you woke during it, and how it compares with your other recent nights. That is used to draw the sleep card and the sleep ring on the Today screen and nothing else. It is used only on your phone: it is not sent to us or to anyone else, it is not written into your diary, and it is not included in the encrypted backup. Apple does not tell an app whether you allowed read access, so on iPhone a refusal and an empty night look the same, and the card simply says it has nothing. You can change the permission at any time — in Settings → Health on iPhone, or in Health Connect on Android. Your Gut Score does not use sleep at all; the card says so, because it is the thing people reasonably assume.

Sleep you type in yourself. You can also add a night by hand: the time you went to bed and the time you woke. That is different from the health-app reading above, because you wrote it: it is saved in your diary with your logs, on your phone, and it is inside your encrypted backup if you have one turned on — ciphertext under a key we never receive, so we cannot read it. Deleting a night, or erasing your data, removes it the way it removes a log. Your Gut Score does not use it either.

Your name, if you choose to add one. Settings has an optional “Name on reports” field, empty unless you fill it in. It is printed on the report you share with a clinician so the document says whose it is. It is stored on your phone like everything else, and it is included in your encrypted backup if you have one turned on — which means it is ciphertext under a key we never receive, so we cannot read it. We never take it from your sign-in provider or your email address: it is only ever what you typed. Clearing the field deletes it.

What we receive, and only if you ask for it

FeatureWhat reaches usWhy
Sign-in with Google, or with Apple on iPhone The account identifier that provider issues for Poopier — an opaque string. We store it as it is given to us. It is what your encrypted backup is filed under, and it is not reversible to your name or address, but it is not a hash either and we would rather say so than round it up. The signed token Google sends us to prove who you are also carries your email address. When Google says the address is verified, we keep a one-way hash of it, the same kind of hash email sign-in keeps, and never the address itself; the address is never stored or logged. Apple's token carries no address, because we ask for no scopes there, so for Apple we keep nothing of the kind. To recognise you as the same person on a new device, so an encrypted backup can be restored. The hash of your Google address is used for one thing only: finding your account if you write to us asking for it to be deleted.
Sign-in by email code Your email address, stored as a one-way hash. Your email address and the sign-in code (and link) are sent through Resend, which delivers the email. We do not keep the plaintext address afterwards. To send a six-digit sign-in code.
The Daily Drop and the Poop map (signed in only) What you post and who you share it with: a badge and a preset caption you pick, a line of up to 80 characters if you write one, the time you post it, and whether it is anonymous or for friends; a community name and an animal if you set them; your friends, and anyone you block; your reactions, hides and reports; and, only if you switch the map on, a point in a grid square about a kilometre across. Not encrypted the way the backup is: we can read it, because the server has to decide who may see each post. Details, and who sees what, are below. So the feed and the map work.
Finding a toilet (the toilet map) The grid square you are in, about a kilometre across: two whole numbers, the same for everybody standing in it. Not your position, and nothing that identifies you. Details below. So a search can be answered from a recent answer for that square, and still works when OpenStreetMap's search services are busy.
Encrypted backup A block of ciphertext. We hold no key to it. So you can restore your record on a new phone.
Buying Plus, or restoring a purchase The payment goes to the App Store or Google Play, and we never see a card. RevenueCat, which manages subscriptions for us, receives what the store transaction carries — which plan, the price and currency the store charged, and the store account's country — and, if you are signed in, an opaque account identifier. That identifier is a one-way hash, computed separately from the one we store, so what RevenueCat knows you by is neither your email address nor the identifier Google or Apple issued. Signed out, it is an anonymous id belonging to that one install. Nothing you log goes with any of it. So Plus unlocks on every device you sign in on, and locks again when the subscription ends.
Seeing the Plus screen The screen that sells Plus is RevenueCat's, and while it is open the app fetches its layout from RevenueCat and tells RevenueCat what happened on it: that it was shown, which plan or control on it was tapped, whether a purchase from it was started, failed or cancelled, and how it was closed — with which set of plans it showed, the screen's language and whether it was in dark mode, against the same identifier as above. Nothing you logged and no health answer goes with it. So we can see whether the Plus screen works, without building our own tracking for it.
Former beta waiting list (this website) — closed The website no longer accepts email addresses. For anyone who joined while it was open, we still hold the address and the time it was submitted, stored under a hash of the address so a listing of the database reveals no addresses. To send one message at launch. It is not used for anything else.
Clinic kit request (this website, for clinicians) The role you chose, your name and clinic if you gave them, your work email address, the time of the request, and the country Cloudflare reports for it — the country only, never a city, your IP address or your browser details. Kept in Cloudflare Workers KV, which is Cloudflare's storage. To email you the clinic kit you asked for. It is not added to a mailing list or used for anything else.

If you never sign in, never joined the waiting list, never open the toilet map and never switch on Share my dot, nothing you log ever reaches us, and the app works fully — including offline, with the radio switched off.

Two things happen without you asking for them. The first: on iPhone and Android the app asks RevenueCat when it opens whether this install has an active subscription, so that a lapsed subscription locks and a renewed one unlocks without waiting for you to find the paywall. Until you sign in or buy anything, what it has is an anonymous id created on the device, the ordinary details an SDK reports about the app and platform it runs on, and the request metadata any server sees, including your IP address. It carries nothing you logged. Offline, the question simply goes unanswered and the last answer stands.

The second is anonymous usage events. They are on until you switch them off, in every country, and you can switch them off at any time. The next section says exactly what they are.

Anonymous usage events

To learn where people give up during setup and whether purchases work, the app sends a short list of events about how it is used. It is a fixed list, written into the app's code as types rather than free text, so nothing outside it can be sent by accident.

The toilet map, which is the first of three exceptions

Finding a public toilet near you cannot be done on the device alone — somebody has to be told roughly where you are. It is switched off until you tap it and agree, and it explains this before it sends anything.

On Android we ask only for approximate location — the permission for precise location is not in the app at all, so it cannot be granted. On iOS we ask for location while you are using the app and tell the system that kilometre accuracy is all we want. That is a request for less work, not a cap the system enforces, so iOS may hand us a better fix than we asked for. It does not travel: the rounding above happens on your phone before anything is sent. We tried iOS's own reduced-accuracy mode and took it out — it answers with the centre of a region one to twenty kilometres wide, which opened the map on the wrong part of town and made the walking distances wrong, while sending no less than the grid square already does.

The live world map, which is the second

The world map shows roughly how many people are going right now, by city, and its leaderboard ranks regions over the last day and the last week. Your phone contributes to them only through Share my dot, which is off until you switch it on; switching it off stops it immediately. You can look at both without appearing on either.

Not every dot on the map is somebody who shared theirs. So that the map is never blank, 20 to 30 regions are picked at random every half hour — by our server, or by the app itself when the server sends none — and the app draws them alongside the real ones and leaves them out of every number. They are chosen without looking at anyone's contributions, so an example dot on a region tells you nothing about who is there.

The Daily Drop and the Poop map, which is the third

The Daily Drop is a feed of joke badges — “Heavy Poop”, “Ghost Poop” — that people post about how it went, and the Poop map shows where your friends' recent drops were, roughly. Both are optional, both need you to be signed in, and they are the only part of Poopier that sends this data. If you never open them signed in, none of what follows exists for you, and the rest of the app works exactly as described above, with no account.

The backup is end-to-end encrypted

Backup comes with Plus. When you turn on backup, the app generates a random key on your device that encrypts your record, and a recovery code that locks that key. Your data is encrypted before it leaves the phone. We store the encrypted record and the locked key, and nothing that can open either.

The recovery code never reaches us. That means we cannot read your backup, cannot recover it for you, and cannot hand it to anyone who asks — including in response to a legal demand, where all we could produce is ciphertext. It also means that if you lose the recovery code, the backup is permanently unreadable. That trade is deliberate, and the app makes you confirm you have saved the code before it continues.

What we do not do

This website

poopier.app uses Cloudflare Web Analytics, which is cookieless and does not fingerprint or track individuals across sites. It reports aggregate page views and performance. The site sets no advertising or tracking cookies, and the typefaces are served from our own domain rather than a third party.

The site has one form: the clinic kit request for clinicians. What it sends, where it is kept and for how long are in the table above, under Clinic kit request.

Cloudflare also serves the site and processes request metadata such as IP address in the ordinary course of delivering it and protecting it from abuse.

Service providers

None of these can read your logged health data. The only copy of it that leaves your phone is the encrypted backup, if you turn one on, and that is ciphertext we hold no key to. A drop you post to the Daily Drop is not a copy of your log: it is a badge you picked, and any line you wrote with it, sent because you posted it, and it is readable by us and by whoever you posted it to.

How long anything is kept

Your choices

Children

Poopier is not directed at children under 13, and we do not knowingly collect personal data from them.

Not a medical device

Poopier organises what you record. Poopier is not a medical device and doesn't give medical advice. The Gut Score is a summary of your own logs rather than a clinical measure.

Changes

If this policy changes in a way that affects what we collect or how it is handled, we will update the date above and, for material changes, say so in the app.