Effective July 27, 2026

Privacy Policy

This policy explains what Mirai processes, where conversation history lives, and when service providers receive data.

1. Scope and controller

This Privacy Policy applies to the Mirai website, browser chat, API, accounts, payments, monthly plans, and unrestricted access requests. satuapps is responsible for the product level processing described here.

Questions, access requests, and deletion requests can be sent to hi@satuapps.com.

2. Account and authentication data

When you sign in, we process your phone number, account identifier, account creation and last sign in times, account status, and quota settings. Raw account session tokens and account generated API keys are not stored in the product database; cryptographic hashes are stored where authentication requires them.

For verification and abuse prevention, we also process OTP session identifiers, delivery attempts, phone numbers, IP addresses, timestamps, and failed verification counts.

3. Guest and device data

Guests receive a random browser identifier. We also process IP based daily usage counters and a browser fingerprint that is hashed in the browser and hashed again on the server.

The guest identifier and hashed fingerprint usage counters are retained to enforce the lifetime free trial and prevent repeated resets. IP usage counters are separated by day. A browser cannot provide a MAC address, and Mirai does not collect one.

4. Prompts, files, and conversation history

Conversation history is stored in your browser local storage by default. It remains there until you delete it, clear site data, or the browser removes it. You can export that local history from Settings.

When you send a request, the prompt, relevant conversation context, and attached images are transmitted to Mirai and to selected inference providers so a response can be generated. Mirai does not keep a server side copy of your complete conversation history by default.

For paid API usage, the billing ledger retains the request identifier, public Mirai model, token counts, and charged amount. Monthly plans and free access retain token or quota counters needed to enforce their limits. Operational logs may also contain errors or security events. Do not submit secrets or personal data that are not needed for the task.

5. Payments and subscriptions

We process order identifiers, account identifiers, plan, amount, currency conversion, payment status, external reference, timestamps, and payment errors. Duitku processes the payment flow and may collect additional payment information under its own privacy terms.

Mirai does not store full card or bank credentials.

6. Unrestricted access requests

If you request an unrestricted profile, we store the submitted name, age, organization, intended use, submission time, review status, reviewer, and approval time.

We use this information to assess authorization, accountability, and the appropriate security profile.

7. Why we process data

We process data to authenticate users, provide model responses, preserve local chat functionality, measure usage, manage plans and credit, process payments, prevent fraud and trial resets, investigate incidents, enforce policies, and comply with law.

Where consent is required, you may withdraw it. Other processing may be necessary to perform a contract, protect the service, or meet legal obligations.

8. Service providers and international processing

We share only the data needed with categories of providers that support inference, hosting, network delivery, OTP or WhatsApp verification, payment, and operational security. Prompts and files may be processed outside your country.

Exact inference routing is proprietary, but that does not remove our privacy obligation to disclose provider categories. Additional subprocessor information may be provided for enterprise review or where required by law.

9. Training and model improvement

satuapps does not currently use your browser conversation history to train a separate Mirai foundation model. Requests are processed to generate responses, operate the service, and enforce security.

Inference providers may retain or use submitted data according to their own terms and the settings available to satuapps. Do not submit highly sensitive data unless your written plan or agreement provides handling suitable for that data.

10. Retention, security, and your choices

We retain account, payment, billing, security review, and audit records only as long as needed for the purposes above, dispute handling, fraud prevention, accounting, and legal duties. Expired sessions are removed when checked; some append only financial records are retained for integrity.

You can clear local conversations, keys, and tokens through the browser or product controls. You may request access, correction, export, objection, or deletion by contacting hi@satuapps.com. We may need to verify your identity and may retain records that law or legitimate security and accounting needs require.

We use access controls, hashed credentials, scoped administration, and operational monitoring, but no system can guarantee absolute security.

11. Children and policy changes

Mirai is not intended for people under 18. We may update this policy as data flows, providers, or legal requirements change. The effective date will be updated when we do.