Mira Privacy Policy

Who is responsible and what this covers

Mira is operated by Oleksandr Tokariev, who is the controller of application data. Contact alexdeveloper909@gmail.com. This policy covers the Mira mobile apps, backend service, and public website. Mira is intended for people aged 16 or older and is not directed to children.

Information Mira processes

Mira processes the Apple or Google identity you choose, profile and preference data, timezone and language, tasks, routines, reminder and follow-up state, temporary conversations, non-sensitive saved memories, short voice recordings and transcripts, device and push-registration data, subscription and usage state, support or privacy correspondence, crash and error reports from the apps, and privacy-bounded operational records.

Mira does not sell personal data, show advertising, or use app content for unrelated marketing. The public legal site uses no cookies, analytics, advertising, forms, or session replay.

Why information is used

Account, content, and device data are processed to provide the service you request: authentication, conversation, personalization, automatic memory when enabled, tasks, routines, reminders, follow-ups, Morning Brief, voice transcription, web research, subscription access, synchronization, support, and account or privacy requests.

Minimal operational data is processed for legitimate interests in security, abuse prevention, reliability, idempotency, diagnostics, and service improvement. Billing and rights records may also be processed to meet legal obligations. Where consent is required, such as an operating-system permission, it can be withdrawn through the device or app settings without affecting earlier lawful processing.

AI, research, stores, and service providers

Mira sends the conversation content and relevant permitted saved memories needed for an answer or action to OpenAI, which provides the AI model, agent runtime, transcription, and model-supported web research. Do not submit information you do not want processed for that request. AI output can be inaccurate; review important results.

AWS hosts application data in eu-west-1 (Ireland) and supplies authentication, storage, compute, queues, logs, and the CloudFront legal site. Apple or Google processes sign-in and push notifications when selected and operates the relevant app store. RevenueCat processes subscription entitlement and purchase-state data. Sentry receives crash and error reports from the mobile apps and stores them in its EU region (Germany); a report contains the error type and stack trace, app version and environment, device model, operating-system version, and performance timings for a sample of app sessions. Mira removes account identifiers, error messages, request details, and breadcrumbs before a report is sent and never attaches screenshots or screen content. These providers may process data in other countries under their applicable terms and transfer safeguards. No separate advertising or general-purpose analytics SDK is enabled for the initial release.

Push notifications are deliberately content-free: the message Mira sends through Apple or Google carries identifiers, an action key, and a deep link only, and your device composes the wording it shows. No task title, note, reminder wording, or conversation text passes through a push network.

Memory and your controls

When automatic memory is enabled, Mira may retain concise, non-sensitive communication preferences, reminder preferences, harmless user facts, and other information likely to help later conversations. Sensitive durable memory is outside the initial product scope. Relevant memories may be included in a later AI request.

In Settings you can disable automatic memory and inspect, edit, delete, or clear saved memories. New Chat deletes the current temporary conversation but not saved memories, tasks, or routines. Clear Memory deletes saved memories but not other account data. Delete Account starts deletion of the account and associated application data.

Retention and deletion

Tasks, routines, profile, preferences, and permitted memories remain while the account is active or until you delete them. Session messages, summaries, and content-bearing recovery data are retained for no more than 72 hours in normal operation. Voice audio is deleted promptly after successful transcription or a bounded retry; an S3 lifecycle rule is a fallback.

Operational and idempotency records expire according to bounded retry needs. Application logs are retained for 7 days in development and 30 days in production and are designed to exclude messages, transcripts, memories, task content, notification text, tokens, and secrets. Queue failure records and backups may persist for a limited technical period before expiry. Minimal billing, legal, security, support, and rights-request evidence may be retained where reasonably necessary or legally required.

A verified account-deletion request blocks new changes, cancels pending work, and removes the profile, tasks, routines, occurrences, memories, temporary sessions and audio, devices and push tokens, derived summaries, and permitted subscription metadata. Some content-free operational evidence or inaccessible backups may remain temporarily. Deleting a Mira account does not cancel an Apple App Store or Google Play subscription.

Your rights and choices

Depending on where you live, you may request access, correction, deletion, restriction, portability, or objection, and withdraw consent where processing relies on it. Contact alexdeveloper909@gmail.com or use the Privacy choices page. Proportionate identity verification may be required; never send a password, access token, conversation, task list, or memory content. You may complain to your local data-protection authority.

Security and changes

Mira uses scoped authentication, encryption in transit and at rest, private storage, least-privilege access, environment isolation, and content-minimizing telemetry. No online service can guarantee absolute security.

Material changes will receive a new effective date and immutable versioned URL. Separate notice or consent will be provided when required. Historical versions remain available.