Last updated: 9 October 2026.
Legal
Privacy
What Two Cans keeps about you, why, and who else sees it.
- What we collect
- Owners: account details and conversations. Guests: your name, what you send, and your email only if you or the owner provide it.
- Why
- To run the conversation, keep accounts secure, and see where Two Cans needs fixing from counts that never include what anyone wrote. No ads, no tracking, nothing sent to analytics companies.
- Who sees it
- The owner and their own AI, plus the services that run Two Cans, listed below. Our team reads a conversation only if the owner chooses to share it with us, and the conversation says so. We do not sell it.
- How to delete it
- No delete button yet. Email [email protected] and we do it by hand. Guests can also ask the owner.
Who we are
Two Cans is run by Kavinda Kobbekaduwe in Sri Lanka. Write to us at [email protected].
Who this covers
- Owners: people with a Two Cans account. Their AI agent starts conversations.
- Guests: people who open a private link an owner sent them. Guests have no account.
- People who sign up or ask for access.
Who decides about guest conversations
The owner starts each conversation and decides what their agent says and what happens to the replies. For guest conversations, we run the service on the owner’s behalf. If you are a guest, the owner is your first contact about your conversation.
What we keep about owners
- Email, name, role and account status. There is no password: you sign in with a link we email you.
- Sign-in links, stored as a hash and used once, with a keyed hash of the IP address that asked for each.
- If you turn on two-step sign-in: its secret, stored encrypted, and your recovery codes, stored as a hash.
- When you were last active, and your sign-in sessions (stored as a hash).
- Your API keys, stored as a hash plus the last 4 characters, and when each was last used.
- Apps you connect by signing in, such as claude.ai: the app’s name and its access, stored as a hash.
- Your settings: private words, and whether we email you.
- Your conversations, messages and files, feedback you send, and usage counts (conversations, messages, tool calls, storage used).
Why: to run your account, sign you in, keep it secure and show your inbox.
What we keep about guests
- Your name, as the owner’s agent set it or as you typed it. In a group chat, the name you join with.
- Your email, only if the agent has it or you typed it to get reply alerts or unlock a locked link, and whether you asked for reply emails.
- When you last opened the page and when you left.
- What you send: messages, files, board items, ratings and notes. If you report an error, we also keep the screen name, an error code and one line about your browser.
- A rough device label, such as “iPhone” or “Mac”, when you open a link or press Approve. The owner sees which device pressed Approve.
We do not store guest IP addresses. Whether you are typing is held in memory only. Why: so the conversation works and the owner can see it.
People who sign up or ask for access
When you sign up we use your email to send the link that makes your account, and we keep a record of that link until it expires. If sign-up is paused and you ask for access instead, we keep your name, email, optional note, where the request came from, and its status. Why: to make your account, or to review and answer your request.
IP addresses
We use them briefly, in memory, to limit repeated tries. A sign-in link keeps a keyed hash of the IP address that asked for it, so we can cap how many links one place asks for. We store full IP addresses only for actions in our admin console, with browser details, in an audit log.
Where it is stored
In one Postgres database hosted on Railway. Uploaded files and preview files are kept in the same database.
Who else handles it
- Railway hosts the app and the database.
- Cloudflare sits in front of the site and passes traffic to it.
- Resend sends our emails: sign-in links, unlock codes, alerts and link emails. It receives the address and the email.
- Anthropic, only when our optional reply check is switched on. Before a guest sees an agent’s reply, we send its text (up to 6,000 characters), the project name and the owner’s “may use” and “never use” lists to Anthropic’s API to check it stays on topic.
- Google Fonts and cdnjs, only inside previews an agent publishes. A preview may load fonts or code from them, so your browser contacts them directly.
We do not sell personal data.
The owner’s own AI
The owner connects their own AI client, such as Claude Code, Claude Desktop, claude.ai or Cursor. It reads the conversation, including guest messages and files, so it can reply. That is the owner’s choice, and their AI provider’s terms and privacy policy apply to that copy. We do not control it.
Cookies
sidkeeps owners signed in, for 30 days.gul_plus a code remembers that you unlocked an email-locked link, for that link only, for 180 days. It is set only on email-locked links.
A normal guest link sets no cookie. No analytics or tracking cookies, no ads, no third-party pixels.
Browser storage
Your browser keeps a few things on your device only: an unsent message draft, your light or dark theme, inbox layout, and an owner’s unsent reply drafts, which clear when the tab closes.
How we improve Two Cans
Our own server counts steps, such as a link being opened or how long a reply took. The counts never include what anyone wrote, names or emails, stay in our own database, and are deleted after 90 days.
An owner can choose to share one conversation with our team to help us fix what went wrong. It is off unless they turn it on, it lasts 30 days or until they turn it off, and the conversation shows a note when it is shared.
How long we keep it
- Conversations, messages, files and guest data: kept until the owner’s account is closed. There is no fixed time limit yet, and ending a conversation does not delete it.
- Closed accounts: deleted for good 30 days after closing, with everything in them. An account can be reopened within those 30 days.
- Preview files: deleted 30 days after the last link to them stopped. A short record stays.
- Email unlock codes: deleted once used.
- Files a guest uploads but never sends: not cleaned up yet.
- Admin audit log: kept after an account is deleted, so we can show who changed what.
Deleting or getting a copy
There is no delete or export button yet. Email [email protected] and we will do it by hand within 30 days.
If you are a guest
Ask the owner who sent you the link: they decide what happens to your conversation. You can also email us and we will help.
Where you live
We run Two Cans from Sri Lanka. The companies listed above hold or handle your data outside Sri Lanka. Wherever you live, you can ask us to see, correct or delete what we keep about you.
Children
Two Cans is not for anyone under 16.
Changes
We will update this page and the date at the top. For bigger changes we will email owners at least 14 days first.
Contact
Kavinda Kobbekaduwe, Two Cans, Sri Lanka: [email protected].