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
| Feature | What reaches us | Why |
|---|---|---|
| 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.
- What is sent: that the app was opened, and the first time a new install opens; which setup screens were shown and finished (the screen, never your answer); that setup was completed; that a log was saved and whether it was a manual entry, a photo or a meal (never what it said); that a photo was read and whether the reading worked (never the result); that a doctor report was created (never what is in it); that a paywall was shown, and whether during setup, as the app opened, or later; that a purchase was started, completed or failed, with the plan length, whether it began a free trial and, on failure, a reason such as “cancelled”; that a restore was tried and its outcome; that you signed in or turned on backup, or that either did not work, with a reason such as “cancelled” or “no connection” (never the error itself); that you switched these events back on; and that a promo code was redeemed, with whether Plus was on afterwards (never the code, which you type into Apple's or Google's own screen). Versions of the app before 19 October 2026 also asked during setup where you heard about Poopier (TikTok, Instagram, Reddit, X, an app store search, a friend, or somewhere else) and sent that answer. On Android, if you installed from a link that carried campaign tags, those tags, which Google Play passes to the app and which say which link it was, go with each event.
- What is never sent: your answers to the setup questions about your goal, condition, symptoms, how long and how often, or the foods you want to test; anything you log; your Gut Score, trial verdicts or the foods on trial; photos or what the model read from them; any other health data; your location; your email address; your name; or your account identifier.
- Who you are to it: a random id the analytics software creates on your phone, so that one install's events can be counted together. It is never linked to your account — the app never tells the analytics service who you are — and it is replaced with a new one when you sign out, delete your account, or switch the events off. No profile is built about you.
- What comes with each event: whether it came from a release or a development build of the app, so our own testing can be told apart from real use; and the details the analytics software reports about the app and device it runs on — app version, phone model, operating system and version, language, and screen size.
- Where it goes, and what happens to your IP address: to
PostHog, in its EU Cloud, hosted in the EU, through a relay we run on
Cloudflare at
e.poopier.app. Your IP address is discarded three times over: the relay never passes it on, every event tells PostHog not to work out a location from it, and PostHog's setting to discard client IP data is switched on for our project. The relay also removes the device's time zone, name and mobile carrier, cuts the language setting to the language alone, drops anything that is not on the list above, and keeps nothing. Our provider, Cloudflare, receives your IP address in delivering the request, as it does for any site you visit; we never store it, never log it and never forward it. - Your choice: the switch is in Settings, labelled Share anonymous usage events. It starts on, and the app says so during setup. Switching it off stops the events immediately and deletes anything still waiting on your phone to be sent, and they stay off across restarts; switching it back on sends only what happens from then on.
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.
- What is sent for the search: the grid square you are in — about a
kilometre across — and nothing finer. Your exact position is never sent to anyone.
The square is deliberately coarse enough to cover a neighbourhood rather than a doorway,
and everybody standing in it sends the identical request.
- To our server first. It answers from its own copy of
OpenStreetMap's public toilets, which we refresh from OpenStreetMap from time to time,
so the square usually goes no further. Only if that copy cannot be read does it use a
recent answer it kept for that square, or ask public services that search
OpenStreetMap data (Overpass instances, not run by us:
maps.mail.ru, run by VK, andoverpass-api.de) on your behalf, sending them the centre of the square and a radius of about two kilometres to search around it — from our server's address, not yours. - To OpenStreetMap's search services directly, if our server is slow.
If it has not answered within a few seconds, the app asks
overpass-api.deand thenoverpass.openstreetmap.fritself, with the same point and radius. These see your IP address, as any web request does. Whichever answers first is shown.
- To our server first. It answers from its own copy of
OpenStreetMap's public toilets, which we refresh from OpenStreetMap from time to time,
so the square usually goes no further. Only if that copy cannot be read does it use a
recent answer it kept for that square, or ask public services that search
OpenStreetMap data (Overpass instances, not run by us:
- What is not sent: nothing else. No logs, no account, no identifier. Our server sees your IP address on the request, as any website does, and uses it only to limit how often one address can search; it is not stored or logged, and neither is the square you searched.
- What is kept: on your phone, nothing. Poopier does not save your location or the results in your record or anywhere on the phone; close the map and both are gone. Our server keeps the public answer for each grid square somebody searched — a list of toilets from OpenStreetMap, filed under the square and nothing else, with no record of who asked — for up to seven days, so the next search there is instant and still works while the search services are busy. It does not say when somebody last searched there: a recent answer carries no age, and an answer older than a day carries its age in whole hours, which the app shows you. The copy sits in Cloudflare's cache in the data centre that served the search, and expires on its own.
- Map tiles come from the OpenStreetMap tile servers
(
tile.openstreetmap.org), which see the tiles you request and your IP address, as any website you visit does. Like the search services, they get only the approximate area — the same grid square about a kilometre across — and never your exact position. The tiles are chosen from that square, not from you: the app fetches every tile covering it and a margin around it, so everybody standing in the square requests the identical tiles. Your exact position is used only on the phone, to draw your own dot on the map.
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.
- What is sent, and when: one region name, at the moment you save a
log, and nothing else. Not your position — the region comes from your device's time zone,
which Poopier can read without asking for any permission and which is far coarser than a
city.
America/New_Yorkis one region covering half a continent, and that is the finest detail this feature ever has. - What is not sent: no account, no token, no device identifier, no coordinates, and nothing from the log itself — not what you recorded, not when. Nothing in the request identifies you: it is a city name on its own, and we store no link between it and your record.
- What your network reveals anyway: the request reaches our server, so our provider (Cloudflare) receives your IP address, exactly as it does for any site you visit. It is used for one thing and then discarded: this is an endpoint with no password, so it has to be rate-limited, and an address is what tells one caller from another. We never store it, never log it, and never write it into anything we keep — including the record of your contribution, which carries a city name and nothing else. We would rather say this plainly than claim a separation the network layer does not give us.
- A region has to be busy before it is counted. Until at least five contributions arrive from it inside the window it is not counted, not named and not drawn as a live region. (A random example dot, above, can land on any region, and says nothing about it.) This replaced an earlier design that leant on a delay, which only hid when somebody contributed rather than whether they were alone. Contributions, not people, is the honest word: a contribution carries no identifier — there is nothing written down that could tell two apart — so the count cannot distinguish five visits from one person from one visit by five. It raises the bar on what a quiet region can reveal; it is not a guarantee about how many people are behind a number. The leaderboard applies the same floor to each of its windows: a region's contributions count towards its day, or its week, only once at least five have arrived from it in that day or that week.
- What the map shows, and when: a count covering a fifteen-minute window that ended at least five minutes ago. The remaining delay is no longer a privacy measure — the threshold above is — it is there so a window is finished before it is counted.
- What is kept: counts, not contributions. Sharing your dot adds one to a number for your region and the five minutes it arrived in, which the map reads and which is deleted within forty minutes, and one to a number for your region and the hour it arrived in, which the leaderboard reads and which is deleted after eight days. There is no row for you to be in — nothing per-person is written down at all — and nothing is written to your record.
- If your time zone is not one of the cities on the map, nothing is sent at all, and the app tells you so rather than showing a switch that does nothing.
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.
- A drop is not your log. It carries one of thirteen badges, one of the preset captions for that badge (chosen from a list), a line you write yourself if you want to (below), whether it is anonymous or for friends, and the time our server received it. There is nowhere in it for a photo, a food, a symptom, a place, or anything from your diary, nothing from your diary is put into the line for you, and the app will not offer to post a log that carries a warning sign such as blood. A badge about a bowel movement is still about your body, and we would rather say so than pretend otherwise.
- The line you write. A drop can carry one line of your own, up to 80 characters, or none. It is shown with the drop to exactly the people who can see the drop: everyone signed in to the feed for an anonymous drop, your friends for a friends drop. On an anonymous drop it appears under the random animal and carries nothing that identifies you, unless you write something that does, so keep your name out of it. Before it is posted, the app and then our server check it for a link, an email address, a phone number or an @handle, and for a word from a list of swear words, slurs and sexual terms in English, German, French, Spanish and Portuguese, and refuse it when one is found. The check catches the common ways of writing these, not every way. It runs on your phone and on our server and sends the line nowhere else; a refused line is not stored. The line is never written to our logs, and it is used for nothing but showing it with its drop and reviewing a report about it: not for advertising, statistics, training any model, or anything else. It is deleted with its drop, except the copy kept with any report about it, which is kept 30 days.
- Who sees an anonymous drop: anyone signed in to the feed. It is shown as “Anonymous” with an animal our server picks at random for that one drop, so nobody reading the feed — your friends included — can tell it is yours, or that two anonymous drops came from the same person. We can: the server records who posted it, so that you can delete it, so that it can be removed with your account, and so that reports can be dealt with.
- Who sees a drop for friends: your friends, and nobody else. They see it under your community name and animal. A community name is 1 to 20 characters, asked for the first time you post to friends, shown only to friends, and changeable in Settings. It and a drop's line are the only things in this feature you type.
- Friends are mutual and made only by a code: you share yours, and the other person enters it. Removing a friend ends it both ways and gives you a new code, so the one they have stops working. Blocking a friend does the same, also stops either of you adding the other again, and hides your friends drops and pins from each other.
- Reactions, hiding and reporting. Your reaction to a drop is counted and shown to you as yours; others see only the counts. Hiding a drop hides it for you. Reporting one hides it for you and keeps a copy for us to review — the reason you chose, the badge, caption and line, the poster's community name if it was a friends drop, and hashed identifiers of you and the poster, and whether your report counted toward hiding the drop from everyone. A drop is hidden from everyone but its poster once three such reports count, and a report counts only from someone who has been using the feed for at least a week, for at most five reports a day each.
- The map, and your location. Off until you switch on Show my drops on the map. When it is on and you post a drop for friends, the app asks for your location: approximate location on Android (the precise permission is not in the app), and location while you use the app on iOS. Your exact position never leaves the phone: the app works out which grid square about a kilometre across you are in and sends a random point inside that square. Our server does not trust even that — it replaces the point with its own random point in the same square, and stores only that. So what a friend can learn from your pins is which square you posted from, not where in it you were — with one exception: if you often post from near the edge between two squares, your pins land in one or the other, and over many pins that shows you were near that edge. You have one pin at a time, only friends see it, and switching the map off removes it at once.
- The map's streets are OpenStreetMap's, and your phone fetches them from OpenStreetMap's tile servers, which see the map squares requested and your IP address, as with any map. The Poop map opens on your own pin; without one, if you have already allowed location, on the middle of the grid square you are in, never your exact position; otherwise on your friends' pins. From there it fetches whatever you move it to, so the tile servers can tell which areas were looked at, including the squares your friends' pins are in. They are not told why, or who anybody is. Opening the map never asks for your location.
- Notifications about the feed. Once you have opened the Daily Drop signed in on a phone, and while its notifications are on in Settings, the app checks the feed in the background there, about once an hour when your phone allows it, to tell you when a friend posts, when your drops get reactions, and at most once a day when there are new drops. The check is the same request opening the feed makes, with the same sign-in, and sends nothing else; we keep no record of it. The notification itself is made on your phone: there is no push service, and no device identifier is sent to us or stored. The app's other notifications (the daily reminder, the evening check-in and the meal nudges) are made on your phone from your record and send nothing at all.
- How you are filed: under a one-way hash of your sign-in identifier, never the identifier itself, and not the same hash RevenueCat receives. The hash does not reveal the identifier, though anyone who already holds the identifier, us included, can compute it. Friends see a random id that is derived from nothing. Requests are rate-limited by that hash. Anonymous drops that carry a line are also limited per network address, five a minute, because an anonymous line reaches everyone: your IP address is used for that count while the request is answered, and is not stored or logged.
- Where it is kept: in a database at Cloudflare (D1), on the same service as the rest of Poopier's server. No one else receives it.
- How long: a drop is gone from the feed seven days after it is posted, and a pin 24 hours after it is placed; both are deleted from the server at the next daily clean-up, so within a day after that. A drop's line, its reactions and hides go with it. Reports, with their copy of the drop and its line, are kept 30 days. A count of how many drops you posted and how many friend codes you tried today, which is how the daily limits work, is deleted after two days. Your profile, friends and blocks stay until you delete your account. You can delete any of your drops yourself at any time. Separately, the database keeps a recovery history of its own changes for up to 30 days, as Cloudflare's databases always do, so a deleted row can be restored from it for that long; only we can restore from it, and after 30 days the row is gone from it too.
- Deleting your account deletes all of it straight away, with no holding period: your profile and code, your friendships and blocks, every drop with its reactions, your pin, the reactions and hides you left on other people's drops, the reports you filed and the reports about your drops. What stays is a marker holding only the hash above, for an hour and then until the next daily clean-up, so a phone still signed in to the account cannot make a new profile in the meantime. The recovery history described above applies here too. Signing out deletes nothing; your drops stay until they expire.
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
- No advertising, and no advertising identifiers.
- No sale or sharing of personal data with data brokers or any third party for their own purposes. We do not and will not sell health data.
- No tracking across apps or websites, and no advertising SDKs. The app ships two third-party SDKs, both described above: RevenueCat's, which manages subscriptions, and PostHog's, which sends the anonymous usage events and can be switched off in Settings.
- No sending your health data to any outside analysis service. The model that reads a photo is bundled in the app and runs locally.
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
- Cloudflare — hosting, storage of encrypted backups, sign-in records,
clinic kit requests, and the Daily Drop and Poop map's posts, friends and map points,
and the relay at
e.poopier.appthat forwards usage events without your IP address. - PostHog — anonymous usage events, in its EU Cloud, hosted in the EU. Receives the events described above with a random id, through our relay; never your IP address, anything you logged, any health data, or anything that identifies you. On until you switch it off in Settings.
- Resend — delivers the email when you sign in by email. Receives your email address, our sender address, and the message: its subject line, a six-digit sign-in code and, when one is included, a sign-in link. It never receives anything you logged.
- Google and Apple — only if you choose their sign-in, and only to verify who you are.
- RevenueCat — subscription and purchase management, and the Plus screen itself. Receives what the store transaction carries, what happened on the Plus screen, and, once you sign in, the opaque account identifier described above, and tells the app whether Plus is active. It never receives your email address or anything you logged.
- overpass-api.de and overpass.openstreetmap.fr — only when you open the toilet map and our server has not answered within a few seconds. Public services that search OpenStreetMap data, run by FOSSGIS in Germany and by OpenStreetMap France. Receive a rounded point, a search radius and your IP address, and return the toilets near it.
- maps.mail.ru (VK) and overpass-api.de, asked by our server — only when its own copy of the toilets cannot be read and it has no recent answer for that grid square. Receive the rounded point and the radius from our server, never your IP address or anything else about you.
- OpenStreetMap tile servers (
tile.openstreetmap.org) — only when you open a map. Receive the map tiles your phone requests, which for the toilet map cover your grid square rather than your position, and for the Poop map the area on screen, starting from your pin, your grid square or your friends' pins; and your IP address. They return the images the map is drawn from. Map data © OpenStreetMap contributors.
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 logs: on your device, until you delete them or remove the app.
- Encrypted backup: until you delete your account. If a subscription ends, the backup stops updating but is not removed. A backup deleted through the service is kept for 30 days before permanent removal, so a stolen sign-in token cannot destroy your record outright.
- A deleted account: the backup is removed and every device is signed out immediately. A copy is held for 48 hours in case the deletion was a mistake, then permanently erased at the next daily clean-up, so within three days at most; a backup you had deleted earlier goes with it rather than waiting out its 30 days. The window is short on purpose: deleting an account is something you meant to do, and we would rather “deleted” be close to literally true. Nothing we keep after the deletion carries your sign-in identifier: that copy, and a marker kept for an hour so a device still signed in cannot sync the backup back, are filed under a one-way hash of it, and the record that limits how often a backup can be written is deleted with the account.
- Sign-in records: sign-in challenges and codes expire within minutes. The hash of a Google sign-in's address is kept until you delete your account, which deletes it.
- Purchases: a subscription record is a record of a transaction and sits with the App Store or Google Play and with RevenueCat, so deleting your account does not remove it. Deleting your account does not cancel a subscription either — that is done in the App Store or Google Play.
- Toilet map searches: nothing about who searched is kept, on your phone or on our servers. The answer for a grid square — public OpenStreetMap data, filed under the square — stays in our server's cache for up to seven days.
- World map contributions: only as counts. Sharing your dot adds one to a number kept against a region and a five-minute period, deleted within forty minutes, and one to a number kept against a region and an hour, deleted after eight days. Nothing about the contribution itself is stored, and the counts are deleted on a schedule. There is no record of who sent it, so there is nothing to delete on request and nothing we could hand over if asked.
- The Daily Drop and the Poop map: drops, with any line written on them, seven days and pins 24 hours, then deleted at the next daily clean-up; reports, with their copy of the drop, 30 days; your profile, friends and blocks until you delete your account, which removes all of it at once. Details are in the section above.
- Former waiting list: no new addresses are accepted. Existing entries are kept until you ask us to remove you.
- Clinic kit requests: deleted automatically twelve months after the request. To have yours deleted sooner, write to hello@poopier.app from the address you gave.
Your choices
- Switch off anonymous usage events in Settings, under Share anonymous usage events, at any time.
- Export your logs as a CSV file. Export does not need Plus, and keeps working if a subscription ends.
- Delete everything from the app at any time. Deleting the app removes the record stored on your phone with it.
- Switch the Poop map off in Settings, under Feed and map, or on the map itself; your pin is removed at once. Delete a drop you posted, at any time.
- Delete your account and backup from Settings inside the app. This removes the backup from our servers, deletes everything you had in the Daily Drop and the Poop map, and signs out every device. Your logs remain saved on your phone — we have never been able to read them, and closing an account does not reach them. Delete the app if you want those gone too.
- Depending on where you live you may have rights to access, correct, port or erase personal data, and to object to processing. Since we hold almost nothing about you, the honest answer to most such requests is that there is nothing to produce — but write to us and we will tell you exactly what exists.
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.