Teach Space Privacy Policy

Version: 1.5
Effective Date: October 26, 2026
Last Updated: October 26, 2026

Note: Step-by-step instructions, lists of supported file formats and video platforms, and other operational details are available in the FAQ section within the App.

1. Introduction

1.1. This Privacy Policy (the "Policy") describes how Teach Space LLC, a company registered in the State of Wyoming, United States (the "Company," "we," "us," or "our"), collects, uses, stores, protects, and discloses information about users of the Teach Space website and mobile applications (collectively, the "App" or the "Service"), and about visitors of the websites that Teachers publish with the Service (see Section 2.9).

1.2. This Policy is incorporated by reference into our Terms of Service. By using the App, you confirm that you have read, understood, and agree to the practices described in this Policy.

1.3. The Company seeks to collect only the minimum amount of information necessary to provide the Service (data minimization principle).

1.4. The Company uses commercially reasonable efforts to protect user data; however, no system can guarantee absolute security. By using the App, you acknowledge and accept this risk.

2. Information We Collect

2.1. Information Provided at Registration

2.2. Profile Data (Provided at Your Discretion)

• Profile photo (avatar) — uploaded by you; stored in cloud storage.
• Bio (about you) — free-form text field.
• Location — free-form text field completed by you manually; the App does not request or determine device geolocation.
• Preferred currency — used to display lesson pricing in your chosen currency.

2.3. Information Generated Through Use of the Service

• Messages — text messages and attached files (images, documents) sent in chats between Users (Teachers, Students, and Parents). If a sender removes a message, its text and attachments are hidden from chat participants and replaced with a visible deletion marker. The original message is retained server-side while the relevant account remains active so authorized personnel can investigate safety reports, abuse, or disputes.
• Files — images, documents, and scanned documents uploaded by Users to lessons, homework, and messages. Permitted formats and size limits are listed in the FAQ. Video file uploads are not supported; video content is available only through external links to supported platforms.
• Video links — URLs of video materials hosted on supported external platforms, added by Teachers to lessons and assignments. The current list of supported platforms is available in the FAQ. The Company does not host video content; only links and public metadata (platform name, thumbnail) are stored.
• Whiteboard drawings — graphical whiteboard data linked to subjects, lessons, or homework, including the version history of drawings.
• Lesson data — schedules, attendance status, lesson price, payment status, cancellation and rescheduling requests, and the video-call link a Teacher adds to a class or lesson.
• Payment records — lesson payments, prepaid balances, payments a Teacher marks by hand and payment claims made by Students or Parents, with their amounts, currencies, dates and statuses. Payments made through a Teacher's payment provider are described in §2.8.
• Homework — assignment content, student answers, grades.
• Reviews — free-form text and numeric ratings (1–5) that Users submit about other Users.
• Tags — user-defined labels for organizing lessons and assignments.
• Calendar feed — if you turn on calendar sync, we create a private link through which the calendar application you choose (for example, Google Calendar or Apple Calendar) retrieves your schedule. Each lesson is titled with the class name and the first names of its Students for a Teacher, the subject and the Teacher's name for a Student, or the child's first name and the subject for a Parent, and also shows the lesson topic and the call link. The calendar application stores this information under its own privacy policy. We record when the feed was last retrieved, how many times, and the retrieving application's technical identifier (user agent). Anyone who has the link can read the feed, so keep it private; turning calendar sync off invalidates the link immediately.
• Support conversations — messages and files you exchange with our support team in the App's help chat.
• Feedback — answers you choose to give us, for example why you did not continue after a trial, including any comment you write.
• Reports and blocks — when a User submits a report regarding objectionable content or User behavior, we record the reporter's identifier, the target of the report (a User, message, or material), the selected reason, an optional free-form description, and a timestamp. When a User blocks another User, we record the identifiers of both parties and a timestamp. This data is used solely for content moderation and platform-safety purposes.

2.4. Technical Information Collected Automatically

• Online/offline status and last-seen timestamp — used to display presence status in chats.
• Push notification tokens — the identifier of your device or, if you turn on notifications in a web browser, that browser's push subscription (an address at the browser's push service and its encryption keys). Used only to deliver the notifications you have allowed.
• Device and app settings — device platform (iOS or Android), app version, and your language and time-zone settings. Used to display content correctly, format dates, times, and notifications, and to understand which platforms our Users are on. This is aggregate, non-advertising usage information; it is not used for advertising or cross-app tracking.
• IP address — recorded in the audit log for specific actions (sign-in, settings changes) for security purposes.
• Feature-usage events — which of certain features you open or use (for example, the plan screens, calendar sync or joining a lesson call), with the platform and app version. Used only internally, to understand which features are used and to improve the Service; never used for advertising and never shared with third parties.
• Email delivery status — whether your email address has been confirmed, and notices from our email provider that a message to your address could not be delivered or was reported as spam.
• Subscription data — subscription and transaction identifiers, plan, status, purchase channel, price and currency, billing period, trial and renewal status, start and end dates, billing email for website purchases, and refund information where applicable.

2.5. Information We Do NOT Collect

In the interest of full transparency, the App:

