Learnara takes your privacy seriously. This policy explains what data we collect on our website and mobile apps, why we collect it, and how it is used and protected. Learnara is operated in the United States; you can reach us anytime at [email protected].
Account information: When you sign up we collect your email address, display name, and sign in method via Firebase Authentication (Google). Firebase also processes your IP address and device information for security purposes.
Learning content: We store the topics you enter, the lessons generated for you, lessons you save, quiz answers, progress, streaks, points, and feedback ratings. This data is stored in Firebase Firestore and tied to your account. Study files you upload are stored so we can generate study tools from them.
Payment information on the web: Web subscriptions are processed by Stripe. Your card details are collected and processed by Stripe and never touch our servers; we receive and store your subscription status, plan, and a Stripe customer reference. Stripe may also process your data as an independent business for fraud prevention and legal compliance under its own privacy policy.
Payment information on iOS: Subscriptions in the iOS app are billed by Apple. We never see your card details. We use RevenueCat to manage subscription status and entitlements; RevenueCat receives your App Store receipt, a user identifier, and purchase metadata.
Payment information on Android: Subscriptions in the Android app are billed by Google Play. We never see your card details. RevenueCat receives your Play Store purchase token, a user identifier, and purchase metadata to manage subscription status and entitlements.
Usage analytics: We use Google/Firebase Analytics on the website and mobile apps to understand product use, subject to regional requirements and your usage analytics choice. Google receives device and usage information, analytics identifiers, and subscription events where permitted. The website may use analytics cookies. See how Google uses this data.
Microsoft Clarity (website only): Clarity uses cookies and similar technologies to create heatmaps and session replays that help us improve Learnara. It receives page content, clicks, scrolling, device and browser information, IP-derived approximate location, and a pseudonymous identifier. Replays may include displayed learning content; profile and checkout pages and sensitive form fields are masked. We do not send your name or email through this integration. Microsoft may also use collected data for Microsoft Advertising under its Privacy Statement. Our integration disables advertising cookies. Clarity runs only when usage analytics is permitted; you can decline it in Privacy preferences.
We also keep limited first-party records, such as active days, app versions and completed lessons, to operate the service and measure aggregate retention.
Emails and engagement: We send transactional emails (welcome, billing confirmations, receipts) and, unless you unsubscribe, a daily learning email. Our marketing emails contain tracking links, provided by Resend, that record when you click a link in them. This engagement information is tied to your account and used to measure whether our emails are useful and to stop emailing addresses that never engage. Transactional billing emails are not used for marketing. You can stop marketing emails anytime with the unsubscribe link in any of them.
Server logs and approximate location: Like most services, our servers log IP addresses and request information for security and abuse prevention. We may derive your approximate location (country or region) from your IP address for fraud prevention, regional pricing and offers, tax and legal compliance, and analytics. We do not collect precise GPS location.
Meta advertising measurement (mobile): Where permitted, Meta's SDK reports app activation, registration and checkout activity. RevenueCat sends verified trial, payment and renewal events. Shared data includes app and permitted device identifiers, a hashed account identifier, device information, IP address, event times, product details and purchase amounts. Meta may combine this information with activity on other websites and apps to measure, target and deliver ads. We do not send names, email addresses, phone numbers or learning content through this integration. The privacy choices and iOS permissions below apply.
Your mobile advertising choices: Open Profile → Settings → Privacy preferences to allow or decline advertising sharing. In the EU, EEA and UK, sharing remains off until you choose Allow. Sharing stays off in identified Maryland, Switzerland and Quebec. In other locations, including when location cannot be established, eligible measurement may start without a separate Allow click, unless you have refused or another applicable restriction prevents it. On iOS, Apple App Tracking Transparency permission is also required for tracking that links your activity across companies; Apple permission does not replace regional consent. Android has no Apple-style permission prompt. On Android, we do not enable advertising-ID collection without an explicit advertising choice. You can withdraw sharing using Privacy preferences, and change Apple's tracking permission in iOS Settings. Your choice does not affect learning, your account or purchases.
We recheck the applicable permissions when the app becomes active and before app advertising events. Withdrawal stops new app event requests and queues removal of RevenueCat's Meta and AppsFlyer matching identifiers; provider cleanup is retried if temporarily unavailable. RevenueCat advertising forwarding follows the same regional eligibility, saved refusals and platform permissions as app measurement. Removal of those matching identifiers is verified with RevenueCat and retried if necessary. Withdrawal cannot recall events already delivered or in flight. Meta's mobile SDK does not provide a supported way to erase all previously queued events, so we cannot promise those batches are deleted. Consent on another platform does not override denied iOS tracking permission. Billing and entitlement records remain separate from advertising sharing.
Apple campaign measurement: Where regional requirements and your advertising choice permit it, we also use Apple’s privacy-preserving campaign measurement to report limited install, trial and purchase conversion levels. This can operate without App Tracking Transparency approval. We do not include an account, device or transaction identifier in these Apple conversion updates. Apple controls delayed campaign reports and may limit their detail to protect privacy. Declining Advertising measurement stops our new conversion updates; it cannot recall reports Apple has already scheduled. This does not enable identifiable Meta or AppsFlyer tracking after an ATT refusal.
Meta advertising measurement (website): Where permitted, Meta Pixel uses cookies and similar technologies to report page visits, registrations and checkout activity. Our server sends verified Stripe trial, payment and renewal events through Meta's Conversions API. Meta receives browser and ad-click identifiers, IP address and browser information, page addresses, event identifiers and times, and purchase amounts and currencies. Meta may combine this information with activity on other websites and apps to measure, target and deliver ads. We do not send names, email addresses, payment card details or learning content through this integration.
AppsFlyer: Where advertising measurement is permitted, AppsFlyer connects ad clicks, download links and QR codes with app installs and eligible subscriptions. It receives campaign and click information, installation and permitted advertising identifiers, IP address and approximate location, device and browser details, and technical data such as launch timing and battery information for attribution and fraud prevention. RevenueCat supplies verified subscription events. Eligible attribution data is shared with Meta to measure our campaigns. We do not send names, email addresses, phone numbers or learning content through this integration. AppsFlyer follows your advertising choice and applicable iOS ATT permission; scanning a QR code does not transfer browser consent to the app.
Your website advertising choices: Use Profile → Settings → Privacy preferences → Advertising measurement to allow or refuse sharing. You can also use the Privacy preferences button on this page without signing in. EU, EEA and UK visitors must choose Allow before Meta tracking starts. Tracking stays off in identified Maryland, Switzerland and Quebec. In other locations, including when location cannot be established, eligible measurement may start by default, with the same ability to decline. Refusal and Global Privacy Control override default eligibility and keep browser tracking and server-side advertising reporting off. Refusal does not affect lessons or checkout. Preferences are scoped to this browser and account. Allow choices last up to 180 days; refusals are preserved and are not converted into permission when a policy changes. A choice made before creating your account can carry into that signup, but existing accounts do not inherit another account's permission. Withdrawal cancels pending server-side advertising reports and stops new browser event requests; it cannot recall requests already sent to Meta.
Lessons are generated using Anthropic, a third party AI provider. The topics you enter, related learning inputs, and lesson context are sent to Anthropic's API to generate lesson content. Under our agreement with Anthropic, Anthropic does not use this data to train its models and deletes API inputs and outputs within about 30 days, except where retention is required for safety or legal reasons.
Please do not include personal, sensitive, or confidential information in topics or study uploads. Generated lessons may be stored in our lesson library and served to other users who request the same topic, as described in our Terms of Service.
For users in the EU, EEA, and UK, our legal bases are: performance of our contract with you (accounts, lesson generation, billing, transactional email), your consent (marketing email and its engagement tracking, and analytics storage where required), and our legitimate interests (security, fraud prevention, and privacy-minimized product analytics where permitted).
Where prior permission is required for mobile advertising measurement, we rely on that permission and allow you to withdraw it in the app. A device-level tracking permission does not replace a separate regional consent requirement.
Learnara shares data with the following providers, who are bound to protect it:
We do not sell personal data for money. Advertising-related sharing is described above and is subject to the privacy choices below.
The website uses cookies and similar technologies for authentication, Google Analytics, and Microsoft Clarity as described above. Google Analytics may set analytics cookies when usage analytics is permitted. Clarity may use first-party cookies such as _clck and _clsk to connect page views and sessions. We do not start Clarity recording before the applicable analytics permission is established. Your browser's Do Not Track signal is not currently given a distinct response. Global Privacy Control is handled as described below.
Advertising preferences and identifiers: A first-party HttpOnly cookie named learnara_ad_preferences lets us remember and enforce advertising preferences and regional eligibility. It is not shared with Meta. Once advertising measurement is permitted, Meta Pixel can set _fbp and a genuine Meta ad click can set _fbc advertising cookies. We retain bounded campaign labels with your browser preference and an authenticated server-side acquisition record. An eligible Stripe payment can create a pending marketing event with its permitted matching context; withdrawal stops future delivery, including queued events. Legitimate billing and first-payment records are kept separately from optional advertising sharing. Allow permission expires after 180 days; saved refusals are preserved. Matching context for eligible payment reporting has a separate, bounded retention period. Advertising retention and deletion also follow the service-specific schedules described in our account deletion policy.
Your usage analytics choices: Use Profile → Settings → Privacy preferences on the website and in the app, or the Privacy preferences button on this page to allow or decline usage analytics independently of advertising. This choice covers Google/Firebase Analytics on the website and mobile, and Microsoft Clarity on the website only. In the EU, EEA and UK, these tools wait for your consent. These tools remain off in identified Maryland, Switzerland and Quebec. In other locations, including when location cannot be established, usage analytics may start by default, subject to applicable restrictions; you can decline at any time. Saved refusals are preserved. Website Global Privacy Control stops Clarity and Meta sharing; it does not turn on or grant permission for any tool. Google's advertising storage, advertising personalization and Google signals remain disabled for usage analytics.
Your signed-in usage analytics choice is saved to your account; signed-out choices are stored on the current browser or device. Withdrawal stops new optional analytics events, stops Clarity recording and disables Firebase collection. Our server rechecks permission before sending queued Google payment reports, and removes the Firebase analytics identifier used by RevenueCat's Google integration, verifying removal and retrying when needed. Other open devices reconcile saved choices when they next become active. Withdrawal cannot recall data already sent or guarantee erasure of every request or batch already held by a provider. It does not disable sign-in, learning progress, subscription verification, payments, or the separate first-party product receipts described above. iOS tracking permission and your advertising choice remain separate.
Learnara is operated from the United States and your data is processed there. Where data of users in the EU, EEA, UK, or Switzerland is transferred to the US, our providers rely on recognized safeguards such as standard contractual clauses and, where applicable, their own certifications.
Your account data and learning content are retained while your account is active. Google Analytics event-level data is configured for 14-month retention, and the linked BigQuery raw analytics export is configured for a maximum of 425 days. Under Microsoft's current standard Clarity schedule, session-playback data is retained for 30 days, while click and heatmap data and labeled or favorited sessions may be retained for up to 9 months. Server logs containing IP addresses are kept for no more than about 30 days.
If you delete your account, your personal data and lesson history are deleted within 30 days. We queue deletion of your Google Analytics user ID and BigQuery-linked rows because those external systems cannot be erased in the same transaction as your Learnara account. Microsoft currently does not provide deletion of one specific Clarity user's project data, so any pseudonymous Clarity records age out under the retention periods above unless the entire Clarity project is deleted sooner. We may retain provider transaction identifiers, amounts, currency, and lifecycle status where needed for billing, tax, accounting, fraud, dispute, or legal obligations; the Learnara user-ID linkage is removed from those retained financial ledger rows. Lessons stored in the shared lesson library may be retained after deletion in a form no longer tied to your identity. Anonymized, aggregated statistics may be kept indefinitely.
You have the right to:
You can delete your account from within the Service, and exercise any of these rights by contacting [email protected]. If you are in the EU, EEA, or UK you also have the right to complain to your data protection authority.
Learnara is a general-audience educational platform. We do not ask for your age during onboarding. If we independently learn that an account belongs to a minor, we restrict optional advertising measurement and usage analytics for that account. Not collecting an age does not establish that a user is an adult.
Learnara is not directed at children under 13, and accounts for children under 13 are not permitted. We do not knowingly collect personal data from children under 13. If we learn that a child under 13 has created an account, we will delete the account and its data promptly. If you believe a child has provided us with personal data, contact us at [email protected].
We use reasonable technical and organizational measures to protect your data, including encryption in transit, access controls, and reliance on established infrastructure providers. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
If you are a California resident, you have the following additional rights:
To exercise your California privacy rights, contact us at [email protected].
The following summarises how Learnara's data use maps to Apple's App Store privacy nutrition labels and the corresponding Android data disclosures. Most data categories below are linked to your identity. Where mobile advertising measurement is enabled and permitted, device advertising identifiers, limited app interactions, and verified purchase data can be used for cross-app tracking. The permission requirements and controls above apply to that use.
| Data Type | Purpose | Linked to User | Used for Tracking |
|---|---|---|---|
| Email address | Account authentication, email delivery | Yes | No |
| Name | Display name in app | Yes | No |
| User ID | Account identification (Firebase, RevenueCat); hashed account identifier for Meta advertising measurement when permitted | Yes | Only when permitted |
| Purchase history | Subscription and entitlement management (RevenueCat); verified trial and purchase measurement (Meta, when permitted) | Yes | Only when permitted |
| Product interaction | Lesson history, progress, feedback, streaks; limited app activation, registration and checkout measurement (Meta, when permitted; no learning content) | Yes | Limited app events only, when permitted |
| Search history | Topics entered to generate lessons (processed by Anthropic) | Yes | No |
| Device identifier | RevenueCat subscription verification; device advertising and Meta app identifiers for advertising measurement when permitted | Yes | Advertising and Meta app identifiers, when permitted |
We may update this Privacy Policy from time to time. We will notify you of material changes by email or by a notice in the product before they take effect. The date at the top shows the current version.
Questions about this Privacy Policy? Contact us at [email protected].
Learnara: Learn Visually