Your network stays yours.
Every system you connect starts read-only, and your saved logins stay in the iOS Keychain on this device, sent only to the console or NAS address you configure. Here’s what LANtern may change, where your data goes — and how you can verify it yourself.
What leaves your device
- Your questions — the text you type and, when needed to answer accurately, tool results (which can include device inventories, IP addresses, or HomeKit accessory names), plus any photo you attach, are sent to Anthropic’s Claude API (
api.anthropic.com). - App infrastructure (always on) — when it opens, LANtern gets the key it uses to reach Anthropic from
getlantern.ai/getkey(skipped in Demo Mode and with your own key), proving it’s a genuine copy with Firebase App Check. It also downloads its AI safety settings from Firebase Remote Config. None of these requests include your conversations, logins, or network data. If you send an in-app report, it goes togetlantern.ai/report; a report on a response includes a redacted excerpt of that response. - Optional telemetry (off by default) — if you opt in, usage analytics, crash reports, and performance data are sent to Firebase. Crash reports may carry a random ID that LANtern keeps in the iOS Keychain (it can survive a reinstall), and Firebase Analytics uses its own app-instance ID, so reports from one device can be linked. They never include your name, email, logins, or message content.
- Siri and Spotlight (only if you use them) — Siri handles what you ask it under Apple’s privacy policy. Saved reports reach Spotlight and Siri only if you choose them.
- Credentials — stored in the iOS Keychain using hardware-backed encryption. Saved logins are sent only to the console or NAS address you configure for sign-in, and a UniFi API key goes with each request to that console. Neither is sent to Ramses Works or Anthropic.
- Network data — LANtern fetches data from the controllers you configure. Tool results, including inventory details, can be sent directly from your iPhone to Anthropic to answer your question; Ramses Works does not relay them.
- HomeKit — home and accessory data accessed via Apple’s HomeKit framework. Accessory or room names may be included in AI requests when needed to answer your question.
- Saved reports — kept in LANtern on this iPhone and left out of backups. Creating or refreshing one uploads nothing.
Read-only by default
Every UniFi console, Synology NAS and HomeKit home you connect starts at Read-only. Only you can raise it, per system, in Settings > Consoles > (system) > Access, and raising it needs Face ID, Touch ID or your passcode. Lowering it never does. The AI has no tool that can change an Access level. Demo Mode’s sample systems start at Ask, so you can see a change work behind a confirmation.
- Read-only: LANtern can look at everything but can't change anything.
- Ask: LANtern asks you to confirm every change before it runs.
- Auto: LANtern makes everyday changes without asking, but still checks with you before risky ones.
| Action | Read-only | Ask | Auto |
|---|---|---|---|
| Look at status, lists, logs and files | Yes | Yes | Yes |
| Everyday changes, like turning on a light or pausing a download | No | After you confirm | Runs |
| Bigger changes, like changing Wi-Fi settings, adding a port forward or deleting an automation | No | After you confirm | After you confirm |
| Highest-risk actions: restarting a network device, blocking or kicking a client, deleting a NAS file, operating a HomeKit lock or door, running a scene | No | Confirm, then Face ID, Touch ID or passcode | Confirm, then Face ID, Touch ID or passcode |
At Read-only, LANtern isn’t offered any tool that changes things, and refuses one if it’s asked anyway. Ask for a change and it tells you changes are off and where to allow them. Auto behaves exactly as LANtern did before access levels existed, so choosing it never makes the app less careful than it was. App settings, like the theme or voice, aren’t affected by Access levels.
Two locks
A change happens only when both locks allow it: LANtern's Access level and the account you connected with. Connect with an account that can only read, and nothing can change your network or NAS, whatever Access level you choose.
Recommended: use a read-only account
The same steps LANtern shows during setup:
Use a View Only local account
A local View Only admin lets LANtern see your whole network but not change it.
- On your home network, open your console's address in a browser (for example https://192.168.1.1), not unifi.ui.com.
- Go to People (Admins & Users on older consoles) → Create New → Create New User.
- Tick Admin and Restrict to local access only, then set a username and password.
- Untick Use a Predefined Role. Set Network to View Only, Protect to View Only if you use cameras, and Control Plane to None.
- Create the account, then enter its username and password in LANtern.
A View Only account can't make changes, even if you raise LANtern's Access. To allow changes, give it Site Admin for Network.
Or use an API key
A UniFi API key has the same power as the admin who created it. UniFi has no read-only key.
- Sign in at your console's local address.
- Open UniFi Network → Integrations (on Network 9: Settings → Control Plane → Integrations).
- Name the key LANtern, create it, and copy it. It's shown only once.
- Paste it in LANtern's API Key field.
Only Super Admins can create keys, so for read-only access use a View Only account instead. With a key, network health, events, alarms, port forwards and client history aren't available.
Protect: read-only by design
LANtern's camera tools only read camera lists, events and snapshots.
- Give the UniFi account View Only for Protect, or None to keep cameras out of LANtern.
Snapshots and events need at least View Only in Protect.
Use a standard DSM user
A standard (non-admin) user can browse the folders you choose but can't change DSM.
- In DSM, open Control Panel → User & Group → User → Create.
- Name it (for example lantern) and set a strong password.
- Join groups: users only. Don't add it to administrators.
- Shared folders: Read only for folders LANtern may see, No access for the rest.
- Applications: allow File Station, and Download Station if you use it. Deny the rest.
- Finish, then enter the username and password in LANtern.
DSM keeps system monitoring for administrators. With this user, LANtern can't show CPU and memory use, storage and disk health, network settings, installed packages or the shared-folder list. Model, DSM version, file browsing and search still work, and downloads show only this user's own tasks.
HomeKit: controlled by Apple Home
HomeKit has no separate account, so LANtern's Access level is the only lock.
- LANtern uses the Home access you allow in Settings → Privacy & Security → HomeKit.
- Keep Access on Read-only unless you want LANtern to operate accessories.
Anyone who shares your home can operate accessories even without Add and Edit Accessories, so the Home app can't make LANtern read-only.
Siri and Shortcuts only read
Siri and Shortcuts can read your systems and open LANtern, whatever a system’s Access level. Any change happens in LANtern, where the Access level and the account you connected with decide. A check of a console signs in with your saved login and sends it only to that console.
A locked iPhone gets no answer until it’s unlocked. With Biometric Lock on, LANtern’s Siri features are off: checks, report search, Ask Siri context and Search indexing.
How credentials are protected
Console and NAS credentials are stored in the iOS Keychain, which uses hardware-backed AES-256 encryption tied to the device’s Secure Enclave. They are never written to disk in plaintext, never synced to iCloud Keychain or restorable to another device, and never transmitted by the app to LANtern’s or Anthropic’s servers. LANtern sends saved logins only to the console or NAS address you configure for sign-in. Controller connections go directly to that address without a Ramses Works relay.
Verify it yourself
On your iPhone, go to Settings → Privacy & Security → App Privacy Report and tap Turn On App Privacy Report. It records from then on and keeps the last seven days. Use LANtern for a while, come back, and tap LANtern under App Network Activity to see every address it contacted. Each one is explained in Every address LANtern contacts below.
Run a network proxy like Proxyman or Charles on your Mac and inspect LANtern’s outbound traffic. You’ll see AI requests to api.anthropic.com, the key request and any report you send to getlantern.ai, Firebase requests for App Check, Installations and Remote Config, and analytics if you opt in. AI requests carry an Anthropic API key in the x-api-key header: the app’s key, fetched when the app opens from getlantern.ai/getkey, or your own key on Lifetime BYOK. Saved console and NAS logins go to the configured address, which can be a public host. Because LANtern pins the certificate for api.anthropic.com, a proxy can see those connections but can’t decrypt them, and AI requests fail while a proxy tries to intercept them.
Check your router, firewall, or DNS logs for LANtern’s traffic. You should see the same addresses as the App Privacy Report: api.anthropic.com, getlantern.ai, Firebase and Google domains (App Check, Installations, Remote Config, and optional telemetry), and the console or NAS addresses you configured.
Every address LANtern contacts
This is the full list your App Privacy Report can show for LANtern, what each request carries, and what happens to it afterwards.
api.anthropic.com
- Who runs it
- Anthropic (Claude AI)
- When
- Each time you send a message, outside Demo Mode. LANtern may also send a short safety check of your message or the reply to the same address.
- What it carries
- Your message and the conversation so far; what LANtern looked up to answer it (device and client names, IP and MAC addresses, storage details, HomeKit room and accessory names); any photo you attach; the API key, in the x-api-key header; and your plan name (free, premium or byok) as the request’s user ID. Console and NAS logins are never included.
- What’s kept
- Governed by Anthropic’s privacy policy and commercial terms, under which API requests are not used to train their models. Ramses Works never sees it.
getlantern.ai (/getkey)
- Who runs it
- Ramses Works, hosted on Google Cloud
- When
- When the app opens, to get the key LANtern uses to reach Anthropic. Skipped in Demo Mode and while your own Anthropic key is in use.
- What it carries
- Only an App Check token: Apple-backed proof that this is a genuine, unmodified copy of LANtern. No messages, device names, network data or account details.
- What’s kept
- Our code stores nothing about the request. Google Cloud keeps standard request logs (IP address and time).
getlantern.ai (/report)
- Who runs it
- Ramses Works, hosted on Google Cloud
- When
- Only when you tap Report Response or Report a Problem and send it.
- What it carries
- The report type and reason, any details you type (up to 2,000 characters), the app version, build and platform. A report on a response adds a redacted excerpt of that response (up to 500 characters), which can still contain device or room names.
- What’s kept
- Stored for up to 90 days, then deleted automatically. Your IP address is used only to limit how often reports can be sent and is not stored.
firebaseappcheck.googleapis.com
- Who runs it
- Google (Firebase App Check)
- When
- Just before a key request or a report, when LANtern needs a fresh App Check token.
- What it carries
- An attestation from Apple’s App Attest and the app’s identifiers. Nothing about you, your network or your conversations.
- What’s kept
- Handled under Firebase’s privacy terms.
firebaseinstallations.googleapis.com
- Who runs it
- Google (Firebase Installations)
- When
- On first launch, and occasionally afterwards to refresh it.
- What it carries
- A random ID that Firebase creates for this install, which the other Firebase services use. It contains no name, email or Apple ID.
- What’s kept
- Handled under Firebase’s privacy terms.
firebaseremoteconfig.googleapis.com
- Who runs it
- Google (Firebase Remote Config)
- When
- Each time the app opens.
- What it carries
- The installation ID, app version, and the device’s language, region and time zone settings. It downloads LANtern’s AI safety settings, such as the prompt-injection deny list and refusal wording, so we can update them without an app release.
- What’s kept
- Handled under Firebase’s privacy terms.
Google telemetry addresses, such as app-measurement.com, firebaselogging-pa.googleapis.com and crashlytics.com
- Who runs it
- Google (Firebase Analytics, Performance Monitoring and Crashlytics)
- When
- Only if you turn on usage analytics, performance data or crash reports. All three are off until you opt in.
- What it carries
- Usage events, performance timings and crash reports, as described under Analytics & Crash Reporting. Never message content, logins, network topology or console and device names.
- What’s kept
- Handled under Firebase’s privacy terms.
Your console and NAS addresses (for example 192.168.1.1)
- Who runs it
- You: the UniFi console and Synology NAS you connect
- When
- Whenever LANtern reads from or makes a change on that system, including checks you run from Siri or Shortcuts.
- What it carries
- Your login or UniFi API key to sign in, then the requests that read data or, if its Access level allows, make a change. Nothing goes through Ramses Works.
- What’s kept
- On your own hardware, under its own logs.
Some work is done by iOS itself rather than by LANtern: HomeKit control, App Attest, in-app purchases, speech recognition when your iPhone doesn’t have the on-device speech model, and Siri, Shortcuts and Spotlight when you use them with LANtern. Siri handles what you ask and speaks LANtern’s answer, and can read your screen when you ask it to. Search gets a saved report only if you choose it. Apple handles that traffic under its own privacy policy.
What we use Anthropic for
LANtern uses Claude, Anthropic’s AI, to understand your questions and generate answers about your network. When you ask a question, LANtern may include tool results (such as device inventories, IP addresses, or HomeKit accessory names) in requests to Anthropic’s API when needed to answer accurately. Your console and NAS passwords and other controller credentials are never sent to Anthropic.
Anthropic’s data handling is governed by their Privacy Policy and Usage Policies.