Privacy is Not Optional

Kansha is a gratitude-based classroom and school management tool. Privacy is a core design principle — not an afterthought. We built the platform so that classroom rosters are encrypted, kept inside Kansha, and never sold or used for advertising. Here is what that means in practice:

• Roster personally identifiable information is encrypted at rest
• We never sell, share, or monetize any user data for advertising or commercial gain
• No roster records are sent to an AI provider. Kansha’s AI features (see below) are teacher-facing design tools and one grammar game the teacher runs, and students cannot type anything that could be sent. The only student detail an AI service receives is a first name on its own, used to read a practice sentence aloud
• Students do not register with email addresses — rosters are created entirely by the teacher
• Teachers maintain full control over their roster data at all times

Kansha collects the absolute minimum information needed to run a classroom. Nothing more.

Teacher Accounts

We collect a name and email address when teachers register using Google or email sign-in. This is used only for authentication and classroom management. Teacher emails are never used for marketing.

Roster Records

Teachers create roster records with just a first name, last name, and an avatar. Later, a teacher may optionally add a student’s pronouns (she/her, he/him, or they/them); no roster record asks for them when it is created. Students never provide an email address, date of birth, or any other personal information directly to Kansha. This data is:

• Encrypted at rest and stored exclusively within the teacher’s classroom records
• Never shared for advertising or commercial use — roster data stays inside Kansha
• Only accessible by the teacher who created the record

Data Minimization: We collect only what is needed to run the classroom — a first name, a last name, an avatar, and optional pronouns if the teacher adds them. No email addresses, no dates of birth, no home addresses, no phone numbers. Ever.

Google Classroom Integration (Optional — Premium plan)

If a teacher chooses to connect Google Classroom, Kansha imports student first names, last names, and Google User IDs to build the classroom roster automatically. Names are encrypted immediately upon import using the same AES-256-GCM encryption applied to all roster PII. The Google User ID is retained solely as a match key so future syncs can recognize the same student (for example after a name change) — it is never shared. Kansha does not request or store student email addresses from Google Classroom. Teachers may disconnect Google Classroom at any time from their account settings.

Access is read-only. With the teacher's permission Kansha reads the teacher's list of active courses (classroom.courses.readonly), each course's student roster (classroom.rosters.readonly), and the teacher's own Google name and email (userinfo.profile, userinfo.email). Kansha never creates, edits or deletes anything in Google Classroom, never reads coursework, grades or submissions, and never uses Google user data for advertising or to train AI models. Disconnecting revokes Kansha's access token at Google and deletes it from Kansha.

Kansha's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Privacy note: All privacy protections described on this page remain in place for rosters imported from Google Classroom. Kansha is not affiliated with or endorsed by Google LLC.

AI Features

Kansha’s AI tools are teacher-facing design tools, plus Grammar Quest, a grammar game the teacher runs. No roster records are sent to an AI provider; Grammar Quest’s read-aloud may send a first name on its own to make speech. Section 3 lists each tool, the provider behind it, and exactly what that provider receives.

Kansha’s AI features are teacher-facing design tools, plus Grammar Quest, a grammar game the teacher previews and opens for the class. A teacher uses them to make classroom materials; students do not chat with, ask questions of, or get feedback from AI in Kansha.

What the AI Tools Do, and What They Receive

• Image generation for coins, classroom branding, group art, and store pictures (via OpenAI and Google Gemini/Imagen) — receives the teacher’s description, and for a coin, the token name the teacher chose
• Token-name and theme suggestions (via Anthropic) — receives the mascot or topic the teacher types
• Store item identification (via Anthropic) — receives the photo the teacher takes of a reward item
• Coin spelling check (via Anthropic) — receives the generated coin image, to confirm the token name is spelled correctly on it
• Grammar Quest practice sentences (via Anthropic) — receives a grade level, grammar topics, and sometimes a general topic like “pizza” or “dolphins”. It never receives a student’s name, pronouns, or anything that identifies a student or class; Kansha adds the names afterward on its own servers. The teacher previews every sentence before students see it
• Grammar Quest read-aloud (via OpenAI) — to read a fixed sentence aloud, receives the sentence with the student’s name taken out, and, as a separate request, a first name on its own, with no last name and nothing that links it to a student, class, or school. Kansha stores the audio and reuses it

Students Do Not Write to AI — They Cannot Write At All

Token Swap lets students send tokens to a classmate with a thank-you note. The note is chosen from a short, fixed list — “Thank you!”, “You helped me”, “Great teamwork!” and a few others. Students cannot type their own, so nothing a child writes is stored, and there is nothing to send anywhere for checking.

Kansha used to let students type that note, which meant screening it for bullying, and screening meant sending a child’s words to an AI provider. The fixed list removed both.

What Is Never Sent

No student writing, and no roster records, are sent to any AI provider. Not avatars, not token history, not pronouns, not last names, and not anything a student produced. The one student detail that leaves Kansha for an AI service is a first name on its own, for Grammar Quest’s read-aloud, as described above. Kansha has no AI tutor, no AI chat, and no AI feedback on student work. It is a classroom behavior and token-economy tool, and every AI feature in it is started by the teacher.

AI Service Providers

Kansha uses the commercial APIs of Anthropic, OpenAI, and Google. Requests travel over encrypted (HTTPS) connections and are handled under each provider’s own API terms.

Teacher Control

