Don't take our word for it.
This page names every connection each of our apps makes, including the ones we're not proud of, and gives you the tools to check. None of them has an account, and none sends your files, collection or settings to us.
WearKeeper
WearKeeper runs its AI on your device — Android phone or Windows PC. Your collection, your photos, your notes and your prices are stored on the device and the app never sends them to us — there is no account, and no server of ours that receives your collection. We only see something if you choose to email it to us, for example with a support request.
You can check this one properly, because you can install it: WearKeeper on Google Play. The Windows version is on the Microsoft Store. Where the two behave differently, this page says so.
What has no network at all
The parts people most expect to be phoning home are the parts that can't. All of the following happen entirely on your device, with no connection of any kind:
- The AI. Inference is local. Suggestions, listing extraction, and diary tidying all run a model on your device via llama.cpp. There is no inference server, and no API key to one exists in the app. Report inappropriate AI output to contact@mirageinteractive.uk.
- The recommendations. Which watch to wear, collection gaps, dates, day counts, statistics and rankings are calculated by ordinary app logic. The model only phrases them, and only in English.
- Your collection. Stored in a local SQLite database. It is never uploaded unless you switch on Google Drive backup yourself (Android only).
- Receipt scanning (Android). The text-recognition model ships inside the app. The Windows version has no receipt scanning. Your receipt photo is never uploaded.
- Stats, wear tracking, reminders, CSV and PDF export — plus, on Android, alarms, the home-screen widget and the app lock. All local.
- There is no update check. The app never asks a server whether it is current.
No analytics. No crash reporting. No tracking SDK.
Not disabled by a flag — absent. There is no analytics, crash-reporting, advertising, or attribution library anywhere in the app, and no Firebase project configured. We checked by searching the entire source for every major vendor by name.
Crash details and a short navigation breadcrumb log are written to a file on your device, capped in size, and (on Android) excluded from Android's cloud backup. The breadcrumb log is structurally incapable of recording your watches, notes, prices, searches or AI prompts — it accepts a fixed list of event names and nothing else. The only way any of it leaves your device is if you tap "send bug report", which hands a text file to your system's share sheet and lets you choose where it goes.
The model download
The AI is an optional download of about 378 MB, fetched from our model host, models.mirageinteractive.uk (on Cloudflare), when you ask for it. It is a plain, unauthenticated download: no account, no device ID, no install ID, no cookies. The host necessarily sees request metadata, including your IP address, as it would for any download.
The app never phones home to check for a newer one. There is no update endpoint and nothing that reports back. If you have never asked for the download, nothing is ever fetched — though a download you already started will finish itself if it was interrupted.
Pasting a listing link
WearKeeper can read a watch listing you paste (or, on Android, share to it) and fill in the details for you. To do that it has to open the page you gave it, on the retailer's own servers. This is the one feature where the app talks to somewhere we don't control, and it deserves saying plainly.
It only ever opens a link you hand it. It never browses on its own, never fetches anything in the background, and never sends any part of your collection with the request. The only thing that leaves your device is the address you pasted.
What that means, without the spin
- You are visiting that retailer. We block the ad and analytics networks we know about, but a retailer's page is their code, not ours, and we can't promise none of it runs. Reading a listing is closer to opening it in a browser tab than to us fetching a file.
- Shortened links get followed. A shared link that redirects will be followed to the real product page, so you'll see those hops in a capture.
- The product photo comes with it. If the listing has one, it downloads from whatever image host the retailer uses. It's held temporarily and only kept if you save the watch.
None of this touches your collection, and none of it reaches us. We note the site's name — not the address — in a log on your own device, and nothing else.
Google Drive backup — Android only, and only if you turn it on
WearKeeper for Windows has no Google Drive backup; a Windows backup is a file you export yourself. On Android it is off by default, and part of the paid unlock. When you switch it on, your backup goes to your own Google Drive, on your own storage quota. We never see it, and there is no Drive of ours involved.
The app asks Google for the narrowest permission that exists for this — it can only touch files it created itself. It cannot read anything else in your Drive, and that is enforced by Google, not by us. Disconnecting revokes the access entirely rather than just signing out.
If you've asked for backups on Wi-Fi only, an automatic backup that can't confirm you're on Wi-Fi will wait rather than guess.
Paying for it
Android: the unlock is handled entirely by Google Play on your device. Your payment details never touch us, and we hold no record of your purchase.
Windows: WearKeeper is paid upfront through the Microsoft Store, with no in-app purchase. Microsoft handles the payment; your card details never reach us.
What you should see
- models.mirageinteractive.uk, when — and only when — you download the AI.
- A retailer's servers, and its image host, when you paste one of its links. Not before, and not after.
- On Android: Google — for the store, and for Drive if you enabled it. On Windows: Microsoft, for the Store.
- No analytics host. Ever. No Google Analytics, no Plausible, no PostHog, no Sentry, no Firebase. Plausible runs on this website only, never in the app.
- No connection to OpenAI, Anthropic, Google AI or any other AI provider. Your data is never sent anywhere to be processed.
Android permissions, and what each is for
- Internet — the four things above. Nothing else.
- Network state — solely to answer "am I on mobile data?" before an automatic backup.
- Notifications — local service and wear reminders. Asked for only when you turn them on.
- Biometrics — the optional app lock, checked by Android, never by us.
- Set alarm — hands a time to your existing Clock app.
No location. No camera. No contacts. No microphone. No storage. Photos come through Android's own photo picker, which hands the app one image and no access to anything else.
How to check it yourself
Pick whichever tool matches your setup. Each shows you, at a different layer, what the app is actually doing.
- Airplane mode. The simplest test, on either platform. Once the model is downloaded, turn the network off and use the app. Everything except reading a link, Drive backup and buying still works — which tells you the rest isn't using the network.
- Wireshark on a network you control. Put the phone or PC on your own network and capture everything from its IP while you use the app.
- mitmproxy. Trust its CA on the device and route through it to inspect TLS contents, not just hostnames.
- Android's own data usage. Settings → Network & internet → Data usage by app. Coarse, but a quick sanity check anyone can do.
The interesting test is the listing reader: paste a link from an ad-heavy retailer and watch what the fallback loads. That is where you'll find anything we've got wrong.
MervanIQ
The app makes no network connections. There is no networking code in it at all: no HTTP client, no telemetry, no analytics, no crash reporting, no update check. Scans read file names, paths and link information on your PC; nothing is uploaded, and no file is changed.
What you should see: nothing from MervanIQ. Connections to Microsoft for purchase, licensing and updates come from the Microsoft Store and Windows, not the app.
VorselunIQ
One connection: the Microsoft Store licence check at start-up. It uses Windows' standard Store licensing interface and carries no file information. Otherwise VorselunIQ has no networking code: no telemetry, analytics, crash reporting or update check.
The audit itself is read-only. VorselunIQ asks Windows for attributes and link targets with read-attributes access only, and opens items in a mode that stops a cloud provider downloading them — so auditing a cloud-only file doesn't pull it down. Links to network shares are recorded, never probed.
What you should see: the Store licence check, and nothing else from the app. No connection to any cloud-sync provider is made on VorselunIQ's behalf.
AmporIQ
One connection: the Microsoft Store licence check. It uses Windows' standard Store licensing interface and never locks you out if it can't be made. AmporIQ has no other networking code.
Audio: AmporIQ reads and sets device levels through Windows' endpoint-volume interface and is notified when they change. It contains no audio-capture code and never opens a microphone recording stream. The optional "keep audio device active" setting plays silence to an output device only.
What you should see: the Store licence check, and nothing else from the app.
WakeAuditIQ
No connections. WakeAuditIQ contains no networking, telemetry, analytics, update-check or Store-licensing code. It reads power information that Windows already records on your PC.
Support: the Contact support button opens your own email app with an empty message. The app adds nothing to it and does not send it.
What you should see: nothing from the app.
MailPackIQ
No email accounts, no mail servers. MailPackIQ has no IMAP, POP or SMTP code and never signs in to an email account. It reads the email files you add, read-only, and writes PDFs only to the folder you choose. Email previews block all remote content, so images and trackers inside emails are never loaded.
Feedback form (version 1.0 only): MailPackIQ 1.0 includes an optional Send feedback form. If you use it, it sends your feedback to us through a Google Apps Script service. Version 1.0.1 removes the form; from then on, support is an email you write in your own email app.
If you find something we missed
If you see a connection that contradicts this page, tell us at legal@mirageinteractive.uk with the timestamp and the host. We'll investigate and either explain it or fix it, and reply within a week.
To report inappropriate AI-generated content in WearKeeper, email contact@mirageinteractive.uk. For help with the app, use the same address.
The Android claims describe WearKeeper 1.9.1, audited on 29 July 2026 against the app's source. The Windows differences describe the WearKeeper 1.10.108.0 Microsoft Store build, checked against its source on 24 September 2026. The MervanIQ, VorselunIQ and AmporIQ statements were checked against each app's current source on 25 September 2026. Mirage Lumen is not shipped; its connection list will be published here before its first install. The website itself uses Plausible Analytics, documented in the privacy policy.