Expense TrackerOur policy
What this deployment stores, why it stores it, and how long it keeps it.
This is the policy shipped on day zero. It describes what the software stores, which is a matter of fact about the code. It is not legal advice, and the operator of this site owes it a review -- and their own contact details -- before it is published to anybody.
What is stored when you read
Reading a public page requires no account and sets no cookie of its own. A page is served from rows in this deployment's own store; nothing about the request is passed to a third party in order to draw it.
What is stored when you sign in
Signing in creates a session -- a row in this store -- and hands the browser a signed ticket that names it. The ticket carries an identity and the permissions it was granted; it is not a database of you, and it expires.
The device the browser is running on is recorded alongside the sessions it holds, so that a person can see where they are signed in and end a session they do not recognise. If a second factor is enabled, the secret behind it is stored for that account and is never shown again after it is set.
What is stored when you write to us
A message sent through the contact form is stored as a row and is readable by whoever holds the ability to read it -- not by every account with a login. Subscribing to the newsletter stores the address given and nothing else; unsubscribing removes it.
How long any of it is kept
Sessions end on sign-out or on expiry, whichever comes first. Everything else is kept until somebody deletes it, and every deletion is an action a role has to be granted before it can be taken. The retention period for contact messages and subscriber addresses is the operator's to set and to state here.