Privacy Policy for Lexiage

Account data. Name, email address, password (stored only as a secure hash by our authentication provider), account role (individual, parent, teacher, school administrator, student), preferred language, and — for schools — school name and billing contact details.

Student accounts. Students created under a school or teacher account do not need an email address — they sign in with credentials issued by their school or teacher. Creating a student account requires only a first and last name (schools may use code names if they prefer) and, during onboarding, a date of birth for level placement. No email address, phone number, or other contact details are ever collected from students.

Age calibration data. Users (or the adult managing their account) may provide a date of birth. We use this only to calibrate difficulty, unlock the appropriate learning levels, and make AI-generated content age-appropriate. We do not use it for advertising.

Learning and usage data. Wordlists created or studied, study-session results, progress and mastery metrics, streaks, class membership, and feature usage. Teachers and school administrators can see the progress data of the students in their classes or school.

Voice recordings. In voice-based exercises, the audio clip is sent to our speech-to-text processor (Groq, see Section 3) for transcription and scoring. Lexiage never stores audio recordings.

AI prompts. When a user requests AI-generated content (wordlist generation, adaptive wordlists, Word Workshop sentence checks, support chat), the only data sent to our AI processors is: the prompt the user types, the user's age (a single precalculated number — never the date, month, or year of birth), and predefined technical parameters needed for the tool to work. No name, no email address, no account identifiers — nothing else.

Support conversations. Messages sent to the in-app support chat. The support chat is available only to teachers and school administrators, and exists solely to help with the effective understanding and use of Lexiage, answering questions about the app within its built-in knowledge base — it is not a general-purpose assistant and will decline unrelated requests.

Community sharing. If you share a wordlist with the Lexiage community, other users see only the nickname you chose and your age band alongside the shared content — never your real name, email address, or any other personal data.