• Does not collect device GPS geolocation data.
• Does not collect or use the IDFA, Google Advertising ID (GAID), Android ID, or another operating-system advertising identifier for advertising measurement.
• Does not request Apple's App Tracking Transparency (ATT) permission from Students, children, Parents, guests, administrators, managers, or Teachers who did not confirm that they are at least 18 years old. An eligible adult Teacher may see the optional request described in §2.7.
• Does not use third-party behavioral analytics or tracking services (such as Google Analytics, Firebase Analytics, Segment, Amplitude, Mixpanel, or the like). On our public website, a Google tag is loaded only after a visitor accepts cookies (§2.11). The App uses Sentry solely for automatic error and crash reporting to improve the stability of the Service; personally identifiable information (PII) is not transmitted to Sentry (the sendDefaultPii: false option is enabled).
• Does not initialize an advertising SDK because of an ineligible account. A Meta App Events SDK is included only in a measurement-enabled release and is initialized only for the optional adult-Teacher flow in §2.7. If an eligible adult Teacher initialized it earlier in the same running app process, automatic logging remains disabled and Teach Space makes no event call for a later ineligible account; the SDK may still perform non-event configuration traffic until that process ends.
• Does not track user behavior outside the App.
• Does not perform automated decision-making or user profiling.
• Does not sell, and will never sell, personal information to third parties.
• Does not share Student, child, Parent, educational-content, or account-profile data for cross-context behavioural advertising. The limited optional disclosure by an adult Teacher for advertising measurement is described in §2.7 and may be disabled at any time.

2.6. Telegram Payment Reminders (Optional)

Students and Parents may choose to receive payment reminders through Telegram instead of, or in addition to, in-app notifications. This is entirely optional and is never enabled by default. Any adult user may connect a Telegram account, and a payer who was invited to a class but has not yet created an account in the App may connect as well; reminders are then sent only to those who actually owe for lessons. A child account can never be connected (see §3.6).

Connection is always initiated by the person themselves: they open a single-use link and press "Start" in the Telegram chat with our bot. A Telegram bot cannot message anyone who has not done this.

Information we receive from Telegram when you connect:

• Chat identifier — the numeric identifier of your chat with our bot, used to deliver messages to you.
• Telegram username (if you have one) and first name — shown to your teacher so they can confirm that the person who opened the link is the person they invited, before any information is sent.
• Language code — the language your Telegram app is set to. It is stored for every connection, and is used to choose the language of the messages for payers who have no account in the App; for everyone else the language chosen in the App is used.

We do not receive your phone number, your Telegram contacts, or any of your other Telegram chats.

Because our bot is a participant in your chat with it, Telegram delivers to us whatever you send in that chat. We act only on the /start, /stop and /status commands and on taps of the buttons inside our own messages; anything else is discarded on receipt and is never stored, read by our staff, or used for any purpose.

Information we send to Telegram — only the content of the message itself: the teacher's name, the name of the subject or class, the outstanding amount, the number of unpaid lessons and the date of the earliest one, and — only where the message goes to a Parent about their child rather than to the student themselves — the student's first name, never the surname. A message addressed to the student contains no name at all beyond the teacher's. The same applies to a confirmation that a payment was accepted or declined. Messages we send are delivered and stored by Telegram in accordance with Telegram's own privacy policy, which we do not control.

Disconnecting. You may disconnect at any time by sending /stop to the bot, by blocking the bot in Telegram, or from Notification settings in the App. Disconnection takes effect immediately and no further messages are sent.

2.7. Adult-Teacher Advertising Measurement (Optional)

Teach Space may offer an optional advertising-measurement setting only to a signed-in Teacher who confirmed during registration that they are at least 18 years old. It is never offered to a Student, child, Parent, guest, administrator or manager, and declining it does not affect any feature.

If an eligible Teacher allows measurement, the App initializes the Meta App Events SDK and:

• sends the standard CompleteRegistration event for a newly registered Teacher, with “email” as the registration method but without sending the email address itself;
• sends the standard InitiatedCheckout event, with the selected plan's price and currency, at the moment the Teacher opens the app store's payment sheet for a paid plan. It is not sent when the Teacher merely views the plan list, and it carries no information other than that amount and currency;
• obtains Meta's app-scoped anonymous identifier ($fbAnonId) and provides it to RevenueCat; and
• allows RevenueCat to send verified initial-subscription and renewal events to Meta, including the product, price and currency needed to measure subscription results.

On iOS, this occurs only after the Teacher also grants Apple's ATT permission. RevenueCat reads the current ATT status from iOS. Teach Space does not collect the IDFA or GAID, does not enable Meta automatic event or purchase logging, does not send a generic app-launch event, and does not use email, phone number, name, Teach Space user ID or advanced matching for Meta advertising measurement. As with any Internet request, Meta receives ordinary connection information such as the source IP address and may receive SDK-supplied technical information such as app, device and operating-system versions.

The App's backend makes the eligibility decision from the current database account, not from a client-supplied role. Measurement is blocked if the account is linked as a child account or otherwise ceases to meet the adult-Teacher conditions. Student names, Parent data, classes, lessons, homework, grades, files, whiteboards and messages are never included.

The Teacher may withdraw permission in Profile → Ads and privacy. On iOS, ATT can also be revoked in system Settings. Withdrawal stops future Teach Space-controlled Meta events and removes the Meta anonymous identifier set by Teach Space in RevenueCat; it does not retroactively delete events already received by Meta. Requests concerning data already held by Meta are governed by Meta's Privacy Policy.

2.8. Lesson Payments Through a Teacher's Payment Provider

A Teacher may connect the Teacher's own account with a payment provider — currently monobank, WayForPay, LiqPay, Stripe or PayPal — so that Students and Parents can pay the Teacher online. The payer pays on the provider's page and the money goes directly to the Teacher; the Company does not receive or hold it (Terms of Service §12.4).

