vlipa
Terms
Privacy
What vlipa keeps, what it never keeps, who else it passes anything to, and how to have all of it deleted. Written plainly, because a policy nobody can read is not consent.
Last updated 1 September 2026.
Who this is
vlipa is a software studio. It runs vlipa.dev: a public site, a
workspace for companies (/studio) and a personal
assistant with a mailbox beside it (/me). Questions,
requests and deletions: contact@vlipa.dev.
What is stored
Only what the thing you asked for cannot work without.
- Your account — email address, the name and picture you chose. Passwords are never stored: what is kept is a PBKDF2-HMAC-SHA256 hash with 210,000 iterations and a salt of your own. A session is a random token whose SHA-256 is stored, never the token itself.
- Signing in with Google — the email address and name Google states, and nothing else from your Google account.
- Your work — companies, members and roles, tasks, tables, groups and their messages, meeting rooms: whatever you or your team put in.
- Your conversations with Vlipa — kept on your account so they are there on your next machine, and the standing instructions you wrote in Skills.
- Your connections — for GitHub and for Gmail, the access token itself, so the connection survives. These live on the server and never reach a browser.
Your mailbox
The Mail page connects to Gmail with your permission and shows your own mail. It is worth being exact about it.
What is asked for, and what it is for
gmail.modify |
Read the messages the page shows you, and change where one sits when you press a button: mark it read or unread, star it, archive it, move it to the bin. Not permanent deletion — this scope cannot destroy mail, and nothing in vlipa tries to. |
|---|---|
gmail.send |
Send the message you press Send on, from your own address, in its own thread. |
userinfo.email |
Know which mailbox was connected, so the page can show you which one it is sending from. |
What is kept from it
No message is stored. Subjects, senders, bodies and attachments are read from Gmail while a page is open and returned to your browser; nothing about a message is written to vlipa's database, and nothing is kept after the request finishes. What is stored is the connection itself: the Google access and refresh tokens, the mailbox address, and the date it was connected.
Nothing is ever sent on your behalf without you pressing Send. A message Vlipa writes is shown to you first, and a recipient it proposes is discarded unless that exact address was already in what you wrote or in the message you are answering.
vlipa's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
The assistant, and what it is shown
Vlipa runs on language models hosted elsewhere. When you ask it something, what you typed is sent to that provider to be answered — and on the Mail page, so is the mail the answer needs: the senders, subjects and previews of the messages listed in front of you, the body of a message you have open when you ask about it or reply to it, and the words of a draft you ask it to write. Nothing from your mailbox is sent anywhere until you ask Vlipa for something.
Providers are used as processors — to answer that one request and nothing else. Model providers used by this deployment are named in the list below. If you would rather no mail reached a model at all, use the mailbox without the panel and the composer: reading, replying, archiving and sending all work on their own.
Who else sees anything
- Vercel — hosting. Every request to the site passes through it.
- Supabase — the database everything above is stored in.
- OpenRouter, and where configured Nebius and Groq — the model providers that answer what you ask Vlipa.
- Google — for the mailbox itself, and for the small icons shown beside senders: your browser asks Google's icon service for the icon of a sender's domain, so that service sees the domains you receive mail from. Not the addresses, not the messages.
- Resend — sends the one message vlipa writes on its own: "somebody gave you a task", to the person it was given to.
- Tavily — where a search key is configured, the search terms Vlipa looks something up with.
- Jitsi — meeting and voice rooms run on it. Nothing said in a room passes through vlipa.
Nothing is sold, and nothing is handed to anybody for advertising. Nothing you write and nothing from your mailbox is used to train a model by vlipa.
How long it is kept
Until you delete it. An account's data stays while the account exists; a company's work stays while the company does. Sessions expire on their own. Published Vlipa Studio sites come down after seven days without anybody asking.
Taking it back
- The mailbox — Mail → Disconnect. The tokens are deleted immediately and vlipa can no longer reach your mail. You can also revoke it from Google's side at myaccount.google.com/permissions.
- GitHub — GitHub → Disconnect, the same way.
- Conversations and skills — Settings on the personal account has a button that deletes the lot.
- Everything else — write to contact@vlipa.dev and it is deleted.
How it is kept safe
- Tokens and keys stay on the server. No API key, and no Google or GitHub token, is ever sent to a browser.
- Sessions are HttpOnly, SameSite=Lax, Secure cookies; only the hash of a session token is stored.
- The database has row level security on and no policies, so it is reachable only by the server's own secret key.
- Every request is checked against your role in the company it touches before it reads or writes anything.
- Eight failed sign-ins lock an account for fifteen minutes.
No system is perfect, and this one is small. If you find something wrong with it, write to us — you will get an answer.
Children
vlipa is not for people under 16.
Changes
If this page changes in a way that matters, the date at the top changes with it and anybody with an account is told before it takes effect.