Controller and relationship to main policy
This page supplements the Privacy Policy. The controller identity and contact are in the Legal Notice; privacy requests can be sent to hello@myreadingroom.net. The final service-provider, payout and processor arrangements must be confirmed before accepting payments.
Information processed
Connect can process account IDs, age confirmation, public names, subjects, languages, applications, profile text, verification status and administrator notes, Q&A, moderation reports, lesson availability, booking times and status, classroom notes, lesson ratings, refund requests and account notifications. Paid activities may require tutor identity, professional and tax data, Stripe account identifiers and transaction references. Do not submit more sensitive information than requested.
Purposes and legal bases
Account and booking data may be processed to perform user agreements (GDPR Article 6(1)(b)); legally required transaction, tax and safety records on legal obligation (6(1)(c)); abuse prevention and dispute handling on legitimate interests (6(1)(f)) where balanced; optional nonessential communications or recording only with a separate valid basis such as consent (6(1)(a)). Exact bases, records and recipients must be validated against actual operations. Sensitive personal-data categories require an additional Article 9 condition where applicable.
Sharing and external providers
An approved tutor profile and verified review may become publicly visible; classroom notes are intended only for authorized participants. Payment-card details are entered directly at Stripe Checkout, not stored in the website JavaScript. Supabase and Netlify support hosting/authentication; Stripe processes payments and payouts; an external video provider receives data when you choose to join its service. Email delivery and analytics/ads, if enabled, require their own disclosures and consent where required.
Retention, international transfers and rights
Use the main Privacy Policy for general rights and details. Account records are held while needed to deliver the service; financial, fraud and dispute records may remain for legally required periods; verification files should not be retained longer than necessary. Exact retention periods and any international transfers/safeguards need a documented data map before live paid operations. You may request access, rectification, erasure, restriction, portability or objection as applicable, and complain to the competent data protection authority.
No covert recordings or AI sharing
The current classroom opens external video links and shared text/whiteboards; it does not automatically record calls. No private classroom material should be fed to an external AI service without a separate legal and product review with clear disclosure. Public Q&A posts are distinct from private academic library files.
Separate activation review required
The community and tutor modules may process public profiles, reports and classroom material when activated; the existence of data tables alone does not establish that sharing, moderation, age controls or deletion works correctly. No public identity documents should be collected by casual uploads. Before Stripe or paid tutoring is enabled, the operator must complete the provider register, legal bases, data-retention schedule, trader-identification workflow, payment contract mapping and security assessment.
No active paid tutoring data flow
Tutoring identity verification, payments, tutor payouts and live public community publication are not operational in this beta. Draft descriptions do not authorize collection of identity documents, card details or new categories of personal data. If such processing is enabled later, this policy and the relevant product disclosures must be updated first, with actual recipients, legal bases, retention rules and any required consent.