Security and privacy
Where your data is stored, where the AI runs, who can act for you, and what deleting removes.
This page covers the hosted version of Stedia. If your company runs Stedia on its own servers, your IT team decides where everything lives.
Where your data is stored
Stedia's servers, its database and the files it stores run in the EU. That covers your chats, files, schedules, assistants and the access to your connected tools. Each workspace's files are stored and signed under that workspace's own access, so one workspace's files cannot be opened with another's. Calculations Stedia runs as code run in the EU too.
Where the AI runs
Every chat message and every schedule run sends a request to an AI model. Which data center handles it is set by Region under Settings → AI settings:
- Global: the provider picks the data center. It can be outside the EU.
- United States: requests stay in the US.
- European Union: requests stay in the EU.
A new workspace starts on Global. If AI processing has to stay in the EU, an admin or owner switches to European Union. Models that do not run there are greyed out in the pickers. A request that cannot stay in the chosen region fails. It never runs somewhere else.
The region covers chat, research and image generation. An admin can give images their own region by switching off Same for images. Dictation and Read aloud run wherever their provider serves them, which may be outside the EU. An admin or owner can turn both off with Voice in the same card.
New workspaces start on Global. Switch to European Union before you put customer data into Stedia if it has to stay in the EU.
Details on every model setting are in Models and BYOK.
Zero data retention
With No data stored by the AI provider on, Stedia only uses AI providers that keep no prompts or answers after a request is done. An admin or owner switches it on under Settings → AI settings. Models without such a provider are greyed out.
It covers image generation too, unless an admin switches off Same for images and sets images apart. It does not cover dictation or Read aloud. Chat and research cannot use it together with your own AI provider; images can, as long as Stedia runs them.
Your own AI provider
On Enterprise, a workspace can send its AI requests to its own cloud account: Vertex AI, Azure OpenAI or Amazon Bedrock. Keep two things in mind:
- Web search always runs on Stedia. Image generation does too, unless you use Vertex AI and turn on Images on your key.
- If Stedia cannot use your key, the request runs on Stedia's own AI access instead of failing, unless an admin turned on Only your key.
How Stedia keeps access to your tools
When you connect Gmail, Slack or any other tool, Stedia saves the sign-in or key it received. Before saving, it encrypts that access with AES-256-GCM. The same applies to MCP server sign-ins and to your own AI provider key.
The AI model never sees these passwords, tokens or keys. Stedia's server calls the tool itself and gives the model only the result.
Nothing changes without you
Reading runs on its own. Actions that send, create, change or delete something ask you first. Each connector page lists which of its actions ask.
An approval covers exactly the action shown on the card. If the details of the call differ from what you approved, it does not run.
Stedia keeps a record of every decision: which action, who approved or denied it, and when. The same record is kept when an action runs because you allowed it in advance, for example with Don't ask again for 7 days or an allowance on a schedule. You see the outcome on the card in the chat and in a schedule run's timeline under Inspect run.
Apps and chat platforms that use Stedia
When you connect an app like Claude or Cursor through the MCP server, the consent screen lists what it may do: read your chats, schedules and assistants, start tasks with your tools, and approve actions waiting on you. Nothing is connected until you click Allow.
Chat bots in Slack, Teams and other platforms act for your account only after you link it. See Chat platforms.
Apps Stedia builds
An app Stedia builds in chat runs in a sealed frame: it loads nothing from the internet and cannot read your session. It does not read your connected tools, so the only data in it is what it was built with and what the people using it type in. An app with shared storage shows everyone what others saved in it. It asks Stedia's AI only after that person clicked Allow. See Files.
What deleting removes
A chat. Only the person who started it can delete it. The chat, its messages and its approval records are removed for everyone in it. This cannot be undone. Files made in the chat stay in Resources → Files until you delete them there.
A file. Only the person who created it can delete it. The file and its stored copy are removed; the stored copy stays recoverable for 30 days and is then gone for good.
A member. When an admin removes someone, or they leave, nothing they made is deleted. Their chats, files, assistants and knowledge bases stay. What would keep acting in their name stops:
- their schedules pause, and runs in progress stop,
- their personal connections are removed,
- their standing allowances and team memberships are removed.
A removed member is also signed out everywhere, and apps they connected through the MCP server lose access. Signing in with SSO does not add them back. An invitation does.
The workspace. Only an owner can delete it, under Settings → General → Leave or delete. The subscription is canceled immediately, with no refund. The workspace and its data are deleted. This cannot be undone. Usage records needed for billing are kept, no longer linked to the workspace.
Schedule runs are deleted on their own: finished runs after 180 days, skipped runs after 30 days, and test runs that no saved schedule adopted after 7 days. Chats and files stay until you delete them.
Sign-in
On Business and Enterprise, your team signs in with Google Workspace or Microsoft work accounts and joins through your verified domains. Personal accounts under a company address never join. An owner can also require it, which turns off passwords and personal accounts for those domains. See Single sign-on. Automatic user provisioning (SCIM) is not available yet.
Data processing agreement
We sign a data processing agreement (DPA) on request. Email info@stedia.ai.