Last updated: October 3, 2026 · Effective immediately
This Privacy Policy explains how LinZi ("LinZi", "we", "us") collects, uses and protects information when you use the LinZi mobile and web applications and the linzi.app website (together, the "Service"). LinZi is designed around a local-first architecture: your learning data lives on your device, not on our servers.
2.1 Learning data (on your device). Study progress, spaced-repetition schedules, decks, placement results, streaks and preferences are stored in your device's local storage. This data never leaves your device unless you deliberately export it or enable cloud sync.
2.2 Purchases. Subscriptions and lifetime purchases are processed by the Apple App Store or Google Play via RevenueCat, or on the web by Stripe. From the stores we receive a pseudonymous entitlement record (an app-user identifier and whether pro_access is active). For web purchases we store the checkout email on the order, which is what links the purchase to your account when you sign in. Card, name and billing details are entered on Stripe's hosted page; we store only the checkout email and identifiers, never payment details.
2.3 Account. An account is an email address plus a password. We keep the email, a salted PBKDF2 hash of the password (never the password itself), the app-user identifier your purchases attach to, and per-device session tokens (stored hashed). We email a one-time code to confirm a new address and to reset a forgotten password. An account lets your cloud backup and purchases - from the stores or the web - follow you to every device. You can delete the account, and its cloud backup, in Stats → Settings → Account.
2.4 Cloud backup. While you are signed in, a compressed copy of your learning data is stored under your account on our server. It is compressed, not encrypted. Without an account nothing is uploaded - use Export progress for a local file backup.
2.5 School seats and class content. Redeeming a class join code sends a pseudonymous install identifier and the code to our licensing server so a seat can be provisioned and your teacher's shared content (decks, stories, audio) can be delivered to your app. We store the seat association, the code's organization, and the content published under it. If you set a display name for the class roster, or submit quiz results, that name and your study statistics (review counts, scores, streaks) are reported to the teacher's roster for that class only.
2.6 School enquiries. The /schools form transmits the fields you type (name, institutional email, institution, seats, message) to our server and inbox so we can respond with a quote or pilot offer.
2.7 Teacher content. Material a teacher publishes, card text, examples, story text, and uploaded or synthesized audio, is stored on our servers so it can sync to students who redeemed the class code.
2.8 Institutional payments. School license purchases are processed by Stripe on its hosted payment page. Card and bank details go to Stripe, never to us. We retain the institution name, contact email, seat count and term needed to issue and renew the class join code.
Each provider processes data under its own privacy terms and only for the purpose listed.
Deletion requests can also be made at linzi.app/delete-account.
Where GDPR, UK GDPR, CCPA or similar laws apply, you may request access to, correction of, portability of, or deletion of the personal data we hold about you, typically a seat association or an enquiry record, since learning data never reaches us. Write to support@linzi.app and we will respond within 30 days.
LinZi is usable without an account and collects no student identity. School deployments use pseudonymous install ids under institution-issued join codes; student identity remains managed by the institution, not by LinZi.
All server communication uses HTTPS. Class content is isolated per organization and readable only by seat-holders of that class. Media files are served from a private bucket through the app's media proxy.
If this policy changes, the updated version will be posted at linzi.app/privacy with a revised date. Material changes will also be noted in the app's release notes.
Privacy questions or requests: support@linzi.app