• What we keep for the Teacher. The access keys or account connection the Teacher gives us for the provider, encrypted at rest and used only to create that Teacher's payments and check their status, together with the provider account identifier and its display name.
• What we send to the provider. The amount and currency, a payment reference, the class name as the Teacher named it and — where the payer is signed in to the App — the email address of the payer's account, so that the provider can send a receipt. We do not send the Student's name or any learning content.
• What we receive from the provider. The status of the payment and, where the provider supplies them, the card brand and last four digits, a link to the receipt, and refund and dispute status, which we keep with the payment record.
• What we never receive. Full card numbers, card security codes and online-banking credentials are entered only on the provider's page and are never available to us.

The provider processes the payment as an independent controller under its own terms and privacy policy, which apply between the provider, the Teacher and the payer.

2.9. Teacher Websites and Their Visitors

2.9.1. Published content. A Teacher whose plan includes it may publish a website at an address of the form teachspace.app/@name (a "Teacher Website"). Everything the Teacher chooses to put on it — for example name, photograph, description, subjects, prices, working hours, places, contact details and reviews — is publicly available on the internet and may be indexed by search engines. On a team's website, the team owner may also show co-teachers' names, photographs, subjects, profile texts and working hours. Unpublished drafts and preview links are not indexed.

2.9.2. Requests from visitors. A visitor may send the Teacher a request through the form on a Teacher Website. We receive the name and contact details the visitor enters and, depending on how the Teacher has set up the form, the lesson or teacher chosen, a message and answers to the Teacher's own questions, together with the page it was sent from. The request is shown to the Teacher who owns the website and, on a team's website, to the co-teacher the visitor chose; they receive a notification with the visitor's name and, where it is one of the website's own lessons, the subject requested.

2.9.3. Our role. The Teacher decides what the form asks and what is done with the answers. For these requests the Teacher is the controller, and the Company processes them on the Teacher's behalf as a processor under the data-processing terms in §5.5 of the Terms of Service. A visitor who wishes to access, correct or delete a request should contact the Teacher; the visitor may also write to support@teachspace.app, and we will forward the request to the Teacher or act on it where the law requires. The Company is a controller only for the protection of the form against abuse (§2.9.4).

2.9.4. Protection against abuse. To limit automated and abusive requests, we process the sender's IP address only in hashed form, as a short-lived counter that is deleted automatically once it is no longer needed (normally after about a day). A field that people never see detects automated submissions.

2.9.5. No cookies or trackers. Teacher Websites set no cookies and contain no analytics or advertising trackers. If a Teacher adds a video, the player is loaded from YouTube (in its privacy-enhanced mode) or Vimeo when the page opens; that provider receives the visitor's IP address and technical information and may use cookies or similar technologies under its own privacy policy. A map link opens the map service only when it is clicked.

2.9.6. Retention. The Teacher can delete a request at any time. Otherwise a request is deleted automatically 12 months after it was sent, or earlier if the Teacher deletes the website or the Teacher's account is deleted (§9). Pictures uploaded for a website are stored in the Teacher's own storage, like other files.

2.9.7. Age. The request form is intended for adults. A person under 16 should ask a parent or guardian to send the request.

2.10. Teaching Teams

If a Teacher joins another Teacher's team, the classes that the team owner assigns to the Teacher — including those classes' Students, lessons, homework, payment and earnings records — are available to both the team owner and the assigned Teacher, within the permissions the owner sets. A Teacher's own classes outside the team are not shared with the team.

2.11. Cookies and the Google Tag on Our Website (Optional)

2.11.1. Your choice. When you first open a page of our public website (teachspace.app, outside the signed-in Service and outside Teacher Websites), a banner asks whether we may use cookies for analytics and advertising. "Only essential" is as easy to choose as "Accept". Your choice is stored in an essential first-party cookie, ts_consent, for 6 months, and you can change it at any time through Cookie settings at the bottom of every page.

2.11.2. Before you accept. Until you accept, our website loads no analytics or advertising tag and sends nothing to Google. A browser that sends a Global Privacy Control signal is treated as declining, and the tag is never loaded in it (§13).

2.11.3. After you accept. Our website loads Google's tag (gtag.js) for Google Analytics and Google Ads. It sets Google's consent signals for analytics storage, ad storage and ad user data to granted and ad personalization to denied, and Google receives:

• the identifiers stored in cookies set by the tag (such as _ga, _ga_<ID> and _gcl_au) and, when you arrive from a Google advertisement, that advertisement's click identifier;
• the pages of our website you open, the page that referred you, and the time of your visit; and
• technical information such as browser and device type, screen size, language and approximate location derived from your IP address.

We use this only to count visits to our website and to learn whether a Google advertisement led someone to it. We do not send Google your name, email address, Teach Space account ID or any educational data; we do not enable ad personalization or remarketing; and the tag does not run inside the signed-in Service or on Teacher Websites.

2.11.4. Withdrawing. If you later choose "Only essential", Google's consent signals are switched to denied for the rest of your visit, the tag is not loaded on later visits, and the Google cookies set on our domain are deleted. Data Google has already received is governed by Google's Privacy Policy.

3. Children's Data (Under 16)

3.1. Data Minimization for Minors

3.1.1. Self-registration in the App is available only to individuals who are at least 16 years of age. Children under the age of 16 cannot create their own account. The Company does not knowingly permit children under 16 to self-register and does not knowingly collect personal data from children in that age group outside of the Parent-managed flow described below.

3.1.2. A child's account may be created only by a parent or legal guardian (the "Parent"). At account creation, the following are provided:

• Name — a free-form name chosen by the Parent. It need not be the child's real name and functions as a pseudonym (nickname).
• Emoji avatar — selected from a predefined set. Photograph uploads are not available for child profiles.

