Privacy and learning information

01

Business identity

Techademy AI is the trading name of a sole-trader business.

The final legal identity and approved business/contact address must be confirmed before real bookings open. No private residential address is published here.

02

Current website and enquiries

The public contact form prepares an email draft locally in your browser; it does not submit or save an enquiry to Techademy. If you choose to send the email in your email application, the message contains the information you provide.

The website uses normal request information to operate pages and security. Existing platform code includes authenticated session handling and learner draft recovery; these are not a claim that production enrolment or reporting is fully released.

The final notice must confirm the actual operational logs, recipients, purposes and applicable lawful bases before release.

03

Accounts, enrolment and payments

The intended service uses parent accounts linked to child accounts, or adult learner accounts. Anticipated information includes necessary name/contact/account information, booking and payment records and minimum information needed for enrolment and learning.

The exact live fields, payment handling and access permissions must be verified before accepting bookings. This page does not claim that payment or parent-consent workflows are operational.

04

Learning evidence and reviewed reports

Planned learning information includes attendance, lesson progress, assignments, submissions, feedback, achievements, skills evidence, project progress, reports and certificates.

The approved reporting model is structured learning evidence → personalised generated report → tutor review → parent/learner access. This is an intended capability, not autonomous profiling of a child’s intelligence, personality or potential.

Final wording, lawful-basis assessment, child-specific risk assessment and safeguards around generation and human review require professional review.

05

Optional Showcase publication

Public publication is a separate choice from learning participation, with teacher review and parent consent intended before publication. Full child names, emails, schools, addresses and private learner data must not automatically be exposed.

Current public Showcase examples are identified sample content, not evidence of released learner-publication workflows.

Publication permissions, attribution choices, withdrawal handling and the applicable lawful basis must be approved separately.

06

Service providers

The anticipated provider categories are hosting, authentication/database, payment processing, Workspace/Calendar/Meet, email/communications and AI tools used in course delivery. This is a planning inventory, not a statement that every integration is live.

Confirm the actual provider/processor list and services enabled at release.

Review contracts, subprocessors, international transfers, locations and appropriate safeguards. No DPA, data-location or compliance certification is asserted here.

07

Retention and access

Public waitlist: we collect an adult email, programme choice and consent choices, not child details. We retain the request for 12 calendar months after the last meaningful interaction. Routine internal review, email opens and duplicate submissions do not restart that period. Withdrawal stops contact and removes or anonymises contact information, except where a documented legal obligation requires restricted preservation. Optional promotional-email consent is separate and unchecked by default; no promotional email is sent without verified valid consent. Contact the privacy address below to withdraw, change consent, or request access, correction or deletion. Other account, booking/payment, learning, operational and recording retention schedules remain subject to review.

Final access restrictions, deletion exceptions and retention wording require review against the actual service and applicable requirements.

08

Requests, rights and complaints

Use the privacy email link below for access, correction, deletion where applicable, consent questions, objections, other applicable rights or a complaint. Identify the relevant account or booking without sending passwords, payment-card details or unnecessary sensitive information.

The final rights notice must confirm applicable rights, identity verification, response procedures and the appropriate external complaint route. This framework does not establish automated deletion or request-handling tooling.