Privacy | klapp

Who is responsible

klapp is run by Cadence AS (org. no. 912 024 652), Svaneviksveien 13, 5063 Bergen, Norway, which is the controller for the processing described here. Write to hello@playklapp.com about anything on this page. On 28 September 2026 the controller changed from the founder personally to Cadence AS; nothing else about the processing changed.

This page describes what the service does today, read from its own code on the date above. When something changes, the date changes and we say what changed.

This page is also available in Norwegian: Personvern på norsk.

What changed on 11 October 2026. This page now describes the subscription (Lærer, Team and Bedrift), the confirmation we send when it starts, the pack of 100 questions, and the sale outside Norway through Link. It also says that deleting the account ends a running subscription at once, with a refund of the unused time for a subscription bought in Norway. Before, the page described card payments only for Q&A and the event package. The event package is now described as sold until the subscription opens.

Also on 11 October 2026, after a read-through against the law by an AI, not a lawyer: the controller's address, how long the customer record at Stripe stays, which part of Stripe's agreement sets out the safeguards for the transfer to the United States, and that we make no automated decisions about you.

What changed on 12 October 2026. If you are signed in as a host, the rounds you open are now saved on your account until you delete them. Before, this page said that nothing about a round is stored on our side. That still holds for a host who is not signed in. From the same day a saved round also keeps how it went, as numbers for the round with no names, also for a game with only a few players, and you can fix or drop a question in a saved round. It is described under “Your rounds on the account” below.

Corrected on 13 October 2026. This page said that a game lives only in the server's memory and that everything is gone if the server restarts. Since 8 October 2026 a game that is running is also written to a file in our storage, so that it can go on after a restart. A quiz inside an event goes on in the same way. What the file holds and when it is deleted is described under “A game while it runs” below.

Changed on 13 October 2026. A subscription bought in Norway is now paid on our own page, in card fields that Stripe runs, and no longer on Stripe's checkout page. The button there is ours and says that the order obliges you to pay. Stripe's script is loaded when you open that step, and only then, and it sets two cookies of its own. “If a host pays”, “The subscription” and “What your browser holds” below say so. On the same day we started looking up the country a subscription purchase comes from. It is the lookup we already use when a game starts: two letters, found in memory from the address, which is then discarded and never stored or logged. It decides whether you buy in Norway from us or outside Norway through Link. “If you buy from outside Norway” below says so.

Changed on 13 October 2026. The event package stays on sale after the subscription opens. An event can also hold a few lines of programme and links to material, written by the host. They are described under “If a signed-in host creates an event” below.

Changed on 14 October 2026. While a game is being played, its file now also holds the hash and the start time that our log line for that game carries, so that a game that goes on after a restart still gets its closing line in the log. “A game while it runs” below says what that means.

Changed on 14 October 2026. Before an event ends, its host can download a file with the results of its polls and quizzes and the questions from the room, which klapp holds in memory until the event ends; “An event” below says what the file holds.

Changed on 14 October 2026. A host can share a moderator link for the questions from the room, and a poll can now be a word cloud or a free-text answer. “Questions from the room” and “An event” below say what each of them holds and for how long.

Changed on 14 October 2026. A subscriber can now upload a logo and pick a colour for the big screen. This page now also says what the Friday quiz on a subscription keeps on the account: the settings, the company name, the logo and the colour. It is described under “The Friday quiz on a subscription” below.

Changed on 14 October 2026. The logo and the colour a subscriber picks are now also shown on the big screen of their events, polls and Q&As. Nothing new is stored; “The Friday quiz on a subscription” below says what is kept.

Changed on 14 October 2026. The file a host can download from an event now also holds the words and free-text answers people wrote in its polls, except those the host hid, and it can be saved as an Excel file or a PDF as well as a web page. “An event” below says what is kept and for how long.

Changed on 14 October 2026. “Players never have an account” no longer says that your e-mail address and your name live only in the sign-in cookie: they also go to Stripe when you add a card or buy something. It now also names the cookie we set only on our own browsers.

Changed on 15 October 2026. An organiser can now take registrations for an event at klapp. If you register, we store your name and e-mail address for the organiser. “If you register for an event” below says what is kept, who is responsible and when it is deleted. Nothing changes for the people in the room.

Changed on 17 October 2026. We can give away Business for a period with a gift code. “What we hold” now says what is stored when you redeem such a code, and that it is deleted with the account. Nothing changes for the people in the room.

Changed on 17 October 2026. In a room with children, a host can now upload a file when they confirm that it is teaching material with no personal data, such as pages from a textbook. Before, file upload was switched off in a room with children. “Files you upload” and “Children” below say what applies. Files are still never stored.

Players never have an account

Players never sign in, and we hold no list of who has played. If you register for an event, the organiser gets a list of who registered; see “If you register for an event” below. A host can run a quiz without signing in too. There are no analytics scripts and no advertising on this site or in the game.

If a host signs in. Sign-in is with a Microsoft or Google account, whichever the sign-in page offers. We never see a password. From the provider we receive an identifier for your account that only klapp gets, your e-mail address, whether the provider confirms that address, and your name.