Payment data. Payments are handled entirely by Stripe. We never see or store card numbers. We store the subscription status, plan, billing country, and invoice records that Stripe reports to us. Stripe collects the billing address and, where applicable, tax IDs, and acts as its own data controller for payment processing (see Stripe's privacy policy).

Technical and security data. IP address, browser and device information, and security signals (for example, the result of the Cloudflare human-verification check at login, and rate-limit counters). Server logs reference internal account IDs, not names or emails.

Error and diagnostics data. If something breaks, our error-monitoring tool (Sentry) records the technical details of the error. It is configured to scrub personal data from error reports before they are stored, and error data is hosted in the EU.

What we do NOT collect: we run no third-party advertising or cross-site tracking, we do not sell personal data, and we do not use third-party product-analytics tools in the app.

We do not use personal data for automated decisions with legal or similarly significant effects, and we do not use student data for marketing.

Lexiage is designed to be used by children through a school, teacher, or parent account — children cannot sign themselves up directly. Individual accounts created directly on Lexiage require an email address and are intended for users old enough to consent for themselves; children's accounts are always created and managed by a school, teacher, or parent.

• EU/UK (GDPR Art. 8): where a child is below the age of digital consent in their country, the school or parent that creates and manages the account provides the required consent/authority. Schools and teachers warrant, when creating student accounts, that they have obtained any parental consent their institution requires.
• United States (COPPA): for students under 13, we rely on the school acting as the parent's agent to authorize the collection of student information for educational purposes only. We use student data solely to provide the service to the school, never for behavioral advertising, and we never sell it.
• US student records (FERPA): where Lexiage receives information from a student's education record, we act at the school's direction as a "school official" with a legitimate educational interest, under the school's control.
• We collect the minimum data needed from students: a first and last name (schools may use code names), a date of birth for level placement, and learning progress. Sign-in credentials are generated automatically by the system. Student accounts have no email address and receive no email from us.
• When AI features are used by a child, only the child's age is sent to the AI provider — a single precalculated number, never the date of birth and no identifying information.
• Schools and parents may review or request the deletion of a student's personal data at any time (Section 6).

• Personal data (name, email address, date of birth): kept while the account exists, and removed on verified request (Section 6). For students, personal data is deleted on request of the school and/or parents.
• Content created in the app and learning-result metrics: retained — in anonymized form once personal data has been removed — for the benefit of other users and to improve Lexiage.
• Voice recordings: never stored by Lexiage.
• Invoices and payment records: 10 years (required by Portuguese/EU accounting law).
• Server and security logs: up to 90 days.
• Error reports (Sentry): 90 days.

If you are in the EU or UK you may: access a copy of your data (the personal data we hold about you — your account details, date of birth, learning progress and results, invoices, and support messages), correct it, delete it ("right to be forgotten" — see the community-content note below), export it (portability), restrict or object to processing based on legitimate interest, and withdraw consent at any time where processing is based on consent.

To exercise any right, email [email protected] from the email address on your account (or, for students, have your school, teacher, or parent contact us). We respond within one month. You may also complain to a supervisory authority — our lead authority is the CNPD (Comissão Nacional de Proteção de Dados, Portugal, cnpd.pt), or your local authority.

California (CCPA/CPRA): you have the rights to know, delete, correct, and to non-discrimination. We do not sell or "share" personal information as defined by the CCPA, and we do not use sensitive personal information beyond what is necessary to provide the service. Requests: same contact as above.

Deletion and community-shared content. Wordlists shared with the community become part of the Lexiage community library under the license granted in our Terms of Service, and remain available after account deletion. Deleting your account removes you, not the words: your name, email address, date of birth, and other personal data are erased, and your community nickname is replaced with an anonymous placeholder so nothing publicly points back to you.

Cancelling a subscription is done through the Stripe billing portal, reachable from the app's billing page ("Manage Billing"). Cancelling stops future charges; data deletion is separate and available on request as above.

Your data is primarily stored and processed in the European Union or United Kingdom (database in Frankfurt, Germany; email in Ireland; error monitoring in the EU; rate limiting in London — the UK holds an EU adequacy decision). Some AI processors are based in the US: OpenAI and Groq, and — if used — Anthropic and xAI. What crosses the border is strictly minimized: for AI requests, only the prompt the user types, the user's age (a single precalculated number, never the date of birth), and predefined technical parameters — never a name, email address, or account identifier; for voice exercises, only the audio clip and exercise context. For US transfers we rely on recognized safeguards (the EU–US Data Privacy Framework and/or Standard Contractual Clauses, per each vendor's data-processing agreement).

Data is encrypted in transit (TLS) and at rest. Access to production data is restricted and role-based; database row-level security enforces that schools, teachers, and families only see their own data. Payments are handled by Stripe (PCI-DSS certified). Logins are protected by human-verification, rate limiting, and monitoring. No system is perfectly secure; if we learn of a personal-data breach that risks your rights, we will notify the competent authority within 72 hours and affected users without undue delay, as required by GDPR Articles 33–34.

We use only strictly necessary cookies: authentication/ session cookies, a short-lived signed cookie that speeds up access checks, and the Cloudflare security check that protects the login page. These cookies are required for Lexiage to load and function — they don't track you across other sites, aren't used for advertising, and don't collect any data beyond what's needed to keep you signed in and the app secure. Because they fall under the "strictly necessary" exemption in the GDPR/ePrivacy rules, we don't show a cookie-consent banner or ask you to confirm anything — there is nothing optional to opt in or out of. We do not use advertising, analytics, or cross-site tracking cookies of any kind.

Parts of Lexiage's learning content (wordlists, feedback, support-chat answers) are generated by artificial intelligence and may occasionally be inaccurate. AI-generated wordlists are labeled as such inside the app, both in text and with an icon. The support chat relies on the safety systems built into the underlying AI providers' models; Lexiage does not alter them, and restricts the chat to app-usage topics only. Our AI providers do not use data submitted through our API integrations to train their models, per their API terms.

We will post any changes on this page and update the "Last updated" date. For material changes affecting schools or children's data, we will notify account owners by email in advance.