Privacy Policy
How information supports accounts, classes, communities and private learning workspaces.
Updated: 4 November 2026 · Terms 2026-11-04 · Privacy 2026-11-04
Operator: Legal operator identity awaiting confirmation
Address: Business address awaiting confirmation
Contact: Public legal contact details are awaiting confirmation. Signed-in users can currently open Help & support. This interim route does not replace a public legal contact.
1. Information involved
Depending on activity, the platform processes account and contact details, profile photos, tutor applications and assessment evidence, academic selections, bookings, payment and access records, messages, community posts, materials, private typed notes and handwriting, and technical or security logs.
Payments use the configured provider. Do not submit card numbers, passports, banking credentials or unnecessary sensitive documents through messages or ordinary feedback forms.
2. Purposes and legal bases
Information supports sign-in, service delivery, tutor applications, access checks, payments and refunds, communication, moderation, fraud prevention and support. Depending on the operation and applicable law, processing may rely on contractual necessity, legal obligations, legitimate interests or consent.
Before commercial launch, the operator must map each purpose to its specific legal basis, document legitimate interests where relied upon, and explain optional consent-based processing. Consent is not a blanket basis for every activity.
3. Visibility and recipients
Published profiles, listing information and selected previews may be visible to visitors. Discussions and shared files follow membership and access settings. Tutors receive information needed to manage classes and purchases. Private notes are account-scoped and not published to students or tutors; authorized service operations may still process them.
Infrastructure supports authentication, hosting, database and files, payments, video delivery and configured email or monitoring. The implementation uses Supabase for authentication, database and files; Railway for hosting; Stripe for payments and onboarding; Bunny for video; Resend where email is enabled; Sentry for configured error monitoring; optional PostHog usage analytics after acceptance; and OpenAI where tutor-controlled generation is enabled. Final review must confirm enabled providers, recipients and international-transfer safeguards. Where enabled, tutors can explicitly send selected PDF or text source material to the configured AI service to draft quizzes or flashcards. Tutors must review drafts before publishing. This does not give AI access to unrelated student assignments or private notebooks.
4. Browser storage
Authentication cookies support sign-in. Browser storage can retain drafts, note recovery data and preferences. Embedded players may use their own storage. See Cookies & browser storage. Clearing site data may remove unsaved local work.
5. Retention and security
Information should be retained only as needed for its purpose, applicable obligations and legitimate disputes. The operator must establish retention periods or criteria for accounts, messages, notes, recordings, transactions, logs and backups before launch. Account deletion does not promise immediate deletion of legally required financial records.
Authentication, access controls and protected delivery limit access. No online service guarantees absolute security or prevents every copy of displayed content. Do not put confidential information in public posts or previews.
6. Your rights
Depending on applicable law, you may request access, correction, erasure, restriction, portability or object to processing. You may withdraw consent where relied upon and complain to the relevant data protection authority. Rights are not postponed because a self-service button has not been built.
Contact Public legal contact details are awaiting confirmation. Signed-in users can currently open Help & support. This interim route does not replace a public legal contact. to make a request. We must respond without undue delay and generally within one month; any lawful extension must be explained within that first month. Account ownership may need verification without unnecessary identity documents. The final notice must identify the controller and relevant authority, and a working request-handling process must be in place.
Supervisory authority
You can contact the data protection authority relevant to your situation. In Hungary, see the Hungarian National Authority for Data Protection and Freedom of Information (NAIH). The final operator review must confirm establishment, cross-border processing and the relevant lead authority, if applicable.
Processing map for launch review
Account access, bookings, paid access and support are proposed service-delivery purposes; tax and legally required records need their applicable legal obligations; proportionate security and fraud controls require a documented basis and safeguards; optional analytics and source-specific AI permissions must stay separate from necessary account processing. The operator and counsel must confirm the basis, recipients, transfer safeguards and retention for each actual processing operation before final publication.
7. Children and future features
Minimum age, guardian authorization and protections for younger users require confirmation before commercial onboarding of minors. Recordings may contain participants’ voices, images or contributions; recording and sharing must be explained beforehand.
Recording, transcription, identity checks and AI assistance require feature-specific disclosures and appropriate permissions; do not assume that agreeing to an account authorizes every later use. Availability depends on enabled features. Live recordings and protected lesson files can contain voices, images and student contributions. Optional PostHog analytics can be declined or withdrawn through Cookies & storage; error monitoring is configured separately. AI generation is optional and requires the tutor’s source-specific permission.