Privacy Policy
1. Data We Collect
| Data type | What | Purpose | Linked to user |
|---|---|---|---|
| Account and eligibility | Email address, user ID, sign-in provider, and adult-eligibility status. Where supported, ORA receives an eligibility result or age range rather than an exact birth date. | Authentication, account security, and enforcing the 18+ product boundary | Yes |
| Story and product activity | Episode starts, progress and completions; follows; chat, creation, Community, Mall interest, and feature interactions | Provide continuity, personalize the experience, measure reliability and improve ORA | Yes |
| Chat, creation, and Community content | Character-chat messages, creation prompts and references, generated results, captions, published posts, reactions, reports, and blocked-account choices | Provide AI features, save requested history, publish selected/default-shared creations, and moderate safety | Yes |
| Purchases and Credits | Product identifier, transaction/entitlement state, renewal state, and server-authoritative Credits ledger | Deliver subscriptions, restore purchases, unlock eligible episodes, and fund creation tools | Yes |
| Device and diagnostics | App version, OS/device class, crash and performance data, notification token and preferences when enabled | Operate, secure, troubleshoot, and deliver requested notifications | Usually |
| Support | Messages, screenshots, account email, and job or transaction identifiers you send us | Respond to support, safety, deletion, and purchase-reconciliation requests | Yes |
| App launch waitlist | Email address, launch-notification consent version and server-recorded time, and an internal notification receipt/status | Keep your requested launch notification signup and notify the ORA team of it | Yes |
We do not collect:
- Full payment-card or bank-account details — App Store purchases are processed by Apple. We receive transaction and entitlement information, not your card number.
- Precise device location
- Your contacts
- Your exact birth date through ORA's age-range flow where the platform supports a privacy-preserving eligibility result
App Launch Waitlist
Joining the launch waitlist is optional and does not create an ORA account, buy a subscription, or authorize general promotional emails. With your explicit consent, we store your email and consent record in a dedicated Cloudflare database for ORA app launch notifications. We also send your submitted email and an internal receipt to the ORA team's existing Discord notification channel. We do not send your IP address, acquisition tags, or app activity in that notification.
Cloudflare processes network information to host and protect the form; our coarse abuse limiter uses a daily pseudonymous IP-derived key, not an anonymous identifier. The waitlist table does not store that IP or key. Cloudflare and Discord may process data in the countries where their services operate. The waitlist does not forward your email to advertising analytics. A saved signup does not guarantee that a notification has already been delivered.
We retain the waitlist record while needed to provide the requested launch updates, or until you withdraw consent, subject to limited legal or security recordkeeping needs. To withdraw or request deletion, email privacy@oraxlabs.io from the address you registered. We verify the request and remove the waitlist entry and its associated ORA-controlled Discord notification where applicable. No launch email is sent merely by submitting this form.
2. How We Use and Disclose Data
We use data to provide accounts and story continuity; operate private fictional-character chat; generate voice, images, and videos; run the moderated Community; fulfill subscriptions and Credits; prevent abuse; send notifications you enable; provide support; and understand product reliability.
We disclose only the data needed for these purposes to service providers such as Supabase (account, database, storage, and server functions), Apple and RevenueCat (App Store purchases and entitlements), OpenAI and approved model routes available through OpenRouter (AI moderation and generation), and notification, hosting, diagnostic, and customer-support providers used to operate ORA. Providers may process data in the United States and other countries where they or their subprocessors operate.
We do not sell personal information. Optional advertising measurement is described below.
Optional analytics profile and engagement measurements
You may choose to share an age range and country or region in Settings to help us understand how different groups use ORA and improve our stories and features. These choices are optional, are associated with your account, and can be changed or cleared at any time. This analytics profile does not request an exact date of birth or infer your age from adult-access verification. Missing information remains unknown.
Alongside the product interactions described above, we measure foreground engagement with episodes, character conversations and Community posts. These improvement reports use detailed activity records, counts and durations, not raw chat messages or creation prompts. Activity records may be associated with your account or guest install and session identifiers.
Reports keep the demographic information available when an activity occurred. Changing or clearing your choices affects future activity and does not retroactively rewrite or delete earlier activity records. When your account is deleted, this optional profile and its change history are removed, and the recorded age range is cleared from retained activity records. Some activity records, including country-level information and install/session identifiers, may remain under the retention practices described in this policy. Requests to access or delete personal data follow the process described in this policy.
Network-based country estimate
For country-level product analytics, ORA may request https://oraxlabs.io/cdn-cgi/trace, exposing your IP address to ORA and Cloudflare to process the request. From this response, ORA’s analytics code retains only the country code and observation time, without persisting your IP address or the raw trace response. It reuses the on-device estimate for up to 24 hours and may attach the code to activity records. Missing or expired estimates remain unknown until refreshed. Travel or a VPN can affect this network estimate; it does not establish your residence or infer your age.
Android install source and account operations
On Android, ORA reads the Google Play install referrer when available to understand how an installation reached ORA. We retain only supported source, medium, campaign, ad-set and creative tags, whether a click identifier was present, and a randomly generated installation identifier. We do not retain the raw referrer or click identifier. This report may be linked to the first account that signs in on that installation. It is client-reported acquisition information, not proof that a specific advertisement caused a registration; missing or unsupported information remains unknown. We do not infer advertising source from your sign-in provider, country or age. These records are used for ORA's own acquisition and product measurement, are not forwarded as advertising events, and are removed when the linked account is deleted, subject to the retention exceptions below.
For internal account operations, ORA sends the account email, sign-in provider and available country, optional age range and reported acquisition information in restricted ORA-team signup notifications through Discord and our email-delivery service. These notifications are not public posts or promotional emails to you. Country estimates and self-reported information are labeled as such. A notification may reflect information available at its first delivery attempt rather than at the instant the account was created. Requests to access, correct or delete personal data follow the process below.
Optional Advertising Measurement
On iOS, only after you grant Apple's tracking permission, ORA enables optional Meta App Events measurement to measure the effectiveness of ORA advertising. You can turn advertising measurement off in ORA Settings at any time. Meta may link a device advertising identifier and limited app interactions with information from its services to attribute advertising results. These interactions can include registration, story/episode viewing and completion, use of character chat and Community, no-charge preorder interest, paywall entry, and verified purchases when available. Technical app/device information may also be processed by the SDK. Meta's processing and retention follow its privacy policy.
ORA does not send chat messages, prompts, generated media, search text, email addresses, or payment transaction identifiers as advertising-event parameters. No-charge preorder interest is not reported as a purchase. First-party product analytics is separate from optional Meta advertising measurement.
You can decline tracking or turn advertising measurement off in ORA Settings without losing normal app features. Turning it off stops new ORA advertising-event forwarding; it does not retract information already sent to Meta. Events already handed to the SDK or in progress may still complete or retry. You can also manage Apple's tracking permission in iOS Settings.
Android Meta install-referrer processing
For supported Android installations, ORA may send an encrypted Meta install referrer, its installation identifier and an ORA authentication token to ORA's dedicated endpoint at https://oraxlabs.io/api/install-referrer, hosted by Cloudflare. The endpoint verifies the signed-in account and decrypts the referrer in memory. ORA retains supported campaign, ad-set and ad identifiers and limited processing evidence in its account database to connect an installation with an approved ORA advertisement. ORA does not retain the raw encrypted referrer or authentication token in its analytics records, and does not send them to Google Analytics or Discord. This first-party attribution path is separate from optional Meta App Events. Missing or unverifiable information remains unknown.
Optional Meta install measurement on Android
On supported Android versions, ORA offers a separate optional Meta install measurement setting while you are signed in. If you choose Allow, ORA can send the first consented activation of an eligible new installation to Meta through ORA’s server and Meta’s Conversions API. This reports an activation after your choice, not a backdated physical installation time. Updates, restored or previously used app identities, and later settings changes are not treated as new installations. Some genuine new installations cannot be measured, including when the app restarts before the choice can be confirmed.
Meta receives a randomly generated installation identifier, event identifier, activation time, app package and version, Android version and, when available, the installation referrer supplied by Google Play. That referrer can include encrypted Meta advertising information. ORA forwards the referrer transiently and does not retain its raw contents in analytics records, request logs or event queues. Meta can use these signals with activity on its services to measure advertising. An accepted event does not by itself prove that an advertisement caused the installation. Meta processes received information under its Privacy Policy.
ORA does not send Meta your email address, ORA account identifier, authentication token, push token, network IP address, chat messages, prompts, search text, media, payment identifiers or the server key used to decrypt advertising information. This integration does not read or send the Android advertising ID. It is separate from ORA’s first-party installation records and optional Google measurement.
Declining does not affect normal ORA features. The choice is not restored automatically: leaving the foreground, signing out, switching accounts or restarting closes measurement on the device. Turning it off cancels new local requests immediately. The server cancels unsent work when withdrawal reaches it, and also checks the current authenticated session and a short foreground authorization period before each send. A request already authorized by the server may still finish, even if the device has since gone offline or withdrawn. A server authorization marker does not prove that the request has already left the server. Withdrawal cannot recall information already received by Meta. Unsent events from a closed choice period are not replayed when you later enable measurement.
ORA keeps restricted installation ownership, choice-generation and event outcome records to enforce these limits. Provider response diagnostics are removed after 30 days. Minimal installation/event identifiers, occurrence times and outcome markers remain until the linked account is deleted, to prevent duplicate or old events from being sent again. These records do not contain the raw referrer, IP address or access credentials.
Optional Google measurement on Android
On supported Android versions, only if you choose the separate optional Google measurement setting, ORA enables Google Analytics for Firebase to measure installations, advertising attribution and limited app activity. Google may process an app-instance identifier, a separate randomly generated account connection identifier, app/device and network information, campaign information when available, and selected activity categories, counts and progress. ORA can use the connection identifier to associate these records with its own account activity. It does not send your account email, ORA authentication user ID, raw installation identifier, chat messages, prompts, search text or payment transaction identifiers as Google event parameters. Advertising-device-ID and SSAID collection and advertising personalization are disabled in this integration.
Google measurement is optional and can be enabled or withdrawn in ORA Settings without blocking normal app features. ORA stops forwarding new activity after withdrawal; this does not retract information already sent, and work already handed to the SDK may complete. Google processes data under its privacy policy. ORA links its Google Analytics property with its Google Ads account and exports the selected Android event stream to its company-controlled BigQuery project in the United States for daily acquisition and product analysis. The export does not include mobile advertising identifiers. Provider reporting may be delayed, incomplete or unavailable; ORA does not treat a missing campaign as proof of organic acquisition.
3. Data Retention
| Data | Retention period |
|---|---|
| Account, follows, library, chat history, creations, and Credits ledger | While the account is active, then deleted or de-identified after an account-deletion request, except where records must be retained for security, dispute, tax, fraud-prevention, or legal obligations |
| Published Community content | Hiding a post removes it from public feeds but retains it in your private My Posts history. Account deletion or moderation may remove it; limited moderation and security records may be retained as required |
| Purchase and entitlement records | For the period needed to restore purchases, reconcile Credits, resolve disputes, and meet legal obligations |
| Diagnostics and product analytics | Only as long as reasonably necessary for reliability, security, and product measurement, then deleted or aggregated |
| Support and safety requests | As long as needed to resolve the request and document the response |
4. Your Rights and Choices
Depending on where you live, you may have the following rights:
- Access: request a copy of the data we hold about you
- Deletion: request deletion of your account and associated data
- Portability: request your data in a machine-readable format
- Correction: request correction of inaccurate data
You can change notification choices in ORA Settings, manage or cancel an App Store subscription through Apple, hide your own Community posts from public feeds and restore them in My Posts, and block another creator in Community. To delete the account and associated content, use Profile → Settings → Delete Account. You may also email privacy@oraxlabs.io. We verify and respond to rights requests within the period required by applicable law.
5. Children
ORA accounts and interactive AI/Community features are for adults age 18 and older. We do not knowingly allow a person under 18 to use those features. If we learn that an underage person created an account, we will restrict or delete the account and associated data as appropriate.
6. Security
We use technical and organizational safeguards designed to protect data, including authenticated access, server-authoritative purchase and Credits records, access controls, moderation, and encrypted network transport. No online service can guarantee absolute security.
7. Changes to This Policy
We will post any changes to this page and update the effective date. Continued use of the app after changes constitutes acceptance.
8. Contact
OraXLabs, LLC
privacy@oraxlabs.io
https://oraxlabs.io/privacy/