Privacy Policy
Applies to: the Ozetta mobile app (news.ozetta.app).
Who is responsible for your data
Nurhak Altin, Duinkerkenlaan 69, 5627 MB Eindhoven, the Netherlands, runs Ozetta personally and is the controller of the personal data described here.
For anything in this policy — including access, correction or deletion requests — write to [email protected].
If you are unhappy with how we handle your data you can complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl), or to the authority in your own EU country.
The short version
Ozetta translates and summarises news so people can follow it in a language they read. You can read it without an account, in English. With an account we keep that account, the settings you choose, the articles you save, and — so your feed and your daily summary are worth reading — which articles you open.
We do not sell your data. There is no advertising in Ozetta and no advertising identifiers. We do not track you across other apps or websites. Your data is held in the European Union.
What we collect, and why
Reading without an account
You can read Ozetta without signing in. As a guest we store nothing that identifies you on our servers: your country and topic choices stay on your device, and articles are shown in English. The other reading languages, saving articles, muting sources and having the same settings on every device are what an account adds — and so is asking for an article to be translated into a language we do not translate for everyone, because each of those translations is generated on request.
One exception, and it is the reason this section exists: we record which articles are opened, so we can tell which stories readers actually read and show you what you missed. For a reader without an account that record is attached to a random identifier your phone generates for itself — never to a name, an email address or a device fingerprint. It is created on your device, sent nowhere except to us, and it disappears from your phone when you delete the app, leaving nothing that can connect those rows back to you. If you sign in later, those records move to your account.
Your account
| What | Why | Where it lives |
|---|---|---|
| Email address, or your Apple or Google sign-in | To let you sign in and to keep your settings across devices | Clerk (see Who else processes your data) |
| The version of these terms you accepted, when you accepted it, and your usage statistics choice | To record your acceptance and respect your choice | Supabase, EU |
| Reading language, app language, home country, time zone | To choose which news you get and in which language | Supabase, EU |
| Topics you follow, countries you follow, sources you mute | To choose which news you get | Supabase, EU |
| Articles you save | So you can find them again | Supabase, EU — the link and headline, not the article text |
| Which articles you open, and when | To build your feed, to show you what you missed, and to rank your daily summary | Supabase, EU |
| Your phone's notification token, platform, app version and language | To send the daily summary you asked for | Supabase, EU |
Usage statistics
The app can send PostHog a record that something happened — an article was opened, a filter was changed, sign-in finished. These carry a short, fixed list of properties such as your reading language and which source an article came from.
When you first open the app we ask how these usage statistics are handled, and we ask again when this policy changes. You can change your choice at any time in Settings → Privacy & data.
| Choice | What is sent | Legal basis |
|---|---|---|
| Linked to your account — once you have an account: if you chose Accept and continue, or choose it later in Settings → Privacy & data. Without an account there is nothing to link to, so events stay anonymous until you sign in. | Events carry your account's ID (never your email address), so we can see how the app is used over time and across your devices. | Your consent |
| Anonymous — if you choose Skip | Events carry a random identifier that is not linked to your account. No profile is built. | Our legitimate interest in knowing which parts of the app work |
| Off | Nothing is sent. | — |
In every mode, usage statistics do not store your IP address or location.
When an account is deleted, our server records one event saying that an account was deleted — with a random identifier, no link to you and no profile — unless you had chosen Off.
Events never carry article text, headlines, links, or your email address. That is enforced in the app's code by an allowlist: a property that is not on the list is dropped before anything is sent, rather than relied on as a rule someone might forget. You can choose Off at any time in Settings, and nothing else about the app changes when you do.
What we never collect
No advertising identifiers. No location. No contacts, photos, calendar or health data. No cross-app or cross-site tracking. No profile of you sold or shared with anyone for their own purposes.
Reading history, specifically
This is the most sensitive thing we store, so it gets its own section.
What it is. One row per reader per article: that this reader opened this article, and when they first did. Not how long you read, not how far you scrolled, not what you did next.
Why we keep it. Three reasons, all for you rather than about you. It builds your feed and lets us show you what you missed. It tells us which stories readers are actually reading, which is how the daily summary picks ten stories out of several hundred. And it stops your summary serving you a story you already read last night.
Who can see it. Nobody, through the app. The table is locked so that no app client can read it — not another reader's rows, and not your own. It is readable only by our server code that builds your feed, what you missed and your daily summary.
How long we keep it. About thirty days in practice. We delete news articles themselves after thirty days, and a reading record is deleted automatically with the article it points at. A second scheduled job removes anything older than ninety days as a backstop, in case that first rule is ever relaxed.
If you delete your account, your reading history is deleted with it — it is the first thing removed. If you never had an account, your reading history disappears on its own within about thirty days, and deleting the app discards the only identifier that connects those rows to your phone.
Who else processes your data
| Who | What they do | Where |
|---|---|---|
| Supabase | Hosts the database and the server code. Everything in the tables above lives here. | European Union (Frankfurt) |
| Clerk | Runs sign-in and holds your email address or social sign-in. | United States — see below |
| PostHog | Usage statistics, unless you choose Off. | European Union |
| Expo (EAS) | Delivers app updates. Receives technical details about the app version, not your content. | United States |
Each of these acts on our instructions only.
Transfers outside the EU. Clerk and Expo are in the United States. Those transfers rely on the European Commission's Standard Contractual Clauses. Everything else — your preferences, saved articles and reading history — stays in the EU.
A note on translation. Ozetta translates and summarises news articles using an external language model. What we send is the published news article. Your preferences, your reading history and your identity are never part of that request.
Why we are allowed to do this
- To give you the service you asked for (Article 6(1)(b) GDPR): your account, your settings, your saved articles, your reading history for your feed and "what you missed", and sending you the summary you switched on.
- Our legitimate interests (Article 6(1)(f)): keeping Ozetta working and secure, the aggregate "most read" ranking, and anonymous usage statistics. We have weighed this against your privacy. Anonymous statistics are minimal: no profile is built, and you can choose Off at any time. Reading history is unreadable by any other user, short-lived, and ends when you delete your account, or within about thirty days if you never had one.
- Your consent (Article 6(1)(a)), where you have given it — for notifications, and for usage statistics linked to your account. You can withdraw consent for linked statistics at any time by choosing Anonymous or Off in Settings → Privacy & data. You can turn notifications off at any time in Settings or in your phone's settings.
How long we keep things
| What | How long |
|---|---|
| Account, settings, saved articles | Until you delete your account |
| Reading history | ~30 days (see above); 90-day backstop |
| Notification token | Until you turn notifications off or delete your account |
| Usage statistics | The retention period of our analytics plan — currently 12 months |
Your rights
You can ask us to show you the data we hold about you, correct it, delete it, restrict what we do with it, hand it over in a portable form, or object to us relying on legitimate interests. Write to [email protected] and we will answer within one month.
You do not need to write to us to delete your account: you can delete it in the app's Settings. Your sign-in account at Clerk is deleted, and everything we store about you in our database goes with it. Usage statistics are kept as described under How long we keep things.
Children
Ozetta is not directed at children under 16 and we do not knowingly collect their data.
Changes
When we change this policy we publish a new version with a new date at the top. The app shows you the change and asks you to accept it before you continue.