ARIEXO

Status: Draft · Effective date: [PLACEHOLDER: EFFECTIVE_DATE]

Privacy Notice

Proposed operator: [PLACEHOLDER: OPERATOR_LEGAL_NAME_AND_ENTITY]. This draft does not identify the legal Data Fiduciary or establish who controls the service.

Information used by the service

How information is used and stored

We use this information to create and secure accounts, display profiles and content according to your visibility settings, provide discovery and creator features, prevent abuse, and respond to support requests. Ariexo uses Firebase for authentication and database services and Cloudflare for site delivery and image storage. Google processes information if you choose Google sign-in and, when enabled, receives the limited Live Room prompt context described above through the Gemini API. These providers process information as part of delivering their services and under their own terms and privacy notices.

Previously submitted voice content is stored in private object storage and may be processed by Cloudflare Workers AI to transcribe speech and translate transcripts. Google Cloud Text-to-Speech receives translated text only when translated speech is requested; it generates a standard synthetic voice and does not imitate the creator. Transcripts, translated captions, and generated speech are cached for reuse. The original recording is kept separately from generated speech and is not replaced. The website currently provides no voice recording or playback controls.

Some pages also load fonts from Google Fonts, the Tailwind CSS browser script from its CDN, and Firebase JavaScript modules from Google's hosting service. When a browser requests these resources, the relevant provider may receive the request's IP address and standard request metadata. The date of birth entered for age eligibility is sent to Ariexo's hosting provider to process the request; the application stores the calculated age rather than the date of birth.

Public profiles and content marked public can be viewed by other people. Content marked private is restricted by Ariexo's access controls to the account that owns it. Do not mark content public unless you are comfortable sharing it publicly.

Ariexo and its providers may use browser storage to preserve your sign-in state and temporary in-session features such as a Visual Trail. Uploaded image files may contain embedded metadata. Existing recordings may include sensitive spoken information and remain subject to the retention practices described below.

Cookies and browser storage

See our Cookie Policy for what we store and how to control it.

When you dismiss the storage notice, Ariexo stores a first-party preference cookie named __Host-ariexo-storage-notice for up to 180 days. Its value is a version marker, not an account identifier or authentication token. If cookies are unavailable, the notice uses local storage for the same preference and duration. You can clear this preference in your browser settings.

Ariexo and its providers use cookies and similar browser storage that are needed to run the service: keeping you signed in (Firebase authentication), completing the Cloudflare Turnstile "I'm not a robot" check that protects sign-in and sign-up from bots, and storing an anonymous viewer identifier and your choice about this notice. We do not use this storage for advertising. You can clear it in your browser settings, but you may then be signed out and asked to repeat security checks. The exact list of cookies and storage keys, and their lifetimes, is [DECISION REQUIRED] and must be confirmed before publication.

Retention and your choices

Existing voice content follows the voice-specific application retention period: 24 hours for Live Room voice messages and the lifetime of the photo for photo voice stories. Room audio objects are also subject to the Cloudflare R2 lifecycle rule documented in docs/voice-system.md; physical object removal may occur after the API has stopped serving the expired message. Other data classes, backups, legal holds, and provider retention remain part of the broader retention schedule: [DECISION REQUIRED]. A support contact and tracked privacy-request process must be verified before publication.

Children

The current code permits accounts from age 16, so it does not exclude all people under 18. The minimum age, age assurance, parental-consent arrangements and child-safety escalation remain [DECISION REQUIRED] and require review by the adult operator and qualified Indian counsel. No parental-consent workflow was found in the repository.

Changes to this notice

We may update this notice as the service changes. We will post the current version here and update the date above.

Privacy contact

[PLACEHOLDER: VERIFIED PRIVACY CONTACT AND REQUEST ROUTE]

Terms of Service · Community Guidelines · Cookie Policy · Support · Accessibility Statement