Security and privacy
This page says what Cora AI does with your organisation’s data today. Each point describes how the console works now, except the AI clients section, which says so at its start. Things that are not built yet are listed at the end, under Not built yet.
Each organisation is kept apart
Section titled “Each organisation is kept apart”Your organisation’s missions, documents, files, memory, connections and usage belong to it alone. Every request is checked on the server against the person’s own membership, not only in the screen. A person who is not a member gets the same answer as something that does not exist, so another organisation cannot even learn that a mission is there. Inside an organisation, a mission’s messages and files are open only to the members of that mission.
Where data lives
Section titled “Where data lives”Your organisation’s data is stored in Australia, in the AWS Sydney region. That covers missions, documents, files, memory, usage records, backups and the team sandbox.
Model inference, the step where an AI model reads a request and writes its answer, may run outside Australia (D0031). The next section says where.
Sub-processors and where inference runs
Section titled “Sub-processors and where inference runs”A sub-processor is another company that handles your organisation’s data on Cora AI’s behalf. There are four.
| Sub-processor | What it does | Where |
|---|---|---|
| Amazon Web Services | Hosts the console, the database, backups, files and the team sandbox; sends email (Amazon SES, in Sydney); runs models through Amazon Bedrock | Sydney for stored data; Bedrock inference as below |
| Anthropic | Runs the Claude models through the Anthropic API | United States |
| Stripe | Takes card payments and holds card details | Stripe’s own regions, under its terms |
| Brave Search | Answers Cora’s web searches when web access is on. Cora AI’s servers send it the search words, the country (Australia unless Cora asks for another), how many results, the safe search setting and, if asked, how recent. It gets no name, email address, mission or organisation | Brave’s own regions, under its terms |
Model calls go to one source after another, each with a monthly cap. The first is the Anthropic API, where inference runs in the United States. The next is Amazon Bedrock, using global. profiles, which may run inference in any AWS region (D0146). An organisation set to Australia only skips the Anthropic API and uses Bedrock on au. profiles, which keep inference in Australia, instead of global ones; there is no setting for this in the console. Inference does not have to run in Australia; stored data does (D0031). Each model call’s usage record notes which source served it and, for Bedrock, which inference profile. It does not note the exact region where inference ran.
The model providers’ own retention
Section titled “The model providers’ own retention”Anthropic deletes API inputs and outputs within 30 days by default. It keeps them longer only where the law requires it or where its systems flag a request as breaking its usage policy, and then for up to 2 years. Amazon Bedrock does not store or log prompts and answers. Under both providers’ commercial terms, your data is not used to train their models.
AI clients
Section titled “AI clients”Not built yet. Using Team Cora from your own AI client, such as Claude, is being built now. This section says how your data will be handled once it is released. Until then none of it happens. See Use Team Cora from your AI client.
- Off by default. It is off for every organisation until an org admin turns it on, and only in the console. Every org admin is emailed each time it is turned on or off (D0903, D0922).
- What is shared. When a member connects their AI client and opens mission content there, such as posts, files, memory and the names of the people in a mission, Team Cora sends that content to the AI client when the client asks for it. It sends only what that member could see in the console. Team Cora never sends the secrets it keeps (passwords, a vault key’s value, a connection’s sign-in token and payment details), and never the private chat with Cora (D0114, D0128, D0914). A post holds whatever someone typed into it, so if someone typed a secret into a post, that post goes as it is.
- Who then holds it. The company behind the AI client, Anthropic or OpenAI, then holds that content under the person’s own account and terms with that company, not under Team Cora’s. Claude is Anthropic’s; ChatGPT, OpenAI’s, is not supported yet (D0926). That company may hold the content outside Australia, usually in the United States. It is not one of Team Cora’s sub-processors: the person chose it, not Team Cora. This is separate from Cora’s own model calls, which the table above covers.
- Who controls it. The org admin controls it with the AI clients switch. Turning it off stops every AI client at once. Content an AI company already holds stays under the person’s account with it, and Team Cora cannot recall or delete it there.
- What Team Cora records. Each call from an AI client is logged with the tool, the person, the organisation, the AI client’s name, whether it worked and how long it took, never its content or the sign-in token. A change made from an AI client goes into the audit trail like any other, marked with the client, for example “via Claude” (D0927).
- Sign-in. The AI client signs in with the person’s own Team Cora account and never sees their password. It reaches only the areas the person agreed to, and the person’s role still applies. See Scopes.
What is kept and what is not
Section titled “What is kept and what is not”Kept: the messages posted in a mission, the mission’s documents with every version, Cora’s memory, and usage records, so you can see who used what.
Never stored: your private chat with Cora is never stored. Its turns live only in your browser while the chat is open, and the server keeps nothing between turns (D0114, D0128). If Cora drafts a post for you there, only her wording is kept, for you alone. Posting or discarding it deletes it. After 7 days nobody can open it any more, you included, but it is not deleted from the database yet. The same goes for Polish with Cora. The text you had before you pressed Polish is kept only in your browser, so you can undo the polish, and is gone once you post or leave the page. The polished wording comes back to your browser too. Cora AI stores neither, and nothing is kept until you choose to post (D0617).
Files shared in a mission are kept with the mission. When you press + in the mission dialogue, the file goes from your browser straight to short-lived storage through a single-use link, in the Sydney region, and is then copied into the mission’s store, where it stays with the mission’s messages (D0548, D0566). A file you add but never send is deleted after about a day (D0581). Only members of the mission can see or download a shared file, and every file is served only as a download through a short-lived link. The type and size are checked on the server: seven types, 25 MB each (D0089, D0548). Shared files are not scanned for malware, so open one only if you expect it (D0562). See files shared in the dialogue.
The cloud sandbox
Section titled “The cloud sandbox”Cora runs commands and keeps working files in a cloud sandbox, not on your device. Each organisation has its own sandbox and its own folder in it (D0528). The folder is in AWS in Sydney, and no outside sandbox company is used (D0529).
- Kept apart. Each organisation’s sandbox mounts only its own folder, through its own access point and role. That role has no rights to another organisation’s folder or to Cora AI’s own systems.
- Least privilege. Each task starts on a fresh, clean machine with only your folder attached, and anything installed outside the folder is gone when the task ends (D0530). A hero called in from another mission can read the folder but cannot write to it.
- Limited in size. The folder holds up to 5 GB.
What comes back from the internet is treated as data, never as an instruction to Cora. See The team sandbox.
Keys in the vault
Section titled “Keys in the vault”A mission’s vault holds keys for other services, such as an API key. A key is typed once by a mission admin and is never shown again, to anyone. Cora AI’s own console and API cannot read a value back (D0738).
Cora never sees the value. She asks for a key by its name, and Cora AI’s worker adds the key to the call for her. The key is sent only to the sites named for that key, over https, and a call to any other site is refused. What comes back has the key removed before Cora reads it (D0741). Each use is written to the audit trail, with the key’s name and the site, never the value (D0739). See The mission vault.
Changes wait for your approval
Section titled “Changes wait for your approval”How a new tool starts depends on how its connection was added (D0657, D0716):
- On an organisation connection an org admin adds by its address, every new tool starts off.
- On an organisation connection an org admin sets up from the catalogue, tools start on: the ones the catalogue marks as reads are Allowed, the rest Ask first.
- On a personal connection, tools start on and Allowed, because sharing it is its owner’s consent. Tools that always ask start on Ask first.
An org admin can then set each group of tools on an organisation connection to Off, Ask first or Allowed; the owner does this for a personal one:
- Ask first puts an approval card in the mission. Nothing happens until a person approves it.
- Allowed lets Cora use the tool without a card.
- Some tools always ask, whatever the setting (D0684).
A key in the vault has the same choice: Ask first waits for an approval of that exact call.
Cora’s memory
Section titled “Cora’s memory”The organisation’s memory, the notes Cora reads at the start of every run, can be changed only by the organisation’s admins and the platform super admin. Members can read it. Cora never writes it: her tools refuse any change there, and in the team folder its files are owned by the team folder’s own file user, not the sandbox, with permissions that let the sandbox read them but not change them. Every change is written to the audit trail, with who made it and which file, never the text. That entry is written after the file has changed, so if it cannot be written the change still stands (D0855). See Cora’s memory.
The audit trail
Section titled “The audit trail”Cora AI keeps an audit trail for each organisation. For a change kept in the database, the entry is written in the same step as the change, so a change that fails leaves no entry and an entry that cannot be written stops the change. A change to the organisation’s memory is a file, not a database record, so its entry is written just after the change, and a failed audit write does not undo the change (D0855). It records who did what and when: people and roles, invitations, connections and tool access, heroes, mission settings, memory changes, vault use, emails Cora sent, and plan changes. It never holds a password, a token, a key or the text of a file. Email addresses are removed from it.
Sign-in with a service’s own page
Section titled “Sign-in with a service’s own page”When you press Connect for a service such as Notion, you approve on the service’s own page, so Cora never sees your password. The access tokens that come back go straight to the secrets store and nowhere else: not the database, the logs, the audit trail or a prompt. Cora’s worker gets only the short-lived access token, for one step, and never the long-lived refresh token. The approval is tied to the browser that pressed Connect: that page makes a random secret, keeps it only in memory and gives Cora’s server just a fingerprint of it. The service’s answer lands on a Cora page that keeps nothing on the server and hands the answer to your own browser only. Your browser then sends the answer, the one-time state and the secret to Cora, and Cora checks all three against the fingerprints. The attempt works once and lasts ten minutes, and only you, signed in, can finish your own Connect. So if someone sends you their sign-in link, or you send yours, and it is approved in a different browser, nothing is connected and no one gets access to the account. Attempts that were never finished are cleaned up every five minutes, with their temporary secrets. If a renewed sign-in cannot be saved, the connection shows Needs reconnect and says why. Cora connects only to public https addresses, through the same safe route as every other MCP server. When you disconnect or leave, Cora asks the service to cancel the access and deletes the tokens. See Connecting with the service’s sign-in.
Backups
Section titled “Backups”The database is backed up automatically every day, and each backup is kept for 7 days. So something deleted from the database stays in the backups for up to 7 days, and then it is gone. Backups are encrypted, stay in the Sydney region and are used only to recover from a failure, never to answer a request.
Accounts
Section titled “Accounts”Sign-in is by email and password. Org admins invite people by email.
What Team Cora staff can see
Section titled “What Team Cora staff can see”For support and billing, Team Cora’s platform super admin can see a list of every organisation’s account: its name, plan and plan dates, how many members and missions it has, when it was last active, its AI usage as a share of what the plan includes, and its admins’ names and email addresses. The list never shows a mission’s name, a message, a file or the organisation’s memory, and it cannot change anything. To open this Admin area, that one staff account needs an authenticator code as well as a password. See The Admin area.
The same staff account can also read and change any organisation’s own memory (its memory page in Settings), so that Team Cora can help set up or correct what Cora remembers. It cannot reach a mission’s Memory tab. This does not need the authenticator code. It reaches nothing else of an organisation it is not a member of.
Payments
Section titled “Payments”Card details are held by the payment provider, Stripe, never by Cora AI. The platform stores a reference to the subscription, not the card.
The waiting list
Section titled “The waiting list”The website’s home page had a waiting-list form until the full site replaced it. It stored two things: the email address you gave and the time you gave it. Addresses already given are kept in a table in the Sydney region. Nothing else is recorded, and the address is never written to a log.
The address is kept only to tell you when the console opens. Once that message has been sent, the waiting-list table is deleted. Your address stays only if you start a trial (D0044).
Analytics on the website and docs
Section titled “Analytics on the website and docs”The website (teamcora.ai) and these docs use Google Analytics 4 to understand visits. It records:
- the pages you view, how far you scroll, searches you make on the site, and when you start or send a form;
- links you follow off the site (for example to Start free or Sign in) and files you download;
- your rough location (city or region, worked out from your IP address, which Google Analytics does not store);
- your device and browser, and how you arrived, for example from a search or a link.
It uses cookies in your browser to tell one visit from the next. Google keeps this data for up to 14 months, and may process it outside Australia, including in the United States. Google Analytics handles data about website visitors, not your organisation’s data, so it is not in the sub-processor table above. How Google uses it: How Google uses information from sites or apps that use our services.
There is no cookie banner. To stop Google Analytics on every site you visit, install Google’s opt-out add-on: https://tools.google.com/dlpage/gaoptout. Blocking cookies in your browser works too.
The console has no analytics. Nothing you do in a mission is sent to Google Analytics (D0897).
Your rights
Section titled “Your rights”Cora AI follows the Australian Privacy Act. You can ask for your organisation’s data to be deleted. When and how a full export is offered is still an open question (OQ22).
Not built yet
Section titled “Not built yet”These are not built yet. Do not rely on them.
- Single sign-on (signing in through your company’s own identity system) and Google sign-in (D0046).
- Choosing where your data is stored. Stored data is always in Sydney; there is no choice of another region.
- A malware scan of shared files (D0562).
- A screen to read the audit trail. The trail is written, but there is no page in the console for it yet.
- Using Team Cora from an AI client, such as Claude or Claude Code. See AI clients.
Questions
Section titled “Questions”If a question is not answered here, the FAQ covers the common ones.
Decisions: D0031, D0044, D0046, D0089, D0114, D0128, D0146, D0528, D0529, D0530, D0548, D0562, D0566, D0581, D0617, D0657, D0684, D0716, D0738, D0739, D0741, D0855, D0903, D0914, D0922, D0926, D0927.