Privacy Policy

Miora processes account identifiers and profile settings; text you submit; conversation messages, corrections, reports, and review records; subscription and usage status; and technical information needed to operate and secure the service. Clerk handles authentication. Miora stores its internal user profile and learning data in PostgreSQL.

When you use voice features, your audio is sent to the configured speech-recognition provider for transcription. Your prompts, transcripts, and relevant conversation context may be sent to configured AI and speech providers to generate replies, corrections, reports, and spoken audio. These providers process data under their own service terms. Do not submit confidential or sensitive personal information that is unnecessary for practice.

We use information to authenticate users, provide and personalize speaking practice, remember learning progress, generate AI features, enforce usage limits, maintain security, troubleshoot failures, and support account requests. We do not use one user's identity to grant access to another user's private learning data.

Miora relies on service providers for authentication, hosting, PostgreSQL storage, file storage, Apple subscription processing when offered, and AI, speech-to-text, and text-to-speech processing. We share only the information needed for those services to operate.

To verify and restore Apple subscriptions, Miora sends your authenticated Miora UUID to StoreKit as an appAccountToken. Miora processes normalized transaction and original transaction identifiers, product and subscription status, relevant dates, App Store notification identifiers, and SHA-256 account-token or payload hashes. Apple handles your full payment details. Miora does not routinely log or retain a raw signed transaction JWS or raw signed App Store notification payload.

Files you upload for learning materials, character images, or Character Studio are stored in private object storage. Miora serves them through authenticated application routes rather than exposing storage credentials or direct storage links. Character images may be visible to other signed-in users when you publish or share a character.

Account and learning data are retained while your account is active and as reasonably needed to operate the service, resolve security or billing issues, and meet legal obligations. When you delete an uploaded material or replace a character image through a supported product action, its stored file is queued for deletion. Account deletion removes your Miora profile, sessions, messages, corrections, reports, learning and review records, and Clerk identity, and queues associated uploaded files for deletion. Storage outages can delay file removal, so Miora retains a server-side deletion task that can be retried. During that retry period the account remains deleted and revoked sessions are not restored. Normalized billing records needed for fraud prevention, accounting, and legal obligations are retained for seven calendar years after the later of final transaction activity, entitlement expiration or grace-period closure, or revocation. Their link to your Miora profile is detached so they are no longer linked to your deleted Miora user ID. Original transaction identifiers and hashes remain reserved to prevent an Apple subscription from being transferred to a different or post-deletion Miora account. We do not claim a fixed retention period for third-party AI or speech providers. You may contact support for help.

Privacy questions and deletion requests: hxdhzx@gmail.com