Legal
Privacy
What Enni reads, what it keeps, for how long, and how to have it deleted.
Effective 16 October 2026
What Enni reads
Only the apps you connect — Linear, GitHub or Slack — and inside each, only what you choose to let it read. Enni reads; it never writes, posts, comments or changes anything in them.
The key you paste to connect an app is encrypted before it is stored, and is decrypted only in memory, for the moment a read needs it. It is never shown again, to you or anyone else.
What Enni keeps
Your account: your name, email address, a hash of your password (never the password), and your second steps — passkeys and authenticator settings.
Where you came from: when a link to Enni names its source (like ?ref=linkedin) or another site linked you here, one cookie keeps that first visit — the source, the linking site's name, the page and the day — and sign-up stores it on your account, with your answer to “How did you hear about Enni?” if you gave one. It is only used to see where accounts come from, and leaves with your account.
What you ask, and Enni's answers with the evidence behind them.
What Enni remembers about your space's work — decisions, who owns what, what went wrong before — so the next answer can start from it.
A record of who did what in a space (sign-ins, invitations, connections, deletions), for security and so you can see what happened.
Short-lived technical records: sign-in sessions (with the IP address they came from, and the city and country our hosting provider says that address is in), request counts used to stop abuse, and whether emails we sent were delivered.
How long
Answers and the evidence behind them: 30 days, then deleted.
Conversations: 90 days from the last message, then deleted.
The record of who did what: 90 days, then deleted.
What Enni remembers: 365 days from the last time an answer used it, then deleted.
Sign-in sessions, invitations and tool tokens: until each expires. Request counts: one day. Email delivery records: 30 days.
Deletion runs every night. Our database provider keeps a short history for recovery; deleted data leaves it when that history rolls over.
Deleting it
Delete your account in Settings → Account. You are signed out everywhere at once, your account is removed, and your name is replaced in the record of who did what, so nothing left points to you.
An admin can delete a whole space in Settings → Your spaces. Everything in it goes: its connections, memory, answers, conversations and record.
Disconnecting an app deletes its key at once.
Who else handles it
Enni runs on Vercel (hosting), Neon (the database) and Resend (email), and reports errors to Sentry. Each handles data only to provide that service to us.
Enni's founders are told about each new account in the team's Slack: the name and email address on it, and where it came from.
To judge an issue, Enni sends it to an AI model through OpenRouter with zero data retention: it is not stored and not used for training.
What is sent is the one item being checked — a GitHub issue or pull request, a Linear issue or a Slack thread: its title, text, labels and state, its linked pull requests, its latest comments with each commenter's role (not their name), and what Enni's own rules found in it. When Enni checks for a duplicate, the title and the start of the most similar open issue in the same repository may be sent too. Never your keys, and never your code.
It goes to OpenRouter, which passes it on to the model's provider. Every request requires zero data retention, so OpenRouter routes it only to providers whose policy is to keep nothing: the provider does not store it after answering, and neither OpenRouter nor the provider uses it for training. Enni's own retention, above, is unchanged.
What you connect is never sold or used for advertising.
If you use the microphone, your browser turns speech into text; depending on the browser, that may be done by the browser's maker.
Questions
Write to support@enni.vibana.com. You can ask what we hold about you, and have it corrected or deleted.