We put exactly that into one cookie, __Host-klapp_okt, signed so it cannot be changed. It lasts 14 days or until you sign out. There is no account database. Your e-mail address and your name are also sent to Stripe when you add a card or buy something, because they appear on the receipt. If you have not saved an event, signing out and letting the cookie go is all there is to delete. While you are at the provider, a second cookie, __Host-klapp_inn, holds random values that stop someone else's sign-in from being slipped into your browser. It lasts at most ten minutes and is removed when you are back.

For each sign-in we log which provider it was and whether it worked, kept for 30 days in Microsoft Azure Log Analytics in Norway East. Not your e-mail address, your name or the identifier. Both cookies are needed for sign-in to work at all, so we do not ask for consent to them. We also set __Host-klapp_intern in the browsers of the people who work on klapp, so their visits are not counted. It holds no identity.

If a signed-in host creates an event. Since 3 October 2026 an event is saved on our server, so that it is still there when you come back and its code and screen links keep working. We store what you put into it: the title, your choices, the quizzes and polls in its running order, a few lines of programme and links to material if you add them (shown to everyone with the code), and whether the event package was bought for it. We also store the account identifier and which provider it came from, so that only you can list, open and delete your events. Not your e-mail address, not your name, and nothing about players: no names, no answers, no results. Registrations are stored apart from the event, as described under “If you register for an event” below. Events are held in Microsoft Azure Storage in Norway East. A draft is deleted when it has not been changed for 180 days, and a finished event 30 days after it ended. To have an event deleted sooner, write to hello@playklapp.com with its title or code. Deleting your account deletes all of them at once, as described below.

If a host pays. You type your card on a page run by our payment provider, Stripe, or, for a subscription bought in Norway, in card fields that Stripe runs inside our page. Either way the card number goes straight to Stripe, never to klapp, and we never see or store the card number. When you first add a card or start a subscription, we create a customer record at Stripe with your e-mail address, your name, and the sign-in provider and account identifier described above. That record is how we find your card and your subscription again without an account database. It stays until you delete your account, apart from the payment records described below. To show you which card is saved, we ask Stripe for its brand, last four digits and expiry date each time. We store none of it.

What is charged to a saved card. Q&A, 100 more answers and the pack of 100 questions are charged to the card you saved, when you press the button. So is the event package. Stripe keeps the amount, the date and a reference to the session, the event or your account.

The subscription. In Norway you start it on our own page: Stripe shows the fields for your card and your billing address there, and you press our button to order. To show those fields the page loads Stripe's script (js.stripe.com) when you open that step, and not before. Outside Norway you start it on Stripe's checkout page, where you give your card and your billing address. Stripe then holds the subscription on your customer record: the tier (Lærer, Team or Bedrift), monthly or yearly, the price, when it started, the current period, whether you have cancelled, each invoice and payment, and the billing address. With it we store the time you ticked the box at our button, which version of that text you saw, the organisation number if you buy for a business, and when we sent you the confirmation described below. Stripe charges the card at each renewal until you cancel. You change the card, see invoices, switch tier or cancel in Stripe's customer portal, which you reach from your account page. What you do there is held by Stripe. When the service needs your tier, we ask Stripe and keep the answer in the server's memory for at most five minutes, or for at most one day while Stripe cannot be reached. Nothing about the subscription is written to our own storage. Cadence AS can see the e-mail address, tier, price, start date and status of paying subscribers on a read-only administration page that reads them from Stripe when it is opened. The page keeps the answer in the server's memory for at most ten minutes and writes nothing to our storage or logs.

For each payment we log its kind (session, extra answers, pack of questions, event package or refund), the amount and the outcome, kept for 30 days like the lines above. For the subscription we log the tier and period chosen at the button, and each change Stripe reports (started, renewed, payment failed, cancelled, refunded) with its outcome. Never the customer, the account or the amount. Not your name, e-mail address, card or customer record. You can remove the card or delete your account in the portal. Deleting the account first deletes every event you saved, drafts and finished ones, and every round saved on the account, then the customer record and the card at Stripe, and signs you out. Deleting the account also ends a running subscription at once. If you bought it in Norway, we refund the unused part of the period you have paid for, pro rata, before the customer record is deleted. Quota you have already used is not deducted. If the refund fails, nothing is deleted and you can try again. If you bought the subscription through Link outside Norway, Link is the seller and we do not refund from here: cancel it in the portal first, and ask Link for any refund. If the events cannot all be deleted, the portal says so, the customer record is left in place and you stay signed in, so you can try again. Payments already made stay in Stripe's records and in Cadence AS' accounts, as the Norwegian Bookkeeping Act requires: for five years after the end of the accounting year. So do the invoices for the subscription at Stripe, and our copy of each confirmation and credit note, described below. Deleting the account does not delete those.

