Mira for Android
Mira Privacy Policy
Effective September 2, 2026. Mira is published on Google Play by Earl Co and is powered by TEKIZ.AI. This policy explains how the Mira Android app accesses, stores, transmits, protects, retains, and deletes user data.
Local by default
Mira stores conversations, tasks, memory, settings, authorization records, recovery records, and security receipts in encrypted app storage on the Android device. Mira sends content off the device only when a feature requires it and the app presents the applicable disclosure or user action.
Data Mira accesses and stores on the device
- Conversation messages, tasks, saved memory, preferences, and local inference history.
- Device authorization, cryptographic identity, disclosure approvals, inference receipts, and recovery records.
- User-created encrypted Mira export packages when the user explicitly chooses where to save or import them through Android's system document picker.
- Bounded operational events with event names, timestamps, and categorical outcomes. These local events exclude prompts, responses, memory text, credentials, and free-form identifiers.
Android permissions
- Internet: reaches approved TEKIZ.AI services for optional authorization and remote inference.
- Hide overlay windows: blocks third-party overlays from sensitive Mira screens on supported Android versions.
- Biometric compatibility: supports device authentication through Android's biometric system. Mira does not receive or store biometric data.
Mira does not request camera, microphone, notification, location, contacts, advertising ID, broad storage, or system-settings permission.
Optional TEKIZ.AI processing
A user-approved remote inference request can send the approved message and selected
saved context to api.tekiz.ai over HTTPS.
TEKIZ.AI may send that approved request to the configured model provider that
performs the inference. The response returns to Mira and is stored in encrypted
app storage. The selected provider may process or retain request data under its
own terms and privacy policy.
Optional device enrollment can send an email address, a device public signing identity, authorization metadata, and security receipts to TEKIZ.AI. API-key compatibility mode sends the configured TEKIZ API key as an HTTPS authorization credential. Mira keeps the stored key inside its protected device-vault boundary.
Hosted operational data
TEKIZ.AI may retain account or authorization identifiers, API-key metadata, usage counters, selected provider and model, request status, timing, error category, estimated token counts, and security records for service operation, quota enforcement, abuse prevention, reliability, support, and legal obligations. TEKIZ.AI launch analytics exclude prompt text, message bodies, raw model responses, provider credentials, sign-in tokens, and plain-text API keys.
When a user reports an AI-generated response, Mira sends the selected report category, a one-way response digest, an opaque local message reference, app version, an optional route-receipt reference, and any optional note the user enters. Mira does not include the response or prompt text in a report.
Parties that process data
Earl Co and TEKIZ.AI operate Mira. TEKIZ.AI uses infrastructure providers such as Cloudflare and Google Cloud to deliver and protect hosted services. A configured model provider processes an approved remote inference request. Android and Google Play provide operating-system services, app distribution, device authentication, and the system document picker. Each provider handles data under its applicable terms and privacy policy.
Security
Mira uses encrypted Android app storage, Android Keystore-backed device identity, HTTPS for remote traffic, a cleartext-traffic prohibition, bounded message validation, explicit disclosure review, and signed authorization and receipt checks where the production route provides them. Users remain responsible for protecting their Android device, recovery material, and any API key they add.
Retention and deletion
Local records remain on the device until the user forgets or replaces them, clears the app's storage, or uninstalls Mira. User-created exports remain wherever the user saved them. Hosted operational and authorization records remain only as long as needed for service operation, security, abuse prevention, support, accounting, or legal obligations. A model provider's retention period is governed by that provider's terms and the configured service relationship.
Request account and hosted-data deletion
To request deletion of a Mira or TEKIZ.AI account and its associated hosted user data, email support@tekiz.ai with the subject “Mira account and data deletion request.” Include the account email and do not include prompts, model responses, API keys, recovery codes, or other secrets. We may retain records required for security, fraud prevention, accounting, dispute resolution, or law and will explain any applicable retention in the response.
Children
Mira is not directed to children. The planned Google Play audience is adults, and the app is not designed for use by anyone under 18.
Changes and contact
We will update this page when Mira's material data practices change. Privacy and deletion questions can be sent to support@tekiz.ai.