Documentation · Legal and privacy

What tidekeeper stores

From Data processing agreement, its part “Annex 1”.

# What tidekeeper stores

- Subject and purpose: counting visits to the sites you add, and showing the figures to you and to whoever you share them with.

- Nature: receiving, enriching, storing, counting, showing, exporting and deleting.

- Whose data: the visitors of your sites, and the people you name with a user ID of your own.

- For how long: while your account exists, and as section 3 says after.

In easy mode, for each request:

- The visitor's network address and browser description. Used once, on our machine, to find the country (and region and city, where the site's settings ask for them; a city with fewer than five visitors in a period is counted only as elsewhere in its country), to reduce the browser to its family, system and kind of device, and to make the visitor key; then dropped. A web server error can name the address, in a log kept for two days.

- The visitor key, made from these, the site and that day's secret. Kept until the end of the UTC day, when the secret is destroyed and the key is removed from that day's records.

- The page (its address, with only the query parameters you choose to keep), where the visitor came from, campaign tags, the window's width, the time, and the events the site's settings turn on (such as links out, downloads and time on the page) or that you send.

What known bots read, on every site:

- When a request is from a bot tidekeeper knows by name (GPTBot, ClaudeBot, Googlebot and the like), from the page's script or from your own server where you set it up to send them: the bot's name, the page, the day, how many times, the answer your server gave where it says, and whether the bot's address was on the list its owner publishes. The address is used once, on our machine, to check that, then dropped. Kept as long as the site's other counts. A request from no bot tidekeeper knows is dropped unread.

In hard mode, as well, for visitors who agreed:

- A random ID, kept in a cookie for as long as your banner says.

- The pages, events, clicks and purchases under that ID, and a user ID and properties if you send them. Deleted the number of days you choose after the visitor's last visit, at most 395.

- Their answer to the banner, with the version of the words they were shown. Kept as proof of it, also after the rest of their data is deleted.

- For visitors who said no, or whose browser sends Global Privacy Control: that answer, with no ID.

Subject and purpose: counting visits to the sites you add, and showing the figures to you and to whoever you share them with.
Nature: receiving, enriching, storing, counting, showing, exporting and deleting.
Whose data: the visitors of your sites, and the people you name with a user ID of your own.
For how long: while your account exists, and as section 3 says after.

In easy mode, for each request:

The visitor's network address and browser description. Used once, on our machine, to find the country (and region and city, where the site's settings ask for them; a city with fewer than five visitors in a period is counted only as elsewhere in its country), to reduce the browser to its family, system and kind of device, and to make the visitor key; then dropped. A web server error can name the address, in a log kept for two days.
The visitor key, made from these, the site and that day's secret. Kept until the end of the UTC day, when the secret is destroyed and the key is removed from that day's records.
The page (its address, with only the query parameters you choose to keep), where the visitor came from, campaign tags, the window's width, the time, and the events the site's settings turn on (such as links out, downloads and time on the page) or that you send.

What known bots read, on every site:

When a request is from a bot tidekeeper knows by name (GPTBot, ClaudeBot, Googlebot and the like), from the page's script or from your own server where you set it up to send them: the bot's name, the page, the day, how many times, the answer your server gave where it says, and whether the bot's address was on the list its owner publishes. The address is used once, on our machine, to check that, then dropped. Kept as long as the site's other counts. A request from no bot tidekeeper knows is dropped unread.

In hard mode, as well, for visitors who agreed:

A random ID, kept in a cookie for as long as your banner says.
The pages, events, clicks and purchases under that ID, and a user ID and properties if you send them. Deleted the number of days you choose after the visitor's last visit, at most 395.
Their answer to the banner, with the version of the words they were shown. Kept as proof of it, also after the rest of their data is deleted.
For visitors who said no, or whose browser sends Global Privacy Control: that answer, with no ID.