Last updated: 9 October 2026
Cory is an AI companion for your browser. You can install the Cory extension for Chrome and Edge from the Chrome Web Store, and you can meet Cory and Corinna here on corybot.com before you install. This policy covers the Cory extension and corybot.com. We wrote it under the EU General Data Protection Regulation (GDPR), the German Federal Data Protection Act (BDSG) and the German Telecommunications Digital Services Data Protection Act (TDDDG).
Cory Co-Writer for Microsoft Word has its own privacy policy.
Cory has no accounts and keeps your chats, memories, keys and settings in your browser. When you ask Cory something, Cory sends your question and the page you're on to the AI provider you picked, using your own key, and we at Fundation never see it. We receive your requests in two cases only: when you use the free prompts included with Cory, which we answer without keeping what you asked, and when you pick AI-Flow, our own platform, as your provider. Nobody gets your data for advertising, and we build no profiles of you.
Fundation GmbH
Hibbelenstr. 10
51107 Cologne, Germany
Managing director: Cosmin Novac
Commercial register: Amtsgericht Köln, HRB 110232
Email: info (at) fundation.one
Phone: +49 (0) 174 3287600
Fundation GmbH is the controller under Art. 4(7) GDPR for the processing described in this policy. Where another company is responsible for data you send to it, we name that company below. You can find more company details in our Impressum.
Cory runs on every page you open, so it can show its menu when you select text. Cory reads the page itself only when you use it: when you send a message, ask for a rewrite, start a voice call or give Cory a task. Cory then works with:
With “Only answer when you look at the screen” on, Cory looks at a small grey copy of the camera picture about four times a second during a voice call, only to check whether a face is turned towards the screen. Cory does this in your browser, keeps no picture and sends nothing of it anywhere, so neither we nor any provider receive it. Cory reads the camera only after you turn the option on and allow the camera in your browser (§ 25(1) TDDDG), and you can turn it off at any time on the Voice & Emotions page.
When you give Cory a task, Cory can click, type, fill in forms and open pages in the tab you are working in. All of this happens in your browser, and we have no access to it. The next sections list what Cory stores on your device and what Cory sends to whom.
Cory keeps its data in your browser, in storage that belongs to Cory. Chrome lets only Cory read it, so websites and other extensions have no access to it.
| Where | What Cory keeps there | How long |
|---|---|---|
| Local extension storage | Your AI provider keys, your TypeSafe key, the AI provider keys Cory fetched from your AI-Flow account if you connected it, your Memry sign-in, your memories, your settings, and usage statistics that count how often Cory used each service. | Until you delete them in Cory or remove Cory. |
| Chat history database in your browser | Your chats and tasks, with the page text and screenshots Cory used for them. Cory keeps screenshots and full page text with your five most recent chats only. For older chats Cory keeps only the messages. | Until you clear the history or remove Cory. |
| Chrome sync storage | Your saved prompts, settings such as Cory's face and outfit, your memory mode, the address of your Memry server, the device identifier, the number of included prompts you have used and the seconds of included voice calls you have used. Cory never puts your keys or your chats in sync storage. | Until you delete them in Cory. If you have Chrome sync turned on, Google copies this storage to your Google account and to your other browsers, and keeps it under your Google account settings. |
We store this data on your device and read it back because Cory cannot work without it, so we don't need your separate consent for it (§ 25(2) no. 2 TDDDG). We have no access to it. When you remove Cory, Chrome deletes the local storage and the chat history.
Cory sends data only for a feature you are using, and only to the parties below. Each party gets only what we list for it.
You can choose OpenAI, Groq, Google (Gemini), Anthropic, Scaleway, AI-Flow, or any OpenAI-compatible service whose address you type in yourself. Only the provider you picked receives anything. For each answer, Cory sends that provider your message, the earlier messages in the chat, the page address, title and text, any text you selected, screenshots where the feature attaches one, and the memories you asked Cory to save. Cory sends your key along with each request, and only to that provider.
Your browser sends all of this directly to the provider, and we never receive it. You have your own agreement with the provider, and the provider is responsible for this data under its own privacy policy: OpenAI, Groq, Google, Anthropic, Scaleway.
AI-Flow is our own platform at ai-flow.eu. When you sign in on the AI-Flow website, Cory receives a sign-in token from it and keeps the token in your browser. If you pick one of your AI-Flow agents to answer for Cory, we receive your requests as the operator of AI-Flow and process them under your AI-Flow account and the AI-Flow privacy policy. We rely on Art. 6(1)(b) GDPR, the AI-Flow terms you agreed to.
With AI-Flow connected, Cory also fetches the AI provider keys you stored in your AI-Flow account, such as an OpenAI or TypeSafe key, and keeps them in your browser's local extension storage, which Chrome does not sync. Cory uses them like keys you type in: your browser sends each key only to the provider it belongs to, together with your request, and we do not receive those requests. When you connect, Cory asks whether to save the keys you typed into Cory to your AI-Flow account too, and saves them there only if you agree. A button on Cory's API & Models page asks the same later. AI-Flow keeps these keys in your AI-Flow account under the AI-Flow privacy policy. We rely on Art. 6(1)(b) GDPR, the service you asked for.
Cory runs voice calls on OpenAI's realtime voice service, with an OpenAI key of your own or, without one, on the 5 minutes of voice calls included with Cory. While a call is open, Cory sends your microphone audio to OpenAI, and OpenAI sends back what Cory says. During a call Cory also sends OpenAI the address, title and text of the page you are on, any text you selected there, and screenshots of the tab, so Cory can talk about what you see. When you have Cory read an answer aloud, Cory sends the text to OpenAI to turn it into speech. With your own key, your browser sends this directly to OpenAI under your own agreement with OpenAI, and we never receive it. See OpenAI's policies.
On the included minutes, Cory first asks our proxy for a short-lived access code. With that request Cory sends the device identifier, the extension's ID and the settings of the call, which are Cory's instructions, her voice and the tools she can use. The call itself then runs directly between your browser and OpenAI, and we never receive your audio or the page content of the call. OpenAI works for us as a processor under a data processing agreement (Art. 28 GDPR), may keep the data for up to 30 days to detect abuse, and does not train its models on it. Cory counts the seconds of the call in your browser and stores the total in Chrome sync storage, so the call ends when your 5 minutes are used up. We rely on Art. 6(1)(b) GDPR to give you the included minutes you use.
Cory has free prompts for people who have no key of their own. We answer them through our own server, a proxy that passes each request on to OpenAI. The proxy receives the same content a provider would: your message, the chat so far, the page address, title and text, any selected text, screenshots and the memories you asked Cory to save. With each request Cory also sends a device identifier and the extension's ID.
Cory calculates the device identifier in your browser from your time zone, screen size and colour depth, platform and language, and stores it in Chrome sync storage. We use it to count how many included prompts you have left. A separate counter of ours receives only this device identifier and the number of prompts you have used. If Groq or AI-Flow turns down a request on a free key because of its rate limit, and you still have included prompts, Cory sends that one request again through our proxy.
We don't store the content of your requests. We keep the device identifier and the count for as long as we offer included prompts, so you keep the same count if you remove and reinstall Cory. Cloudflare, Inc. (USA) runs the proxy and the counter for us and processes your IP address to deliver each request. OpenAI generates the answers. Both work for us as processors under data processing agreements (Art. 28 GDPR).
We rely on Art. 6(1)(b) GDPR to give you the included prompts you use, and on Art. 6(1)(f) GDPR, our legitimate interest in stopping one person from using up the free prompts meant for everyone. Cory reads your time zone, screen size, platform and language only to calculate the device identifier, which is strictly necessary to give you the included prompts (§ 25(2) no. 2 TDDDG).
Cory sends nothing to TypeSafe until you enter a TypeSafe key. With a key, Cory sends the text it is working with to TypeSafe's Jev model: your message, Cory's reply, the page's address, title and text, and the list of buttons and fields on it. Jev answers a typed question about that text, and Cory uses the answer for its next step. Cory never sends screenshots to TypeSafe. Of your saved memories, Cory sends only the topic names. Cory also sends each new fact to Jev once before saving it, so Jev can flag anything that looks like a password or another credential. TypeSafe processes this data under its own terms and privacy policy, see typesafe.ai.
Cory sends nothing to Memry until you switch memory to it. From then on Cory saves your memories on the Memry server at the address you entered, which is a server you run yourself or one you chose, and fetches the memories that relate to each conversation from it. If you log in with a Memry account, Cory keeps the sign-in tokens in your browser and sends them only to that server. We receive none of your memories. Whoever runs that Memry server is responsible for them.
If you switch memory to AI-Flow, Cory copies your memories, including the ones you already had, to your personal agent on ai-flow.eu and keeps a copy in your browser. We receive them as the operator of AI-Flow and process them under your AI-Flow account and the AI-Flow privacy policy (Art. 6(1)(b) GDPR).
Cory's face is the orb unless you pick Corinna in Cory's Closet. With Corinna picked, Cory loads her page from corybot.com into the side panel and checks corybot.com at most every 10 minutes for a newer version. Our host Netlify receives the same data as with any visit to corybot.com, listed in the website section below. Inside your browser, Cory passes Corinna's page the mood she should show and how loudly Cory is speaking. Cory also passes the background, hair and jacket you chose. We never receive any of it, and Cory passes Corinna's page nothing about your chats or the pages you visit. We rely on Art. 6(1)(f) GDPR, our legitimate interest in showing you the face you chose.
If you have Chrome sync turned on, Google copies Cory's sync storage, as listed above, to your Google account under Google's privacy policy.
When you remove Cory, Chrome opens our feedback form on Google Forms, and the Give Feedback button in Cory's settings opens the same form. You decide whether to answer. Google hosts the form and receives your IP address when the form opens, and we receive the answers you submit. We use them to improve Cory and delete them once we no longer need them for that. We rely on Art. 6(1)(f) GDPR, our legitimate interest in improving Cory.
Google processes your data when you install Cory from the Chrome Web Store, under Google's own terms. We see only summary numbers in the store's developer dashboard, such as how many people installed Cory, and we cannot tell who you are from them.
Cory sends nothing to advertisers or data brokers. We sell no data.
Chrome shows three warnings when you install Cory.
The warning "Read and change all your data on all websites" is there because Cory reads the page you ask about, and clicks and types on it when you give Cory a task. Cory also uses this access to show its menu when you select text.
You see "Read your browsing history" because Cory has the tabs permission. Cory uses it to read the address of the page open in the tab you are working in, including a page Cory opened during a task, and to update the side panel when you switch tabs. Cory keeps no list of the pages you visit and stores a page address only with a chat you had about that page.
For the debugger permission, Chrome warns "Access the page debugger backend". Cory uses the debugger to take screenshots of the tab you are working in, including pages longer than the screen, and to click and type on the page when you give Cory a task.
Cory can also open a sign-in window, which it does only when you log in to a Memry server, and Cory never reads your Google account.
Cory connects to our servers and to every built-in provider over encrypted HTTPS. If you type in a custom provider or Memry address that starts with http://, Cory uses it as you typed it, and that connection is unencrypted. Cory keeps your keys in local extension storage, which Chrome does not sync, and sends each key only to the service it belongs to. We keep the OpenAI key for the free prompts on our server, so it is never in your browser. We keep no copy of your chats on our servers, and we take technical and organisational measures under Art. 32 GDPR to protect the data we do receive.
We host corybot.com at Netlify, Inc. (USA). When you open a page, Netlify records your IP address, the date and time, the page you asked for, the page you came from, and your browser and operating system. We use this only to deliver corybot.com and keep it secure. Netlify processes the data for us under a data processing agreement (Art. 28 GDPR), and Netlify sets how long it keeps these logs, see Netlify's privacy policy. We keep no copy of them. We rely on Art. 6(1)(f) GDPR, our legitimate interest in a working and secure website.
We put no cookies and no tracking tools on corybot.com. Your browser may keep the files of corybot.com, including Corinna's 3D model, in its cache so the page loads faster next time (§ 25(2) no. 2 TDDDG).
When you talk to Cory or Corinna here, your browser stores how many seconds you have talked, in its local storage for corybot.com, so the calls end after 5 minutes in total. The number stays in your browser, and we never receive it. We need it to offer the free voice calls you start yourself (§ 25(2) no. 2 TDDDG). You can delete it by clearing the site data for corybot.com in your browser.
When you press Talk, your browser shows a prompt for access to your microphone. We then request a short-lived access code from OpenAI, and your browser uses it to open the voice call directly with OpenAI. During the call, your browser sends your microphone audio to OpenAI, and OpenAI sends back the spoken answer. If we have switched on text answers for voice calls, our server also sends a transcript of what you say and the conversation so far to Groq, and Groq generates the answer that Cory or Corinna speaks. We don't store your conversations.
OpenAI and Groq work for us as processors under data processing agreements (Art. 28 GDPR). OpenAI may keep the data for up to 30 days to detect abuse, and neither company trains its models on data we send them. We rely on Art. 6(1)(f) GDPR, our legitimate interest in letting you try Cory by voice in a call you start yourself. Please don't share sensitive personal information in this demo.
If you email us, we use your name, email address and message to answer you. We rely on Art. 6(1)(f) GDPR, our legitimate interest in answering you, and on Art. 6(1)(b) GDPR where you ask about a contract. We delete your email once your request is settled, unless we have to keep it under German commercial or tax law, which for business letters means up to six years (§ 257 HGB, § 147 AO).
Several recipients in this policy are based in the United States, among them Netlify, Cloudflare, OpenAI, Groq, Anthropic and Google. For the processors we work with ourselves (Netlify, Cloudflare, OpenAI and Groq), we base the transfer on the EU Commission's adequacy decision for the EU-U.S. Data Privacy Framework (Art. 45 GDPR) where the company is certified under it, and otherwise on the EU Standard Contractual Clauses in their data processing agreements (Art. 46(2)(c) GDPR). When you use a provider with your own key, you transfer the data under your own agreement with that provider. Scaleway is based in France, and a Memry server is wherever its operator runs it.
You have no legal or contractual duty to give us personal data. Without an AI provider key or the included prompts, Cory cannot answer you, and without microphone access you cannot make voice calls.
We make no decisions about you based solely on automated processing, including profiling (Art. 22 GDPR). When Cory works on a task you gave it, the AI model generates the next step of that task, and that step has no legal or similarly significant effect on you.
You have the right to access your data (Art. 15 GDPR), to have it corrected (Art. 16) or deleted (Art. 17), to restrict its processing (Art. 18), to receive it in a portable format (Art. 20) and to object to its processing (Art. 21, see the next section). To use these rights, write to info (at) fundation.one.
We can act only on data we hold: the device identifier and prompt count, emails you sent us, feedback answers and, if you use AI-Flow, your AI-Flow data. You can delete the data in your browser yourself in Cory. For data you sent to a provider with your own key, contact that provider.
You also have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR), in particular in the EU country where you live or work. The authority responsible for us is the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen, Kavalleriestr. 2-4, 40213 Düsseldorf, Germany, www.ldi.nrw.de.
Where we process your data on the basis of our legitimate interests (Art. 6(1)(f) GDPR), you can object at any time on grounds relating to your particular situation (Art. 21(1) GDPR). We then stop processing it, unless we can show compelling legitimate grounds that override your interests, rights and freedoms, or we need the data to establish, exercise or defend legal claims. Send your objection to info (at) fundation.one.
We update this policy whenever we change what Cory or corybot.com sends, and to whom. The date at the top shows when we last changed it.