Signing in requires internet
The board is local, but sign-in isn't: the first time you sign in, the app talks to our authentication server. What travels is email, password and the session token. Never the board's content.
privacy · data map
Privacy you can actually check
Almost everyone writes "we take your privacy seriously." Few publish the table. Here's ours.
data-map
seven kinds of data · what leaves is flagged
| What | Leaves your machine? | Where it lives / where it goes |
|---|---|---|
| Your cards, columns, descriptions, tags and milestones | Never | In the folder you chose, one YAML file per column. |
| Attachments and recorded audio | Never | In attachments/, inside the board's folder. |
| Theme, language and recent folders | Never | Preferences saved locally by your system. |
| Your Claude Code plan usage | Never | Read from a command that runs on your machine and shown only to you. |
| Your account email and password | Leaves | Go to our authentication server (api.vibe.venda.plus) at login, password recovery and password changes. It's the only thing the app sends on its own. |
| What you have a coding agent execute | You decide | Vibe assembles the prompt on your machine and hands it to the CLI of the agent you chose. From there on, its privacy rules apply, not ours. |
| Pages you visit on this website (vibe.venda.plus) | Leaves | Aggregate, anonymous visit counts to our own self-hosted analytics (analytics.venda.plus). No cookie, no IP stored, no personal data. Disclosed by a dismissible notice on every page. |
Focus on privacy
Private by default means one concrete thing: sending any data out is your decision, made with eyes open, never a side effect of turning on a feature. Whenever a new data output is added, it arrives turned off, the notice says what leaves, where to and when, and turning it off reverts everything to how it was.
Vibe also doesn't ask for what it doesn't use. No full name, phone number, company, job title or onboarding questionnaire: just email and password.
Local files
Each column of your board is a readable YAML file inside a folder you chose. That's not an implementation detail. It's what makes the board yours: you can version it with git, open it in your editor, sync it your own way, copy it to another machine and pick up where you left off.
There's no proprietary database in the middle, and uninstalling the app deletes nothing. The only way to lose the board is for you to delete the folder.
Zero telemetry or analytics
No analytics inside the app itself. No automatic crash reporting. No silent "ping" telling us you opened it. This website you're reading right now is the one named exception: it runs a self-hosted, cookie-less analytics script to count visits, with no IP stored and no personal data, and tells you so with a dismissible notice. The server also still runs with access logging turned off.
And there's a boring part we insist on telling you: inside the app's code there's an automated test that breaks the build if anyone adds a network call outside the login screen. A promise that depends only on good intentions ages badly.
Simplicity
Two screens: the board and settings. Open it, pick a folder, use it. No project to create, no workspace to configure, no six-step wizard.
When a feature depends on some external program installed on your machine, the app notices it's missing, warns you in plain language, and keeps working without it. No blank screens.
Cost savings
We don't store your board, so we're not paying for storage on your behalf. That's why the subscription is cheap and doesn't grow with the size of your project: the cost of one more user, for us, is close to zero.
The app also shows how much of your coding agent plan has already been used, instead of letting you find out mid-task. Cost you can see up front is cost under control.
What we don't promise
What the app doesn't do: real limits that apply today.
true today
3
Real limits of the app, not legal fine print.
The board isn't encrypted on disk
Vibe isn't an anonymity tool or a vault. Whoever has access to your folder has access to your cards. The protection is whatever your filesystem provides.
Third-party agents are third parties
When you have Vibe run a card, its content goes to the CLI of the agent you chose, which typically sends it on to the model's provider. Vibe tells you this, but doesn't control what happens next. And it won't pretend to.
The five principles live in the repository
These five principles aren't marketing copy written after the fact: they live in the app's repository as numbered, verifiable rules, and changing any one of them means changing that document.