IT office answer pack
Version 1.12 · Updated Oct 31, 2026
Tapsity is classroom polling for large lectures. Students answer on their own devices without an account. It keeps nothing that identifies a student and stores no individual answer, only the totals for each question.
Address it
Optional
Student data
- What does Tapsity collect about students?
- Nothing that identifies one. Students join with a session's code or link: no account, no sign-in, no name or email, and no cookie on the student page.
- Are individual answers stored?
- No. Each answer is held in memory while the session runs. When a question closes, only its totals are written: how many devices chose each option, how sure they were and how long they took. No table holds an individual answer.
- Is a device identifier or fingerprint collected?
- A random token for each device, for one session, so that a device cannot answer twice. The room issues it, and it is not derived from anything on the device. It is kept in the device's open tab and the room's memory, is never a cookie, is never written to Tapsity's storage, and ends with the session.
- Is anything kept about network addresses?
- The join service counts the wrong codes each network address sends, for a few minutes in memory and never written, to stop code guessing. Cloudflare's network keeps its own request logs, with IP addresses, on its own schedule. Tapsity's own logs hold no network address.
- Does this create a FERPA education record?
- No. FERPA applies to records tied to an identifiable student, and none is created.
- Does COPPA apply?
- No. 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.
Instructor data
- What is collected about instructors?
- Email, name and an identifier from the sign-in provider; account dates, passes bought and sessions used; for each AI Assistant request, when and on which page it was made and what it cost Tapsity, which counts against the plan's AI limits and is shown only as a percentage of them; the university check, by domain; and the courses, questions, images and session totals they make.
- How is an educator verified?
- By the domain of an institutional Google or Microsoft sign-in, matched against a list of university domains. There is no review and no email. On the free plan, it decides whether the AI Assistant is included; an account not on the list uses the rest of the product as before.
- How long is it kept?
- While the account exists. Deleting it in Settings erases everything 30 days later, unless they sign in first. Unused for 365 days, it is erased after an email 30 days before. Tapsity keeps no other copy; Cloudflare can restore Tapsity's storage to any point in the past 30 days.
- Can an instructor take their data out?
- Yes, from Settings: one JSON file of their courses, questions, results, images, passes, and when and on which page they used the AI Assistant. Anything else kept about them is given to them on request: they write to the privacy officer.
- Which privacy laws apply?
- PIPEDA and Quebec's Law 25 for instructor data. Tapsity keeps a written privacy program with a designated privacy officer, an incident runbook and an incident register.
Security
- Where is data hosted?
- On Cloudflare, kept apart for each instructor. It may be processed outside Canada, including in the United States, and is encrypted in transit and at rest.
- Who else handles data?
- Cloudflare (hosting, storage, the network and email), Anthropic (the AI Assistant's model), Google (sign-in only), Microsoft (sign-in only) and Paddle (checkout as the merchant of record, once payments open). There is no analytics, advertising or session-replay vendor.
- How do instructors sign in?
- With Google or a Microsoft work or school account, asking only for their name and email. Scripts cannot read the session cookie and other sites cannot send it. Students do not sign in.
- Is card data in scope for PCI?
- No. Payments are not open yet. When they are, Paddle is the merchant of record and handles every card, so card data never reaches Tapsity, which is outside PCI scope beyond embedding Paddle's checkout.
The AI Assistant
- When does AI run?
- Only when an instructor asks the AI Assistant something in its panel. Nothing else uses AI, and reports never do.
- What does the AI model receive?
- The course the instructor wrote, and a question's result from a session only if at least 5 devices answered it in that session. What the instructor writes, attaches or pastes is sent with its content unchanged, though an attachment may first be prepared in the browser, for example made smaller or read as text. Never the instructor's name, email, payments or an account identifier, and nothing about a student.
- Who runs it, and what do they keep?
- Anthropic runs the model. Requests reach it through Cloudflare, which is told not to keep them. Anthropic deletes inputs and outputs within 30 days. If its safety systems flag them, it keeps them up to 2 years and the scores up to 7 years, and longer where the law requires. It does not train on them; Tapsity sends it no feedback and joins no program that would allow training.
- Is the conversation stored?
- Not by Tapsity. It stays in the open browser tab, and Anthropic keeps what it receives as above. A request is recorded by its page, never by its words, and no log line holds a request's words.
Accessibility
- What is the conformance status?
- Partially conformant with WCAG 2.1 Level AA. Automated testing finds 0 violations on 111 screen states, and 53 driven checks run the product from the keyboard alone. It has not been tested with screen-reader users yet, and known gaps are open.
- Can a student answer without a mouse?
- Yes. The options are radio buttons or checkboxes, reached with Tab and chosen with Space or the arrow keys, and a driven test checks every kind of question.
Operations
- What uptime is promised?
- None. A public status page shows the current state and keeps every incident.
- How are breaches handled?
- A written runbook covers detection, containment, assessment, notification and the record. Where the law requires, the regulators are told within the time PIPEDA and Law 25 set, and the instructors affected as soon as possible. Every incident is published, including those where no data was involved.
- How many devices has it been tested with?
- Not load-tested yet. Tapsity will publish how many devices one room has been tested with once the load test has run on the live service.
Documents
- Privacy policy: https://tapsity.com/privacy
- What we store: https://tapsity.com/transparency
- Accessibility conformance: https://tapsity.com/accessibility
- Terms of service: https://tapsity.com/terms
- Status: https://tapsity.com/status
Questions about this document, or requests about your own data: contact@tapsity.com.