Privacy policy

Last updated: 14 September 2026.

What we collect

• Tool content you type. For browser-only tools such as the spinner wheel, your options stay on your device. If you copy a share link, the options are encoded in the link itself.
• Read Aloud and your browser's voices. Read Aloud speaks with the voices your browser offers, and where your text goes depends on which one you pick. A voice installed on your device speaks without touching the network. A voice marked Streamed — Edge's Online (Natural) voices, Chrome's Google voices — is not installed at all, so your browser sends the text you typed to Microsoft or to Google — or to whichever service that voice belongs to — to be spoken, under their privacy terms rather than ours. Gleekit is not in the path either way: we never receive your text, and we never send it anywhere on your behalf.
• Shared tools, such as Live Poll. These are the tools where other people see what you do, so they are the only ones where what you type reaches a database of ours. When you make a poll we store its question and its choices. When you vote we store which choice you picked, and nothing else — a vote carries no name, and Live Poll never asks for one. Stored next to your vote are two things that are not about you by name: a random token your own browser invented, which is the only reason you are allowed to change your own vote later, and your IP address put through a one-way hash with a secret that stays on our server. We use that hash to stop one person creating a thousand polls an hour. We cannot turn it back into an address, and we never store the address itself. If you report something, we store the reason you typed and the same kind of hashed address.
• Group Card, and the pictures on one. A card stores the recipient's name, what the card is for, and each message with whatever name the person signing chose to put on it — plus the same hashed address and browser token described above. Two things about the pictures. The animated stickers are ours: they are part of the page, they load from Gleekit like the rest of it, and nothing leaves your browser to fetch one. A GIF is different. If this site is set up with a GIF provider, a GIF you pick is linked rather than copied onto Gleekit — so when anybody opens that card, their browser fetches the image from the provider's servers directly, and the provider sees their IP address and their browser's user agent, under their privacy terms rather than ours. We never see it and we never send it to them on your behalf. We do not store what you typed into the GIF search box; the words go to the provider with the search and are written down nowhere here. If no GIF provider is configured there is no search box and no card can carry a GIF at all.
• Gift Pledges, and the money it does not touch. Start with what is not collected, because the tool's name invites the opposite assumption: Gleekit never takes or holds money, there is no payment processor behind this tool, and there is no field anywhere in it for a card number, a bank account, a sort code, an IBAN or a payment link. We could not take a payment if we wanted to. What a pool stores is what the gift is for, a currency label — which we never convert and never add across — an optional target, and one line per person: the name they typed, the amount they said they would put in, and an optional note, plus the same hashed address and browser token described above. The organiser can also mark a line as handed over; that is their note that the money reached them in the real world, and it changes nothing anywhere else. Everybody with the share link can read the whole list, which is the point of it. If a page ever asks you for bank or card details in our name, it is not us.
• When Are You Free. A board stores what you called it, the days you chose, and one entry per person: the name they typed and which slots they ticked, plus the same hashed address and browser token described above. There is no calendar anywhere in this — we do not read one, we do not ask for one, and nothing here is connected to Google Calendar, Outlook or anything else. We also do not work out where you are: the tool converts nothing between time zones, so it never needs to know your zone and never stores one. Your name is on the board beside your answer, which is the point of it, and everybody with the link sees it.
• Memory Board, and the photos on one. This is the only tool on Gleekit that keeps a file rather than a sentence, so it is worth saying exactly what is kept and what is not. A board stores what you called it, and for each photo: the picture itself, the description you wrote of what is in it, an optional caption, and the name you put down — plus the same hashed address and browser token described above. What is not kept is what your camera wrote into the file. A phone records the exact place a photo was taken, along with the time and the camera, and most people have no idea it is there; before anything is sent, your browser redraws the photo at a smaller size and saves it fresh, which discards all of it, and we strip it again on our side so it holds even for a file that did not come through our page. We never see those coordinates and we could not give them to anybody if we wanted to. A photo is not visible to anybody but you until the person who started the board approves it — the file is held somewhere that will not hand it out for a photo nobody has approved, even to someone who knows exactly where it is stored, and what the organiser reviews in the meantime is a small preview. When the board goes, the photos really go: the nightly job that deletes an expired board deletes its files out of storage too, rather than merely unlinking them from a page. There is no archive and nobody here can bring one back.
• An organiser account, if you choose to have one. Nothing on Gleekit needs an account and nothing ever will; the only thing one does is keep what you made from expiring after ninety days and list it in one place. If you sign in we store your email address, because it is how you sign in again, and — where you signed in with Google — whatever Google tells us about that account, which is the address and nothing more. We never email you anything except the sign-in link you asked for: no newsletter, no product news, no reminders. Your address is not shown on any page anybody else can see, is not attached to anything you or anybody else typed into a tool, and is never sent to Google Analytics, to an advertiser, or to anyone else. Signing in also records, on each space you keep, that it is yours — which is a row in our database and is not visible to anybody opening the page. Deleting the account deletes the address and every space on it, immediately and for everybody; there is a button for it on your account page and it is the whole of what it says.
• Local preferences. We store your cookie choice and a list of recently used tools in your browser's local storage. This never leaves your device.
• Analytics. With your consent, Google Analytics collects anonymised usage data (pages viewed, tool events, approximate region). IP addresses are anonymised.
• Advertising. Gleekit shows ads served by Google AdSense. With your consent, Google may use cookies to personalise ads. Without consent, ads are non-personalised. See how Google uses data.

The token your browser holds, and what we could do with it but do not

Your browser holds one random token. It was made up on your device, it is not derived from anything about you, and its only job is to let you change something you wrote — your own vote, in a poll you took part in.

But it is one token, not one per poll. It travels with everything that browser writes, in every space it takes part in. So if you vote in two different polls from the same browser, those two votes carry the same string.

Nothing on Gleekit joins them up. No page shows it, no feature uses it, no report counts it, and it is never sent to Google, to an advertiser, or to anyone else — it goes to our database alongside your entry and nowhere else. We do not build profiles and we have no interest in doing so.

We would rather be straight about what kind of assurance that is. Because the same string sits in both rows, our database could in principle be asked which entries came from one browser, across polls that have nothing to do with each other. What stops that is our undertaking not to do it, not the way the data is shaped. It is a promise about our conduct rather than something we have made impossible, and you deserve to know which of the two it is. Clearing this site's data in your browser discards the token, and the next thing you write starts a new one.

How long we keep it

A poll is deleted ninety days after the last time anybody used it. Deleted means the question, the choices and every vote are removed from our database — and for a Memory Board it means the photo files are deleted out of storage as well, by the same nightly job, rather than merely unlinked from a page. Gleekit has nothing that can put any of it back: there is no archive to restore from and no bin to fish them out of. A poll whose organiser deletes it goes the same way within about a week. The one exception is a page whose organiser signed in to keep it: that one is kept until they delete it, or until they delete their account, and it says so on the page in place of a date. Every shared page shows either its own expiry date or that it has none, so nobody has to take our word for the count.

Cookies

We ask before setting any non-essential cookie. You can change your choice at any time by clearing this site's data in your browser, which brings the banner back.

Your rights

If you have an account, the fastest route is the delete button on your own account page: it removes the account, the address on it and every space you kept, without asking us. Otherwise, and in any case if you are in the EU, UK, or another region with data protection laws, you can ask what data we hold about you and ask us to delete it. Email hello@gleekit.com.

Children

Gleekit is not directed at children under 13 and we do not knowingly collect personal information from them.

Changes

We will update this page when our practices change and update the date at the top.