privacy.
short version: your entries are yours alone.
what we store.
Your email address. A bcrypt hash of your password, never the password itself. The text and the date of every entry you write. Your settings, such as language, time zone, accent colour and date format. Hashed tokens for the devices you are signed in on, and for any confirmation or reset link we send you. That is the whole list on our side.
On your device, words you have typed but not yet saved wait in your browser's local storage for up to 14 days, so a dropped connection loses nothing. Signing out tries to save them, then clears them. A few cookies remember your session, language, time zone and display settings.
what we don't do.
We don't sell or share your writing. We don't train models on it. We don't analyse it for marketing. There are no third-party trackers, ad pixels or social-network beacons in the app. There are no engagement nudges, streak emails, or shareable cards made from your writing.
where it lives.
Entries are stored in a managed Postgres database run by Neon, on Amazon's servers in the United States. The site itself runs on Vercel, which keeps short request logs, with your IP address and browser, for at most 30 days. Confirmation and reset emails are sent through Resend. Your session is kept in a cookie for daylogg.com and ends after a year. Password reset links work for two hours.
So your data leaves the EU for the United States. Vercel covers that transfer with the European Commission's standard contractual clauses.
how it is kept safe.
Every connection is encrypted: between your browser and daylogg (HTTPS), and between daylogg and the database.
The database is encrypted on disk (AES-256).
Neon keeps encrypted backups of the database. When you delete your account, its last copies leave those backups as they age out.
who can read your entries.
Entries are encrypted on disk, but not end to end: the server can read them, because that is how search works. Peter, who runs Daylogg, does not read them. The one exception is when you ask him to fix a problem with an entry.
your controls.
In settings you can change your password and sign out your other devices. You can export every entry you have written. You can delete your account, and with it every entry and session. There is no undo once you do.
You can also ask for a copy of your data, or to have it corrected or erased: write to the address below. If you think your data is handled wrongly, you can complain to the Swedish Authority for Privacy Protection, IMY.
who runs this.
Daylogg is made and run by one person, Peter, at Redpoint9 (redpoint9.com) in Sweden. Redpoint9 is responsible for your data under the GDPR. more about Peter and why he built it.
if daylogg ever closes.
You will hear about it at least 90 days before it happens. Export stays open until the last day, so you can take every entry with you.
changes.
If this policy changes in a way that matters, every account gets an email before the change takes effect, so you can export your writing or delete your account first.
questions? write to info@daylogg.com.