Privacy Policy
Last updated: August 24, 2026
Information we process
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.
Interest personalization
After registration, you may optionally choose up to five interests from Miora's fixed list: Everyday life, Travel, Food & dining, Work & career, School & study, Movies & TV, Music, Gaming, Technology, Sports & fitness, Culture, and Social life. Miora stores the corresponding stable category keys with your account, not free-form interest text, and uses them only to personalize English Talk prompts and Practice topic recommendations. You can skip this step and change or clear your choices later in Settings. Skipping does not restrict core features, open a paywall, or change voice quotas.
Interest-preference logging and analytics, when present, are limited to selected stable category keys and content-free operational state; they do not include full conversation text, transcripts, or audio. The interest-preference system does not infer or store unselected interests from full conversations. Miora does not sell these choices or use them for advertising or tracking. Account deletion removes the selected keys when Miora deletes your user profile, subject to the general retention terms below.
Voice and AI processing
Miora uses Alibaba Cloud Model Studio (Qwen and DashScope) for AI conversation generation, speech recognition, speech synthesis, realtime voice processing, and HTTP fallback processing. Depending on the feature, Miora sends typed conversation content, voice audio, transcripts, relevant conversation context, learning preferences or memories, AI-generated response text for speech synthesis, and necessary pseudonymous request identifiers. Miora does not send your Clerk account identifier merely to generate an AI response. Do not submit confidential or sensitive personal information that is unnecessary for practice.
Before the first such transfer, Miora identifies this provider and data scope and offers two choices with nothing preselected: “Agree and Continue” and “Not Now.” Choosing Not Now leaves non-AI account, settings, and legal functions available. You can agree later in Settings. You can also withdraw consent there at any time; withdrawal immediately blocks future Miora AI and voice requests. A material provider or data-scope change requires a new policy version and new consent. Microphone permission is a separate system permission and is not consent to third-party AI sharing.
How we use information
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.
Service providers
Clerk provides authentication; Vercel provides application hosting, functions, logs, and private object storage; Neon provides PostgreSQL storage; Alibaba Cloud Model Studio (Qwen and DashScope) provides the AI and speech processing described above; and Apple provides Sign in with Apple and App Store subscription processing. Miora shares only what is needed for each service and requires providers to protect it consistently with their applicable terms, agreements, and law. Miora does not sell personal data or share it for cross-app advertising or tracking.
What is retained and where
- Miora: account preferences and saved conversation, transcript, correction, report, review, and learning-memory records remain in Miora's database while needed to provide the account, until deletion or the retention rules below apply.
- Live audio: Miora does not persist raw microphone audio or generated speech audio in its application database. The bytes are processed in memory, in transit, and in temporary local playback or request storage only as needed to complete the live request; the resulting transcript or response may be saved as conversation content.
- Clerk: account and external sign-in records are retained under the authentication service until the Clerk identity is deleted, subject to its legal and security obligations.
- Alibaba Cloud: the provider processes the submitted AI and speech data. Its current documentation says model-call data is not used for model training, but Miora does not claim a fixed retention period for Alibaba Cloud because the applicable account, region, logging, and contract evidence has not established one.
- Infrastructure: Vercel and Neon may retain encrypted backups, security logs, and operational records under their configured retention and contractual terms. Application logs are designed to contain request correlation and timing data rather than raw conversation or credential content.
Withdrawing AI consent prevents future transfers; it does not by itself erase information already retained by Miora or a provider. Delete your account or contact support to request deletion, subject to legal retention and provider processing already completed.
Apple subscriptions and billing records
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.
Uploaded files
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.
Retention and deletion
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 that provider-processed audio is immediately deleted or excluded from collection without provider evidence. You may contact support for help.
Contact
Privacy questions and deletion requests: hxdhzx@gmail.com