Verify

Don't take our word for it.

Both Mirage Atlas and Mirage Lumen run inference on your device. Your questions, audio, notes, and pulls are processed locally and never sent to us. This page names every connection the apps make, and the tools to confirm it yourself.

Mirage Atlas — the network, in full

In the current release build, Atlas contacts exactly one host, for two things.

Model manifest — automatic, at most once a day. When you reach the model step (and no more than once every 24 hours after), Atlas fetches a small file — about a kilobyte — from our Cloudflare R2 bucket at pub-f07e1612d57d476faf5948b53fcf3764.r2.dev, so it knows which model fits your device. It sends standard HTTP cache headers and nothing else: no account, no device ID, no install ID. Cloudflare necessarily sees your IP, as with any download.
Model download — only when you tap it. The model weights (a multi-gigabyte file) download from the same bucket only when you tap Download now. Resuming a download sends a byte offset, nothing more.

That is the complete list. Game data ships inside the app and updates only when you update the app through the store — there is no other endpoint.

In the binary, switched off

Several SDKs are compiled into the app for planned future features — analytics (PostHog), crash reporting (Sentry), subscriptions (RevenueCat), ads (AdMob), and Google Drive sync. In the current build each is held off by a compile-time flag and a placeholder key, so none can initialise or transmit. You can read this in the source: feature_flags.dart, telemetry_config.dart, subscription_config.dart, ads_config.dart.

Crash reports: none are sent in this version. Crash details are written to a local log on your device only.

The honest asterisk

The ad SDK is still compiled into the Android build. Because of that, the release app requests Android's advertising-ID and Ad-Services permissions — added by Google's library, not by our code — and we have not yet set the flag that delays Google's app-measurement at startup. We have not confirmed by packet capture that nothing reaches Google at launch. So we do not claim "zero third-party contact": only that no ad is ever requested or shown, and we have never enabled measurement. We are removing the ad SDK from the build; this note goes when it does.

Mirage Lumen (in development)

Not shipped. By design, dictation audio and text are processed on the device, and the app makes no network calls of its own. The full connection list will be published here before the first install.

What the studio itself holds — waitlist emails, website analytics — is a separate, shorter list. See "Everything we hold" in the privacy policy.

How to check it yourself

Pick whichever tool matches the device you're testing on. Each one shows you, at a different layer, what the app is actually doing on the network.

Airplane mode. The simplest test. Once the model is downloaded, launch the app in airplane mode. If a feature works, it isn't using the network.
Little Snitch (macOS) or LuLu (macOS, free). Mirror your phone or run the app under emulation; both block outbound connections by default and prompt you for each.
Wireshark + a local network bridge. Put your phone on a Wi-Fi network you control; capture all traffic from your phone's IP while you use the app.
mitmproxy. Trust mitmproxy's CA on the device, route through it, and inspect everything the app sends — TLS contents and all.
iOS & Android system tools. On iOS, Settings → Cellular → scroll to per-app data usage. On Android, Settings → Network & internet → Data usage by app. Coarse, but a quick sanity check.

What you should see

A connection to pub-f07e1612d57d476faf5948b53fcf3764.r2.dev when Atlas checks for or downloads a model. That is the only host our code contacts.
No connection to any analytics host — no Plausible, no Google Analytics, no PostHog. Plausible runs on this website only, never in the apps.
No connection to OpenAI, Anthropic, Google AI, or any other model-hosting provider. Inference is local.
On Android, the ad SDK is still in the build (see "the honest asterisk"). If you observe Google measurement traffic at launch, that is the open item we are closing by removing the SDK.

If you find something we missed

If you ever see a connection that contradicts what's on this page, tell us at legal@mirageinteractive.uk with the timestamp and the host you observed. We'll investigate and either explain it or fix it, and reply within a week.

These claims describe the current release build. Mirage Lumen's list will appear at launch. The website itself uses Plausible Analytics, documented in the privacy policy.