Privacy Policy

1. Scope

This Privacy Policy applies to the OraOrb service, including the physical OraOrb companion device, the OraOrb iPhone app, and the cloud and web services that support them.

The current OraOrb product consists of two connected parts:

• The physical OraOrb device, where users have free-form voice conversations with Ora.
• The OraOrb iPhone companion app, which provides account access, OraOrb setup and device management, Echo Archive, account settings, and privacy controls.

The current iPhone app does not use the iPhone microphone for Ora conversations. Voice input for conversations is captured by the physical OraOrb device.

2. Information We Collect

Account Information

We collect information needed to create and operate your OraOrb account, including:

• email address;
• account identifier;
• authentication and verification-code records;
• account status; and
• profile information you choose to provide, such as a display name.

Birth and Personalization Information

If you choose to provide birth information, we may collect:

• birth date;
• birth time;
• birth city;
• time zone; and
• geographic coordinates derived from the birth location.

This information may be used to create personalization context that helps Ora provide a more individualized experience.

Conversations and AI-Generated Content

Voice conversations are initiated through the physical OraOrb device.

When you speak with Ora through the physical OraOrb device:

1. voice audio from the OraOrb device is transmitted to a speech-recognition service and converted into text;
2. the resulting transcript, together with relevant conversation and personalization context, may be processed by AI services to generate Ora’s response; and
3. Ora’s generated response text is processed by a text-to-speech service so that the physical OraOrb device can speak the response.

OraOrb may store:

• conversation transcripts;
• Ora’s text responses;
• conversation history;
• session summaries;
• selected personalization and memory context; and
• conversation records displayed in Echo Archive.

OraOrb’s normal saved conversation history is based on transcripts and generated content rather than the original voice stream.

Voice audio is transmitted to the applicable speech-recognition provider for processing and may be handled by that provider according to its applicable service terms, configurations, legal obligations, and privacy practices.

The current iPhone app itself does not capture or transmit microphone audio.

Memory and Profile Summaries

OraOrb may derive useful facts, preferences, recurring themes, and summaries from conversations to make future interactions more coherent and personalized.

Relevant portions of memory or profile context may be included when AI services generate a response.

Stored sensitive information may receive additional encryption and access-control protections.

OraOrb does not currently provide a user-facing interface for reviewing or deleting individual memory items. Deleting your OraOrb account removes associated active account data as described in Section 6.

OraOrb Device and Provisioning Information

We may collect information about your OraOrb device, including:

• device identifier;
• device binding information;
• firmware version;
• connectivity and network status;
• diagnostic information; and
• the Wi-Fi network name used during supported setup flows.

The current iPhone app requests Bluetooth access because Bluetooth is used to discover, configure, bind, and communicate with an OraOrb device during supported device setup flows.

During Wi-Fi provisioning, Wi-Fi credentials are transferred from the iPhone to the OraOrb device for setup and are not intended to be stored as part of the user’s OraOrb server-side account profile.

The current Store version of the iPhone app does not request access to the iPhone microphone, Photos library, camera, contacts, or precise location.

Usage, Analytics, Crashes, and Logs

We collect information needed to operate, secure, diagnose, and improve the service, which may include:

• product interaction events;
• device and operating-system information;
• crash reports;
• IP address and request metadata;
• service performance information; and
• server and diagnostic logs.

Some diagnostic records may contain account identifiers or limited conversation or request information when necessary to investigate a service failure or security issue.

3. How We Use Information

We use information to:

• create and authenticate OraOrb accounts;
• send one-time login verification codes;
• pair, configure, and operate OraOrb devices;
• convert OraOrb voice input into text;
• generate Ora’s AI responses;
• generate Ora’s spoken responses;
• synchronize and display conversation history in Echo Archive;
• personalize conversations and maintain relevant memory;
• provide requested information such as weather;
• maintain service reliability and diagnose failures;
• protect accounts and prevent misuse;
• understand product performance through analytics and crash diagnostics;
• provide customer support; and
• process privacy and account-deletion requests.

We do not sell personal information.

OraOrb does not use third-party advertising SDKs, perform cross-app tracking for advertising, or use personal information for targeted advertising.

4. Service Providers and International Processing

OraOrb uses specialized third-party service providers to deliver its services. Depending on the provider and the function being used, information may be processed in the United States, China, or other jurisdictions where those providers operate.

Current production service providers supporting OraOrb include:

Alibaba Cloud Model Studio / DashScope

Purpose: Speech recognition for voice conversations conducted through the physical OraOrb device.

Information processed: Voice audio streamed from the physical OraOrb device for speech-to-text processing.

Current processing region: Beijing region, China.

AiHubMix

Purpose: AI API gateway used to access AI models for conversation generation, intent processing, memory processing, and related functions.

