CoraBack to home

Last updated 12 November 2026

Privacy Policy

This policy explains what personal data Cora AI ("Cora", "we", "us") processes when you visit coraai.app or use the Cora app, why we do it, who helps us, and the rights you have under the EU General Data Protection Regulation (GDPR).

Draft pending legal review

Items marked "To be added" are details we still need to complete. Until then, you can reach us at the contact address in section 1 with any privacy question.

1. Who is responsible

The controller responsible for processing your personal data is:

Cora AI, operated by [To be added: full legal name of the controller (person or company)]
[To be added: postal address]
Email: [To be added: privacy contact email address]

Data protection officer: [To be added: name and contact of a data protection officer, or a statement that none is required]

2. Data we collect

We only collect data that is needed to run Cora:

  • Account data: your email address and, if you sign in with Google, your name and profile picture. If you sign in with Apple, your name (only if you share it) and either your email address or an Apple private relay address if you choose "Hide My Email". If you sign up with email, your password is stored only as a secure hash by our authentication provider.
  • Content you create: your chats and messages, projects, things you ask Cora to remember, files and images you upload, documents, images and animations Cora creates for you, and Forge projects.
  • Published content: if you publish a Forge site, its content becomes publicly accessible at its link until you remove it.
  • Usage and plan data: message and generation counters, credit balances, your plan (FREE or PRO) and subscription status.
  • Payment data: when you buy PRO, our payment provider processes your payment details. We do not receive or store your full card number; we receive a customer reference and subscription status.
  • Connected services: if you connect a plug-in (for example Gmail or GitHub), a credential that lets Cora act for you, and the data Cora retrieves when you ask it to (see sections 5 and 6).
  • Technical data: IP address, browser and device information and error logs created when you use the service, needed for security and to fix problems.

Data that stays on your device: folders you open with device file search are indexed in your browser only and are not uploaded. A file's text is sent to Cora only after you confirm sharing it. Voice dictation uses your browser's built-in speech recognition. We do not store audio, but your browser vendor may process the audio under its own privacy terms.

3. Why we use it and legal bases

  • Providing Cora (your account, chats, memory, creation tools, Forge, plug-ins you request): performance of our contract with you, Art. 6(1)(b) GDPR.
  • Connecting third-party accounts: your consent, Art. 6(1)(a) GDPR. You can withdraw it at any time by disconnecting the plug-in in Settings → Plugins.
  • Payments and invoices: contract, Art. 6(1)(b), and legal retention duties under tax and commercial law, Art. 6(1)(c) GDPR.
  • Security, abuse prevention, usage limits and error fixing: our legitimate interest in a safe and reliable service, Art. 6(1)(f) GDPR.

We do not sell your personal data and we do not use it for advertising.

4. AI processing

