Exit TicketsSign in

Legal

Privacy policy

Last updated 3 November 2026

Exit Tickets keeps classroom data to what is needed to run exit tickets: who is in a class, what was asked, what was answered, and what it scored. This page explains that in detail.

1. Who this policy covers

Exit Tickets is a classroom tool for creating exit tickets, sharing them with a class, and reviewing what students answered. This policy explains what we collect when you use the app, why we collect it, and the choices you have.

It applies to teacher accounts, student accounts, and to people who open a share link without an account (“guests”).

2. What we collect

  • Account details. Your name, email address and role (teacher or student). You can authenticate with email/password or Google sign-in. Google shares your name, email address and profile picture, and we never receive your Google password. If you enable optional MFA, we store the authenticator factor metadata needed to verify your one-time codes; we do not store the codes themselves.
  • Classroom setup. Classes you create or join, the syllabus, grade and subject attached to a class, your school name, and roster email addresses a teacher adds.
  • Study preferences. The subjects a student picks on their profile, used to group their progress on the dashboard. Visible to the student and to teachers of their classes.
  • Tickets and answers. Exit tickets you generate or upload, the answers submitted to them, the resulting score, and when the attempt was completed.
  • Guest submissions. If someone takes a ticket through a share link without signing in, we store the display name they type, their answers, the score, and which link they used. Nothing else is required from them.
  • Generation inputs. When a teacher asks the app to generate a ticket, the lesson overview, learning outcomes, grade and curriculum position are sent to our language-model provider. Student data is never sent for generation.
  • LMS connection (optional). If a teacher connects Google Classroom, we store OAuth tokens and the course and roster names needed to import a class. Access is read-only.
  • Technical data. Session cookies, IP address and request metadata in server logs, and error reports.

3. How we use it

  • To sign you in and keep you signed in.
  • To run the product: build tickets, score multiple-choice answers, aggregate progress by topic, and produce CSV reports for teachers and students.
  • To show a teacher the attempts made on their own tickets and classes.
  • To generate new exit-ticket questions at a teacher’s request.
  • To keep the service secure and diagnose faults.

4. What we do not do

  • We do not sell personal data.
  • We do not run advertising, ad retargeting, or third-party analytics trackers.
  • We do not use student answers to build marketing profiles or to train models.
  • We do not show one teacher’s students or reports to another teacher.

5. Legal bases

Where the GDPR or similar law applies, we rely on: performance of a contract (providing the app to you), legitimate interests (keeping the service secure and improving it), consent (connecting an LMS account, which you can revoke at any time), and legal obligation where a record must be kept.

6. AI-generated tickets

Generation sends the teacher’s lesson overview, outcomes, grade and curriculum path to the configured model provider — Ollama running on the school’s or teacher’s own machine, or an OpenAI-compatible API. The response is stored as a draft ticket that the teacher reviews before sharing. Please do not paste student names or other personal data into the lesson overview.

7. Google Classroom data

If you connect Google Classroom, we request read-only access to your courses and rosters, and use it only to import the class you ask for. Tokens are stored server-side and are never sent to the browser. You can disconnect at any time, which deletes the stored tokens; we do not share Google user data with third parties, use it for advertising, or allow humans to read it except where you ask us to, where it is needed for security, or where the law requires it.

8. Who processes data for us

  • Supabase — database and authentication.
  • Our hosting provider — serves the application and keeps short-lived request logs.
  • An LLM provider — Ollama locally, or an OpenAI-compatible API — receives generation prompts only.
  • Google — only if you connect Classroom.

Each processor is bound to use the data only to provide its service to us. We may also disclose data where the law requires it.

9. Cookies

We use only the cookies needed to keep you signed in and to protect the Google connection flow. Details are in the cookie policy.

10. How long we keep it

  • Account and classroom data: while your account exists, then deleted when you ask us to delete it.
  • Attempts and scores: until the ticket, class or account they belong to is deleted.
  • Guest attempts: until the teacher deletes the ticket or class they belong to, or asks us to remove them.
  • Server logs: a short operational window, then discarded.

11. Security

Traffic is encrypted in transit. Accounts are separated at the database level with row-level security, so a signed-in user can only read their own profile, classes, tickets and attempts. Scores are calculated on the server and correct answers are not sent to the browser that takes a ticket. OAuth state is held in a short-lived, HttpOnly cookie. No system is perfectly secure, so please use a unique password and tell us about anything that looks wrong.

12. Your rights

You can ask for a copy of your data, correct it, delete it, or object to a particular use. Two of these are built in: students can download their whole attempt history as CSV from the progress page, and teachers can export a class or a single student.

For anything else, email info@mobilecrmtech.com. We reply within 30 days. Teachers and students whose account was created by a school should contact that school first — it usually controls the account.

13. Students and children

The app is designed for classroom use and students may be minors. We ask for the minimum needed to run a class: a name and an email, or just a display name for a guest submission. We do not require a date of birth, do not advertise, and do not build marketing profiles. Schools and teachers are responsible for obtaining any notice or consent their jurisdiction requires before asking students to use the app.

14. International transfers

Our processors may store data outside your country. Where that happens, transfers rely on the safeguards those providers put in place, such as standard contractual clauses.

15. Changes and contact

If this policy changes materially we will update the date above and, for significant changes, tell signed-in users in the app.

Questions or requests: info@mobilecrmtech.com.