Last updated: pending legal review (see notice below)
O-03
in this project's decision ledger). Everything below describes
Styved's actual, real, already-implemented data behavior accurately;
only the legal framing/wording around it is a placeholder.
Styved is an on-device AI tutor. Almost everything it does — generating courses, rendering visualizations, running quizzes, answering follow-up questions — happens entirely on your device, offline. This page states exactly what does and does not leave your device, in full.
| Data | Why |
|---|---|
| Topic strings + cache lookups | To look up cached course sources and, when nothing suitable is cached, to search for new ones. |
| URLs you provide or capture | A link you paste, or a page you explicitly capture, is fetched so its content can be used to build a course. |
| One-time sign-in identity | Created once at first launch so Styved can be operated as a real product (account-based quota, abuse prevention). |
| Optional profile | If you choose to add one: an age range (never a date of birth) and profession. Both are skippable. |
| Pseudonymous usage events | Topics created/read, feature use, and device tier — for product improvement. Never the content of a lesson or course. |
| Anonymized “a topic was searched” records | When Styved fetches sources for a topic, our server records the topic and the broad subject it falls into — so we can see what people are learning about and cache it better. These records carry no account, no device, and no time of day: just the topic and the date. They cannot be traced back to you. |
| Anonymized “a course was created” records | When a course finishes generating, our server records what kind of course it was — which engine and model built it, how many modules and lessons it has, the tone, and whether it used web sources. Never the topic, the title, or a word of the lessons. Like the record above it carries no account and no device: because there is nothing on it to match, it is also not something we can delete for you individually. |
| Anonymized crash reports (opt-in, off by default) | Only if you turn crash reporting on in Settings → Privacy & Legal. After a crash, the app sends a short fingerprint of where it happened, plus the app and OS version — never the error message, never a stack trace, never a file path, and never your account. Nothing is even written down on your device unless you have turned it on. It is grouped with everyone else's report of the same crash, so all we learn is “this crash happens, on these builds”. |
| Coarse, IP-derived country | Derived server-side from your network connection. Styved never requests GPS or precise-location permission — this is the only location signal it ever has. |
.styved files. None of it is ever sent anywhere,
unless you explicitly export a course file yourself to share it.
Generated courses live only on your device. Uninstalling the app erases them — there is no server-side copy to fall back on. Your account identity, optional profile, and usage events live on our servers until you delete your account, which you can do at any time from Settings → Profile & Account inside the app, or via the web instructions on the account deletion page.
The three anonymized records above — “a topic was searched”, “a course was created”, and crash reports — are the exception, and not because we keep them back. They carry no account and no device identifier at all, so once written there is nothing on them that could be matched to you, by us or by anyone else. That is what makes them safe to keep; it is also why deleting your account cannot reach them. They are deleted on a fixed schedule instead: 180 days.
Questions about this policy or your data can be sent to privacy@styved.com.