When a host buys something. Before you pay, you tick a box asking us to start delivery. The time you ticked it is stored with the payment or the subscription at Stripe, next to the amount and what you bought, so that we can show what was agreed. For each purchase charged to your card, and each refund, we send a confirmation to the e-mail address of the account you signed in with: it is your receipt, and it says how to withdraw. We read the address and your name from the customer record at Stripe when the e-mail is sent. When you add a card, Stripe asks for a billing address. It is printed on the confirmation, because a sales document must name the buyer, and its country and the card's country decide whether we can sell to you. We sell directly only to buyers in Norway. Outside Norway, see below. We keep one copy of each confirmation and credit note, as text and as a PDF, with your name, billing address and e-mail address, in our storage in Norway (Microsoft Azure, Norway East). It is accounting material that the Norwegian Bookkeeping Act requires us to keep for five years after the end of the accounting year, and deleting your account does not delete it. The receipt number is also stored with the payment at Stripe. The log gets one line saying that a confirmation was sent or failed, with no address. The e-mail is sent through Microsoft Azure, which keeps the e-mail data at rest in Norway. If you say you are buying for a business, you give its organisation number. We look it up in the Norwegian register of legal entities (Enhetsregisteret, at Brønnøysund) to get the name, and from 1 January 2027 also in the Peppol network, to see whether the business receives e-invoices. The number and the name are stored with the payment at Stripe and printed on the confirmation. The number of a sole proprietorship points to a person. It is never written to the log. Confirmations started on 4 October 2026. A purchase made before they started did not get one.

When a subscription starts. Stripe sends a receipt by e-mail for each payment of the subscription, renewals included, to the address on your customer record. When a subscription bought in Norway starts, we also send one confirmation to that address. It says what you bought, the price, when the next charge is, how to cancel and how to withdraw, and it has a withdrawal form. We read your name, e-mail address and billing address from Stripe when it is sent. We keep no copy of it. Stripe records that it was sent and which version of the text it was. The log gets one line saying that it was sent or failed, with no address.

If you buy from outside Norway. When that sale is open, the subscription and the pack of 100 questions are sold outside Norway through Link, a Stripe company, which is then the seller to you. Which way you buy a subscription is decided by the country the purchase comes from. Our server looks it up in memory from the address, as two letters, and discards the address: it is never stored or logged (this product includes GeoLite2 Data created by MaxMind). The country you choose only picks among the countries outside Norway. We guess it in your browser from its time zone and language, and you can change it. Your choice is kept in your browser, described below. It goes to our server with the question about prices and with the purchase, and is neither stored nor logged there. If a subscription is paid in the Norwegian checkout with a card or a billing address from another country, which we read from Stripe, we cancel it at once and refund the whole amount. You pay on Link's checkout page. Link collects the payment, the VAT or sales tax and what it needs for that, such as your address and how you pay, and sends you the receipt. For that, Link is responsible itself, under its own privacy policy, which it shows at checkout. A subscription or pack bought this way is held in our Stripe account on the same customer record as above, and we read it the same way. We do not send our own confirmation for it, because Link is the seller.

What we hold

A game while it runs. Questions, answers, scores, nicknames and any prizes the host typed live in the server's memory while the game runs. So that a game can go on after the server restarts, the same state is also written to a file in our storage (Microsoft Azure Storage in Norway East), one file per game, updated as the game moves on. The file holds what the game holds in memory: the questions with their answers, the nicknames, each player's score and current answer, the prizes, and a random key for the host and for each player that lets them back into the same game. It has no IP address, no e-mail address and no name other than the nicknames. If a signed-in host plays a round from their account, the file also holds a key that ties the game to that account's folder and to the round, so the result can be added to the round. The key is a hash, not an e-mail address or a name, but someone who can read our storage can see which account folder the game belongs to for as long as the file exists. While a game is being played, the file also holds the hash and the start time that our log line for that game carries (see “A game, from start to finish” below), so that a game that goes on after a restart still gets its closing line; someone who can read both our storage and our log can match that log line to the game for as long as the file exists. The file is deleted when the game ends. The game itself is deleted from memory ten minutes after it ends, or after two hours without activity, and then the file goes too. If the server stops and nobody returns to the game, the file is left until the server next starts or someone tries the code; a file more than two hours old is then deleted without being read. A generated set nobody has opened yet is kept in memory for up to two hours. A signed-in host's own rounds are also saved on the account, described under “Your rounds on the account” below.

Nicknames. Every player is handed a name. A player can type their own only when the host has said the room is adults only, which is not the default; in a room with children, typed names are ignored. The name lives in the game and in the player's own browser, never in a log.

Teams in the Friday quiz. A subscriber who plays the Friday quiz in teams keeps the team names on their account. Each player picks a team on their own phone; the phone remembers the last team in its own browser storage, and we keep no player account. When a game reaches the podium we store, on the subscriber's account, the week, each team's score and place, and the nicknames of the players who played for each team, so the season standings can show who was on the team that week. At a workplace a nickname can point to a person. The nicknames are kept for the current and the previous season (a season is a calendar quarter) and then removed; the scores stay for two years. The subscriber can delete the teams and the whole history at any time, and deleting the account deletes them too. Who answered what is never stored.

