Claro Privacy Policy
Effective date: October 2, 2026
Last updated: October 20, 2026
This policy explains what Claro (made by Breakpoint Labs LLC, Denver, Colorado) collects about you, why, who else touches it, and what you can do about it. Short version: we collect what the app needs to teach you Spanish and bill you, we don't sell it, and you can delete all of it from inside the app.
What we collect
Account. Your email address (that's your login). You can sign in with an emailed magic link, Sign in with Apple, or Sign in with Google. If you use Apple or Google, they pass us your name and email address (Apple may give us a private relay address instead of your real one). You can also set or change a display name.
Learning preferences. Which Spanish you chose (Spain, Mexico, or Colombia), your daily goal, your theme, and whether you finished onboarding.
Learning data. Which chapters, sections, readings, and checkpoints you've started and finished, your exercise and quiz scores, the flashcards in your repository (including custom ones you create), your review ratings and their timing, and quiz attempts.
Your turn answers. The Spanish or English you write in Your turn practice, which prompt it answered, your dialect setting, and the feedback we return. We keep it so you can see your past answers and so we can enforce the daily check limits.
Level check. If you take the placement quiz, the chapter and level it places you at.
Notifications. If you turn on notifications: a push token for your device (iOS), which kinds you want (tips, reminders, cards due, streak, news), your preferred time and time zone, and a log of what we sent you. You can change or turn these off any time in You → Notifications or your phone's settings.
Translator inputs. The text you type into the translator, the direction, your dialect setting, and the result we return. We keep this history so you can see it again and so we can enforce the daily limits.
Purchase status. Whether you're on Free or Pro, which plan, when it renews or expires, and identifiers from the billing provider (a Stripe customer id, or a RevenueCat app user id). We never see or store your card number; Apple, Google, and Stripe handle payment details.
Usage events. Things like "opened chapter 5", "completed a review session", "hit the translation limit", with a timestamp, tied to your account id along with your dialect and your plan (Free or Pro). The mobile app and the website both send them, through our own database and through PostHog. We use these to see what's working in the product.
Feedback. The text you send through the feedback form.
Technical. Standard server logs (IP address, request path, timestamps, app version, device type) kept for security and debugging.
We do not collect your contacts, location, photos, or microphone. We don't collect advertising identifiers and we don't track you across other companies' apps or sites. Claro has no ads. One related detail: on iOS, our purchase provider (RevenueCat) passes Apple an Apple Ads attribution token so Apple can tell us whether an App Store install came from an Apple Ads campaign. It's an Apple token, it isn't used to follow you across apps, and we don't use it for anything else.
Why we use it
- To run the product: sign you in, show your progress, schedule your flashcards, translate and explain your text, check your practice answers, place you at the right level, send the notifications you chose, and unlock Pro.
- To bill you and keep purchases in sync across devices.
- To enforce limits (free-tier translation cap, fair use).
- To improve Claro: which lessons people finish, where they get stuck, which features they use.
- To answer you when you write to us.
- To keep Claro secure and to comply with the law.
The legal bases, for people in the EEA and UK: performance of our contract with you (most of the above), our legitimate interests (product improvement, security), consent (optional analytics cookies on the website), and legal obligations.
Who else is involved
We use a small set of providers. Each one only gets what it needs for its job:
| Provider | What it does | What it gets | |---|---|---| | Supabase | Database, authentication, sends your sign-in codes | Your email, name, all learning data, translator history, Your turn answers, feedback, push token, purchase status | | Render | Hosts our website and API | Request logs (IP address, path, timestamps, app version, device type), translator inputs in transit | | Anthropic | Runs the language model behind the translator and the Your turn answer checks | The text you ask to translate or explain, the practice answers you submit with their prompt, and your dialect setting. We don't send your name, email, or account id. Anthropic does not use API inputs to train its models. | | PostHog | Product analytics in the mobile app and on the website | Usage events tied to your account id, with your dialect and plan. Before you sign in it uses an anonymous device id. On the website it only starts if you accept analytics cookies. Session replay is off. | | RevenueCat | Keeps app-store purchases in sync | Your Claro user id, purchase receipts, subscription status, storefront country, and on iOS the Apple Ads attribution token described above | | Apple | Sign in with Apple, iOS in-app purchases, Apple Ads attribution | Your Apple sign-in details (name, email or relay email), purchase details, handled under Apple's own privacy policy | | Google | Sign in with Google, Android in-app purchases | Your Google sign-in details (name, email), purchase details, handled under Google's own privacy policy | | Stripe | Web billing | Your email, plan, payment details (handled entirely by Stripe) | | Resend | Sends transactional email (sign-in codes on the web, receipts, account notices) | Your email address and the message | | Expo | Delivers push notifications and app updates | Your device's push token and the notification text; for updates, your IP address, platform, and app version (no account id) |
We don't sell personal data and we don't share it with advertisers. We'll disclose data if the law requires it, to protect Claro or its users, or as part of a merger or acquisition (we'd tell you first).
How long we keep it
- Your account and learning data: until you delete your account.
- Translator history and Your turn answers: until you delete your account, or you can ask us to clear them sooner.
- Notification settings, push tokens, and the send log: until you turn notifications off or delete your account. A token that stops working is disabled automatically.
- Purchase records: 7 years after the purchase, because tax law requires it. We keep only the minimum (amount, date, plan).
- Server logs: kept by our hosting provider, Render, under Render's own log retention. We don't keep a separate copy.
- Usage events: kept until you delete your account. At that point they are de-identified, which means we remove your account id from them and they can no longer be tied to you.
When you delete your account (You tab → Delete account, or learnclaro.com/account/delete), we erase your profile, preferences, level check, progress, flashcards, reviews, quizzes, Your turn answers, translator history, notification settings and push tokens, and feedback immediately, and delete your login. Usage events are detached from your identity. Backups clear within 30 days.
Your rights
Wherever you are, you can: see what we hold about you, correct it, export it, delete it, and object to or restrict how we use it. Most of this you can do yourself in the app. For the rest, email hello@breakpointlabs.space and we'll respond within 30 days.
California (CCPA/CPRA). You have the right to know, delete, correct, and to opt out of "sale" or "sharing". We don't sell or share personal information as those terms are defined, and we don't use sensitive personal information beyond what's needed to run Claro. We won't treat you differently for exercising your rights.
EEA and UK (GDPR). Breakpoint Labs LLC is the controller. You can lodge a complaint with your local supervisory authority. Data is processed in the United States; transfers rely on standard contractual clauses with our providers.
Children
Claro isn't directed at children under 13, and we don't knowingly collect data from them. If you think a child under 13 has an account, email us and we'll delete it.
Security
Data is encrypted in transit (TLS) and at rest. Access to production systems is limited to the people who run Claro. Every database table is protected so that you can only ever read your own rows. No system is perfect; if we ever have a breach that affects you, we'll tell you promptly.
Cookies
The website uses a session cookie to keep you signed in, Stripe's cookies on checkout, and optional analytics cookies you can decline. The mobile app uses on-device storage, not cookies. Details in the Cookie Policy (/legal/cookies).
Changes
We'll post changes here and update the date at the top. For material changes we'll notify you in the app or by email at least 14 days ahead.
Contact
Breakpoint Labs LLC Denver, Colorado, USA hello@breakpointlabs.space