Privacy
Effective October 14, 2026
This page explains what Parkboard stores, how it protects it and who can see it. It adds to the general jato.run privacy policy, which covers every *.jato.run app.
What we store
- Your account: the email, name and picture Google shares when you sign in, managed by Clerk.
- What you park: titles, notes, links, tags and project names. When an agent parks a card, also the session summary, its id, the working folder and the vault note.
- Board metadata: status, priority, kind, area, canvas positions, colors, dates and which agent created each card.
- API keys: only their SHA-256 hash, never the key itself.
How it is protected
- Everything you write (titles, notes, links, tags, project names, origin, session summary and id, folder and vault note) is encrypted with AES-256-GCM before it reaches the database. The key lives outside the database, so a copy of the database or of its backups cannot be read without it.
- Encryption started on October 14, 2026. Backups taken before that date may still hold that text in clear until the provider deletes them under its retention.
- Each value is bound to your account and its field: it cannot be moved into someone else’s account and read there.
- Traffic goes over HTTPS, and each user only ever sees their own board.
- Not encrypted: the board metadata above (including the name of the agent that created a card), which the server needs to sort and draw the board, and the name you give each API key.
Who can see it
Your board belongs to you. Only your account can see it: no other user can open, search or list it, and what you park is never shared with anyone.
Encryption happens on the server: the app decrypts your cards to show them to you, so whoever runs the service technically holds the key. We will not open the contents of your board unless you ask us to (for example, to fix a support issue) or a competent authority requires it, and we will tell you when the law allows.
We do not sell or share your data, there are no ads or third-party analytics, and your data is not used to train AI models.
Providers
- Clerk: sign-in and accounts.
- Google: sign-in with your Google account.
- Vercel: hosts the app.
- Railway: hosts the database, which only holds the encrypted text.
Cookies and local storage
Only Clerk’s session cookies. Your browser also remembers the view and sort order you picked (localStorage). No tracking cookies.
Your rights
Under Colombia’s Law 1581 of 2012 and, if you are in the EU, the GDPR, you can access, correct, export and delete your data. Edit or delete cards and projects from the board or the CLI; `park export` saves your whole board as JSON. To delete your whole account, write to contacto@jato.run and we will do it within 15 business days. Database backups expire on the provider’s normal cycle.
Rather not trust anyone?
The code is public. Run your own Parkboard on your own servers, with your own key.
Changes
If something important changes, this page will say so, with a new date.