Information processed: Conversation text and relevant recent, personalization, memory, system, and tool context when needed to provide the service.

OpenAI

Purpose: AI model processing accessed through AiHubMix.

Information processed: Conversation text and relevant context routed through AiHubMix to the applicable OpenAI model.

xAI

Purpose: Text-to-speech generation for Ora’s spoken responses.

Information processed: Ora’s generated response text.

AstrologyAPI

Purpose: Background personalization-context calculations based on birth information.

Information processed: Birth date, birth time, latitude, longitude, and time-zone information. OraOrb does not need to provide your email address or OraOrb account identifier to AstrologyAPI for these calculations.

Open-Meteo

Purpose: Weather lookup when weather information is requested in a supported Ora experience.

Information processed: City or location-name information necessary to complete the weather request.

Resend

Purpose: Transactional email delivery, including one-time login verification codes.

Information processed: Email address and information required to deliver the verification message.

Google Cloud Platform and Firebase

Purpose: Cloud hosting, databases, authentication infrastructure, storage, synchronization, push notifications, configuration, analytics, crash reporting, encryption-key management, and service logging.

Information processed: Depending on the function, this may include account information, stored product data, device information, usage information, diagnostics, push tokens, and service logs.

OraOrb’s primary production cloud infrastructure is hosted in the United States. Certain specialized processing, including the speech-recognition processing described above, currently occurs outside the United States.

We provide service providers with information reasonably necessary for them to perform the relevant service.

Third-party providers may process or retain information according to their applicable service configurations, agreements, legal requirements, and privacy practices. Their retention practices may differ from ours.

OraOrb does not make a blanket representation that every third-party AI or speech provider operates under zero-retention or no-training terms unless such a commitment has been separately verified.

We do not authorize our service providers to use OraOrb information for targeted advertising on our behalf.

5. Retention

We retain information for as long as reasonably necessary to operate the OraOrb service, maintain account continuity, protect the service, comply with applicable obligations, and resolve disputes.

While your account is active, retained information may include:

• account records;
• saved conversation history;
• Echo Archive content;
• birth and personalization information;
• OraOrb device-binding information; and
• long-term memory and profile summaries.

Certain detailed diagnostic traces are automatically deleted after approximately 48 hours.

General operational and server logs are generally retained for approximately 30 days.

Backups and disaster-recovery copies may continue to exist for a limited period according to applicable backup lifecycles.

Third-party providers may retain information according to their own applicable service configurations, agreements, legal obligations, and privacy practices.

6. Account Deletion

You can permanently delete your OraOrb account from:

Settings → Account → Delete Account

You may also use OraOrb’s web account-deletion service or contact us for assistance.

Account deletion is irreversible.

When account deletion is completed, active account data associated with your OraOrb account is deleted, including applicable:

• authentication and account records;
• profile information;
• saved conversation records;
• Echo Archive data;
• long-term memory;
• birth and personalization information;
• product records associated with the account; and
• OraOrb device binding.

Limited operational logs, diagnostic traces, security records, or backup copies may remain for a limited period where technically necessary and will expire according to the applicable retention schedule.

Ordinary production logs are generally removed within approximately 30 days.

Information that has already been processed by third-party providers may be subject to those providers’ applicable retention practices and may not always be directly retrievable or deletable by ROLENEO LLC.

7. Security

We use administrative, technical, and organizational safeguards designed to protect information, including:

• encrypted network connections;
• encrypted cloud storage;
• managed secrets and encryption-key services;
• role-based internal access controls;
• separation of production and development environments;
• monitoring and audit logging; and
• additional protections for certain sensitive stored information.

No system can guarantee absolute security. Please contact us if you believe your OraOrb account or information may have been compromised.

8. Your Choices and Privacy Rights

Depending on the feature and your account, you may be able to:

• edit profile or personalization information;
• manage or unbind an OraOrb device;
• manage product settings;
• delete your account; and
• contact us to request access, correction, or deletion of personal information.

Depending on where you live, applicable privacy laws may provide additional rights regarding your personal information.

You may contact us at hi@roleage.ai to make a privacy request.

OraOrb does not currently provide an automated full-data export feature or a user-facing interface for reviewing and deleting individual long-term memory items.

9. Adults Only

OraOrb is intended for adults age 18 and older.

We do not knowingly design or market OraOrb for children. If we learn that information has been collected from a child in circumstances where applicable law requires deletion, we will take appropriate steps to remove it.

10. Changes to This Policy

We may update this Privacy Policy when the OraOrb product changes, our service providers change, or applicable legal requirements change.

When we update this policy, we will update the effective date above. Where appropriate or legally required, we may provide additional notice of material changes.

11. Contact

For questions about this Privacy Policy or privacy-related requests, contact: