Cookie Policy
Last updated: 24 October 2026
This page explains which cookies and similar technologies Estimay uses, which of them need your consent, and how you can change your choice.
What cookies are
Cookies are small text files a website stores in your browser. They let the site remember something between pages or visits, for example who you are in a room. Websites can store similar information in your browser's local storage or IndexedDB; this policy covers that too.
Strictly necessary
These cookies make Estimay work, so they're always on and don't need consent:
| Name | Set by | Purpose | Contents | Expires |
|---|---|---|---|---|
storyvote.guest | Estimay | Keeps you the same participant across tabs, page reloads and browser restarts, so your votes stay yours and the host keeps control of their room | A random participant ID and your display name | 30 days after your last visit |
storyvote.slack-state | Estimay | Only while you add Estimay to Slack: checks that the installation Slack sends back is the one you started | A random value | 10 minutes, or as soon as the installation is done |
storyvote.trello-state | Estimay | Only while you connect a room to Trello: checks that the sign-in Trello sends back is the one you started | A random value | 10 minutes, or as soon as the sign-in is done |
storyvote.jira-state | Estimay | Only while you connect a room to Jira: checks that the sign-in Jira sends back is the one you started | A random value | 10 minutes, or as soon as the sign-in is done |
storyvote.linear-state | Estimay | Only while you connect a room to Linear: checks that the sign-in Linear sends back is the one you started | A random value | 10 minutes, or as soon as the sign-in is done |
storyvote.asana-state | Estimay | Only while you connect a room to Asana: checks that the sign-in Asana sends back is the one you started | A random value | 10 minutes, or as soon as the sign-in is done |
They are sent only to Estimay, only over HTTPS, and are not readable by other websites. In the Telegram Mini App the first isn't set: Telegram's signed launch data identifies you instead, in the Discord Activity Discord does, and in a room opened from its card in Slack Slack does. In Google Meet, where the cookie can't be set, the local storage entry below keeps you instead. Our analytics (Cloudflare Web Analytics) works without cookies or any browser storage, and so does the Buy Me a Coffee button on our public pages until you open it: its page then loads from buymeacoffee.com in a frame and may set its own cookies, under its own cookie policy.
Estimay also keeps these entries in your browser's local storage and IndexedDB, which stay until you clear them. They are never sent to Estimay, except the Google Meet entry, and need no consent:
| Name | Set by | Purpose | Contents |
|---|---|---|---|
storyvote.rating | Estimay | Remembers that you were asked to rate Estimay, so the question isn't repeated | The value 1 |
storyvote.meet-guest | Estimay | Only in Estimay's Google Meet add-on: keeps your name and seat, as the guest cookie does on the website, and is sent to Estimay when you join a room | Your name and a random participant ID |
emoji-picker-element-en (IndexedDB) | Estimay | Only once you open a room's emoji picker: keeps its list of emoji, so it isn't downloaded again, the skin tone you chose and the emoji you use most, shown first | The emoji list (from our own server), your skin tone, and how often you picked each emoji |
Your consent choice
Google's consent message, which we use to ask for your consent, remembers your answer so it doesn't ask on every page:
| Name | Set by | Purpose | Expires |
|---|---|---|---|
FCCDCF | Google, on estimay.io | Stores your consent choices (IAB TCF consent string) | 13 months |
FCNEC | Google, on estimay.io | Stores the state of the consent message | 1 year |
Advertising (only with your consent)
Estimay is funded by ads from Google AdSense. If you consent, Google and its advertising partners store and read cookies and similar entries in local storage to show ads, including ads based on your interests, to limit how often you see the same ad, to measure ads and to prevent fraud. The main Google cookies are:
| Name | Set by | Purpose | Expires |
|---|---|---|---|
__gads, __gpi | Google, on estimay.io | Show and measure ads, and limit how often you see them | 13 months |
__eoi | Google, on estimay.io | Security and preventing ad fraud | 6 months |
IDE | Google, on doubleclick.net | Personalised ads and measuring them across websites | 13 months |
test_cookie | Google, on doubleclick.net | Checks whether your browser accepts cookies | 15 minutes |
Google may change these names over time; its current list is in how Google uses cookies. The advertising partners Google works with, and what each one does, are listed in the consent message under "Manage options". If you refuse, Google shows limited ads that don't use advertising cookies.
Your choice
Under the EU ePrivacy Directive, Polish law (art. 399 of the Electronic Communications Law, Prawo komunikacji elektronicznej) and the UK's PECR, cookies that aren't strictly necessary need your consent. That's why, when you first visit from the European Economic Area, the United Kingdom or Switzerland, Google's consent message asks you first. Advertising cookies are set only if you agree. You can accept all, refuse all, or choose purposes and partners one by one; Estimay works the same whatever you choose.
You can change or withdraw your consent at any time with Privacy & cookie settings at the bottom of our pages.
Managing cookies in your browser
You can also see, delete and block cookies in your browser's settings. Blocking Google's cookies doesn't affect how Estimay works. If you block Estimay's own cookie, rooms won't work properly: you may appear as a new participant each time you reload, and a host will lose control of their room. Deleting it makes you a new participant in every room you were in. You can opt out of personalised ads from Google in My Ad Center, and from other companies at youronlinechoices.eu.
More information
How we and Google handle personal data is described in our Privacy Policy. Questions? Write to [email protected].