The Friday quiz on a subscription. A subscriber on Team or Business can choose the number of questions, the topics and the language, swap questions, write a company name, upload a logo and pick an accent colour for the big screen. The logo and the colour are also shown on the big screen of the subscriber's own events, polls and Q&As. We keep the settings, the company name and the colour in one file per account, named by a hash, and the logo in a file of its own, named by the same random number as its address, in our storage in Norway (Microsoft Azure, Norway East). The logo is redrawn in your browser before it is sent, as a PNG or WebP image of at most 600 × 300 pixels; an SVG file is never stored. The big screen fetches the image from an address with a random number that says nothing about your account, so anyone who has that address can see the logo, as anyone in the room can. Replacing or removing the logo deletes the old image. Deleting the account deletes the settings, the company name and the logo.

Gift codes. When you redeem a gift code, we store a marker with an unrecognisable account identifier (a hash, not your e-mail address or your name) and the end of the period, so Business applies until that day. We do not store the code itself: we store only when it was issued, when it expires and that it has been used, under a hash. If the code was made for an organisation, we store a hash of the organisation number and domain, never in plain text, so that the same organisation does not get a second code. The marker is deleted when you delete the account; the code stays used. When we make a code, we may add a short note on which organisation it is for (never a name or e-mail address), and the note is deleted 30 days after the code expires, or sooner if the account that redeemed it is deleted.

Rounds of your own. Since 11 October 2026 rounds of your own start with 50 free trial questions per signed-in account, and 10 without signing in. For a signed-in host we keep, on the account, how many trial questions are used, how many questions were used this month, how many bought questions are left, and the payment reference of each pack of questions at Stripe, so the same payment never gives rounds twice. The server keeps it in one file per account, named by a hash, with no IP address. No topic, no text and no e-mail address. Deleting the account deletes it. For a host who has not signed in, the count lives only in the server's memory and is gone at the next new version of the service. Since 13 October 2026 the 10 trial questions are counted per browser and not per network: your browser makes a random value (klapp:prove, under “What your browser holds” below) and sends it with the request, and the server keeps the count under a salted hash of that value. The value itself is never stored on our side and never logged. So that nobody can get new trial questions by swapping the value, the server also counts trial questions per network for 24 hours, at most 50, under the same scrambled key as the hourly limit. If your browser blocks storage, the count is per network only. The IP address is never stored.

Playing a round again. When you open a round of your own, the questions and a signature from our server are saved in your own browser, so you can play the same round again, for another class for example. At most five rounds are kept, each for at most seven days, and you can delete them under “your rounds” on the page where you start a game. If you are signed in, that list shows the rounds on your account instead; the copy in the browser is still removed after seven days. When you play one again, your browser sends the round back, our server checks the signature and opens a new game. If you are not signed in, nothing about the round is stored on our side.

Your rounds on the account. If you are signed in as a host, each round you open is saved on your account: a set we generated for you, as you opened it after reading it through, or a set you wrote yourself. The file holds the title, the topic, the questions with their answers, and when the round was made, saved, last edited and last played again. It is kept in one folder per account, named by a hash, with no e-mail address, no name and no IP address. The same file holds how the round went, as numbers only: how many games were played with it and how many players took part in all, how many answers were given and how many were correct. For a game with at least eight players it also counts answers and correct answers for each question. A game with fewer players adds to the totals for the round only. Nothing about a single player is saved: no nicknames, no scores, no podium, and never who answered what. In a small game the host may know who the players were, so the share of correct answers for that game can point to them. There is no limit and no expiry: a round stays until you delete it or delete the account, and the numbers go with it. You find the rounds under “my quizzes” in the portal, where you can play one again, fix the text of a question, drop a question, or delete the round. A fix replaces the saved text, and the earlier text is not kept; the answer counts for a question you fix start again from zero. Playing one again opens a new game from the saved file, from any browser you are signed in on. Deleting a round removes the file, and the copy in the browser you delete it from; a copy in another browser is removed there after seven days at most. We save it so that you can find it again, and we use it for nothing else. The demo set, the ready-made sets and the Friday quiz are not saved this way.

Page visits. For each page request we log the path, which kind of page it was, and the browser's user agent. Not the IP address, and not anything after a question mark in the address.

The marketing pages: the view and the click. For a request for one of these pages (the front page, /quiz, /fredag, /pricing and the others, but not the app) we also log one line with the path, the browser's main language such as “en” — never the region — the page name in the link if the address carried one of our own, and the domain of the site the link was on, taken from the Referer header and cut to its host name: “google.com”, never the page or the search there. A browser that calls itself a crawler is left out. When you follow a link from one of these pages to start or join a game or to our shop, we log one line with the page the link was on and where it led. Neither line holds the user agent, the IP address, a cookie or anything after a question mark in the address, and nothing is stored in your browser.

