Security
Last updated 28 August 2026
A LiveOps calendar is an unreleased roadmap. Here is exactly how it is protected, and what is not protected yet.
Who runs this
One person: Aleksandar Šoškić, in Belgrade. Not a company and not a team — which means exactly one human being can reach the database, and you know his name.
In transit
Everything travels over TLS, always. The session cookie is marked secure unconditionally, so it cannot be sent over a plain connection even by mistake.
At rest
AES-256 disk encryption at our database provider. That defeats a stolen disk. It does not defeat someone with database access — see below.
Who can see your boards
People you invited, limited to the role you gave them, and anyone holding a share link you created, until you revoke it or archive the board.
Those limits are enforced inside the database, not just in the interface, so they hold even if a bug in the app tried to ignore them. 143 automated checks prove it on every change.
And us
Board content is not encrypted at the application level, so whoever operates the database is technically able to read it. This is true of every comparable tool: Figma and Miro both hold the keys to your files, which is how they can search them, render previews and let you reset a password without losing your work.
What we commit to
We do not look at your boards. Access to the production database is limited to one named person, and it happens only when you ask for it — to investigate a fault you have reported. Never to browse, never to train anything, never for analytics, and never to show a third party.
We do not sell your content and we do not share it, except where the law leaves us no choice. If we were ever compelled to hand something over, we would tell you unless we were forbidden from doing so.
That is a promise about conduct, not a mathematical guarantee — the honest distinction between we will not and we cannot. End-to-end encryption, where the server holds text it is unable to read, is planned as an option you can switch on for yourself or for your whole organisation. It is not available today.
And here is every time we did
A promise nobody can check is just a sentence, so this is the record. It lists every occasion a human opened the production database — not deploys, which never touch it, and not migrations, which change the shape of the database without reading anything you wrote.
Nobody has opened it since this record began on Aug 28, 2026.
Entries begin on Aug 28, 2026; access before that date was not recorded, and saying so is the difference between a record and a claim. Each entry is committed to this product’s source history, which lives outside the database — so an entry cannot be quietly removed by the one person who could reach the database. No entry names a customer, a board or an address: a log that identified whose work was opened would leak the very thing this page promises to protect.
Signing in
No passwords exist anywhere in this product, so there is no password database to leak. Your email inbox is the key to your account; protect it accordingly.
Analytics never sees your work
Product analytics records which steps you reach, never what you typed. Board names, notes and share links are stripped before anything leaves the browser, and you appear as an internal id rather than an email address. That was verified by pointing the analytics client at a local server and reading every request it made, rather than by trusting it to behave.
Where your data lives
| Company | What it does | What it receives | Where |
|---|---|---|---|
| Supabase | Stores your account and every board | Your email address and all board content | European Union (Frankfurt) |
| Vercel | Runs the application and serves the pages | Requests and IP addresses | United StatesEU–US Data Privacy Framework |
| Resend | Sends your sign-in links | Your email address | United StatesEU–US Data Privacy Framework |
| PostHog | Product analytics, only if you agree to it | Which steps you reach. Never board content, never your email | European Union |
| Cloudflare | Checks that a sign-in is a person, not a script | Your IP address, briefly | Global network, closest location to youStandard Contractual Clauses |
Your account and your boards are stored in the European Union. This page changes at least 30 days before anybody joins that list.
The service is operated from Serbia, so the one person named above reads the database from outside the EU when fixing a fault you have reported.
Found a problem?
Write to mail@soskic.me and say what you found. One person reads it, usually within two working days. There is no bug bounty, and nobody who reports something in good faith will be threatened for it.
What is not done yet
Being straight about this is worth more to you than a longer list of what is:
- No end-to-end encryption yet. Planned as something you can switch on.
- No backups. Deleting something is immediate and permanent.
- No SOC 2 or ISO certification, and no audit log of who viewed what.
What we hold about you, and your rights over it, are on the privacy page.