Privacy
Last updated: 28 August 2026
If you just vote
No account, no email, no name. We set one cookie with a random identifier so the one-vote-per-day limit can work.
That identifier is never stored as-is. What goes into the database is an HMAC of it — a one-way fingerprint. If our database were ever exposed, nobody could work backwards from it to your cookie, which means it cannot be used to follow you anywhere.
To stop the same device resetting the allowance in a private window, we also keep a separate daily HMAC made from the request's approximate network address, browser user-agent and language. The raw signals are not stored. Those guard rows are purged as they become stale; the guard is an abuse-control token, not a profile of you.
If you sign in
We use Google Sign-In and request only openid, email and profile — nothing else. We store Google's permanent account identifier, your verified email address, and your display name and picture if Google provides them.
We do not ask for, and cannot see, your Google password, your contacts, your files, or anything else in your account.
What is public and what is not
- Your free votes are never shown individually. Only totals.
- Paid actions appear in the Live Battle, and by default they appear as Anonymous. Showing a public alias or a country flag is opt-in and off unless you turn it on.
- We never publish your email, your name, your IP address, or your precise location.
Payments
Payments are handled by Stripe as merchant of record. Card details go to Stripe and never reach our servers. We keep the payment identifiers and amounts we need to credit your balance and to keep our books straight. For purchases, we also retain the version and server timestamp of the immediate-delivery consent you submitted before checkout. This evidence is not public and is used only to administer the purchase, support requests, fraud prevention, and legal or accounting obligations.
Abuse controls
We use the request's IP address and network information temporarily to rate-limit activity and derive the daily guard described above. The raw address is not stored in vote records; only a one-way daily HMAC is kept until stale guard rows are purged. It is not published and is not used as an account identity.
Analytics (optional)
Google Analytics 4 is optional. Google Tag Manager and the Analytics tag load only after you choose Accept analytics in the banner or on the cookie settings page. We use the resulting reports to understand visits, votes, sharing, Pass usage, checkout and confirmed purchases.
The application sends controlled event context such as vote type, category, page type, vote source, and anonymous or logged-in state. It does not deliberately send your email, name, username, vote text, account ID, payment details or Stripe secrets to GA4. Advertising storage and advertising signals remain denied.
The consent choice and limited browser-only event deduplication markers are held in first-party local or session storage. They are not sent to Poopularity.
Cookies
- Voting — the random identifier described above. Essential.
- Session — only if you sign in. Essential.
- Sign-in marker — a short-lived first-party marker used to distinguish a Google login from a new account. It has no identity fields and expires after one minute.
- Analytics — optional Google Analytics storage, only after your explicit choice. There are no advertising cookies.
Your rights
You can request access to your data, correction, deletion, or a copy of it, by writing to the address below.
One honest limitation. Deleting your account removes your personal data, but the votes and payments themselves stay in the record with your identity removed. Two reasons: financial records have to be kept, and this site's whole promise is that the numbers can be explained. Erasing the events would break every total that depends on them. What disappears is any link back to you.
Controller: Eduardo Guerrero Romero · 45844134M
Avenida Alfonso XIII, 15, 03600 Elda, Alicante, España
support.poopularity@gmail.com