A game, from start to finish. When the host starts a game we log one line with the kind of set (the demo, a generated set, the host's own, a ready-made one, or the Friday quiz), how many players were in the room at that moment, whether a big screen was connected, the country the host is playing from (two letters, such as NO, looked up in memory from the address, which is then discarded: the address itself is never stored or logged; this product includes GeoLite2 Data created by MaxMind), and a hash of the room code made with a random salt that is never written down, so the two lines of one game can be read together without the code ever being logged. When the game reaches the podium, when the host ends it, or when it expires, we log one line with how many questions were played of how many, how many answered the last one, how long it took and how it ended, plus a list of how many questions each player answered, largest first, with nothing to tie a number to a person. The start line also carries which of our pages the game came from. Counts for the room, never a name, a score or who answered what.

Which page a game came from. The “Start a game” links on these pages carry the name of the page they sit on, for example /host?fra=quiz. When a host creates a game from that link, the line we log for the new game holds that page name and nothing else. A name that is not one of our own pages is logged as empty. It is a rough proxy for which pages lead to games, not a record of who came from where: it only sees a host who clicked the link and created a game in the same tab, no cookie is set, and nothing is stored in your browser.

The link to our shop. A game played from one of our ready-made quizzes ends with a line pointing to playklapp.com/etsy, which sends you on to our shop on Etsy. Each time that address is opened we log one line saying so and, if the link on a phone was tapped, which ready-made quiz it came from. Not the IP address, not the browser, not the game code, and no cookie is set. What Etsy holds once you are there is described by Etsy, not by us. If you buy a ready-made quiz there, Etsy is responsible itself for what it holds about you. We see your order in Etsy's seller pages: the name on your Etsy account, what you bought, and anything you write to the shop. We use that to answer you and to keep our accounts, and for nothing else. The legal basis is that we need it to deliver what you bought and to answer you, under Article 6(1)(b) of the GDPR, and, for the accounts, the Norwegian Bookkeeping Act, under Article 6(1)(c). Etsy's monthly files of orders, sales and payouts, which include your order, are kept with our accounts for five years after the end of the accounting year. Messages you send to the shop are deleted from our shop's inbox 12 months after the last reply, unless they document a sale or a refund; those are kept with our accounts for five years after the end of the accounting year. We do this by hand every three months, so a message can stay up to three months longer. Etsy keeps its own copy under its own policy.

The Friday quiz by e-mail. If you type your e-mail address on the Friday quiz page and choose a language, we store the address, the language, the time you signed up and whether you have confirmed, and nothing else. We first send one e-mail asking you to confirm the address; the sign-up counts only after you click the link in it, and an address that is not confirmed within seven days is deleted. From then on we send one e-mail every Friday at 07:00 Norwegian time with the link to that week's free quiz in your language, one sample question, a link to switch language and a link to unsubscribe. Unsubscribing deletes the address at once; we keep no list of former subscribers. Nothing about who plays the quiz is tied to the address. The addresses are held in Microsoft Azure Storage in Norway East, and the e-mails are sent through Azure as described below. The log gets one line per sign-up, confirmation, unsubscribe, language change and weekly send, with the language and a count, never the address. To keep robots from filling the form, the server checks a hidden field no person sees, a signed time stamp it put on the page, and how many sign-ups come from the same sender: for that it keeps, in memory only, a hash of the sender's network address with the day and a key that changes at every restart, together with the times of that day's sign-ups. The hash is not stored, not logged and not tied to the address you type, and it is gone within a day. A sign-up the check stops is logged with the reason only. The legal basis is your consent, under Article 6(1)(a) of the GDPR, which you withdraw by unsubscribing.

The host's language, counted per day. When a game is created, the host's browser sends its main language, such as “en” — never the region. The server adds one to a count for that language, in memory. When the first game of a new day (UTC) is created, or when the server restarts, it logs one line per language with the date and the count so far, and starts again from zero. The count is not attached to a game, a time of day, a name or an address. We use it to decide which languages the site should be translated into.

Whether a room mixes languages, counted per day. When a player joins, their browser sends its main language, such as “de” — never the region. The game keeps, in memory, the set of languages of players joining for the first time, and stops at two: it never records which player had which language. When the game reaches the podium, the server adds one to the day's count of finished games. If it saw two languages, it also adds one to the count of mixed games; if no player sent a language, it adds one to the count of games without one. These numbers are logged in one line per day (UTC), next to the day's totals of games created, started and finished, players, questions and answers, with no game code, name or time of day. The set is gone with the game. We use it to decide whether players in one room should be able to play in different languages.

The sign-in line, counted once per visit. The page where a host makes a quiz shows one line offering to sign in, to anyone who is not signed in. You can ignore it and start a quiz as before. We log one line with one of two words: that a host signed in from that line, or that a host who had seen it went on without signing in. The line carries nothing else: no provider, no name, no address and no game code. We use it to check that the offer does not get in the way of starting a quiz.

These lines are kept for 30 days in Microsoft Azure Log Analytics in Norway East, like the lines below.

IP addresses. To stop one machine from running up our model costs or flooding a Q&A, the server reads the address the request came from and turns it into a salted hash in memory. The salt is random and never written down, the hash is used for a one-hour window and dropped after that (for 24 hours where it counts the trial questions made from one network, described under “Rounds of your own”), and neither the address nor the hash is logged.

The topic you type. When a set is generated we log the topic (at most 80 characters), the language, the room settings you chose and what the generation cost. When a game ends we log the topic, the number of questions and players, how many times questions were flagged, and how many answered each question and how many of those were right. These are counts for the room, never who answered what, and in a room of fewer than eight only the totals for the whole set are kept. No names, no pasted text. These lines are kept for 30 days in Microsoft Azure Log Analytics in Norway East, and in a file inside the server that is deleted whenever it restarts; that file also keeps the model's own notes on questions it dropped.

Stars and comments after a game. When a game is over, the host and the players can give the quiz one to five stars and, if they want, write a comment of up to 280 characters. Nothing asks twice, and the game goes on without it. We store the stars, the comment, which quiz it was (and, for a generated or self-written quiz, its questions and answers, so we can read what the room reacted to), the language, the week, and how many were in the room. Not who gave it: no nickname, no game code, no IP address, and nothing that links it to a browser or a person. E-mail addresses, phone numbers and links in a comment are replaced with a marker before it is stored. Please do not write personal details about yourself or others in a comment. The files are held in Microsoft Azure Storage in Norway East for 12 months, and we delete a comment on request: write to hello@playklapp.com with roughly when the game was played and what the comment said. The log gets one line per rating with the stars, the role and the kind of quiz, never the text.

Files you upload. A file is only used after the host confirms that the content is theirs to share and holds no personal data about other people. In a room with children, or when the host has not said the room is adults only, a file is accepted only when the host also confirms that it is teaching material, such as pages from a textbook or test instructions, with no names, pictures of people or other personal data. Word, Excel, PowerPoint and plain text are read on our server in memory. A PDF or an image is sent to Anthropic to have its text written out. Before it is sent, we remove a photo's location, camera details, date and caption or author fields, and a PDF's title, author, subject, keywords, creating program and XMP metadata, including those details in JPEG photos inside a PDF. What is visible on the page is sent as it is, and comments and attachments in a PDF stay in. A locked PDF, or one we cannot rewrite, is sent unchanged. The file name is never sent. We never write a file to disk or to a log; we log only its type, size, how many characters came out, and whether it was refused. The extract is cut at 12 000 characters and shown to the host before anything is generated. Pasted text needs the same confirmation before a set is made from it, in every room.

Q&A material. A speaker who prepares a Q&A adds slides, a document or pasted text, under the same confirmation as the files above, and a PDF has the same metadata removed. The material lives only in the server's memory, tied to that one Q&A session, and is never written to disk or to a log. It is deleted when the host ends the session. If nobody ends it, it is deleted six hours after the session opened to the audience, or one hour after a draft was started if it never opened, and in every case when the server restarts. Pages the host leaves out are removed on our server and never sent anywhere. The pages that are kept are sent to Anthropic with each question, so the answer suggestion can quote them; Anthropic holds them in a temporary cache for up to one hour after the last question.

Questions from the room. The audience needs no account and gives no name. A question is shown to the room, unless the host approves questions first, and is sent to Anthropic together with the material to find an answer suggestion that only the host sees, and a moderator if the host shares a moderator link. A moderator link lets the person the host sends it to approve, hide, pin and mark questions answered in that one Q&A, and see the suggestions. The moderator needs no account, and we store nothing about them. The link stops working when the host makes a new one or turns it off, and when the session ends. Questions and votes are deleted with the session. The host can download the questions with their votes before ending; that file is made in the host's browser and we never see it. We log, for each question, only which kind of suggestion was shown and what it cost, and for each session the tier, the number of answers, the total cost and the size of the material. Never a question, an answer, the material or the session code.

An event. A host who is signed in can put quizzes, polls and a Q&A under one code for a whole talk. The event holds the title the host typed, the activities the host ticked, and which one is running. It is saved as described under “If a signed-in host creates an event” above. While it runs it is held in the server's memory: it stops when the host ends it, after two hours without activity or after twelve hours at most. A poll or a Q&A that was running inside it is gone if the server restarts. A quiz that was running is not: it is saved like any other game, as described under “A game while it runs” above, and goes on inside the event. Ending an event ends its Q&A, so the Q&A material and the questions are deleted then too. A quiz inside an event is deleted like any other game, or when the host goes back to the waiting screen. An event can also hold a running order: quizzes the host has read and polls the host has written. They are the host's own text, kept with the event and deleted with it. A poll is a question with options to tap, a word cloud (up to three short words each) or a free-text answer (up to 140 characters). Answers are kept only in the server's memory, are never linked to a name, and the host can hide a word or an answer from the screen. For options, the count per option is kept until the event ends, so the host can download it. Words in a word cloud, with how many wrote each one, and free-text answers are kept in the same way, in memory only and never with a name. A word or an answer the host hid is not kept, only how many were hidden. All of it is gone when the event ends or the server restarts. Do not type personal data into a free-text answer: it is shown to the room if the host lets it through. While a poll is open, the server holds which option each phone chose, tied to the random identifier below and never to a name, so a second tap replaces the first. When the host shows the result, that link is forgotten and only the number of answers for each option remains. Those numbers are kept until the event ends, as described below. Until the host shows the result, the big screen shows only how many have answered. To use a phone as the remote control, the host scans a QR code shown on their own screen. The code works once, for five minutes, and the phone then holds the same key as the laptop. We log, for each event, only how it ended, which kinds of activity it used and how long it lasted. Never the title, the code, who held it, or any answer.

Before an event ends, its host can download a file of what the event held: the result of each poll (counts only, never who answered), the words and free-text answers people wrote, except those the host hid, the questions from the room with their votes, and the top ten nicknames and scores of each quiz. The file can be a web page, an Excel file or a PDF. klapp keeps these in memory only until the event ends, the file is made in the host's own browser, and klapp keeps no copy.

If you register for an event

An organiser can take registrations on the event's own page at klapp. If you register, we store your name, your e-mail address and the ticket type you chose. We also store whether the registration is active or cancelled, when it was made, when the ticket was sent and when you first signed in with the link. We do not ask for an address, a phone number, a date of birth or anything else.

Who is responsible. The organiser is the controller for the registrations. Only a business with an organisation number can take registrations, and Cadence AS processes them on the organiser's behalf under the data processing terms. The organiser sees the list of who registered and can download it. Questions about your registration go to the organiser, and we help the organiser answer. You can also write to hello@playklapp.com. Cadence AS is itself responsible for the log and for stopping misuse of the registration form.

E-mail. We send your ticket by e-mail from playklapp.com on the organiser's behalf. Otherwise we send only sign-in links you ask for, changes to the programme and word of a cancellation. You get no newsletter, and klapp sends you no advertising. The e-mail goes through Microsoft Azure, which keeps the e-mail data at rest in Norway.

Signing in without a password. To see your ticket, you ask for a sign-in link. The link works once and for 30 minutes, and we store only a hash of it. The answer is the same whether the address is registered or not, so nobody can use the form to find out who has registered. The link gives you a cookie of its own, __Host-klapp_billett. It holds a number for the registration, not your name or your e-mail address, and it lasts until the day after the event, 30 days at most.

In the room you are anonymous. When you go into the room, you are anonymous like everyone else. Questions, answers, nicknames and scores are never linked to your registration. What is kept from the room is described under “An event” above.

How long. Your name and e-mail address are deleted 30 days after the last day of the event, and the organiser can download the list before then. The rest is deleted 180 days after the last day, because questions about a registration can come long after the event. That is the registration number, the ticket type, the status and the times. If you cancel your registration, your name and e-mail address are deleted at once. All of it is stored in Microsoft Azure Storage in Norway East, one file per registration. It is never stored with the event and never in the log. The log gets one line for each registration, cancellation, sign-in link and e-mail, with no name, address or link.

Protection against misuse. The form must not be usable to send e-mail to strangers. So the server counts registrations per sender and per e-mail address, with a hash that exists only in memory. It is not stored, not logged, and it is gone within a day.

Age. The organiser sets an age limit, and the default is 18. If you are under 18 and the organiser allows it, you tick a box saying that your parents know you have registered.

The legal basis. The organiser decides the legal basis. For a registration it is usually that the data is needed to give you the place you asked for, under Article 6(1)(b) of the GDPR.

What your browser holds

The game stores a few things in your browser's local storage. The only cookies we set are the two sign-in cookies above, and only if a host signs in, one more that only we set on our own browsers, and one that is set only when someone who registered for an event signs in with the link we e-mailed. If a host opens the subscription checkout, Stripe's script sets two cookies of its own there, __stripe_mid (one year) and __stripe_sid (30 minutes), which Stripe uses to stop fraud. They are not set anywhere else on klapp. Our own extra cookies:

__Host-klapp_intern — tells our own browsers apart from visitors, so our own checks and tests are not counted as visits or games. It is set only when someone opens a link we use ourselves (/?intern=1), holds the value 1 and nothing else, is the same in every browser that has it, and lasts 400 days or until /?intern=0 removes it. A visitor who never opens such a link never gets it. The lines we log for that browser carry one extra field, intern, and nothing more.

__Host-klapp_billett — set only when someone who registered for an event signs in with the link we e-mailed. It holds the number of the registration, never a name or an e-mail address, and lasts until the day after the event, 30 days at most.

klapp:okt: plus the game code — a random key that lets you rejoin the same game, and the name you typed if you typed one. Ignored after three hours and removed the next time the game opens; at most three games are kept. klapp:siste — the last game code, to fill in the join field. klapp:utkast — a host's own questions while they write them, until they start the game or clear the list. klapp:runder — up to five rounds of your own that you opened, with our server's signature, so you can play them again. Each is deleted after seven days, and you can delete it sooner. klapp:minekoder — for a signed-in host who plays a round from their account again: which of the last five game codes belonged to which saved round, so the end screen can offer the same round once more. It holds the round's identifier and the code, never the questions. klapp:tilbud-utkast — if you press a sign-in button on the page where you make a quiz, what you had filled in (the topic, your choices, prizes and any text you pasted) is kept in this tab so it is still there when you come back. It is read once and deleted, it is ignored after ten minutes, it goes when the tab closes, and it is never sent to us. klapp:tilbud-talt — the value 1, in this tab only, so the count described under “The sign-in line” above happens once per visit. klapp:prove — a random value your browser makes the first time you open a page where you can make a quiz of your own without signing in, so the 10 free trial questions are counted for your browser and not shared with everyone on your network. It holds nothing about you or your browser, it is sent only to our server, which keeps a salted hash of it in memory and nothing else, and it stays until you clear your browser's storage. It is never made if you are signed in. klapp_land — the country you chose on the pricing page or at a buy button, as two letters, so the next page shows prices for the same country. It stays until you clear your browser's storage.

klapp.qa.vert — a random key that lets the host's browser run the Q&A they are preparing or holding. It means nothing once the session is deleted. klapp.arr.vert — a random key that lets the host's browser, on the laptop or on the phone used as the remote control, run the event they created. It means nothing once the event is deleted. klapp.qa.deltaker — a random identifier for an audience member's browser, so a vote or a poll answer counts once and your own questions show what happened to them. It is never linked to a name.

Who else receives anything

Anthropic writes the quiz questions and the Q&A answer suggestions. It receives the topic, any text you paste, and the extract or the file, with its metadata removed, when you upload one. For a Q&A it receives the pages the host kept, the topics the host blocked, and each question from the room. When the host asks for a “new round on what you missed”, it receives the questions and answers in the set, also a set the host wrote, and the room's numbers per question: how many got it right and how the answers were spread. It never receives player names, or who asked or answered what. Our contract is with Anthropic Ireland Limited. The processing happens at Anthropic in the United States and with its cloud providers, whose location Anthropic gives as worldwide. Anthropic's commercial terms say it may not train models on customer content.

How long Anthropic keeps it. Anthropic says it deletes what we send, and what it writes back, within 30 days. If its automated safety systems flag a request as breaking its usage policy, it may keep that request for up to two years and the classification score for up to seven. Its data processing addendum covers transfers out of the EEA with the EU standard contractual clauses. Anthropic was not on the EU–U.S. Data Privacy Framework list when we checked on 4 October 2026, so those clauses are what the transfer rests on.

If you run a Q&A for an organisation. The material you upload and the questions from your audience are processed for your organisation's purpose, not ours. For that material your organisation is the controller and Cadence AS is its processor, with Anthropic and Microsoft Azure as sub-processors. The data processing terms for this are part of the terms. For everything else on this page Cadence AS is the controller.

Microsoft Azure hosts the service and the logs in Norway East. Every connection passes through its network. Azure also sends the confirmations by e-mail, and for that receives the host's e-mail address, name and the text of the confirmation. It also sends the Friday quiz e-mails, and for those receives the subscriber's address and the text. The e-mail data is kept at rest in Norway.

Microsoft and Google, if a host signs in with them. Signing in happens on their pages and under their own privacy policies; they learn that you signed in to klapp. We receive from them only what is listed above.

Stripe, if a host adds a card. Stripe Payments Europe, Limited (Ireland) handles the card and the payments for Cadence AS. It receives the card details you type on its page, and from us your e-mail address, name, sign-in identifier, and the amount, session reference, receipt number and time of consent for each payment, and the time of consent for a subscription. For some of what it does with that, such as preventing fraud and meeting financial regulation, Stripe is responsible itself, under its own privacy policy. Stripe also sends the receipts for the subscription by e-mail. Outside Norway, Link is the seller, as described above. Its data processing agreement covers transfers to Stripe, LLC in the United States. The safeguards for that transfer are set out in the Data Transfers Addendum, which is part of that agreement.

If you write to hello@playklapp.com, the message is forwarded by our domain registrar, Porkbun, to a Google Gmail inbox. We use the message only to answer you. The legal basis is our legitimate interest in answering what you write, under Article 6(1)(f); when you write about something you bought or about your account, it is that we need it to give you the service, under Article 6(1)(b). We delete the message 12 months after our last reply in the conversation, unless it documents a sale or a refund; that is kept with our accounts for five years after the end of the accounting year. We go through the inbox by hand every three months, so a message can stay up to three months longer. The full list is on subprocessors. How the service is run and secured is on security.

Why, and your rights

We process this to run the game, to keep the model costs from being abused, and to see what the generator costs and where it goes wrong. The legal basis is our legitimate interest in doing that, under Article 6(1)(f) of the GDPR. When a host signs in, the legal basis for the sign-in is that we need it to give you the service you signed in for, under Article 6(1)(b). The same goes for events you save, a card you add, a subscription and the payments charged to them. Keeping records of payments already made is a legal obligation, under Article 6(1)(c). The Friday quiz e-mail rests on your consent, under Article 6(1)(a); the unsubscribe link in every e-mail withdraws it and deletes the address.

You have the right to object to that processing, under Article 21, and the right to access, correction, deletion and restriction, and to receive what you gave us in a form you can take with you. You do not have to give us anything to play or to host a quiz; an event needs a sign-in, and a purchase needs a card. Write to hello@playklapp.com. Most of what we hold cannot be tied to you by us — for players we have no name, no account and no address to search by, and a signed-in host's details live only in their own cookie, as an account identifier on events they saved, and, if they added a card, in their customer record at Stripe — so tell us what you typed and roughly when. You can also complain to the Norwegian Data Protection Authority, Datatilsynet.

We make no decision about you based only on automated processing that has legal or similarly significant effects for you (Article 22 of the GDPR). Cadence AS has no data protection officer. It is not required to have one, so write to hello@playklapp.com.

Children

A new game starts as a room with children in it. There, names are handed out rather than typed, and a file is accepted only when the host confirms that it is teaching material with no personal data. The host decides this; we do not ask anyone's age.

What we hold, and for how long.