3.1.3. For a child's account, the following are neither collected nor required: last name, email address, phone number, date of birth, photograph, geolocation data, or any other personal information.

3.1.4. COPPA (United States). For children under 13 who are residents of the United States, the Parent-managed account flow described in this Section 3 is designed to provide "verifiable parental consent" within the meaning of the Children's Online Privacy Protection Act (COPPA, 15 U.S.C. §§ 6501–6506) and its implementing regulations (16 CFR Part 312). By creating an account for a child, the Parent provides informed and verifiable consent for the limited collection and use of the child's information described in this Policy. Parents may at any time (a) review their child's information through the "My Children" section of the App, (b) refuse further collection by deleting the child's account, or (c) request deletion of the child's information by contacting support@teachspace.app. For COPPA-specific inquiries, contact us at the same address with the subject line "COPPA Inquiry."

3.2. Child's Access to the App

3.2.1. A child signs in to the App solely using a PIN code generated by the Parent. A child has no separate password, email address, or other sign-in credentials.

3.3. Parental Control

3.3.1. The Parent has full and unrestricted access to all of the child's activity within the App:

• Sees all of the child's lessons, homework, schedule, and grades.
• Is automatically added by the system as a participant in every chat between the child and the Teacher and can see the full content of the correspondence, including all uploaded files. The Parent cannot be removed from the child's chat.
• Sees a visible marker whenever the child or Teacher removes a message. Removed content is not silently erased from the safety record and remains available to authorized Company personnel for moderation, safety investigations, and dispute resolution.
• The child can exchange messages only with the linked Teacher — communication with other Users is technically impossible.
• If the teaching link ends, the existing chat remains available to the child, Parent, and Teacher as read-only history; no participant can send new messages or files in that chat.
• Sees all files uploaded by the child (for example, photographs of completed assignments or scans of worksheets).

3.3.2. The child may upload files to homework and chats with the Teacher within the overall limits of the Service (see FAQ) — for example, photographs or scans of completed worksheets, or screenshots of solutions. All files uploaded by the child are accessible to the Parent and the Teacher.

3.3.3. Only the Parent may delete a child's account. Before deleting their own account, the Parent must first delete each linked child account via the corresponding function in the App; automatic cascade deletion of child accounts does not apply — this is intended to ensure that any decision to delete a child's learning progress is made deliberately by the Parent.

3.4. Parental Responsibility

3.4.1. By creating an account for a child, the Parent represents and warrants that they are the child's legal guardian and provides informed consent for the child to use the App as described in this Policy.

3.4.2. All responsibility for the child's use of the App, including any content created by the child (whiteboard drawings, assignment answers), rests solely with the Parent.

3.4.3. If we learn that we have inadvertently collected personal information from a child under the age of 16 without the Parent's consent, we will take reasonable steps to delete it.

3.5. AI Features and a Child's Work

3.5.1. A teacher may ask the App to prepare a draft review of homework a student has submitted. Where this is done, the submitted work (for example, a photograph of a completed exercise) and the assignment text are sent to our AI provider, OpenAI, solely to produce that draft.

3.5.2. Only the work itself is sent. The child's name, pseudonym, avatar, account identifier, class and any other profile data held by the App are not transmitted to the AI provider. Please note that the submitted work is sent as the student created it: if a student has written their name on a page, that page is transmitted as photographed.

3.5.3. The AI never grades a child and never decides anything. Its output is a draft visible only to the teacher, who reviews, edits or discards it before any of it reaches the student or Parent. No result is stored on the child's record unless the teacher confirms it. Accordingly, the Service performs no automated decision-making producing legal or similarly significant effects within the meaning of Article 22 of the GDPR.

3.5.4. The AI provider does not use this content to train its models. It is retained by the provider only for a limited period for security and abuse-monitoring purposes, and is then deleted.

3.5.5. AI features are initiated by a teacher on a per-action basis. They never run automatically or in the background over a child's data.

3.6. Children and Telegram

3.6.1. A child account can never be connected to Telegram. The App refuses the connection at every point where it could be made, and no message about a child is ever addressed to a child's own chat.

3.6.2. Where payment reminders concerning a child are sent through Telegram, they are addressed to the Parent, who connects their own Telegram account and may disconnect it at any time. Such a reminder identifies the child by first name only — never by surname — and contains nothing about the child beyond the class name, the amount owed and the lessons it covers.

3.6.3. Advertising measurement is unavailable to child, Student and Parent accounts. Their account can never cause the Meta SDK to initialize, and no account event or Meta matching identifier is created from their Teach Space session. If an adult Teacher initialized the SDK earlier in the same running app process, automatic event logging remains disabled and Teach Space makes no Meta event call for the later ineligible account.

3.6.4. RevenueCat's subscription SDK identifies only authenticated Teacher accounts. A child, Student, Parent, administrator or manager account is never logged in to RevenueCat and its Teach Space account identifier is not sent to RevenueCat. If a Teacher previously used RevenueCat in the same running App process, entering an ineligible account immediately requests that the previous RevenueCat identity be reset to an anonymous state. Anonymous store access may still be used in the unauthenticated Teacher demo solely to display store-localised subscription prices.

4. How We Use Information

4.1. We use the information we collect for the following purposes:

4.2. We do not use your information for:

• Targeted or behavioural advertising based on Teach Space profile, educational content or in-App behaviour.
• Marketing communications (we do not send marketing messages).
• User profiling or automated decision-making.
• Sale or rental to third parties.
• Training of artificial intelligence or machine learning models.
• Any purposes not expressly set forth in this Policy.

5. How We Store and Protect Data

