Lince is a language-learning app that teaches Spanish from short video clips. This policy explains what we collect, why, and the control you have over it. We keep the data we hold to the minimum the app needs to work.
What we collect
- Account details — your name and email address when you sign up, or the name, email and account identifier returned by Google or Apple if you choose their sign-in option. Apple may provide a private relay email address.
- Your name on Lince — the first and last name you register with is public in Lince: other learners see it on leagues and the Top learners board, and it can appear on the weekly highlight posters (such as top learners, streaks and milestones) that Lince publishes on its own social media accounts. Your email address is never shown. To change it, contact us.
- Country and preferences — your selected country, languages and time zone personalize lessons and reminders. Network country is used to enforce video availability. We do not request GPS location.
- Learning data — your progress, streak, hearts, XP, saved clips and quiz results, so your learning syncs across devices.
- Notification tokens — if you enable reminders on a mobile device, a push token so we can deliver them. Web reminders never leave your browser.
- Support messages — what you send to support, its category, your app language and native platform. We deliver a copy to our support inbox at info@getlince.app and use your account email as the reply address when available.
- Reminder emails — if you sign up and don't come back, we may send up to two short emails in your first days to invite you back. If your learning streak of two or more days ends, we may send one short email about it, at most once a week. Each has a link to unsubscribe.
- Duel emails — if you take part in learning duels, we may email you when other learners challenge you and you have not opened the app for a few days (at most two such emails a week), and on Monday with the results of last week's duels. The emails show the public names of the learners you dueled and your duel results. Each has a link to unsubscribe, and you can turn them off in the app's duel settings.
- Welcome emails — on the day you sign up we may send up to two emails: a few hours after you start, one naming your first lesson if you have not finished one yet, and later that day, if you finished clips or lessons that day, a short recap of them with their key words. Each has a link to unsubscribe.
- Weekly recap emails — during your first weeks with Lince, if you earned XP that week, we may send one email a week with your week's XP, your streak, the clips and lessons you finished and your next lesson. Each has a link to unsubscribe.
- Win-back email — if you are on the free plan and have not practised for a while (usually two weeks or more), we may send one email, only once, naming your next lesson. It has a link to unsubscribe.
- Feature news emails — when a new Lince feature becomes available to you, we may send one email about it, at most one a week. It has its own link to unsubscribe from feature news.
- How we measure these emails — Brevo, our email provider, adds a tiny image to each email that records when it is opened; Brevo records those opens on its side; when Brevo reports them to Lince, we discard them without storing or using them. Brevo also sends links through its own address (em.mail.getlince.app) to count clicks. Lince counts deliveries, clicks, bounces, spam reports and unsubscribes: we link each event to your account (we do not store your email address with it, or the full address of a clicked link), keep it for 180 days, and pass these events to Mixpanel. We judge whether an email helped by its clicks and by whether you come back to the app. Blocking images in your email app stops the open image.
- Stopping these emails — the unsubscribe link in a welcome, reminder, streak, weekly recap or win-back email stops all of these emails and feature news. The link in a feature news email stops feature news, and the link in a duel email stops duel emails (you can also turn those off in the app's duel settings). Unsubscribing through your email app or marking an email as spam stops all of them. Account emails, such as sign-up confirmation and password reset, are still sent.
- Product analytics — the screens you open (which screen, the one before it and how long you stay), the controls you tap (the control’s name and the screen only, never what you type, your answers, names or on-screen text), and selected funnel, learning, subscription, retention and failure events, handled by Mixpanel in the EU on Android and iOS and linked to an account identifier. Internal and test accounts and debug builds are excluded. The Android app also records session replay in every session, uploaded on Wi-Fi only, with no audio or camera and with on-screen text and images masked; the iOS app does not record session replay. The iOS app also uses New Relic in the EU for crash reports, handled errors and a limited set of operational failure events linked to an account identifier. Learning progress still syncs to our API on both platforms. On first launch, the Android app also reads the Google Play install referrer (the store page, ad network or campaign that led to the install, including Meta's encrypted campaign and ad identifiers if you came from a Meta ad) and records it in Mixpanel to measure our advertising. It contains no contact details, and we do not send it back to ad networks.
- Optional ad measurement in the app (Meta) — only if you opt in, the Lince app on Android and iOS uses the Meta (Facebook) SDK to tell Meta when the app is installed and opened, and about in-app purchases and other app events the Meta SDK logs automatically, together with an anonymous app ID that the Meta SDK creates for this device. We use it to see which of our Meta ads lead to installs. It is off by default: you can opt in with the separate checkbox when you sign in or register, or in Settings → Privacy, and turn it off there at any time. If you opt in, RevenueCat also receives that anonymous app ID so it can tell Meta when you start a trial or subscription. We do not collect your device advertising ID (Android advertising ID or Apple IDFA), and we do not send your lessons, messages or email to Meta.
- Apple ad attribution (iOS) — on first launch the iOS app registers the install with SKAdNetwork, Apple’s privacy-preserving, aggregated ad attribution. Lince sends nothing itself: Apple may later send the ad network a delayed, anonymous confirmation that an ad led to an install, without any device or user identifier.
- Optional website cookies — if you allow analytics, Google measures page visits and app store link clicks (App Store and Google Play). If you allow advertising, Google and Meta measure campaigns and create audiences for more relevant ads. This can include browser/device, referrer and campaign information. You can accept or reject each purpose in Cookie settings; the tags stay unloaded without the corresponding permission or when Global Privacy Control is enabled. We remember the choice for no more than 24 months before asking again.
- Basic technical data — standard request logs (IP and timestamp), app/device identifiers, crash reports, performance traces and network diagnostics kept as needed to run and debug the service. API response bodies are not collected for diagnostics.
Guest accounts
You can start learning without an email address, Google or Apple. The app then creates an anonymous guest account for you. It has no name, email or password. The app generates a random install identifier and a random secret key, keeps the key in the secure storage of your device, and uses them to sign your device back in to the same guest account. Our server stores the identifier, only a one-way hash of the key (not the key itself), and the country your device connected from when the account was created, which we use to prevent abuse. These are random values, not a hardware or advertising identifier. A guest account stores the same learning data as any other account (see “Learning data” above). You can link it to an email address, Google or Apple at any time and keep your progress, or delete it and its learning data in the app (Settings → Manage account → Delete guest data). If the app can no longer prove the guest account is yours, for example because its key is missing, the app cannot delete it; you can ask us to delete it, and otherwise it is deleted automatically after 90 days without use. A guest account that is not used for 90 days (no sign-in or session renewal from the app) is deleted automatically, with its learning data. A guest account cannot buy Plus, so RevenueCat receives nothing about it; product analytics and diagnostics work as for any other account, and product analytics also record that the account is a guest. On Android, reinstalling the app or clearing its data removes the key, and with it access to that guest account. On iPhone the key can survive a reinstall, so the app may sign you back in to the same guest account.
What we don't collect
We don't sell personal information for money. Some US privacy laws may treat disclosures to advertising platforms as ‘sharing’; our Google and Meta website tags are optional, stay off until you consent, and can be disabled at any time through Privacy choices. Rejecting them does not change access to the site.
Third parties
- YouTube — Lince uses YouTube API Services: video clips play through YouTube's official embedded player. By using Lince you agree to the Google Privacy Policy.
- Google Sign-In / Sign in with Apple — verify your identity when you choose them.
- Apple Push Notification service — delivers iOS notifications using a device token linked to your account, after notification permission.
- RevenueCat with Google Play and the App Store — process subscriptions on Android and iOS. We associate purchase history and subscription status with your Lince account to enable access and restore purchases; we do not receive card details. If you opted in to ad measurement, RevenueCat also receives Meta’s anonymous app ID and reports trial and subscription starts to Meta for that measurement.
- Refund requests to Apple and Google Play — when you ask Apple to refund an App Store purchase, Apple may ask us about that purchase, and RevenueCat replies on our behalf with limited information about it: whether the subscription was delivered to your Lince account, that Lince lets you try free lessons before you pay, our refund preference if we have one, and confirmation that you agreed to this sharing. When Google Play reviews a refund request for a Play purchase, RevenueCat replies the same way but sends only the free-lessons fact and our refund preference. We do not send your lessons, learning progress, messages or email. The store uses the reply only to decide that refund request, and the final decision is always the store’s. If you would rather we did not reply about your purchases, email us and we will stop for your account.
- Payment providers — subscriptions are handled by the app store or our billing provider; we never see your card details.
- Mixpanel — product analytics on Android and iOS (screens opened, controls tapped by name, and selected funnel, learning, subscription, retention and failure events), plus Android session replay with on-screen text and images masked, hosted in the EU.
- Google Analytics / Google Ads — optional public-website measurement and advertising attribution, activated only after consent.
- Meta Pixel — optional public-website measurement and advertising attribution, activated only after consent.
- Cloudflare Web Analytics — cookieless, aggregate measurement of public-website visits (page, referrer, country, browser and device type, page-load speed). It sets no cookies, uses no identifiers to follow you across visits or sites, and we only see totals.
- Meta SDK in the app — optional measurement of installs, app opens, in-app purchases and other automatic app events for our Meta ads, active only after you opt in (see “Optional ad measurement in the app” above).
- New Relic — crash reports, handled errors and limited operational failure events on Android and iOS, processed in the EU. Reports can include an account identifier and app/device details. iOS automatic network and interaction tracing, session replay and log collection are disabled. API response bodies are not collected.
- Firebase Cloud Messaging — creates and delivers an Android push token only after you enable mobile reminders.
- Brevo (Sendinblue SAS, France, EU) — sends all Lince emails: account emails (sign-up confirmation, password reset) and the welcome, reminder, recap, win-back, duel and feature news emails described above, and records their deliveries, opens and link clicks (Lince discards the opens) as described in “How we measure these emails”.
- Zoho Mail — delivers support messages to our support inbox and sent account emails until October 2026.
Lince para escuelas: class data
- Who decides — in Lince para escuelas a teacher creates a class and gives students a join code. For the class data described here, the school (or the teacher who runs the class) is the controller, and Lince processes it on their behalf only to run the class, under our data processing agreement for schools. For the rest of your account, such as your own learning, settings and subscription, Lince remains the controller as described in this policy.
- Classes are for adults — Lince para escuelas is for adult education: classes are only for learners aged 18 or older.
- Joining is your choice — you join a class only with its code or class link, or by accepting an invitation addressed to you, and only by agreeing to share your class work with its teacher. A Lince Live game in class is joined separately, with the PIN the teacher shows. Until you join a class or a Live game, no teacher sees anything about you, except an invitation a teacher imports from their own Google Classroom (see “Google Classroom import” below).
- What the teacher sees — your name on Lince and the date you joined; for each homework assignment, how many of its lessons you completed, whether it is done, in progress, late or overdue, how many of its lesson questions you answered and got right, your score and your last activity on it. For lesson questions Lince keeps only whether you were right, how many tries you took and when, never what you typed. For a homework task (a worksheet), the teacher sees the answers you submit, how each one was marked, and the score, rubric and comment the teacher gives; you see them too. The teacher can download the gradebook as a spreadsheet. Results per lesson question are shown as totals for the whole class, so they show what the group missed, not who answered what. In a Lince Live game the teacher sees your name on Lince (or, if you are not in the class, the nickname you choose) and your score. The teacher does not see your email address, your other lessons or your subscription (an invitation imported from Google Classroom shows the address it is for, until it is declined or deleted).
- Legal basis — the school uses class data for its educational task carried out in the public interest (GDPR art. 6(1)(e)) or to perform its contract with its students (art. 6(1)(b)). Lince processes class data only on the school's instructions and only for that purpose.
- How long class data is kept — while you are in the class; an archived class keeps its data. If you leave a class, the teacher stops seeing you at once and your lesson question results for that class are deleted; your own learning progress stays in your account. The homework tasks you submitted stay readable for you, and the teacher no longer sees them (unless you join the class again); they are deleted when the teacher deletes the task. When a teacher deletes a homework assignment, its lesson question results are deleted with it. A Lince Live game, with the nicknames, answers and scores in it, is deleted automatically 24 hours after its last activity. When you delete your account, your class memberships, results and submitted tasks are deleted with it. When a teacher deletes their account, their classes, their homework and the class work sent to them are deleted. Deleted data can remain in our encrypted daily backups for a limited time, about a week, until they expire.
- Who else receives it — class data is stored with the rest of your account data on the servers that run Lince, in the EU. We do not sell it or use it for advertising. When you join a class, our product analytics (Mixpanel, in the EU) record it with the class level, the course and whether you joined from your profile or a class link. On Android, the session replay described under “Product analytics” above (on-screen text and images masked) can also record the class screens you use. The providers that help us run Lince handle class data only as listed in the data processing agreement for schools.
- Your rights — you can leave a class at any time in the app. To access, correct or delete class data, ask your school or teacher, or email us and we will help you and your school with the request.
Google Classroom import (for teachers)
- What it does — a teacher in Lince para escuelas can connect their own Google Classroom account to turn their Classroom courses into Lince classes and invite the students in them. Connecting is optional, and only the teacher who connects gives Lince access. Lince asks Google only for read-only access: to see the teacher's courses (classroom.courses.readonly), their class rosters (classroom.rosters.readonly) and the email addresses of the people in their classes (classroom.profile.emails). If the teacher does not grant all three, Lince revokes the grant at once and keeps nothing. Lince never creates, changes or deletes anything in Google Classroom.
- What Lince reads — the email address of the connected Google account; the teacher's active Classroom courses, with their name and section; and, for each course, its students' names, email addresses (when Google shows them to the teacher) and Google user IDs. Lince does not read coursework, grades, posts, files or any other Classroom content.
- Why — only to run the import the teacher asks for: to list the teacher's courses with the number of students in each and, for each course the teacher chooses, to create a Lince class named after it (course name and section) and add its students who have an email address as invited students, up to the class size limit. Importing a course that is already linked to a Lince class invites its students not yet invited to that class; if that class is archived, a new class is created. An invited student is not a class member: like every student, they join a class only by choosing to. Until then the teacher sees their name and email address on the class.
- Invitations for students — a signed-in student sees an invitation only when it is addressed to one of their verified email addresses, including the email address of a Google account linked to their Lince account. They can accept it, which joins the class only once they agree to share their class work with its teacher, or decline it. When they join the class, the invitations to it addressed to one of their verified email addresses (including a linked Google account's) are deleted. A declined invitation is no longer offered to the student or shown to the teacher, and is kept, marked declined, so that a later import does not invite them again.
- What Lince keeps — for the connection, Google's refresh token, encrypted at rest (AES-256-GCM), the connected account's email address, the permissions granted and the date of connection. The short-lived access token is used only for the request in progress and is not stored. For each imported course, the Lince class with the course's name and section and the ID of the Classroom course it came from; for each invited student, their name, email address and Google user ID. Courses the teacher does not import, and the student counts, are not kept. This data is stored on the servers that run Lince, in the EU.
- How it is used — Google Classroom data is used only for the import in the teacher panel and the classes it creates. We do not sell it, use it for advertising, or use it to develop, improve or train AI or machine-learning models. The classes and invited students an import creates are class data, handled as described in “Lince para escuelas: class data” above and in our data processing agreement for schools.
- Limited Use — Lince's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- Disconnecting and deleting — when a teacher disconnects Google Classroom, Lince revokes its access at Google and deletes the stored token, account email and permissions. You can also remove Lince's access at any time in your Google Account; Lince then cannot read Classroom until the teacher connects again. Disconnecting does not delete the classes and invitations already imported: an invitation addressed to one of the student's verified email addresses (including a linked Google account's) is deleted when the student joins the class or deletes their Lince account; when a teacher deletes their Lince account, the connection, their classes and the invitations in them are deleted. Deleting the account deletes the stored token and revokes Lince's access at Google. To delete Classroom data sooner, email us. Deleted data can stay in our encrypted daily backups for a limited time, about a week, until they expire.
Keeping and deleting your data
We keep your account data while your account exists. Support messages in the Lince database are deleted after 90 days and are removed immediately with your account. Support-inbox correspondence is kept only as long as needed to respond, resolve the issue or meet legal and security obligations. You can delete your account at any time from Settings → Manage account → Delete account in the app. Deleting is permanent and immediately removes your profile, learning progress, saved clips, support messages and notification tokens from our database. No access to the app? Request deletion from this page instead.
Your choices and regional rights
You can access, correct or export your data, and ask us to erase it, by contacting us. Depending on where you live, you may have additional rights under the GDPR or US state privacy laws, including rights to know, delete, correct or opt out of certain disclosures. Use “Privacy choices / Do not sell or share” in the website footer to change your tracking choice. We also honor browser Global Privacy Control signals by keeping Google and Meta tracking off. In the app, ad measurement with Meta stays off unless you opt in when you sign in or in Settings → Privacy, where you can turn it off again at any time.
Contact
Questions about your privacy? Email info@getlince.app.
This policy is a plain-language summary and not legal advice.