What we store

In short

Nothing is kept for one student or for one answer. A student's answers are added up when a question closes, and only the totals are kept. There is nowhere to keep anything finer.

Where it is kept

With Cloudflare, kept apart for each instructor. Cloudflare can restore stored data to any point in the past 30 days.

A question your class answered

For each question in each session, one set of figures for the whole room, and nothing else:

Which question

The session and the question the figures belong to.

When

When the question was shown, and how long it stayed open.

Devices connected

How many were connected while it was open.

Answered

How many answered, and how many did not.

Right answers

How many were right. Empty for a question with no right answer.

Choices

How many chose each option, and how sure they were.

Sure and right

How sure the right answers were, and how sure the wrong ones were.

Time to answer

The median and the 90th-percentile time to the first tap, and to sending.

Counts only: nothing says which device chose what. Totals over very few devices can still 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.

Sessions

For each class you run in which an answer comes in, from any device. A rehearsal keeps nothing, and neither does a room nobody answered in.

Which lecture

The lecture the session started from.

Join code

The code the room used.

Label

A label you may give the run, such as “9 AM section”.

Times

When the room opened, when the first answer came in, and when it closed.

Peak

The most devices connected at once.

Your courses and questions

Courses

Identifier

A random identifier.

Name and description

The course's name and what it covers.

Created

When it was made.

Lectures

Course

The course the lecture belongs to.

Name and topics

The lecture's name and what it covers.

Place

Its place in the syllabus.

Picked by hand

Made by presenting questions picked by hand, and kept out of the syllabus.

Archived

Hidden from planning, its history kept.

Questions

Course

The course the question belongs to.

Text

The question's text.

Figures

Formulas, code, diagrams, graphs, molecules and images the question shows, each with its description.

Options

The options' text.

Language

The language the question is written in, chosen when it is written, or your account's language if none is chosen. It tells each device which language that is.

Answer and mistakes

Which option is right, and the mistake each wrong option stands for.

More than one answer

Whether more than one option may be chosen.

Confidence

Whether students are asked how sure they are.

Explanation

Your explanation of the answer.

Place

Its place among the course's questions, and whether it is archived.

Edited

When it was last edited.

Running orders

Running order

Which questions a lecture holds, and in what order.

Images

Image

The image itself, kept with its course.

Uploaded

When it was uploaded. 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.

Each image is a JPEG, at most 1,600 pixels on its longest side and at most 4 MB.

The AI Assistant

Each plan includes the AI Assistant within limits, the free plan with a university sign-in, and a request counts against them by what it costs Tapsity to run. That cost is used only to count it against your limits, and is never sold or shared: you see it only as a percentage of a limit. For each request:

Request

A random identifier.

When

When its first step ran.

Page

The page the request was made on, by its identifiers. Never the request's words.

Use

How many steps the model ran, and what they cost Tapsity.

For the account, one record of the limits:

Used

How much of this week's limit is used, and of the extra for busy weeks.

Week

When a new week was last started. A week starts on Monday at 00:00 UTC.

Your account

One record for each instructor:

Sign-in identifier

The identifier your sign-in provider gives the account.

Email and name

As your sign-in provider gives them.

Dates

When the account was made and last used.

Agreement

When you agreed to the Terms of service and confirmed that you had read the Privacy policy.

Purchases

Each pass bought, and Paddle's references for you and for each purchase.

Disputes

How many payments were disputed.

University check

When your sign-in matched, the domain, and whether it was a Google or a Microsoft sign-in.

Sessions this month

How many sessions you have used this month.

Deletion

When you asked to delete the account.

Language

The language you read Tapsity and its email in, and the one the AI Assistant writes in unless you ask for another.

Erasure notice

When Tapsity last emailed that the account would be erased for not being used, or found that the address no longer takes email. Any use after it keeps the account.

Change notice

Which version of the Terms of service and Privacy policy Tapsity last emailed you about, before it took effect.

Beside it: a record of each university match, of when each session counted against the month, of each payment applied or reversed, of a checkout you have open, and of the day unused images were last cleared.

Sign-in tokens are checked and dropped. They are never stored or logged.

Joining a session

While a session runs

Its join code, the session, and which instructor's room it leads to. Removed when the session ends.

In memory only

For each network address that sends a wrong code, a count of its wrong codes, used to refuse an address that guesses. Held a few minutes, and never written.

On a student's device

The student page keeps two things in the open tab, for the session: a random token for the device, and the answers this device sent, so a reload shows them. Both are cleared when the session ends and are gone when the tab closes. The page sets no cookie.

Logs

Tapsity's logs 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, to find universities the list misses. They never hold a request's words, a name, an email or a network address. Cloudflare keeps them 7 days.

Cloudflare's network keeps its own request logs, with IP addresses, on its own schedule. Tapsity itself writes no IP address anywhere, and a join address holds only the session's code.

An AI Assistant request passes through Cloudflare on its way to the model, and Cloudflare is told not to keep it.

Cloudflare, which sends Tapsity's email, keeps a record of each email, with the sender, the recipient and the subject, for 31 days, and a list of addresses an email bounced from or that reported one as spam.

What is never stored

Student names and emails

Never asked for. There is no field for them.

Student accounts

There are none. The student page has no sign-in.

Individual answers

Added up when a question closes. Nothing holds one.

Device fingerprints

Not collected. The device token is random and given by the room, not read from the device.

Rosters and grades

There is no class list to upload, and nothing to export per student.

AI Assistant conversations

Held in the open browser tab, never by Tapsity.

How this is kept true

A device gets only the question

Which option is right, the mistakes and the explanation never reach a student's device. A test checks it on every change.

Answers are never written one by one

Only the room's totals are written, after a question closes. There is nowhere an individual answer could be kept.

A student's connection is never written

It is held in memory while the session runs, and is gone when it ends.

The AI Assistant reaches only what it needs

It cannot read your account, your AI use or your payments, and it gets no question's result from a session in which fewer than 5 devices answered it. A test checks everything it may do.

What this page does not claim

Anyone with a session's code can answer, and Tapsity cannot tell whether they are enrolled. That follows from keeping no identity: the results are a reading of the room, not attendance or a grade. A code belongs to one session at a time and stops working when it ends.

Who else handles data is in the privacy policy.