Privacy policy

1. Who is responsible

The data controller is Elisma, which trades as Slide Roulette. The full details are at the end of this page. Write to support@slideroulette.com about anything on it.

2. Signing in

To host a game, keep a history or buy something you need an account, and an account is an email address. We send you a link to sign in; there is no password. Sign-in and the account record are run by Supabase, on servers in the EU (Frankfurt), and the mail itself is sent by Resend.

We process your email address to give you the account you asked for, which is the contract between us. A display name is taken from the part of the address before the @ and is used nowhere a stranger can see it.

3. Buying something

Payments run through Stripe. You type your card details on Stripe's own checkout page, and we never see them, receive them or store them. For the payment itself Stripe is an independent controller and its own privacy policy applies.

What we keep is what tells us you have paid: Stripe's customer reference, the checkout session reference, the subscription reference where there is one, which product it was, whether it is active, and when it started and ends. We process it to give you what you bought, which is the contract, and we keep the record of the sale because Danish bookkeeping law says to.

4. Playing a game

A player joins a room with a display name and nothing else. No account, no email address, no sign-up. While the room is alive it holds the display names in it, the votes, the reactions and the scores, so that the game can be played. That is our legitimate interest in running the game the room asked for, and it goes when the room goes.

If a signed-in host opened the room, the evening is also written to that host's history: the room, and for each scored talk the presenter's display name, the deck, its topic, the score and how many people voted. That is what the host came for, and it is what the highlight card is made from. Nothing about a player leaves the room and the host's history.

A highlight card is reachable by anyone holding its link, which is a long unguessable address. Share it as widely or as narrowly as you like; we do not list them anywhere.

5. Decks and pictures

A deck or a picture uploaded through the deck studio is stored in our Supabase storage, together with the pages rendered from it, and is used to show slides in a room. Whoever uploads it is responsible for it and warrants the right to share it, as the terms say. Documents are not read for anything except turning them into slides.

6. How we count, and why there is no banner

We measure whether the product works. It matters to us how many rooms are opened, how many people are in one, how long a talk runs, and whether somebody who started a checkout finished it. We use PostHog on its EU cloud, in cookieless mode.

• Nothing is stored on or read from your device. No cookie, no local storage, no session storage. PostHog works out an identifier on its own servers from a salt that changes every day, so it cannot follow you from one day to the next, and there is nothing to consent to storing.
• No free text is ever sent. Not a name, not a room code, not a deck topic, not a slide, not an email address, not a referrer and not the address of the page you are on. The events carry a fixed list of named values and numbers and nothing else, and a test refuses to build the app if one of them could carry a string.
• No IP address is sent as part of an event. PostHog does use the IP address of the request, together with the daily salt and your browser's user agent, to work out that day's identifier, and it does not keep it as data about you.
• If your browser says Do Not Track or Global Privacy Control, nothing happens at all. We do not load the analytics library, so no request is made. That is the opt-out, and it works whatever the law would have allowed.

We rely on our legitimate interest in knowing whether the thing we built works. There is no consent box, because nothing is stored on your device and nothing is asked of you; a dialogue in front of the code box on the front page would cost more evenings than the numbers are worth.

7. Cookies

Two cookies exist, and we use no others. A sign-in session cookie set by Supabase when you sign in, which is what keeps you signed in. And, while the product is in private beta, a cookie holding the beta passcode so you only type it once. Both are necessary for something you asked for. Analytics sets no cookie at all.

8. Who else processes it

Supabase, for the account, the history and the files, on servers in the EU. Stripe, for payments. Resend, for the sign-in email. PostHog, on its EU cloud, for the counting. Vercel, which serves the website, and Cloudflare, which runs the rooms. Vercel and Cloudflare both run servers around the world and a request of yours may be handled by one of them outside the EU; what is stored rather than passed through is stored in the EU.

One more, when the deck-writing feature is switched on: Anthropic, in the United States, whose model writes a deck from the topic a host asks for. It is off at the moment and nothing is sent to it. When it is on, what crosses is the topic, the tone and the language of the deck being asked for — never a display name, an email address, a room code or anything a player typed. The transfer out of the EU rests on Anthropic's data processing addendum and the European Commission's standard contractual clauses, and the terms say the same thing from the other side: a deck written on demand is written by an AI model.

9. How long it is kept

• Your account and its history, until you ask us to delete it. Write to support@slideroulette.com and it goes.
• A room, 24 hours after the last thing that happened in it. Then its storage is deleted, display names and all.
• The record of a sale, five years from the end of the financial year it falls in, because the Danish bookkeeping act says so. That record is the one Stripe holds and the one in our accounts. It is not the row in our own database: the entitlement is attached to your account and is deleted with it, which is why deleting an account also ends any subscription it was carrying. Ask us to delete the account and the app forgets you; the bookkeeping keeps the sale, because it has to.
• Analytics events, under an identifier that changes every day and is not tied to you.

10. Your rights

Under the GDPR you may ask us for:

• a copy of what we hold about you, and to have it corrected if it is wrong;
• deletion of it, or that we stop using it for a while;
• it in a portable form, or sent to somebody else;
• that we stop processing it where we rely on a legitimate interest, which includes the counting above.

Write to support@slideroulette.com. We answer within a month.

You may also complain to the Danish Data Protection Agency: Datatilsynet, Carl Jacobsens Vej 35, 2500 Valby, Denmark (datatilsynet.dk).

11. Children

Slide Roulette is not directed at children under 13 and we do not knowingly collect anything about one. A player joins a room with a display name and no account, so nothing about a player who is a child reaches us beyond that name and what they did in the game. If you believe a child has an account here, write to support@slideroulette.com and we will remove it.

12. Changes to this policy

We may change this page. A change is announced here, and the date at the top is the date the version you are reading took effect.