Miri privacy policy
For the app Miri (Miri Next). Effective 22 October 2026.
Who we are and what this covers
This policy explains what the Miri Next app ("Miri") reads, sends and keeps, and the choices you have. It is published by Dominapp Technologies ("we"), the developer of Miri. Contact: [email protected].
It covers:
- Miri Next on Google Play (package
dominapp.number.next). Conversations run on the Miri server. Accessibility is used only to send WhatsApp messages you approve. - Miri Next from our website. The same app with more features: it can also operate other apps on the screen, read Gmail, send SMS and read the call log. Where the two differ, this policy says so.
- The Miri server, which carries your conversations to the AI model when you use the Miri server route, and keeps your account, usage and subscription.
Miri is an AI assistant. It acts on your phone only when you ask it to, and we never sell your information or show ads.
Information Miri handles on your phone
Miri reads phone data only to carry out a request you made, and keeps what it stores in the app's private storage. Android backup is turned off for the app.
| Information | When Miri uses it | Kept on the phone |
|---|---|---|
| Google account (name, email, account ID) | Sign-in, required to use Miri | Yes, until you sign out |
| Chats, and the photos and files you attach | Every conversation | Yes, until you delete the chat |
| Personal memory (preferences, saved places, usual contacts) | To avoid asking you again | Yes; you can view, delete or pause it |
| Contacts | When you ask to call or message someone | No; matches are looked up each time |
| Calendar | When you ask about or add events and reminders | No copy |
| Photos | When you ask to send a photo. Google Play build: you choose it in Android's photo picker, and Miri receives only that photo. Website build: recent photos are listed by date and size, and image content is used only for a photo you choose | A photo you picked, for up to a day so it can be sent |
| Microphone | Voice conversations, dictation, and "Hey Miri" if you turn it on | No recordings |
| Location | When you ask for something nearby, for the weather where you are, or set up a place-based automation | Saved places only |
| Installed apps | When you ask to open an app; Miri looks up the apps you can open on the phone | No copy |
| Notifications | When you ask what you missed or to reply (see below) | No copy |
| Paired Bluetooth devices | To start drive mode when you pick your car | The car you picked |
Miri also keeps, on the phone, a record of the actions it carried out (for example whom it called or messaged and the text), so it never repeats an action by mistake.
"Hey Miri" is detected on the phone; no audio leaves the phone for it. Dictation uses your phone's speech recognizer (usually Google's), under its own terms.
The website build also reads the call log and sends SMS when you ask. The Google Play build does neither.
Accessibility service and notification access
Both are off until you turn them on in Android settings, and Miri explains what they do and asks for your agreement before it sends you there.
Accessibility in the Google Play build is used for one thing: sending a WhatsApp message you approved, hands-free.
- What it sees: only WhatsApp and WhatsApp Business, and only while it sends a message you approved. It sees no other app.
- What it does: fills in the exact message you approved and taps Send. It sends nothing without your approval in the conversation, and never during an automation that runs while you are not there.
- What leaves the phone: when WhatsApp shows several matching chats, their names go to the AI model so it can pick the one you meant. Screen content is not stored; the record of a sent message keeps the recipient and the text.
Accessibility in the website build can also read and operate other apps for a task you asked for. While that task runs, the text on the screen, and a screenshot when needed, goes to the AI model to decide the next step. Between tasks it reads nothing, and screenshots are not kept. Miri may remember the steps a task took in an app so it can repeat them; you can pause this in Settings.
Notification access lets Miri read your current notifications and reply to a message from them, only when you ask. The notifications you ask about go to the AI model to summarize or answer; Miri does not keep a copy. A reply is sent only after you approve its exact text.
You can turn either one off at any time in Android Settings. If you decline Miri's explanation while Accessibility is already on, Miri turns it off.
What leaves the phone and who receives it
Your conversations go to the AI model through the Miri server. We do not sell your data or use it for advertising. We use Firebase Crashlytics to diagnose crashes and app stability problems, as described below.
| Recipient | What it receives | Why |
|---|---|---|
| Miri server (operated by us) | Your messages and the files and photos you attach; the results of the phone actions in the conversation (for example the contacts or installed apps that matched a name, or notifications you asked about); your saved memory relevant to the chat; your Google account ID, name and email; your phone's Android ID and Firebase push token; technical usage and setup information; your Google Play purchases of Miri plans | To run the conversation, apply your plan and its limits, give the free allowance once per phone, keep your account and send relevant Miri updates |
| OpenAI (the AI model) | What the Miri server forwards for each conversation; voice conversation audio, streamed from the phone straight to OpenAI | To understand your request and answer it |
| Your Google sign-in (Firebase Authentication); payment for a plan (Google Play); location requests through Google Play services; dictation audio through the phone's speech recognizer | Sign-in, payment, location, dictation | |
| Google Firebase Crashlytics | Crash and ANR stack traces, app and device details, installation and session identifiers, and limited technical state | To diagnose crashes, measure app stability and fix bugs |
| Open-Meteo (weather forecasts) | When you ask about the weather: an approximate point (rounded to about a kilometre) for the place you asked about, with no account or other personal data | To get the forecast |
| The app you choose (WhatsApp, Maps, Waze, YouTube, Spotify, your phone or messaging app) | Only what that action needs: a recipient and message, a destination, a search | To hand the action to that app |
The AI model may search the web to answer a question; the search terms come from your request, not from your personal data. OpenAI processes data under its own terms and privacy policy; Google under its privacy policy.
Technical usage and Miri notifications
The Miri server keeps technical usage records: model and tool names, outcomes, counts and timings, voice connection and error categories, and the app version. It also receives limited setup information such as permission states, whether Accessibility is connected, voice and drive settings, and the number of memory items. These records help us understand reliability and improve Miri; they contain no chat text, tool arguments, tool output or audio.
Miri uses Firebase Cloud Messaging to deliver its own notifications. The server keeps the push token for your account and phone and can select relevant Miri updates based on usage and setup information. You can disable these notifications in Android Settings. Merely receiving a notification does not open another app or website; tapping its link opens Chrome.
Crash and stability reports
The Google Play and website release builds automatically send crash and application-not-responding (ANR) reports to Google Firebase Crashlytics. Reports contain stack traces, exception classes, app version and build channel, device model and Android version, available memory and storage, and installation identifiers. Firebase Sessions also sends app-start session events for crash-free statistics. There is currently no in-app switch to disable this collection.
Miri adds only the build channel, server/local route, whether voice is active and whether Accessibility is connected. It does not attach your name, email, Firebase account ID, chat text, contacts, tool arguments, personal memory or audio, and writes no custom Crashlytics logs. Exception messages are removed from crash reports because they can contain user content. No Firebase Analytics SDK or Analytics breadcrumbs are included.
Google processes these reports for us. Firebase retains crash stack traces and associated installation identifiers for 90 days before starting removal from live and backup systems. See Firebase privacy and security.
Plans and purchases
Miri plans are sold as Google Play subscriptions, in both builds. Google Play takes the payment; we never see your card or payment details.
- What the Miri server keeps about a purchase: the plan and its billing period, Google's purchase token and order ID, when it started and when it renews or ends, whether it renews automatically, and whether it was a test purchase.
- How a purchase is tied to you: the app gives Google Play a one-way code made from your Miri account ID, not your name or email. The Miri server checks each purchase with Google before it applies the plan, and asks Google again when a subscription renews, changes or ends.
- Usage and limits: each plan, including the free allowance, has usage limits. The server counts your usage against them and shows it in the app as a percentage.
- Free allowance once per phone: the free allowance is given once per phone, not once per Google account. To check this, the app sends the Miri server your phone's Android ID, an identifier Android gives Miri on your phone that other apps cannot see. The server does not store the ID itself, only a one-way code made from it with a secret key, when the phone received the free allowance and which Miri account received it. We use it only for this, never for advertising or tracking.
Deleting your Miri account does not cancel a subscription. Cancel it in Google Play → Payments and subscriptions, or from Miri's Settings, which opens that page.
Storage, retention and security
Your chats live on your phone; the Miri server deletes a conversation 7 days after it was last used.
| Where | What | How long |
|---|---|---|
| Your phone | Chats, attachments, personal memory, settings | Until you delete them or uninstall Miri |
| Miri server | Conversation threads and the files you attached | Deleted 7 days after the last change; temporary files after 1 day |
| Miri server | Technical logs of the AI engine | 10 days |
| Google Firebase Crashlytics | Crash stack traces and associated installation identifiers | 90 days before removal from live and backup systems begins |
| Miri server | Your account: Google account ID, email, name, sign-in method | Until you ask us to delete your account |
| Miri server | Technical usage and setup records, Firebase push tokens and notification delivery records | Until you ask us to delete your account; invalid push tokens are removed |
| Miri server | Your plan and your Google Play purchases of it | Until you ask us to delete your account |
| Miri server | A one-way code of your phone's Android ID, and when and to which account it gave the free allowance | While Miri offers a free allowance. If you delete your account, it is kept without any link to you, so the allowance is not given again on that phone |
Usage records hold no message text, audio, tool arguments or output, or IP address. If you return to a chat after the server deleted it, Miri continues from the copy on your phone.
The Miri server runs in a data center in the Netherlands (European Union). OpenAI processes conversations in the United States, and Google in its own data centers around the world. Traffic between the phone and the server is encrypted (TLS, with the server's certificate pinned in the app). Each connection must carry a valid Google sign-in token, and each user's conversations and files are kept in a separate workspace that other users cannot reach.
Your choices
Every permission is optional except Google sign-in, and you can delete your data on the phone or ask us to delete it on the server.
- Permissions: grant or revoke contacts, calendar, photos, microphone, location, notifications, notification access and Accessibility in Android Settings at any time. Miri keeps working without them; only the matching features stop.
- Personal memory: view what Miri remembers, delete single items, or pause learning in Settings.
- Earlier chats: turn off Miri's use of earlier chats in Settings, or delete a chat from the chat list.
- Sign out: in Settings. This ends the server connection; your chats stay on the phone.
- Delete everything on the phone: uninstall Miri, or clear its storage in Android Settings.
- Delete your account and server data: in Miri, Settings → Account → Delete account, or by email as described on Delete your Miri account. Within 30 days we delete your account, your usage and purchase records, and any conversations and files still on the Miri server. We keep only the one-way code of your phone, without any link to you, so the free allowance is not given again on that phone.
Depending on where you live, you may also have the right to access, correct or export your data, or to object to its use. Write to [email protected] and we will answer within 30 days.
Children, changes and contact
- Children: Miri is intended for users aged 16 and over, and we do not knowingly collect information from children. If you believe a child uses Miri, write to us and we will delete the account.
- Changes: when this policy changes, we update the date at the top. If a change affects what Miri reads, sends or keeps, the app asks for your agreement again before using that permission.
- Contact: Dominapp Technologies, [email protected].