Privacy & student data

Plain language, no legal fog. This page explains exactly what we hold and who can see it.

Who controls your data

Teacher Tribe AI is operated by Charles Sacco, who is the data controller for the personal information described on this page. Questions, or any request about your data, go to teachertribeai@gmail.com.

What we collect and why

Account details (name, email, login credentials) — to create and secure your account and contact you about the service. Legal basis: performance of our contract with you.
Teaching content (curriculum documents, class lists limited to a first name and last initial, plans, drafts) — to produce your lesson materials. Legal basis: performance of our contract.
Community posts — to run the moderated idea feed. Legal basis: performance of our contract.
Support messages — to answer your questions. Legal basis: performance of our contract.
Usage and device information (pages used, IP address, browser, error logs) — to keep the service secure, prevent fraud and abuse, and improve the product. Legal basis: our legitimate interests.
Marketing emails, only if you opt in. Legal basis: your consent, withdrawable at any time.

Who we share it with

Service providers who host the app, store files, send email, and provide the AI models that generate your materials — all under contract and only to run the service.
Stripe, our payment provider, for the sale of the membership, subscription management, payments, tax handling and invoicing.
Professional advisers (legal, accounting) where needed, and authorities where the law requires it.

We do not sell your data, and we do not use it to train AI models.

How long we keep it

We keep your account data for as long as your account is open. Class lists older than two school years are deleted automatically, and you can delete your content at any time. When data is no longer needed it is deleted or anonymised. Records we must keep for tax or legal reasons are retained for the required period.

Your rights

You can ask us to give you a copy of your data, correct it, delete it, restrict or object to how we use it, or move it elsewhere, and you can withdraw consent to marketing at any time. Email us and we will respond within one month. If you are in the UK or EEA you may also complain to your local data protection authority. Data we hold is processed in the United States.

Security and cookies

We use appropriate technical and organisational measures — encryption in transit and at rest, strict access controls, and per-account isolation of your files. We use only essential cookies needed to keep you signed in and keep the site secure; we do not use advertising cookies. You can clear cookies in your browser at any time, though you will be signed out.

Class lists

We only ever ask for a student's first name and last initial. That information is stored against your account alone. No other teacher, school or member can see it, and it is never shown in the community idea feed. Our support team can view it only when you ask us to look at a problem with your account.

You can delete any student, or your whole class list, at any time from the Class list page. Deleting removes the record immediately. At the end of each school year we prompt you to clear the previous year's list, and lists older than two school years are deleted automatically.

Curriculum documents

Curriculum files you upload are stored privately and used only to write your own lesson plans. They are not shared with other members, not published in the community feed, and not used to train any model.

Lesson plans and drafts

Weekly plans, slide decks, learning targets and parent message drafts belong to you and stay private. Parent messages are drafts only — we never email families. You copy the text and send it yourself from your school email.

The community idea feed

Anything you post to the idea feed is reviewed by a moderator before it appears publicly, and is visible to other signed-in members along with your display name. Never include student names or identifying details in a post.