AI Daily Journal (the aidailyjournal.com website and the Android app) is built to be read without signing up. This page says exactly what we store about readers, why, and how to delete it.
What we don't collect
We don't ask for your name, email, phone number or a reader account. We don't use tracking cookies, we don't show ads, and we don't sell or share data with anyone.
Audience measurement
We count visits with Cloudflare Web Analytics, which uses no cookies and doesn't identify people: it only records aggregate data such as page views, country, device type and browser.
We also measure, without cookies, how long each page stays open on screen and how far it was scrolled. Each page opening gets its own random number, which is not linked to other openings, to the device or to the person. We keep these records for about 13 months. We also count how many times each audio starts playing and how many times it is heard to the end, only as a daily total.
Like any website, our servers keep technical access logs (IP address, requested page, date and time) for a few days, used only to keep the site running and to investigate failures and abuse.
Device identifier
So that likes and notifications work without signing up, your browser creates a random code and stores it only on your device. It has nothing to do with your name, email or phone number.
When you like a story or turn on notifications, that code is sent to our server, which stores only a transformed, irreversible version of it (a hash). The database alone can't be used to rebuild the code.
Likes
We store which stories each device liked (using the hash above) and when, to show the like count and prevent repeated likes.
Notifications
If you turn on the daily briefing, we store the technical delivery address your browser provides (from the Google, Apple, Mozilla or Microsoft notification service), the keys that encrypt the message, and your chosen language and notification types. This data is used only to send the notifications you asked for.
In the Android app, notifications arrive through Firebase Cloud Messaging, Google’s notification service: we store the delivery code (token) it gives the app, plus your language and chosen types, only to send what you asked for.
When you turn notifications off, the sign-up is deleted. If the browser service reports that the sign-up has ended, it is deleted on the next send.
What stays on your device only
Saved stories, theme and default language are stored only in your device's browser. They never reach our server.
Editorial team
The dashboard login (controlroom) is for the editorial team only. Readers don't have accounts.
How long we keep data and how to delete it
Likes and sign-ups are kept while you use the site or app. On the Settings page, the "Delete my data" button immediately deletes this device's likes and notification sign-up from our database, along with the saved stories and preferences stored on the device.
For questions or access and deletion requests, email wzcortex@gmail.com. Since we don't know who you are, we have no way to find one person's data: the "Delete my data" button on your own device is how to delete it.
Who processes the data
We don't share data with third parties. The services that run the infrastructure are Cloudflare (hosting and audience measurement), Supabase (database) and the browsers' notification services (Google, Apple, Mozilla and Microsoft), which only deliver the encrypted message.
Contact
Privacy questions and requests: wzcortex@gmail.com.