No account. No raw IP address on disk.
There is very little to write a policy about, which is the intention. What follows is the complete list, and every claim on it can be checked against the code.
- No account, no login, no personal profile. Nothing asks who you are.
- No raw IP address is ever written to the database. It is used in memory and discarded.
- A vote is stored as a count, not as a person. It cannot be traced back to you.
- One cookie from this site, for the vote cooldown. No first-party tracking cookie.
- Your country is looked up only if you press the button to reveal it. Never on page load.
If you press a vote button
The site records that a vote happened, and what it counted towards. Specifically:
- Which activity
- eating, sleeping, laughing - the site you were on.
- Your answer
- yes or no.
- When
- the UTC date and time.
- Your country
- only if you revealed it. Otherwise this is left empty.
- Your local hour
- only if there is a country to derive it from.
That is the whole record. It does not include your name, your email address, your IP address, or your browser's user-agent string. There is nowhere in the database for those to go.
Your vote joins a running total that is shown to everyone - the figure under the vote buttons. The totals are public. The individual record is not, and there is no name attached to it to look up.
How you are counted without being identified
One person should not be able to vote fifty times, so a vote is de-duplicated against a hash. Building that hash is the only moment your IP address is touched.
The hash is made, in memory, from your IP address and your browser's user-agent string, combined with a secret value and today's date. Nothing about that is reversible, and the date is the important part: the same visitor produces a different hash tomorrow. A day's records therefore cannot be joined to the next day's, so even somebody holding the entire database could not assemble them into a history of one person.
The trade-off is deliberate and worth stating: a cooldown longer than twenty-four hours cannot be enforced by the hash alone, because the hash changes at midnight. Long cooldowns are enforced per-session instead.
There is also a limit of twenty votes per day across the whole network, counted against that same daily hash. Clearing your cookies does not reset it.
Your location
No page on this network works out where you are when it loads. The lookup happens only when you press the button that offers to reveal your country, and only then - it is the single place in the software permitted to look at an IP address, and it runs on an explicit click or not at all.
The lookup uses a local copy of MaxMind's GeoLite2 database on the server. The two-letter country code is kept so the site can tell you what your country is doing; the IP address is discarded immediately afterwards. If the lookup fails, nothing is stored.
Revealing is also recorded as a country-level count, so the site can say how many people from a country chose to share today. Again: a country, not a person. Country totals are displayed on the site, and they are a self-selected sample - only people who pressed the button are in them.
Cooldowns
The timer that stops you voting twice in a row is kept in your session and in the server's memory, and expires on its own. It is never written to the database. That is a deliberate choice rather than a happy accident: a timestamp tied to a visitor is exactly the piece of data that would otherwise link a person to a time and a place, so it is the piece that is not kept.
Cookies
This site sets one cookie of its own: a session cookie, which lets the server remember that you have just voted and how long you must wait before voting again. It has no advertising or analytics purpose and it follows you to no other site. The session ends after six hours of inactivity.
Beyond that, Google sets cookies through the consent message and the advertising served on the page. Those are Google's cookies, governed by Google's policies, not ours.
Advertising and analytics
Pages on this network carry advertising served by Google AdSense. Google may use cookies or similar technology to select and measure those ads, as described in Google's own privacy policy.
The tag manager is loaded only after Google's consent message reports that consent has been given. There is no Google Analytics 4 property configured for these sites, and no other third-party analytics runs on them.
Server logs
The application keeps no log of visits - its own page-view logging is switched off, so the software does not record who read which page. The web server hosting these pages may keep standard access logs, as web servers generally do.
Your rights, and what they amount to here
There is no account and no stored identifier, which means there is nothing to look up, export or delete on request. Requests to erase data held about you cannot be actioned against a record that does not exist: the votes are aggregate counts with no name attached, and the hashes rotate daily and are not reversible.
If you have a question about any of this, or you think something here is inaccurate, write to info@ing-now.com.
Changes to this page
If the software starts storing something it does not store today, this page is edited in the same change. Last reviewed September 2026.