Your workspace stays protected.
Your data is encrypted, never used to train anything, and deleted when you leave. This page explains what that means in practice.
How access works
Teddo lives in your Slack workspace and acts only when one of your team asks it to. Every message it receives is checked to be really from your Slack, and every sign-in to the dashboard goes through Slack or Google, so no one outside your workspace can pose as your team.
Each person connects their own Google account. Teddo acts only in the account of the person who asked, and asks Google for the narrowest permissions that let it do the job:
| Permission | Why Teddo needs it |
|---|---|
| Read, draft, send and label email | To search your inbox, summarise threads, draft replies and send them when you say so |
| Manage calendar | To check availability, book, move and cancel meetings |
| Create and open files in Drive | To save documents and reports it makes for you. It sees only files it created or you opened with it, not your whole Drive |
| Edit Google Docs and Sheets | To write and update documents and spreadsheets. Google grants this for all Docs and Sheets in the account; Teddo opens only the ones you ask it to work on |
| Your email address | To know which account it is acting in |
Teddo does not ask for your other Drive files, your contacts, or anything it cannot explain. You can revoke Google access at any time, and it ends the moment you do.
Teddo sends, books and edits only when one of your users asks it to. Before it emails or invites anyone outside your company, it asks for confirmation in Slack. Its instructions tell it to treat the text of emails, web pages and documents as information, not as orders, and files you upload are scanned for hidden instructions. This is a rule the model follows, not a guarantee; the check that stops anything from going to an outsider without your confirmation is in code.
Each company also has a limit on how fast requests can arrive, so a runaway script cannot burn through your plan.
What Teddo can see
In Slack, Teddo sees only messages that mention it or are sent to it directly, and the thread they are in. It does not read the rest of your channels.
In Google, it sees the mail of the people who connected their account, and only the documents and sheets you ask it to work on. In other tools, it sees what the key you gave it allows.
At Teddo, by default, nobody sees your data. Our staff do not have a “look at customer data” button. Access is granted per person, per case, only for support you asked for or a security investigation, and that access is itself logged. Production servers accept only key-based logins, and the admin console is password-protected and limited to the founder.
Every request Teddo handles is recorded with who asked, when, and how many tool calls it took. Owners and admins can download the workspace’s conversation history from Settings at any time. We keep these records for 12 months.
Where data lives
Teddo runs on DigitalOcean in Frankfurt, Germany, inside the European Union. Backups stay in the same region.
The AI providers that write Teddo’s replies process each request in the United States. They may keep request data briefly under their own policies to detect abuse, and never use it for training.
Nothing you give Teddo, whether messages, email, documents or memories, is used to train or improve any AI model, ours or our providers’. What Teddo learns about your business stays in your account.
Encryption
In transit. Every connection, between you and Teddo, Teddo and Slack, Teddo and Google, and Teddo and our servers, uses TLS, the same protection as online banking.
At rest. Everything Teddo stores (memories, conversations, documents, logs, backups) sits on encrypted disks.
Credentials. The keys and logins you connect are encrypted a second time, individually. Each is encrypted with your company’s own key, and that key is itself encrypted with a master key kept in the server’s protected configuration, separate from the database and backups. Plain credentials exist only in memory, for the seconds a task needs them, and are never written to disk or to logs.
Retention and deletion
Press Delete everything in the dashboard, remove Teddo from Slack, or ask us, and Teddo stops at once. Within 30 days your memories, conversations, credentials and files are permanently deleted.
If a Personal or Pro payment fails, Teddo moves to the free Starter plan. Google access ends the moment a person disconnects it.
Subprocessors
These are the companies whose services we use to run Teddo: OpenRouter and Anthropic (the AI behind the replies), Slack, Google, Stripe (payments), DigitalOcean (servers, in Frankfurt) and PostHog (product usage analytics, EU cloud, never message content). Each receives only what it needs and is bound by terms that forbid any other use.
The full list, with what each one receives and where, is on the subprocessors page. How we process data for you is set out in the data processing agreement and the privacy policy.
Reporting a problem
If you find a security problem in Teddo, tell us through Message us. Describe what you found and how to reproduce it. We reply within 2 business days, keep you informed, and will not take action against good-faith researchers who give us reasonable time to fix the issue before publishing.
We monitor Teddo for errors and unusual activity. If we discover a security incident affecting your data, we tell your account owner within 72 hours with what happened, what was affected and what we are doing about it, and keep you updated until it is resolved.