Privacy Policy

1. Information stored on your device

Alasia stores your conversation history and personalization information in the app's local storage on your device. Depending on how you use Alasia, this may include your messages or voice transcripts, Alasia's responses, Moments, memories, patterns, rejected interpretations, personalization information, interests or focus areas, preferences, and learning controls.

App preferences such as conversation mode, voice settings, appearance, text size, and related settings are also stored locally.

2. Information processed to provide AI responses

When you ask Alasia for an AI response, Alasia sends information needed to fulfill that request to Alasia's backend infrastructure. Depending on the request, this may include your current input and selected relevant conversation context, memories, user-declared context, confirmed or inferred patterns, and rejected interpretations.

Alasia's backend sends the information required for AI generation to OpenAI's API. Alasia's current text-generation implementation uses OpenAI's Responses API with storage disabled for the response request.

OpenAI may independently process and temporarily retain API data under its applicable API data policies, including for abuse monitoring and service security. OpenAI states that API data is not used to train its models by default unless the API customer opts in.

3. Voice and speech processing

If you use voice input, microphone audio is provided to Apple's Speech framework for speech recognition. Alasia does not require speech recognition to occur exclusively on-device, so speech recognition may involve processing by Apple depending on device and system behavior.

Alasia's code does not persist raw microphone recordings.

If neural voice responses are enabled, portions of Alasia's response text are sent through Alasia's backend to OpenAI's speech service to generate audio. Generated neural audio is streamed or temporarily buffered for playback and is not persistently stored by Alasia's implementation.

4. Alasia backend storage

Alasia's backend is designed not to persist your prompts, conversation transcripts, AI response text, memories, patterns, or speech text.

The backend does retain content-free operational information needed to operate and protect the service. This can include anonymous install and security identifiers or hashes, App Attest validation information, request and turn identifiers, usage counters, speech character counts, service-performance information, token or cost telemetry, and related timestamps.

5. Subscriptions and usage information

If you start a trial or purchase a subscription, Alasia processes information needed to verify entitlement and enforce the applicable usage allowance. This may include Apple transaction identifiers, an anonymous app account token, product and plan identifiers, entitlement status, trial status, subscription-period dates, AI and voice usage counts, counted turn identifiers, and associated anonymous install identifiers.

Conversation text, transcripts, memories, patterns, Insights, AI responses, and speech text are not stored in Alasia's subscription usage records.

Purchases are processed by Apple through the App Store. Apple's handling of purchase and account information is governed by Apple's own terms and privacy practices.

6. Service providers

Alasia currently relies on service providers to deliver core functionality, including:

• Apple for App Store purchases, StoreKit subscription functionality, App Attest, and Apple speech-related services used by the app.
• Cloudflare for Alasia's backend infrastructure, security, routing, and operational services.
• OpenAI for AI response generation and neural speech generation.

These providers may process technical or request information necessary to provide their respective services and may maintain their own operational or security logs under their applicable policies.

7. Advertising, tracking, analytics, and location

The current Alasia application does not include advertising SDKs, third-party analytics SDKs, App Tracking Transparency tracking, IDFA-based advertising tracking, or location collection. Alasia's backend may maintain operational logs and telemetry necessary for security, reliability, usage enforcement, and service-cost monitoring.

8. Your controls

Alasia provides controls that allow you to manage information stored by the app. Depending on the feature, you can delete individual memories, clear memories, delete individual patterns, clear learned patterns, clear conversations and Moments, and export your Alasia data to a human-readable file using the iOS share sheet.

Deleting a memory or pattern does not necessarily delete the source conversation from which it was learned. Clearing conversations removes locally stored conversation transcripts, Moments, and the active conversation and removes associated conversation or Moment references from learned state.

9. Accounts and device identity

Alasia does not currently require you to create an Alasia account or sign in. The app uses anonymous technical identifiers for security and subscription functionality, including App Attest/install credentials and a StoreKit app account token. Certain identifiers are stored in the device Keychain. Alasia does not currently provide cross-device synchronization of conversation or learned-content data.

10. Data retention

Locally stored Alasia content remains on your device until it is removed through available app controls, the app's storage is otherwise removed, or applicable system behavior removes it.

Alasia's backend retains content-free operational, security, usage, telemetry, and subscription records as necessary to provide, secure, administer, and account for the service. Third-party service providers may retain information according to their own policies and applicable law.

11. Security

Alasia uses technical measures intended to protect access to its backend, including Apple's App Attest architecture and server-side validation. No method of electronic processing, transmission, or storage can be guaranteed to be completely secure.

12. Children's privacy

Alasia is not intended to be used in violation of applicable age requirements for the App Store or applicable law. If we learn that information has been processed in a manner requiring deletion under applicable children's privacy law, we will take appropriate steps consistent with our legal obligations.

13. Changes to this policy

We may update this Privacy Policy as Alasia changes. When we make material changes, we will update this page and revise the effective date where appropriate.

14. Contact

Alasia is operated by Jennifer L. Warren. For privacy questions or support, contact support@alasia.app.