Privacy Policy

We collect only what the product needs to work. Grouped by where it comes from:

Account and profile

• Identity: your name and email address, and the role you chose (student or teacher). When sign-in runs through Clerk, Clerk verifies the address (an emailed code or a Google account) and tells us the verified email and name; we never see your password.
• Learning profile: the background level and goal you enter at sign-up, the AI mentor you pick, the names you give your tutors, your interests (optional, editable in the account menu), and your time zone (so meeting times are shown on your clock).
• Teacher approval: for teachers, whether an admin has approved the account and when.

Student learning data

• Lesson progress, quiz answers and attempts, free-response answers and the grades and feedback on them (and any earlier regrade requests), coding-lab, Business Lab and Math Lab attempts, notebook notes, and the signals the product keeps about what you have understood.
• Your conversations with the AI tutor and mentor, and the questions you send to a teacher, with their replies.
• Activity time: when you are actively using a page. Only timestamps are kept — never what you typed, where you clicked or which keys you pressed. See the Cookie Policy for how it is measured.

Teacher, class and admin data

• Classes and their rosters, invitations (the invited email addresses), co-teacher and co-mentor assignments, join requests, class pricing, teacher profiles, grading decisions, and the resources a teacher attaches to a class.
• Live chat between a teacher and a student: messages, pictures, videos and voice notes, and scheduled meetings.
• For admins, the actions taken on the platform (approvals, retention clean-up, billing settings).

Uploaded material and generated content

• The text, documents, images and archives a teacher uploads to make a course, the course outline and lessons generated from them (including images kept from the material), the review and edit history of that content, and class resources (files and links).

Messages to us

• App feedback you send from the account menu, and any email you send to support. Feedback is stored and emailed to our support mailbox with your name and email so we can reply.

Billing

• Payments are handled by Stripe. Your card number and bank details are entered on Stripe’s pages and are never sent to or stored by the product. We keep a Stripe customer reference, which plan or class you paid for, the subscription status and renewal date, and the identifiers of the Stripe events we processed.

Usage and technical data

• AI usage: for every AI request the product makes on your behalf we record which feature made it, the tokens used, its cost, how long it took and whether it failed. This is what your AI credits are counted from. It is linked to your account by an opaque id.
• Request data: your IP address and browser type, used for security (rate limits on sign-in attempts and expensive actions) and in short-lived server logs when something goes wrong.
• Cookies and local storage: the sign-in cookies and the preferences described in the Cookie Policy. The product has no advertising or third-party analytics trackers.

• To provide the product: sign you in, show you your courses and classes, save your progress, grade your work, run the labs, deliver teacher help and live chat, and send the emails the product sends (invitations, approval notices, reminders about unread questions and chat messages, billing confirmations).
• To personalise learning: the AI tutor is given your level, goal, interests and learning record so its explanations fit you. Interests shape examples only — they are never used to grade you.
• To generate and improve course content: uploaded material is sent to an AI provider to produce the outline, lessons, exercises and the review warnings teachers see.
• To give teachers and admins the oversight the product promises: teachers see the work and progress of students in their classes; admins see the whole platform. The Student Data and School Use Policy lists exactly what each can see.
• To bill: to enforce plan and class access, count AI credits, and reconcile Stripe payments.
• To keep the product safe and working: rate limiting, abuse prevention, security headers, error logs and cost monitoring.
• To respond to you: support requests and feedback.

We do not sell personal data, and we do not use your data for advertising. We do not train AI models of our own on your content; see the AI Usage and Learning Data Disclosure for how AI providers handle requests.

The product runs on a small number of service providers. Each receives only what its job needs and acts on our instructions under its own terms and security commitments.

Data may be stored and processed in the country where these providers host it, which may be outside the country you live in. Where the law requires it, we rely on the providers’ standard contractual safeguards. A school that needs a specific hosting region or a data processing agreement should contact us before use.

• Every connection is encrypted in transit (HTTPS), and the product sends browsers a strict content security policy, frame denial and related security headers on every response.
• Sign-in sessions are httpOnly, same-site cookies signed with a server-side secret; the admin access code is never stored, only a digest of it.
• Every API route checks who is asking and what they own; a student can only reach their own records and the courses their classes or plan include, a teacher only their own classes. Cross-site requests to the API are refused before any cookie is read.
• Uploaded files are scanned for size and type, kept in private storage, and served only through the product after an access check; links added to class resources are reviewed before students see them, and every external link in course text opens through a “you are leaving” notice.
• Student code in the coding lab runs in the student’s own browser in a sandbox, never on our servers.
• Secrets (API keys, database credentials) live only in server configuration, and automated checks on every build confirm none reached the browser.
• Sign-in attempts and expensive actions are rate-limited.

No system is perfectly secure. If you believe your account has been accessed without permission, write to support at clikservinc.com straight away.

• While your account exists: your profile, learning data, classes, conversations and billing records are kept so the product can show you your history.
• Deleting your account: students and teachers can delete their own account at any time from Account menu → Account → Delete account. Deletion is immediate and cannot be undone. It removes your profile, learning records, grades, lab attempts, notes, questions, live-chat conversations, memberships, billing mirror, onboarding state and the original files you uploaded to make courses. Any live Stripe subscription is cancelled first so you are never charged again. The account page lists, before you confirm, exactly what will be removed and what stays.
• Files uploaded to make a course: each file a teacher or admin uploads is kept exactly as uploaded for one year from the upload, in private storage, so the course’s owner, the staff who manage it and admins can download the original. Students never can. After that year the file can no longer be downloaded and is deleted (the course itself is not affected). Deleting the course, or the account that uploaded the file, deletes it sooner.
• What stays after deletion: courses a teacher created are kept, with the creator anonymised, for up to one year so the students who were taking them are not cut off; admins can remove them sooner and they expire after that. Feedback you sent is kept without your name and email. AI usage and cost records keep only an opaque id, with no identity attached. Invoices stay in Stripe as its records require.
• Demo and unused accounts: an admin may remove accounts that never got past the demo courses, and may set how long demo access lasts.
• Logs and backups: server logs are short-lived; database backups are kept for a limited rolling window and then overwritten.

The product is built for classes: a teacher or school invites students, and a school or a parent or guardian is responsible for a student who cannot agree to these terms alone. We do not knowingly collect personal data from a child outside such an arrangement; if you believe a child has created an account without one, contact us and we will remove it. The Student Data and School Use Policy explains what teachers and admins can see of a student’s work, and how a school or parent can make a request.

• See and correct: your profile is in the account menu and the Account page; what your mentor knows about you is on My learning; your numbers are on My stats. Your name, level, goal, mentor, tutor names and interests can be changed there.
• Delete: from the Account page, at any time, as described above.
• Export or ask a question: write to support at clikservinc.com from the email on your account. We may ask you to confirm it is you. Depending on where you live you may have additional rights (access, portability, restriction, objection, or a complaint to a supervisory authority); we honour them to the extent the law requires.
• Emails: the product sends only emails needed to run it (invitations, approvals, reminders about unread questions and messages, billing). There is no marketing mailing list.
• Cookies: see the Cookie Policy.

When this policy changes in substance we will update the date at the top and, for material changes, tell signed-in users in the product or by email before the change takes effect. Earlier versions are available on request.

Privacy questions and requests: support at clikservinc.com. See Contact and Support for what to include.