5.1. Storage

5.1.1. Account and Service data are stored in a PostgreSQL database hosted by Neon on Amazon Web Services in the United States (us-east-1 region, N. Virginia).

5.1.2. User-uploaded files (images, documents, and scans) are stored in Amazon Web Services S3 cloud storage (eu-central-1 region, Frankfurt, European Union). Access to files is provided via short-lived presigned URLs; no direct public access to the files is permitted.

5.1.3. Passwords are stored solely as cryptographic hashes (bcrypt with a cost factor of 12, i.e., 2^12 key-derivation iterations) and cannot be recovered in their original form by us or by any third party.

5.1.4. Whiteboard data (drawings) is stored in the database in a structured format (JSON) together with version history. Access to whiteboard data is provided within the scope of the active subscription plan.

5.1.5. Where Telegram payment reminders have been connected (§2.6), we store the chat identifier, Telegram username, first name and language code in the same database. Single-use connection links are stored only as an irreversible cryptographic hash (SHA-256), never in readable form.

5.1.6. The access keys a Teacher provides to connect a payment provider (§2.8) are stored encrypted and are used only to create and check that Teacher's payments. When the Teacher disconnects the provider, the keys are deleted as soon as no payment through it is still pending or open to a refund.

5.1.7. Backups. To be able to restore the Service after a failure, our database provider keeps a recovery history for 7 days and daily snapshots for 14 days, and an encrypted copy of the database is made every day and kept for 30 days in Amazon Web Services S3 in the European Union (eu-central-1, Frankfurt). Backups are used only for disaster recovery. Data deleted from the Service remains in backups until they expire on this schedule.

5.2. Security Measures

5.2.1. We employ a combination of technical and organizational safeguards, including:

• Cryptographic password hashing (bcrypt).
• JWT-based authentication with limited-lifetime access tokens and refresh token rotation that detects and blocks reuse of compromised tokens.
• Storage of authentication tokens in hardware-backed device keystores (Keychain on iOS, Keystore on Android), which provide operating-system-level encryption.
• Rate limiting to protect against brute-force attacks on passwords and codes.
• Audit logging of actions, including IP address, to detect anomalies.
• Storage-quota controls to prevent abuse.
• One-time verification codes with limited lifetimes and attempt limits.
• Removal of EXIF metadata (including geolocation, camera model, and capture date) from images: the mobile App's image picker is configured to exclude EXIF data before upload, and the server additionally strips EXIF from profile avatar images as a second layer of protection.
• Server-side encryption of all files in cloud storage (AES-256).

The specific lifetimes of tokens and verification codes, as well as the image formats supported for EXIF scrubbing, are listed in the FAQ.

5.3. Data Transmission

5.3.1. All data transmitted between the App and our servers is sent over encrypted protocols (HTTPS for HTTP requests; WSS for WebSocket connections).

5.4. Security Limitations

5.4.1. Notwithstanding the safeguards we employ, the Company cannot guarantee absolute security of data during transmission over the internet or storage on electronic media. You transmit data at your own risk.

5.4.2. Data breach notification. In the event of a personal data breach, the Company will notify the competent data protection supervisory authority within 72 (seventy-two) hours after becoming aware of the breach, as required by Article 33 of the GDPR and analogous provisions of applicable law. Where the breach is likely to result in a high risk to the rights and freedoms of data subjects, the Company will, without undue delay, inform affected Users of the breach, its likely consequences, and the measures taken. If notification within 72 hours is not feasible, the Company will provide the notification together with reasons for the delay.

6. To Whom We Disclose Data

6.1. Service Providers and Payment Partners

We share the minimum amount of data necessary with the following third parties solely to operate the Service:

Website subscriptions are sold through Link, Stripe's merchant-of-record service. Link charges the payment, handles applicable sales tax and VAT, sends receipts and purchase emails, and offers payment support and subscription management at link.com; for these purchases it uses the payment and billing data as a separate controller under its own privacy policy. Teach Space does not store full payment card numbers or card security codes.

Each service provider maintains its own privacy policy, which you may review on its website, including RevenueCat and Stripe. The Company does not control, and is not responsible for, the data practices of third parties.

6.2. We Do NOT Share Data With:

• Advertising networks or platforms, except the limited, optional adult-Teacher Meta measurement described in §2.7 and the Google tag a website visitor accepts (§2.11).
• Data brokers.
• Analytics or marketing platforms, except Google Analytics on our public website after a visitor accepts cookies (§2.11).
• Any third parties other than those listed in Section 6.1.

A calendar application you connect (§2.3) and a video provider whose player a Teacher adds to a Teacher Website (§2.9.5) receive information directly from your calendar application or browser, at your or the Teacher's choice; they are not service providers of the Company.

6.3. Other Disclosures

6.3.1. We may disclose your data in the following circumstances:

• In response to a lawful request from a governmental authority (court order, subpoena, law-enforcement request) in accordance with applicable law.
• To protect the rights, property, or safety of the Company, our Users, or the public, where we reasonably and in good faith believe disclosure to be necessary.
• In connection with a reorganization, merger, acquisition, or sale of Company assets — provided that the successor assumes the obligations of this Policy with respect to previously collected data.
• With your express consent, in cases not otherwise provided for in this Policy.

6.4. Internal Administrative Access

6.4.1. A limited number of authorized Company personnel (administrators and managers) have access to User data through internal administrative tools solely for the following purposes: technical User support; content moderation; resolution of disputes between Users; platform security; and diagnosis and remediation of technical issues.

