Privacy Policy

Last updated October 7, 2026

1. Scope of this policy

This policy applies to the Orea website at tryorea.xyz, the Orea web application, Orea's remote MCP server, and the Orea experience made available inside ChatGPT and Codex. In this policy, those services are collectively called the “Service.” “Orea,” “we,” “us,” and “our” refer to the operator of the Service.

This policy covers information that Orea receives or controls. ChatGPT, Codex, Google, OpenAI, Supabase, Vercel, Slack, and other third-party services may independently process information under their own terms and privacy policies. For example, OpenAI controls the ChatGPT or Codex conversation surrounding an Orea tool call, while Orea receives only the authentication details, tool inputs, and files needed to provide the requested Orea feature. Orea does not request or reconstruct your full ChatGPT or Codex conversation history.

2. Information we collect

We limit collection to information reasonably necessary to authenticate users, provide image edits, maintain credits and generation history, secure the Service, troubleshoot failures, and respond to support requests. Depending on how you use Orea, we may collect the following categories of information.

Account and profile information

Authentication and connection information

Images and other user content

Portraits can reveal a person's face, appearance, and other personal characteristics. Orea processes those characteristics only to perform the visual edit you request. Orea does not use uploaded portraits for facial recognition, identity verification, biometric matching, surveillance, or the creation of biometric templates. You should upload only images you own or have permission to edit.

Generation and transaction information

Technical, security, and operational information

When you use the Service, Orea and its hosting and infrastructure providers may process standard request and security information such as timestamps, requested routes, response status, browser or device type, IP address, authentication success or failure, and limited error logs. We use this information to deliver the Service, detect abuse, protect accounts, maintain availability, and diagnose technical problems. Orea does not use this information for behavioral advertising or to build a profile of your activity across unrelated services.

Support communications

If you contact support, we receive the information you choose to provide, such as your email address, the approximate time of an issue, a generation status, and the content of your message. We ask that you do not send passwords, API keys, authentication codes, or other secrets. You do not need to email your original image for us to investigate most issues.

3. How we collect information

We collect information in the following ways:

4. How we use information

Orea uses the categories of information described above to:

Orea does not sell personal information, serve targeted advertising, or use your photos to create a public profile. Orea does not use uploaded images or generated results to train an Orea-owned AI model.

5. How image processing works

When you choose a photo, Orea creates a one-time, path-scoped destination in a private Supabase Storage bucket. The selected file is uploaded directly to that private destination, validated against Orea's permitted file types and size limit, and normalized before a generation is started. An upload that cannot be validated or reserved for a generation is normally removed during error handling.

For a valid request, Orea sends the selected image and the instruction for your chosen preset to the OpenAI API. OpenAI processes that request and returns an edited image to Orea. Orea then stores the result in the same private storage environment and updates the generation record. The input is not obtained from an arbitrary internet address: the current workflow requires you to select and upload the file yourself through Orea.

Orea returns short-lived signed links when your account needs to display an input or result. These links currently expire after approximately ten minutes. The storage bucket itself is not public, and images are not placed in a public gallery. Someone who receives a still-valid signed link may be able to view the associated file until that link expires, so you should not share signed links with people you do not trust.

6. Service providers and categories of recipients

We disclose information only to providers that help operate the Service, to a new operator in a properly managed business transaction, or when legally required. Our current principal service-provider categories and the information they may process are:

We may disclose information if we reasonably believe disclosure is necessary to comply with law or valid legal process; protect the rights, safety, or security of users, Orea, or others; investigate fraud or abuse; or establish or defend legal claims. If Orea is involved in a merger, acquisition, financing, reorganization, or sale of assets, information may be transferred as part of that transaction subject to appropriate confidentiality protections and applicable law.

7. Retention

We retain information only for as long as reasonably necessary for the purposes described in this policy. Our current retention approach is as follows:

Deletion from active systems may not immediately remove information from encrypted backups. Residual backup copies are isolated from ordinary use and are removed or overwritten through the provider's normal backup lifecycle. We may retain de-identified or aggregated information that can no longer reasonably be linked to you.

8. Cookies, local storage, and similar technologies

Orea uses cookies and similar browser storage that are necessary to sign you in, maintain and refresh your session, protect the authorization flow, remember limited interface state, and prevent unauthorized access. These technologies are used for functionality and security rather than cross-site advertising. Blocking necessary cookies may prevent sign-in, account access, or the ChatGPT and Codex connection from working.

9. Security

Orea uses technical and organizational safeguards designed to protect information against unauthorized access, alteration, disclosure, or destruction. These measures include private object storage, signed and time-limited image access, authenticated requests, OAuth token verification, per-user database and storage access rules, server-side credentials, restricted administrative access, file-type and file-size validation, and generation idempotency controls.

No internet transmission or storage system can be guaranteed completely secure. You are responsible for maintaining the confidentiality of your sign-in credentials, protecting access to your email account, and signing out of shared devices. Contact support promptly if you believe your Orea account or an image link has been accessed without authorization.

10. Your choices and controls

Depending on your location and applicable law, you may:

To exercise a privacy right, visit Orea supportand contact us from the email address associated with the account. Tell us whether your request concerns an account, a specific generation, or a particular image. We may need to verify your identity before fulfilling a request so that we do not disclose or delete another person's data. We aim to respond within 30 days, or within the period required by applicable law. We will explain if we need additional time or cannot fulfill part of a request.

11. Account and image deletion

During beta, deletion requests are handled through Orea support. You may request deletion of individual stored images without necessarily closing the account, or request deletion of the full account. A full account deletion is intended to remove the active profile, credits, credit history, generation records, and private Orea image objects associated with the verified account, subject to the limited exceptions described in the retention section above.

Disconnecting Orea from ChatGPT or Codex prevents future use of that connection but does not by itself delete an Orea account or previously stored Orea images. Likewise, deleting a ChatGPT conversation does not automatically delete records held by Orea. Contact Orea support when you want Orea-controlled data deleted.

12. International processing

Orea and its service providers may process information in the United States and other countries where they operate. Those countries may have privacy laws that differ from the laws where you live. Where required, we rely on appropriate contractual or legal safeguards for cross-border transfers. By using the Service, you understand that information may be processed outside your country of residence as permitted by applicable law.

13. Children and teens

Orea is not directed to children under 13, and we do not knowingly collect personal information from children under 13. Users must also meet any higher minimum age required in their country to consent to an online service. If you believe a child provided information to Orea contrary to these requirements, contact support so we can investigate and delete the information where appropriate. Teen users should upload only images they own or have permission to edit and should avoid images that reveal sensitive information.

14. Changes to this policy

We may update this Privacy Policy as Orea develops, our providers or practices change, or legal and platform requirements evolve. When we make changes, we will update the “Last updated” date at the top of this page. If a change materially affects how we use previously collected personal information, we will provide additional notice or request consent when required by law. Your continued use of the Service after an update is subject to the revised policy.

15. Contact us

Questions about this policy, privacy rights, data retention, or deletion requests can be sent through Orea support. Please do not include your password, authentication token, API key, or other secret in a support message. If your request concerns a generation, include only the approximate date, selected preset, and visible status unless support asks for additional information.