Privacy Policy

We currently collect and process the following categories of data:

Account and authentication data: email address, user ID, and session/authentication information used to sign in through Supabase.

Chat content: messages you send, assistant responses, and optional files you upload (for example images or PDFs) when using supported features.

Usage and technical metadata: timestamps, thread identifiers, message identifiers, usage counters, route/model metadata, and basic error/debug logs needed to operate the service.

Optional web search inputs/results: if you enable web search in chat, your query and related results may be processed through configured web search providers.

We use data to provide and improve the product, including authentication, conversation history, usage tracking, safety/abuse prevention, support, and reliability monitoring.

We may review logs and limited account information to troubleshoot bugs, investigate abuse, and respond to support requests.

Account and application data are stored primarily in Supabase (including authentication and application tables used for chat threads/messages and related metadata).

Hosting and runtime infrastructure may process data in transit to deliver the application and proxy API requests.

Depending on the feature you use, Oracene may send prompts/content to third-party model providers to generate responses.

If web search is enabled in a conversation, search queries and related request data may be sent to a configured web search provider to retrieve results.

We aim to use providers that support secure transport and enterprise-friendly data handling, but provider practices are governed by their own terms and policies.

During private beta, we generally retain account and chat data while your account is active so core product features (including history) continue to work.

If you request account deletion, our default target is to delete or de-identify account-associated application data within 30 days, unless we need to retain specific records for security, fraud prevention, or legal compliance.

Operational logs may be retained for a shorter period as needed for debugging and service reliability.

We use best-effort security measures appropriate for a private beta, including HTTPS, authenticated access via Supabase, server-side secret handling for backend integrations, and access controls on application data where configured.

No system can be guaranteed perfectly secure. Please avoid submitting highly sensitive information unless necessary.

You may contact us to request access to or deletion of your account data and chat history, subject to verification and any legal/security retention requirements.

For privacy questions or requests, contact support@oracene.com.

Oracene uses essential cookies/session storage for login and access control (including beta access gating and Supabase authentication/session handling).

We may also use optional analytics or telemetry to understand product usage and improve performance, reliability, and support workflows.

Where opt-out controls are available, you can use them in product settings; browser controls may also limit certain tracking behaviors. You may also contact us to request guidance on available opt-out options.