6.4.2. Administrative access is provided on a least-privilege basis. Administrator actions that affect user accounts or user data are recorded in an audit log. The Company does not use administrative access for any purpose unrelated to providing and operating the Service.

6.4.3. Report review. Reports submitted by Users through the in-App "Report" function (see Terms §5.3) are reviewed by authorized personnel within 24 (twenty-four) hours of submission. Where a violation is confirmed, the Company takes appropriate action, which may include removal of the offending content and suspension or termination of the violator's account. Report records are retained for up to 12 (twelve) months after resolution for audit and dispute-resolution purposes, after which they are deleted.

7. Authentication Token Storage and Tracking Technologies

7.1. Mobile App. The mobile App does not use cookies. Authentication is performed using JWT tokens of two types — an access token and a refresh token. Both are stored in hardware-backed device keystores: the iOS Keychain and the Android Keystore, which provide operating-system-level encryption. Specific token lifetimes are listed in the FAQ.

7.2. Web-based Service. Website authentication is maintained using only essential cookies that are set HttpOnly, Secure, and SameSite=Strict. These cookies store only the session token needed to keep you signed in and are not used for tracking, analytics, advertising, or any non-essential purpose. Our public website also sets one essential cookie, ts_consent, which remembers your cookie choice for 6 months (§2.11). Payment-provider technologies are described separately in Section 7.4.

7.3. Except for payment-provider technologies described in Section 7.4 and, on our public website, the Google tag after you accept cookies (§2.11), we do not use:

• Non-essential cookies (first-party or third-party).
• Tracking pixels, web beacons, or similar technologies.
• Device fingerprinting.

7.4. Website payments. Payment-provider components may use cookies, device information, and related technologies for payment authentication and fraud prevention. These practices are described in Stripe's Privacy Policy and Cookie Policy.

7.5. Teacher Websites. Teacher Websites set no cookies and use no trackers; embedded video players are described in §2.9.5.

7.6. Managing cookies. Use Cookie settings at the bottom of any page of our public website to change your choice at any time. You can also delete cookies in your browser's settings.

8. Your Rights

8.1. General Rights of All Users

Regardless of your location, you have the right to:

• Access — request information about what data of yours we hold and how it is processed.
• Correction — update or correct inaccurate data through the App's profile settings or by contacting us.
• Deletion — delete your account and all associated data via the "Delete account" function in the App. The deletion process is described in Section 9.
• Export — request a copy of your personal data by written request to support@teachspace.app. Requests are processed manually: after verifying your identity, we will compile the data in a structured, machine-readable format (JSON) and send it to you within 30 days of receipt of the request.
• Withdrawal of consent — where we rely on your consent (for example, for push notifications or for optional profile data), you may withdraw that consent at any time without affecting the lawfulness of processing carried out before the withdrawal. You may do so by disabling the relevant feature in the App, revoking the corresponding permission in your device settings, or contacting us. You may also delete your account at any time.

8.2. Additional Rights for EU/EEA Residents (GDPR)

If you are a resident of the European Union or the European Economic Area, you additionally have the right to:

• Restriction of the processing of your personal data in certain circumstances.
• Object to processing based on our legitimate interests.
• Data portability — receive your data in a structured format for transmission to another controller.
• Lodge a complaint with the data protection supervisory authority in your country.

Legal bases for processing:

8.3. Additional Rights for California Residents (CCPA/CPRA)

If you are a California resident, you have the following rights under the California Consumer Privacy Act, as amended by the California Privacy Rights Act (together, the "CCPA/CPRA"):

• Right to know — the categories and specific pieces of personal information we collect, the sources of that information, the business or commercial purposes for collecting it, and the categories of third parties to whom we disclose it.
• Right to delete — request deletion of personal information we have collected from you.
• Right to correct — request correction of inaccurate personal information we maintain about you.
• Right to limit use of sensitive personal information — direct us to limit the use and disclosure of any sensitive personal information (SPI) to purposes necessary to provide the Service. We do not use SPI for purposes that would require this limit to be exercised; see §8.3.2 below.
• Right to opt out of sale or sharing — we do not sell personal information, and we receive no money or other consideration for any disclosure described in this Policy. We do not share personal information for cross-context behavioral advertising except for the optional adult-Teacher advertising measurement described in §2.7, which takes place only where that Teacher has given separate, affirmative, withdrawable consent (and, on iOS, App Tracking Transparency authorization). That disclosure is limited to Meta's app-scoped anonymous identifier, the standard registration, checkout-initiation and subscription events, and the associated amount and currency. To opt out, turn the setting off in Profile → Ads and privacy at any time, or contact us using §8.4; on iOS you may also revoke App Tracking Transparency in system Settings. Student, child and Parent accounts are never eligible, and their data is never shared for advertising under any circumstances. On our public website, the Google tag described in §2.11 is loaded only after you accept cookies, with ad personalization switched off; you can opt out at any time through Cookie settings, and a browser's Global Privacy Control signal is treated as an opt-out.
• Right to non-discrimination — we will not deny you the Service, charge different prices, provide a different level or quality of Service, or suggest that we may do any of those things because you exercised your CCPA/CPRA rights.

8.3.1. Categories of Personal Information We Collect

8.3.2. Sensitive Personal Information (SPI)

The Company does not collect or use sensitive personal information for purposes that would trigger the CCPA right to limit its use. Passwords are stored only as irreversible cryptographic hashes (bcrypt) and are used solely for authentication; they are never disclosed, shared, inferred from, or used for any other purpose. We do not collect precise geolocation, racial or ethnic origin, religious beliefs, union membership, genetic or biometric data, health data, or data concerning sexual orientation.