Each design tool runs only when a teacher uses it, and AI image generation is part of the Silver and Premium plans. Grammar Quest runs only when a teacher opens one for a class. Token Swap itself stays off unless the teacher turns it on for a class, and can be turned off again at any time. None of the AI tools are needed for Kansha’s core token economy, store, bank, raffles, or games.

Data Retention

Images and suggestions a teacher chooses to keep are saved in Kansha as part of that classroom’s content. Grammar Quest keeps each quest’s sentences and results in the classroom until the teacher deletes them; read-aloud audio is stored once and reused wherever the same words come up. A Token Swap note is saved with the transfer as the choice the student picked, so the teacher can review it. Either can be deleted on request — see Your Rights below.

Information is used strictly to operate the classroom management tool. Never for advertising, never for profiling, never for commercial gain.

Teacher Information

• Account authentication and security
• Classroom management and roster administration
• Service-related communications (not marketing)
• Platform feature updates and educator resources

Roster Information

• Roster PII remains encrypted within teacher-controlled records at all times
• Teacher-only access: Only the teacher who created a record can view that student’s name
• Classroom administration only: Roster data is used exclusively for classroom and school management — running the token economy, classroom store, group activities, and reports

No Commercial Use: Personal information is never used for targeted advertising, sold to third parties, or shared for commercial gain.

We do not keep roster data longer than necessary. Roster records are automatically deleted after twelve months of inactivity. Inactivity is defined as no teacher login or activity within the associated classroom for twelve consecutive months. Teachers can delete individual roster records at any time from their classroom dashboard.

Teacher accounts are retained as long as needed to provide the service, or until the teacher deletes their account. After that, data is deleted or anonymized within 30 days. Deleting an account also revokes Kansha's Google access at Google, if Google Classroom was connected, so the grant does not linger in the teacher's Google account after the data is gone.

IP addresses and location: Kansha does not store IP addresses or any location. A request’s IP address is used only in memory, to slow down repeated requests (such as sign-in attempts and form submissions), and the country our hosting provider derives from it is checked only when someone signs up, because Kansha is available to US schools only. Kansha never uses GPS or device location, and school hours are checked against the school’s own time zone, not a student’s location. Our hosting provider keeps standard request logs for a short time under its own policies (see Sub-Processors).

Classroom rosters often include records of minors. Kansha treats those records with extra care:

• Encrypted at rest, with keys held only on our servers
• Visible only to the teacher who created the record
• Never shared with advertisers, sold to third parties, or used for commercial profiling
• Roster records are never sent to AI providers — roster information stays inside the encrypted Kansha database (Grammar Quest’s read-aloud may send a first name on its own; see section 3)
• Minimal collection — we only store a first name, a last name, and an avatar, plus pronouns if the teacher chooses to add them

What classmates can see: In shared classroom activities — the class roster picker, live games, and the shared 3D “Class World” — students in the same class see one another’s first name and avatar only, never a full last name. The realtime layer that powers these activities carries only anonymous position data; first names come from an authenticated, per-class lookup. In Grammar Quest, classmates also see a featured student’s pronouns, and sometimes one favorite that student chose on their profile, inside a practice sentence. A student can turn that favorite off with “Let my class see my favorites in games”. Nothing is ever visible across classes or publicly.

Teachers should ensure their use of Kansha aligns with their school’s student-records policies. Parents or guardians may submit a data access or deletion request for a minor’s record at any time — see Your Rights below.

To operate the platform, Kansha uses a small number of trusted third-party services. The table below lists every service that may process data in connection with Kansha, what it receives, and its role. We never share roster data with any of these services for advertising or commercial purposes.

Not used: No advertising networks, no data brokers, no session-recording tools, and no product-analytics trackers like Mixpanel, Segment, or LogRocket.

Our platform is built with privacy as a foundational requirement, not an add-on. Every layer of the system is designed to keep roster data secure.

How We Protect Roster Data

Roster data is encrypted the moment it is saved, and the encryption keys live only on our servers — they never reach the browser.

• Encrypted at rest: All roster PII — including names and any in-classroom credentials — is encrypted using AES-256-GCM before storage
• Server-side only: All encryption and decryption happens on the server — no encryption keys or plaintext PII ever reach the browser
• No student self-registration: Students don’t create accounts with emails — rosters are managed entirely by the teacher, with any in-classroom passwords verified server-side
• Minimal data collection: We store only a first name, last name, and avatar, plus pronouns only if the teacher chooses to add them, encrypted like names

We are committed to being transparent about our privacy practices. If we make significant changes to this Privacy Policy, we will notify you prominently within the service or via email. You always have the right to understand how your data is handled, and we welcome questions at any time.

You have the right to access, correct, or delete your personal information at any time.

• Roster data: Teachers can delete individual roster records directly from their classroom dashboard. Parents or guardians may submit a data access or deletion request on behalf of a minor.
• Teacher data: Manage through account settings or contact us directly.
• Data portability: Teachers may request a complete export of their classroom data at any time via our contact form — we prepare it for you.

To submit a data access, correction, or deletion request, contact us at admin@beechtree.ai or use our contact form. We respond to all requests within 10 business days.

By using Kansha, you acknowledge that you accept this Privacy Policy and consent to the data practices described here. If you do not agree with this policy, please do not use our services. If you have any concerns, we are always happy to discuss them — reach out at admin@beechtree.ai.