Privacy Policy
ThinkEdge Learn is a learning platform for K-12 students. Because we knowingly collect data from children, this policy is more detailed than a typical privacy notice — every section maps to a specific legal requirement (COPPA, GDPR Article 8 / UK AADC, DPDPA, FERPA).
1. Who we are
ThinkEdge Learn is the name this learning platform is published under, at thinkedgelearn.com. In this policy, “ThinkEdge Learn”, “we” and “us” mean the team that operates the platform.
This policy explains what information we collect when you or a child uses ThinkEdge Learn, why we collect it, who we share it with, how long we keep it, and what rights you have over it. It applies to the website, the lessons, the in-browser simulator and the teacher dashboards.
Write to us at admin@thinkedgelearn.com for anything in this policy — a privacy request, a question about a child’s data, or a copy of this policy. The same address reaches our Data Protection Officer.
2. Children and parental consent
We do not knowingly collect personal data from a child under the parental-consent age for their region without verifiable parental consent. The age thresholds we apply are:
- Under 13 — United States (COPPA).
- Under 16 — European Economic Area (GDPR Article 8).
- Under 13 — United Kingdom (UK AADC).
- Under 18 — India (DPDPA).
- Under 16 — everywhere else, as a conservative default.
When a child signs up, we route them to a parent-consent flow: the parent enters their email, ticks an explicit guardian-consent checkbox, and confirms through a one-time verification link. Until that consent is verified, we do not open the child’s account.
Schools: when a child joins a teacher-managed class, we treat the school as acting under FERPA’s legitimate educational interest and the teacher as the data controller for the class roster. The teacher must acknowledge this authority at class creation.
3. What we collect
We collect only what we need to operate the platform:
- Account: a parent-verified email address and a display name chosen by the student.
- Date of birth — used to work out which children’s privacy rules apply. It is never shown publicly.
- Learning progress: lessons started and completed, quiz scores, and project state, stored per account.
- Teacher-managed class rosters: student display names and the class code.
- Payment: handled by Razorpay. Card numbers never touch our servers.
We do not collect phone numbers, home addresses, photographs, biometric data, or advertising identifiers. We do not allow behavioural advertising to under-13s or under-16s, whichever threshold applies in your region.
4. How we use data
- To create and operate your account.
- To deliver and improve the lessons, the projects and the virtual lab.
- To track learning progress and produce the teacher dashboards.
- To verify parental consent under COPPA, GDPR-K and DPDPA.
- To meet legal obligations — account-deletion requests and school-transfer requests.
- To read aggregate, de-identified, cookie-less analytics (Plausible) that tell us which lessons need work.
5. Cookies and analytics
We use Plausible for product analytics. Plausible is cookie-less, sets no persistent identifier, and does not profile individual users. Per ICO guidance, cookie-less analytics does not require consent under PECR or GDPR.
We may also load Google Analytics 4 when you explicitly accept analytics cookies. GA4 sets first-party cookies (_ga, _gid) for campaign attribution. We do not enable Google Signals, remarketing audiences, or any feature that creates persistent cross-site profiles for minors.
You can change your choice at any time with the “Manage cookie preferences” button on this page, or the “Cookie preferences” link in the site footer.
6. Sharing and third parties
- Supabase — database and sign-in. A data processing agreement is on file.
- Vercel — hosting. Logs are retained for 30 days.
- Razorpay — payments. PCI-DSS scope is theirs; we see order IDs only.
- Plausible — analytics. Cookie-less, no personal data sent.
- Google Analytics 4 — analytics, only after you consent.
We do not sell personal data, and we do not share it for anyone else’s advertising.
7. International transfers
Where data is transferred outside the country of the user — for example an EEA user whose data is stored in the United States — we rely on Standard Contractual Clauses or an equivalent safeguard, and we keep the transfer limited to what the service needs.
8. Retention
We keep learning progress while the account is active. Inactive accounts are anonymised after 24 months. Deletion requests are fulfilled within 30 days, as required by GDPR Article 17 and DPDPA Section 12. Backups roll off within a further 30 days.
9. Your rights
Parents and, where applicable, children can:
- Request a copy of all the data we hold about the child.
- Request deletion, which we complete within 30 days.
- Withdraw parental consent, which stops further processing.
- Correct inaccurate data.
- Lodge a complaint with their data protection authority.
Use the Delete my data page to start a request, or email admin@thinkedgelearn.com.
10. Security
Data is encrypted in transit (TLS 1.2 or better) and at rest (Supabase Postgres encryption at rest, with row-level security on every table). Access to production data is restricted to named engineers through single sign-on and just-in-time access. We commission an annual third-party security review.
11. Changes to this policy
Material changes are notified to the parent email on file at least 30 days in advance. Continued use of the service after the effective date means the change is accepted. The date at the top of this page is the last time it changed.
12. Contact
ThinkEdge Learn
Data Protection Officer
Email: admin@thinkedgelearn.com
Write to us from the address above and we will reply within 30 days.