Privacy Policy

1. Overview

This Privacy Policy explains how Project Aurora collects, uses, stores, and shares information when you use the Aurora website, mobile application, AI companion, media features, account features, and related services (collectively, the "Service").

Aurora includes live authenticated AI companion and Aurora Pro subscription features. Some other features may remain experimental or change over time. Please do not submit payment-card numbers, government identification numbers, protected health information, or other information that is not needed to use the Service.

2. Information We Collect

• Account and profile information, including your Aurora user ID, name, email address, profile image, Google sign-in identity, account status, and login timestamps.
• AI companion content, including your messages, Aurora responses, conversation and session identifiers, summaries, safety signals, remembered details derived from conversations, relationship and personality state, and related metadata.
• Voice information, including audio you choose to record and upload for transcription, the resulting transcript, and generated audio of Aurora responses.
• Content you choose to provide through supported features, such as a profile image.
• Service and diagnostic information, including request and error logs, timestamps, feature usage, model and provider usage, token or character counts, audio or file sizes, response latency, and subscription activation events.
• Subscription information, including your Aurora user ID as used with RevenueCat, Aurora Pro entitlement status, product and store identifiers, transaction identifiers, subscription environment, event type and time, and expiration time when provided.

3. Cookies and Device Storage

The website uses necessary cookies for authentication, administrator sessions, sign-in security state, and related security functions. It also stores a browser privacy selection so Aurora can honor the user's choices. These necessary functions remain available when optional storage is rejected.

With permission, the website uses local storage to remember nonessential interface preferences such as theme. Optional browser storage can be accepted, rejected, or changed through Privacy Choices. Aurora currently does not use optional browser analytics or optional browser-side Aurora personalization storage. These choices do not delete or control account, conversation, billing, or other records stored on Aurora's servers. The mobile application uses device secure storage for authentication credentials and pending sign-in state.

4. How We Use Information

• To create and authenticate accounts, maintain sessions, and display account and profile information.
• To provide AI conversations, conversation continuity, personalized companion behavior, transcription, and spoken responses.
• To provide media browsing and playback features and remember related activity where those features are used.
• To verify Aurora Pro access and process purchase, renewal, cancellation, expiration, restoration, and related entitlement events.
• To enforce access controls and rate limits, investigate errors, maintain security, prevent abuse, and operate and troubleshoot the Service.
• To comply with legal obligations and protect the rights, safety, and integrity of Aurora, its users, and others.

5. AI, Voice, and Third-Party Processing

Aurora sends conversation messages and relevant conversation context to OpenAI to generate companion responses and related summaries or memory candidates. When you use voice input, Aurora sends the uploaded audio to OpenAI for transcription. Aurora sends the text of Aurora's responses to ElevenLabs to generate spoken audio.

These providers process the information under their own terms and privacy practices. The repository does not establish provider-side retention periods or model-training settings, so Aurora does not promise that providers never retain or use submitted information. Do not include information you do not want processed in this way. AI output may be inaccurate, incomplete, or inappropriate for your situation.

6. Audio, Images, and Other Content

Audio uploaded for transcription is written to a temporary backend file, sent to OpenAI, and then removed from that temporary location after the request. Aurora stores the resulting transcript if you send it as a companion message. Generated response audio is stored in Google Cloud Storage and associated with your account, session, and message so it can be played through an authenticated endpoint.

Profile images submitted through the supported upload feature are also stored in Google Cloud Storage. The current mobile companion does not provide a general document-upload feature. Only provide content you have the right to use and share.

7. Storage, Security, and Retention

Account, conversation, memory, companion-state, usage, and entitlement records are stored in Aurora's PostgreSQL database. Generated audio and uploaded profile images are stored in Google Cloud Storage. The backend is configured to operate on Render. Aurora uses authenticated endpoints, authorization checks, rate limits, environment-managed secrets, and device secure storage for mobile credentials. No system is completely secure.

Aurora retains records while needed to operate and secure the Service and for legitimate recordkeeping purposes. The current implementation does not define a general retention schedule, a guaranteed deletion timeframe, or documented backup-deletion timing. Memory confidence may decay and low-confidence memories may be pruned, but this is not a substitute for account or data deletion.

8. Sharing and Service Providers

Aurora shares information with service providers as needed for the functions described above: Google for sign-in and cloud storage, OpenAI for AI and transcription, ElevenLabs for speech generation, Render for backend hosting, Stripe for web checkout and subscription administration, and Apple and RevenueCat for iOS purchases and subscription entitlement administration. Aurora may also disclose information when required by law or when reasonably necessary to protect the Service, users, or others.

The implementation does not include a feature for selling personal information or sharing it for cross-context behavioral advertising.

9. Subscriptions and Purchase Information

Stripe processes web checkout and payment details and provides Aurora with customer, subscription, and event information used to maintain web entitlements. Apple processes iOS purchases and handles store billing information. Aurora does not receive full payment-card details from Stripe or Apple. RevenueCat's software connects an iOS purchase to your Aurora user ID and reports subscription events to Aurora. Aurora's backend stores resulting entitlement and event records and makes the final access decision for Aurora Pro features.

Prices, billing periods, and any trial terms are shown in Apple's purchase flow using the current RevenueCat offering. Manage or cancel an iOS subscription through your Apple account's subscription settings. Deleting an Aurora account does not cancel an Apple subscription.

10. Your Choices and Requests

Depending on where you live, you may have rights to request access, correction, deletion, or restriction of certain personal information. Contact roubideauxchristian@gmail.com to make a privacy request.

The mobile Account screen includes a Delete Account control. It disables the account, records the deletion request time, and signs the device out; it does not currently erase every retained conversation, memory, generated audio file, profile image, usage record, subscription record, or provider-held copy. Contact the address above if you also want to request deletion of retained data. No specific completion timeframe is promised.

11. Children's Privacy

The Service is not intended for children under 13 years old. Aurora does not knowingly collect personal information from children under 13. If you believe a child under 13 has provided personal information, contact us at the address below.

12. Experimental Features

Some Aurora features, content, or interfaces may be experimental, incomplete, or changed or removed. This does not mean that authenticated companion processing or Apple subscription purchases are simulated.

13. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we do, we will update the Effective Date above. Material changes may require additional notice where required.

14. Contact

For questions about this Privacy Policy or your information, contact Christian Roubideaux at roubideauxchristian@gmail.com.