Privacy policy
Version 1.12 · Updated Oct 31, 2026
Tapsity keeps nothing that identifies a student. Instructors are the only people with an account, so most of this policy is about them.
Students
A student joins a session with its code or link. There is no account and no sign-in, no name or email is asked for, and the student page sets no cookie.
Each answer is held in the room's memory while the session runs and is never written to Tapsity's storage. When a question closes, Tapsity writes its totals: how many devices chose each option, how sure they were, and how long they took. When the session ends, the answers in memory are gone. No table holds an individual answer, so none can be looked up or exported.
Totals over very few devices can show what each chose, so the AI Assistant reads a question's result from a session only if 5 or more devices answered it in that session.
So that a device cannot answer the same question twice, the room gives each device a random token for the session. The device keeps it in the open tab, with the answers it sent, so a reload shows them, and clears both when the session ends. The room holds the token in memory only.
To stop people guessing codes, the join service counts the wrong codes each network address sends. The count is held in memory for a few minutes and is never written.
With no student data kept, there is none to see, correct or delete, and Tapsity creates no FERPA education record.
Instructors
You sign in with a Google account or a Microsoft work or school account. Tapsity keeps:
- Your email address
- To identify the account, and to send you the notices these documents promise.
- Your name
- As your sign-in provider gives it, shown in the app.
- A sign-in ID
- The identifier your sign-in provider gives the account, used as its key.
- Your account
- When it was made and last used, when you agreed to the Terms of service, the passes bought and any chargebacks, and the sessions used this month.
- The university check
- Whether your sign-in matched Tapsity's list of universities, the domain it matched, whether it was a Google or a Microsoft sign-in, and when. There is no review, so nothing else is collected for it.
- Your teaching
- Your courses, lectures and questions, the mistakes you wrote for wrong options, explanations, images you upload, the labels you give sessions, and the totals of the sessions you run.
- AI Assistant use
- For each request: when it was made, the page it was made on, how many steps it took and what it cost Tapsity to run. For the account: how much of this week's limit and of the extra for busy weeks is used. What a request cost is used only to count it against your limits, and you see it only as a percentage of a limit. Never the request's words.
What we store lists everything Tapsity keeps.
The one cookie Tapsity sets keeps you signed in. Scripts on the page cannot read it, and other sites cannot send it. The site and the app run no analytics or advertising code.
Payments are not open yet. When they are, Paddle runs checkout as the merchant of record: it is the seller and handles your card, the invoice and sales tax, and your card details never reach Tapsity. Tapsity keeps Paddle's references for you and for each purchase, and what each purchase bought.
The AI Assistant
Nothing you do reaches a model unless you ask the AI Assistant something in its panel. The rest of this section is about what happens when you do.
The AI Assistant runs on a model from Anthropic. Each request reaches it through Cloudflare, which is told not to keep it. What the model receives:
- The course you wrote: its name and what it covers, its lectures, questions, options, the mistakes you wrote, explanations and session labels.
- Your sessions and their results, for a question in a session only if at least 5 devices answered it in that session: how many chose each option, how sure they were and how long they took.
- What you write, attach or paste. An attachment may be prepared in your browser first, for example made smaller or read as text, without changing its content.
It never receives your name, your email, your payments, your AI use, or any identifier of your account. Nothing about a student is sent, because nothing about a student is kept.
Tapsity does not save the conversation. It is held in the open browser tab, and closing the tab or clearing the conversation ends it. Each request is recorded by the page it was made on, never by its words, and no log line holds a request's words.
Anthropic deletes what it receives and what it returns within 30 days. If its safety systems flag a request as breaking its usage policy, it keeps the request for up to 2 years and the scores that flagged it for up to 7 years, and longer where the law requires. It does not train its models on what it receives, except feedback a customer sends and programs a customer joins. Tapsity sends Anthropic no feedback and joins no program that would allow training.
From Anthropic's own pages, read on Oct 15, 2026: How long Anthropic keeps API data (updated Jul 1, 2026) and Whether Anthropic trains on API data (updated Aug 18, 2026).
Session reports are written without a model. The assistant can read them, under the same 5-device rule, and never writes them.
How long things are kept
Each kind of data has a stated life:
- An answer
- In the room's memory while the session runs, and in the device's open tab. Never written by Tapsity.
- A device token
- For the session, in the device's open tab and the room's memory. Never written by Tapsity.
- A wrong-code count
- A few minutes, in the join service's memory. Never written.
- Session totals
- While your account exists. A question or lecture that has run can be archived but not deleted, so its history stays whole.
- Your teaching
- While your account exists.
- Uploaded images
- While a question uses it, as long as your account exists. An image is deleted when the last question that uses it is deleted, and one that no question uses (never saved in a question, or taken out of one) is deleted once it is 30 days old, the next time you open the app.
- The university check
- While your account exists.
- Your account and its AI use
- While your account exists, and up to 30 days after you ask to delete it, then for up to 30 days more in Cloudflare's recovery. An account not used for 365 days is erased: 30 days before, Tapsity emails you the date, and signing in keeps it. If your address no longer takes email, it is erased on that date all the same.
- What Anthropic receives and returns
- Up to 30 days. If its safety systems flag it, up to 2 years, and the scores that flagged it up to 7 years, or longer where the law requires.
- Emails Tapsity sends
- Cloudflare, which sends them, keeps a record of each, with the sender, the recipient and the subject, for 31 days. An address an email bounced from, or that reported one as spam, stays on Cloudflare's list of addresses not to send to, in some cases with no end date. Tapsity removes an address from it on request.
- Tapsity's logs
- 7 days, with Cloudflare. They hold alerts, errors and payment events: which session or purchase, what went wrong and where, and the domain of a sign-in that is not on the university list. Never a request's words, a name, an email or a network address.
- Cloudflare's request logs
- On Cloudflare's own schedule. Its network logs each request with its IP address. Tapsity itself writes no IP address anywhere. A join address holds only the session's code.
Deleting your account
Ask for deletion in Settings. 30 days later your account and everything in it are erased: courses, questions, reports, images and AI use. Signing back in before then cancels the deletion.
Tapsity keeps no other copy. Cloudflare can restore stored data to any point in the past 30 days, so for 30 days after the erasure that recovery may still hold it. Paddle, as the seller, keeps its own record of each purchase.
Who else handles data
- Cloudflare
- Hosting, storage, the network and email. Everything Tapsity keeps is kept here, AI Assistant requests pass through it on their way to the model, and Tapsity's emails are sent through it.
- Anthropic
- Runs the AI Assistant's model, and receives what a request sends.
- Sign-in, for instructors with a Google account. Nothing else.
- Microsoft
- Sign-in, for instructors with a Microsoft work or school account. Nothing else.
- Paddle
- Checkout and payments, as the merchant of record, once payments open. Nothing has been sent to it yet.
That is the whole list. When it changes, these documents get a new version and date. A change of who runs the AI Assistant's model changes the list before the change ships.
Where data is processed
Cloudflare, Anthropic and Paddle work in many countries, the United States among them, so your data may be processed outside your own. Cloudflare and Anthropic handle it under written data processing terms with Tapsity, and Paddle, as the seller, under its own terms. Everything Tapsity keeps is encrypted in transit and at rest, and the IT office answer pack describes how it is protected.
Your rights
Tapsity gives everyone these rights, wherever they live: to see, correct and delete what is kept about you, to take a copy of it, to object to or restrict how it is used, and to withdraw your consent to its use, which you do by deleting your account. Some or all of them are also yours in law under PIPEDA and Quebec's Law 25.
Your account and your teaching are in the app, and Plan shows how much of each AI limit you have used. In Settings you can download a copy of your account and your teaching in one file, with when and on which page you used the AI Assistant, and delete your account. Your name and email come from your sign-in provider: change them there, then sign in again.
Write to Tapsity's privacy officer at contact@tapsity.com for a correction, for anything Tapsity keeps about you that the download does not hold, for a complaint, or for any other request. Tapsity answers in writing within 30 days. You can also complain to the privacy regulator where you live.
Breaches
Tapsity keeps a written incident runbook and an incident register. Where the law requires, the regulators are told about a breach, and the instructors affected are told as soon as possible. The register is published on the status page, including entries where nothing was exposed.
Children
Tapsity is offered for teaching at universities and colleges, and is not directed to children under 13. It keeps nothing that identifies a student, of any age.
Changes
Account holders are emailed about a material change before it takes effect. The version and date at the top of this page record which version applied when.
Questions about this document, or requests about your own data: contact@tapsity.com.