Privacy policy

Who is responsible

Habujo is run by Julen Rodriguez Sanchez, based in Denmark, who is the data controller for your information. Danish and EU law applies, including the GDPR, and the supervisory authority is Datatilsynet. You can reach me at hello@habujo.com.

If you never sign in

Your planner is written to your browser’s local storage on the device you are using, along with your preferences: your theme, your typeface and the switches in settings. Nothing is sent anywhere, the app works with no connection, and clearing your browser’s data for this site erases all of it.

If you sign in

Signing in is with Google. Habujo never sees or stores a password. What is kept then:

• Your planner: the collections, day entries, habits and preferences you have made, as a single private row only you can read.
• Your Google account id and email address, so the app knows which row is yours.
• A record that you agreed to this: the moment you ticked the box and which version of this policy it was. The law asks me to be able to show that consent was given, and a note in your browser proves nothing.
• Any backups you ask for. “Save backup” keeps a snapshot of your planner; the three most recent are kept and older ones are deleted automatically.

All of it lives in a Postgres database run by Supabase in Frankfurt, inside the EU. It is encrypted in transit and at rest. Every table is protected by row-level security, which means the database itself refuses to return one person’s rows to another, rather than the app being trusted to ask the right question.

A journal can hold genuinely personal things: health, relationships, beliefs, other people. Habujo never reads, analyses, indexes or infers anything from what you write, and none of it is ever used to train a model. That is also why the cloud copy is something you deliberately turn on rather than something you end up with: using the app without an account is a first-class path, not a degraded one.

To know whether any of this is working, I look at counts and never at content: how many people have an account, how many edited something this week, and how many entries, collections or habits a planner holds. The database works those out by counting how many things are in a list, without ever opening one, and they reach me as totals on a page only I can open. Nothing on it can show what an entry says, because nothing on it ever reads one.

If you connect a calendar

Habujo can show what is already on your Google Calendar beside your day, so the day you plan is the day you actually have. This is off until you connect one, and connecting is a separate step from signing in with a separate Google permission screen.

The permission asked for is read-only. Habujo cannot create, change or delete anything in your calendar, and it never asks for a permission that would let it.

• What is read: for events in a window around today, the title, start and end time, all-day flag, location, and which calendar it came from.
• Why: to draw those events in the day log, in order, next to the things you wrote yourself. Nothing else.
• Where it is kept: the events themselves stay in the browser you are using, in a cache that is thrown away and refetched rather than stored on a server. What is kept on the server is the access token that lets Habujo fetch them, so a refresh does not need you present.
• For how long: until you disconnect the calendar, which deletes the token and clears the cache. Events fall out of the cache on their own as the window moves.

You can revoke Habujo’s access from Habujo’s settings, or at any time from your Google account at myaccount.google.com/permissions. Calendar data is never sold, never used for advertising and never used to train a model.

If you ask for an invitation

Habujo is invite-only while it is in beta. If you ask to join, the email address and the note you send are kept until the request is decided, and they are used for nothing else: no mailing list, no marketing, nothing passed on. Ask me and I will delete the request.

If you send feedback

The feedback form inside the app keeps what you wrote, the kind of report it is, and your email address, so a fixed bug can be answered. It comes straight to me and goes nowhere else. Deleting your account leaves a report standing, with your address beside it, unless you ask me to remove it too.

What you can do

• Take it with you. The app exports your whole planner as a file whenever you want, no account needed.
• Empty it. “Delete all data” in settings wipes your planner on this device, in your account, and every saved backup of it.
• Close the account. “Delete account” on the account page deletes the account itself along with everything attached to it — your planner and its history, your photos, every backup, your consent record, and any calendar you connected. Feedback you sent is kept, with your name, address and device taken off it, so a bug you reported still gets fixed for everyone else.
• Ask what is held. You have the right to a copy of your data, to have it corrected, to object to it being held, and to complain to Datatilsynet if you think this is being handled badly.

There is no retention schedule beyond this: what you keep is kept until you delete it, and what you delete is gone rather than archived.

Changes

If this policy changes in a way that affects what is collected or why, the date at the top changes and you will be asked to agree again before anything new happens with your data.