8.3.3. Authorized Agents

You may authorize another person to make a CCPA/CPRA request on your behalf. We require written proof of authorization (such as a power of attorney) and verification of both your identity and the agent's identity before acting on the request.

8.3.4. No Financial Incentives

The Company does not offer any financial incentives or price/quality differences in exchange for the collection, retention, sale, or sharing of personal information.

8.4. How to Exercise Your Rights

To exercise any of the foregoing rights, contact us at support@teachspace.app. We will respond within no more than 30 days (for GDPR requests) or 45 days (for CCPA requests). We may request verification of your identity to protect against unauthorized requests.

9. Data Retention and Deletion

9.1. Retention Periods

The Company retains your data while your account remains active. Access to your own historical content (messages, lessons, homework, earnings records, and saved whiteboards) is determined by your current subscription plan — older content may be temporarily hidden and is automatically restored when you upgrade to a plan that covers it. The Company deletes your data only in the circumstances described in §9.2 (account deletion) and §9.5 (prolonged inactivity).

Short-lived technical identifiers — verification codes, JWT access tokens, and refresh tokens — have automatically expiring lifetimes. Specific values are listed in the FAQ.

9.2. Data Deletion Procedure

9.2.1. When you delete your account through the App:

• Profile data is flagged as deleted and immediately becomes unavailable to other Users and via the API.
• Linked child accounts (if you are a Parent) must be deleted by you before deleting your own account; cascade deletion does not apply (see §3.3.3).
• Messages and lesson data are flagged as deleted and no longer displayed.
• Uploaded files in cloud storage (AWS S3) are marked for deletion and are physically deleted within 30 days after account deletion.
• Whiteboard data (drawings) is flagged as deleted together with the account and is physically deleted within 30 days.
• A Teacher Website is taken offline immediately; it is deleted, together with its visitors' requests, when the account is physically deleted.
• Backup copies expire on the schedule described in §5.1.7.
• De-identified audit log records (from which an individual user cannot be identified) may be retained for up to 1 year for security, dispute resolution, and legal compliance purposes.
• Subscription data held by RevenueCat is governed by RevenueCat's own retention policy, which the Company does not control.

9.2.2. Account recovery window. Within 30 days after deletion, you may restore your account by signing in with the previous email and password — the system will automatically restore access, and all data retained up to that point will again become available. After the 30-day period, the data is physically deleted and recovery is no longer possible.

The recovery mechanism applies only to accounts with an email and password (Teacher, Parent, or self-registered Student). Child accounts created by a Parent, which use PIN sign-in, cannot be recovered — after deletion, the Parent may only create a new account for the child with a new PIN.

Recovery also does not apply to an account blocked by the Company under §11.2 of the Terms of Service.

9.3. Plan-Based Access to Historical Data

9.3.1. No deletion on plan change. Downgrading a subscription plan, the end of a trial, or allowing a paid subscription to lapse does not delete any of your data. Content that falls outside the limits of your current plan becomes temporarily inaccessible ("hidden") and is automatically restored in full when you upgrade to a plan that covers it.

9.3.2. Scope of plan-based access. The limits that define what is visible under your current plan (for example, the length of the history window, the number of linked Students, storage quota, and whiteboard saving) are determined by the plan terms shown in the App at the time of purchase and in the FAQ. The Company may revise plan limits over time.

9.3.3. Storage quota behavior. If the total size of your uploaded files exceeds the storage quota of your current plan, your existing files remain stored and visible within the App. Only new uploads are blocked, until the total falls below the quota — which you may achieve either by deleting files yourself inside the App or by upgrading to a higher plan. The Company does not automatically delete any files because of a plan change.

9.3.4. Linked Students. If the number of Students linked to a Teacher exceeds the new plan's limit, existing links are preserved; however, adding new Students is blocked until space is freed under the new plan or an appropriate paid plan is activated.

9.4. Request for Expedited Deletion

9.4.1. You may request expedited physical deletion of your data by contacting support@teachspace.app. We will use commercially reasonable efforts to fulfill the request within 30 days, except for data that must be retained under applicable law or to protect the Company's legitimate interests (for example, for dispute resolution or fraud prevention).

9.5. Inactive Accounts

9.5.1. To limit the long-term retention of data for abandoned accounts, the Company operates an automated inactivity policy in addition to user-initiated deletion.

9.5.2. Definition of activity. An account is considered "active" whenever the User signs in, opens the App while authenticated, or performs any authenticated action (for example, sending a message, scheduling a lesson, or uploading a file). Any such action resets the inactivity counter for that account.

9.5.3. Warning. If an account shows no activity for 12 (twelve) consecutive months, the Company will send a notification email to the address on file warning that the account will be deleted if no activity occurs within the next 30 days. The Company takes reasonable steps to avoid duplicate warnings, but transient delivery failures may occasionally result in a second notification being sent. Child accounts (which do not have their own email address) inherit the status of the Parent account linked to them and do not receive a separate warning.

9.5.4. Soft deletion. If no activity is recorded within 30 days after the warning email is sent, the account is soft-deleted automatically, in the same manner as a user-initiated deletion under §9.2.

9.5.5. Recovery window. The 30-day recovery window described in §9.2.2 applies to accounts soft-deleted under this Section in the same way. Within that window, the User may restore the account by signing in with their existing credentials.

9.5.6. Physical deletion. After the 30-day recovery window expires, the account and all associated data are physically deleted as described in §9.2.1, subject to the same limited exceptions for audit logs, subscription records, and legally required retention.

10. International Data Transfers