To answer you, the content of your request, including the relevant conversation, uploaded files and images, saved memories, and data retrieved from connected services, is sent to external AI processing providers. They generate the reply, image or document and return it to us. The providers are listed in section 7.

  • We use these providers only to deliver the feature you asked for. We do not use your content to train AI models.
  • Our providers process data on our behalf under their business or API terms. [To be added: confirmation of each AI provider's data retention period and that they do not use API data for training]
  • When you use web search, your search query is sent to a web search provider.
  • AI answers can be wrong. Do not rely on them for medical, legal or financial decisions.

Cora does not make decisions that have legal or similarly significant effects on you based solely on automated processing (Art. 22 GDPR).

5. Google sign-in and Google permissions

Sign in with Google gives us your name, email address and profile picture. We use them only to create and identify your account.

Google plug-ins are optional. Each one asks for its own permission on Google's consent screen:

  • Gmail: read your messages and labels (gmail.readonly) to search and read emails when you ask, and create drafts (gmail.compose). Cora creates drafts only and never sends email for you.
  • Google Calendar: view and create calendar events (calendar.events), so Cora can list your events and add an event when you explicitly ask.
  • Google Drive: read-only access to your files (drive.readonly) to find and read files when you ask.
  • Every Google plug-in also requests your basic profile and email address (userinfo.profile, userinfo.email) to identify the connected account.

Cora accesses Google data only when you ask for it in a conversation, and only to answer that request. Retrieved data is shown in your chat and is kept as part of that chat's history until you delete it.

Limited Use: Cora's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide the features you request. We do not sell it, use it for advertising, or use it to train general AI models. People do not read it unless you ask us to, it is needed for security or abuse investigation, or the law requires it. We share it with the AI providers in section 7 only to generate the answer you asked for.

You can revoke access at any time in Settings → Plugins, or at myaccount.google.com/permissions.

6. Other connected services

Blender (Blender Foundation): the optional local Cora companion pairs privately to one Forge project with a one-use five-minute code and a hashed 30-day credential. The credential stays in memory on your computer. When you enable scene access, bounded object names, transforms, geometry counts, materials, requested scene details and command receipts are shared with Cora and its AI processors. Cora can create and modify native objects with undo checkpoints. Saving/export separately requires your permission and a chosen output folder: .blend, .fbx and .glb files remain on your computer and existing files are not overwritten. Saved file paths and sizes are reported privately to Cora; files are not automatically uploaded to Roblox. No arbitrary Python or shell execution is allowed. Disconnecting in Forge revokes access and removes stored scene reports/commands; project/account deletion also removes them.

Roblox Studio (Roblox Corporation): the optional local Forge companion downloads the paired project's Roblox scripts and map to your computer and reports connection, place name, place ID, applied-version and error status to Cora. Connection codes expire after five minutes and can be used once; the resulting project-scoped credential expires after 30 days and is stored only as a hash on our servers. If you save your Roblox user ID in Forge for one-click connect, we store that ID with your account; Studio connect requests show a short code and connect only after you approve them in Forge. Studio keeps the credential in its plugin settings until you disconnect, so it reconnects automatically. Live sync is optional and applies saved changes automatically when you enable it. Whole-place editing is separately enabled in Studio: it shares a bounded scene hierarchy, selected objects, requested object properties and script source, and captured error logs with Cora and its AI processors, and permits undoable changes to existing objects and scripts. These scene reports and command receipts remain private to your project and are removed on disconnect or project/account deletion. No game is automatically published. Disconnecting in Forge revokes the credential; deleting the project or account removes it. Roblox's privacy terms apply when you use Studio or publish to Roblox.

You can also connect GitHub, Notion, Slack, Linear, Microsoft OneDrive and Microsoft Outlook. Each one asks you for permission on the provider's own sign-in page. Depending on the service, Cora can:

  • GitHub: read your profile, repositories, issues and code, and create an issue when you ask.
  • Notion: read only the pages you choose to share during sign-in.
  • Slack: list and read public channels and post a message when you ask.
  • Linear: read your issues and teams and create an issue when you ask.
  • OneDrive: read-only file search.
  • Outlook: read your mail and calendar.

Your sign-in credential for each service is stored encrypted on our servers. It is never sent to your browser and never shared with other users. Cora writes to a connected service only when you explicitly ask. Disconnecting a plug-in revokes Cora's access and deletes the stored credential. The provider's own privacy policy applies to the data held in your account there.

7. Service providers and recipients

We use these service providers (processors) to run Cora. They may only use your data on our instructions:

  • Lovable (Lovable Labs Incorporated): app hosting, database, sign-in, file storage and connection management for plug-ins, through its infrastructure subprocessors.
  • Anthropic (Anthropic PBC, USA): AI processing for chat replies.
  • Google (Google LLC / Google Ireland Ltd.): AI processing for creating and editing images, and Google sign-in.
  • Tavily: web search, if you or Cora use it.
  • Stripe (Stripe Payments Europe Ltd.): payment processing for PRO subscriptions bought on the website.
  • Apple (Apple Inc. / Apple Distribution International Ltd.): Sign in with Apple, and App Store payment processing for PRO subscriptions bought in the iOS app. We receive the subscription status and transaction IDs from Apple, never your payment details.
  • Plug-in providers you connect (section 6) receive the requests Cora makes for you.

[To be added: confirmation that data processing agreements are in place with each provider, plus any further subprocessors]

We may also disclose data where the law requires it.

8. Transfers outside the EU

Some providers are based in, or process data in, the United States or other countries outside the EU/EEA. Where this happens, we rely on the EU–U.S. Data Privacy Framework where the provider is certified, or on the European Commission's Standard Contractual Clauses (Art. 46 GDPR).

[To be added: the transfer safeguard used for each provider, and the regions where data is hosted]

9. Storage and retention

  • Account, chats, memories, projects and files: kept while your account exists, until you delete them or your account.
  • Plug-in credentials: kept until you disconnect the plug-in or delete your account.
  • Payment records: kept for as long as tax and commercial law requires. [To be added: applicable retention period, e.g. 7 years under Austrian law]
  • Technical logs: kept only for a short period for security and error fixing. [To be added: log retention period]

10. Security

We protect your data with encrypted connections (HTTPS) and access controls, so each account can only reach its own data. Plug-in credentials are additionally encrypted before they are stored. Access to production systems is restricted. No system is completely secure, so please use a strong, unique password.

11. Deleting your data

  • You can delete individual chats at any time in the app.
  • You can remove plug-in access in Settings → Plugins.
  • To delete your whole account and all associated data, email us at the address in section 1. We will complete the request within one month (Art. 12(3) GDPR), except for data we must keep by law.

12. Your rights

Under the GDPR you have the right to:

  • access your data (Art. 15) and receive a copy;
  • have inaccurate data corrected (Art. 16);
  • have your data deleted (Art. 17);
  • restrict processing (Art. 18);
  • data portability (Art. 20);
  • object to processing based on legitimate interests (Art. 21);
  • withdraw consent at any time, without affecting processing that took place before (Art. 7(3)).

To exercise your rights, contact us at the address in section 1. You also have the right to lodge a complaint with a data protection supervisory authority. In Austria this is the Datenschutzbehörde, Barichgasse 40–42, 1030 Vienna, dsb.gv.at. You can also complain to the authority in your own EU country.

13. Cookies and local storage

Cora uses your browser's local storage only for things that are strictly necessary: keeping you signed in, remembering your interface choices, and installing the app on your home screen. We do not use advertising or tracking cookies. [To be added: confirmation that no analytics or third-party tracking tools are used on the website]

14. Children

[To be added: minimum age for using Cora and how consent from a parent or guardian is handled for younger users (in Austria, children under 14 need a parent's consent, § 4 DSG)]

15. Changes to this policy

We will update this policy when Cora or the law changes. The date at the top shows the latest version. We will notify you in the app or by email about significant changes.