10.1. The primary database is located in the United States (Neon, on AWS us-east-1, N. Virginia), and our application servers run in the United States (Render, Virginia). User-uploaded files and database backups are stored in the European Union (AWS S3, eu-central-1, Frankfurt, Germany).

10.2. Some of our service providers are located outside the EEA:

10.3. The Company is registered in the United States (Wyoming) and may access data from the United States for administrative and technical support purposes.

10.4. When data is transferred outside of the EEA, we secure the transfer through appropriate legal mechanisms (EU Standard Contractual Clauses, adequacy decisions, or other mechanisms provided for in Chapter V of the GDPR).

11. Device Permissions

11.1. The App may request the following permissions on your device:

11.2. All permissions are requested only upon first use of the corresponding feature (just-in-time permission) and may be declined. Declining a permission will limit that specific feature but will not prevent use of the remaining functionality of the App.

11.3. You may revoke granted permissions at any time through your device settings (Settings → Teach Space → Permissions).

12. Apple App Store and Google Play Store Disclosures

12.1. Apple App Store (iOS)

12.1.1. A measurement-enabled iOS release uses ATT only for the optional eligible adult-Teacher flow in §2.7. ATT is never requested from Student, child, Parent, guest, administrator or manager accounts. Denial does not limit any App feature.

12.1.2. In accordance with Apple Privacy Nutrition Labels requirements, the App discloses the following data types: contact information (email, and — only for users who connect Telegram — their Telegram username and first name), user content (messages, files), identifiers (user ID, device push token, Telegram chat identifier where connected, and the Meta app-scoped anonymous identifier only under §2.7), purchase data (subscription history, transmitted to RevenueCat and optionally measured with Meta under §2.7), product interaction, and diagnostic data. The Meta identifier, product interaction and purchase data involved in §2.7 must be disclosed as used for tracking where required by Apple's definitions.

12.2. Google Play Store (Android)

12.2.1. In accordance with Google Data Safety Form requirements, the App discloses: collection of contact information, user content and identifiers; transmission of payment-reminder content to Telegram where connected; transmission of data to RevenueCat for subscription processing; optional adult-Teacher app-interaction, anonymous-identifier and purchase measurement with Meta under §2.7; transmission of de-identified crash data to Sentry; data encryption in transit; and the user's ability to delete data. The App does not request Android's advertising-ID permission.

12.3. Priority of App Store Disclosures

12.3.1. The accurate and current content of the Apple Privacy Nutrition Labels and Google Data Safety Form is displayed directly on the App's listings in the App Store and Google Play Store and may be more detailed or more restrictive than the wording of this Policy. In the event of any discrepancy, the disclosures on the applicable app store listing will apply, provided that they do not conflict with this Policy or with the requirements of applicable law.

13. Do Not Track and Global Privacy Control Signals

13.1. Some browsers and devices transmit "Do Not Track" (DNT) or Global Privacy Control (GPC) signals. Native mobile apps do not receive browser DNT/GPC signals. The optional processing in §2.7 is controlled instead by the App's adult-Teacher setting and, on iOS, ATT. All other Users remain ineligible regardless of a browser signal.

13.2. On our public website, a GPC signal is treated as declining cookies for analytics and advertising: the Google tag described in §2.11 is never loaded in that browser. DNT signals are not acted on separately, because no analytics or advertising tag runs on our website without your consent.

14. Additional State-Specific Rights

14.1. Nevada Residents

14.1.1. Under Nevada Senate Bill 220 (NRS 603A), Nevada residents have the right to submit a request to opt out of the sale of certain personal information to third parties.

14.1.2. The Company does not sell personal information as defined under Nevada law. If you are a Nevada resident and wish to confirm this, you may send a request to support@teachspace.app with the subject line "Nevada Privacy Request."

14.2. California Minors (Online Eraser)

14.2.1. Under California Business & Professions Code § 22581, California residents who are under 18 years of age and who are registered users of the App have the right to request removal of content or information they have publicly posted in the App. To exercise this right, contact support@teachspace.app with the subject line "California Minor Removal Request." Please note that content may remain on our servers in backup form for a limited period, as described in Section 9.

15. De-identified and Aggregated Data

15.1. The Company may create, use, and disclose de-identified and aggregated data (that is, data that cannot be used to identify an individual user) for any lawful purpose, including: improvement and development of the Service; statistical analysis; research; publication of aggregate statistics (for example, "X lessons have been conducted on the platform"); marketing materials; and presentations.

15.2. De-identified data is not personal information and is not subject to this Policy.

16. Changes to this Policy

16.1. We reserve the right to update this Policy from time to time as necessary. The Last Updated date is always shown at the top of the document.

16.2. You will be notified of changes via the App. Material changes (expansion of the categories of data collected, new processing purposes, transfers to new third parties) may require your renewed consent where required by applicable law.

16.3. Your continued use of the App after publication of changes constitutes your acceptance of the updated Policy. If you do not agree to the changes, stop using the App and delete your account.

17. Governing Language

17.1. This Policy may be translated into other languages for your convenience. In the event of any discrepancy or conflict between the English version and any translation, the English version shall govern.

18. Contact Information

For any questions relating to privacy and data protection, please contact:

• Company: Teach Space LLC
• Jurisdiction: State of Wyoming, USA
• Privacy email: support@teachspace.app
• Response time: Up to 30 days (GDPR) / up to 45 days (CCPA)

If you believe your rights have been violated, you may file a complaint with the data protection authority of your country (for EU/EEA residents) or with the Attorney General of your state (for U.S. residents).

By using Teach Space, you acknowledge that you have read, understood, and agreed to this Privacy Policy.