Privacy Policy

Effective Date: October 27, 2026

Introduction

Ramses Works LLC, a Maryland limited liability company (“Ramses Works,” “we,” “us,” or “our”) is committed to protecting your privacy. This policy explains what data we handle, what we collect for app improvement, and what we never touch.

Former Beta Sign-Up List

Before LANtern reached the App Store, this website offered a form for joining its beta, which collected Apple ID email addresses solely to send beta invitations. That form is retired, the stored list of sign-up email addresses has been deleted, and this website no longer collects email addresses for that purpose.

Contact Form Submissions

If you submit the contact form on this website, we collect your email address, the category you select (such as General Question, Support / Help, or Bug Report), and the free-text message you write (up to 2,000 characters). These are stored in the contacts collection in Firebase Firestore: your email address is stored encrypted at rest, and the category and message are stored in plaintext at rest. We use this information solely to respond to your inquiry. Submissions are reviewed by our team through the internal Ramses Works admin app. We do not sell this information or use it for marketing. You may request deletion of your submission at any time by emailing hello@getlantern.ai.

Integration Votes

If you vote for a future integration on this website, we store the integration you chose and a keyed hash of your IP address in the integration_votes collection in Firebase Firestore, so each visitor can vote once. We do not store the IP address itself.

In-App Reports

If you choose Report Response or Report a Problem inside the iOS app, LANtern sends the report type, selected reason, optional details you enter (up to 2,000 characters), app version, build number, and platform to getlantern.ai/report, which stores them in the ios_reports collection in Firebase Firestore. For a response report, LANtern also uploads a redacted excerpt of the reported AI response (up to 500 characters) and, when that response was a guardrail refusal, a short code naming which check produced it. The app and backend redact known secrets, email addresses, IP addresses, MAC addresses, and similar patterns before storage, but free-text reports may still include device names, hostnames, room or accessory names, file paths, or other personal information you typed.

In-app reports are used only for support, safety review, and product quality triage. Firestore encrypts data at rest; report fields are readable by authorized Ramses Works administrators for review. Reports are retained for up to 90 days and include an automatic deletion date. When a report is submitted, the app shows a report ID and deletion code. We store only a hash of the deletion code. To request earlier deletion, email the report ID and deletion code to hello@getlantern.ai.

Information We Never Collect

Ramses Works does not collect, store, or transmit the following information on our servers. Some of this information may be sent directly from your device to Anthropic as described in the AI Processing section below, and excerpts may be included in an in-app report only when you explicitly submit one, but it is otherwise never collected by Ramses Works.

  • Your conversations with Claude (queries and responses)
  • Network credentials, passwords, or API keys
  • Network topology, IP addresses, or device names
  • Device inventories or client lists
  • Smart home accessory data or room layouts
  • File contents or directory structures
  • Audio recordings, voice data, or speech samples
  • Diagnostic reports you save in the app
  • Personal information beyond what Apple provides for app distribution and what you choose to send us through the website forms described above

AI Processing

LANtern uses Claude, an AI assistant developed by Anthropic, PBC, to process your natural language queries. When you ask a question in LANtern, the text of your query and, when necessary to respond accurately, contextual information about your setup (such as device names, IP addresses, or HomeKit accessory names returned by tool calls) is sent directly from your device to Anthropic’s API servers for processing. If you attach an image — for example, snapping a photo of a device label for identification — the photo is also sent to Anthropic for that request. Anthropic’s use of this data is governed by their Privacy Policy. We do not send your network credentials or passwords to Anthropic, and Ramses Works does not operate any relay server — requests go straight from your device to api.anthropic.com over a connection protected by certificate pinning (SPKI), so an attacker who controls a certificate authority still cannot intercept your traffic.

No AI training. Your queries, conversation history, device context, and attached images are used only to generate responses to you. Ramses Works does not train any AI model on your data, and Anthropic’s API services do not use API requests to train their consumer models — see Anthropic’s Commercial Terms of Service for details. Your conversations are not retained on our servers (we operate no servers in the request path).

The Anthropic API key that authenticates your requests is delivered through one of two paths, depending on your subscription tier:

  • Free and Premium tiers — the key is delivered to your device when the app opens by an App Check-enforced Firebase callablebacked by Secret Manager. App Check uses Apple’s App Attest framework on supported devices, which produces a hardware-backed device assertion, so only genuine, unmodified copies of LANtern running on real devices can fetch the key. You never see or handle the key, and there is no Settings UI to view or edit it. Each AI request carries this key to Anthropic in its x-api-key header. The app fetches the key from getlantern.ai/getkey, so that is the address your iPhone’s App Privacy Report shows. The request carries none of your messages, device names, network data, or account details. Our code stores nothing about it; Google Cloud, which hosts it, keeps standard request logs (IP address and time). LANtern skips the request in Demo Mode and while your own key is in use.
  • Lifetime (Bring-Your-Own-Key) tier — you provide your own Anthropic API key in Settings, which is stored in the iOS Keychain on your device only. The key never syncs to iCloud or any other device. If your Lifetime purchase is no longer found, LANtern deactivates the saved key and stops using it; the key stays in this device’s Keychain until you delete it in Settings. When an active key is saved, AI requests carry your key to Anthropic instead of the app’s.

Controller and HomeKit Access

LANtern connects directly to the UniFi and Synology addresses you configure, which may be on your local network or reachable remotely. HomeKit access uses Apple’s HomeKit framework. Ramses Works does not relay your controller traffic.

Because UniFi and Synology controllers typically use self-signed TLS certificates, LANtern verifies them using out-of-band SPKI pinning: the first time you add a controller, you confirm its certificate fingerprint by paste or QR code. Future sessions are only trusted if the controller presents a key matching that pinned fingerprint, so an attacker on your LAN cannot impersonate the controller even with a valid CA-signed cert. If a controller can only be reached over unencrypted HTTP, LANtern asks before connecting that way; that connection, including your login, is not encrypted.

HomeKit

If you connect HomeKit accessories, LANtern uses Apple’s HomeKit framework to read device status and send commands on your behalf. HomeKit data is handled by Apple’s HomeKit framework. HomeKit commands are not relayed through Ramses Works servers. Accessory and room names may be included in AI requests to Anthropic when needed to answer your questions, or in a report you choose to send.

Siri, Shortcuts and Spotlight

Using LANtern with Siri, Shortcuts or Spotlight is optional, and you start it. When you ask Siri or run a shortcut to check a system, Siri handles your request under Apple’s privacy policy and speaks LANtern’s answer. The check reads the console or home you asked about directly, signing in with your saved login.

LANtern can save what a check finds as a report in the app on this iPhone. Saved reports are left out of backups, and creating or refreshing one uploads nothing. They’re separate from the in-app reports you choose to send us, described above. Delete All Conversations and Reset App erase them.

Saved reports reach Siri and Spotlight only if you turn on “Make saved reports available to Siri and Search” in LANtern’s Settings › Privacy › Siri & Search and then choose each report; it’s off by default. LANtern then offers a chosen report’s title, type and date to Search, and its saved text to Siri when asked. Turning it off, deleting the report, Reset App or turning on Biometric Lock removes LANtern’s entries, but can’t take back what Apple already received. Turning Biometric Lock off restores the choices you’d already made.

Siri can read what’s on your screen when you ask it to, and LANtern can’t block that. 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.

Voice & Speech Processing

LANtern offers optional voice input and text-to-speech output, both handled by Apple’s built-in speech frameworks.

  • Speech recognition uses SFSpeechRecognizer. When Apple’s on-device recognition model is available, your spoken words are converted to text entirely on your device. When an on-device model is not installed, Apple may transcribe audio on their servers per Apple’s privacy policy. LANtern itself never receives, records, or stores your audio — only the resulting text transcript.
  • Text-to-speech uses Apple’s on-device synthesizer to read responses aloud. Audio is generated locally and played through your speaker or headphones.
  • Voice transcripts are sent to the Anthropic API as regular chat messages, following the same path as typed text. There is no additional data exposure from using voice.
  • Microphone and speech recognition permissions are requested just-in-time when you first tap the voice button. You can revoke these permissions at any time in iOS Settings.

Analytics & Crash Reporting

LANtern can collect optional telemetry via Firebase, a Google service, to help us improve app quality. All telemetry is off by default on new installs and requires your explicit opt-in through the cookie-style consent prompt at first launch or via Settings > Privacy.

  • Firebase Analytics — usage events such as which screens are viewed, which features are used (e.g. theme changes, dashboard views, suggestion chip taps), query success/failure rates, names of the tools used, the Claude model, token counts, response latency, and subscription tier. Events never contain message content, credentials, network topology, or your console / device names.
  • Firebase Crashlytics — automatic crash reports and non-fatal error logs with device model, OS version, and app state at the time of the crash. Crash data includes diagnostic context such as active theme, subscription tier, and Claude model in use — but never conversation content, credentials, or console names. Crashlytics is hard-disabled in development builds and never collects in DEBUG.
  • Firebase Performance Monitoring — app startup time and custom performance traces (e.g. query response latency).

Identifiers. This telemetry is not anonymous. Crash reports may carry a random ID that LANtern generates and keeps in the iOS Keychain, so recurring crashes from the same device can be linked. Keychain data can survive deleting the app, so this ID may persist if you reinstall. Firebase Analytics and Performance Monitoring use Firebase’s own app-instance and installation IDs, and Firebase Analytics also collects Apple’s identifier for vendor (IDFV). None of these IDs contain your name, email, or Apple ID. LANtern never asks for App Tracking Transparency permission, so it cannot access Apple’s advertising identifier (IDFA).

You can change your analytics, performance, and crash-reporting preferences at any time in Settings > Privacy. Optional telemetry can stay off while the app continues to function.

Separately, some Firebase services run as required infrastructure, before and regardless of your telemetry choice. Firebase App Check and Firebase Installations verify that this is a genuine install of LANtern before it requests a key or sends a report. The key request itself goes to getlantern.ai/getkey, which runs on Google Cloud and reads the key from Secret Manager. Each time the app opens, Firebase Remote Config downloads LANtern’s AI safety settings, such as its prompt-injection deny list and refusal wording; that request carries a random installation ID, the app version, and the device’s language, region and time zone settings. These services may collect diagnostic data described in Firebase’s privacy documentation. They are not used for advertising or tracking and are separate from optional Analytics, Crashlytics, and Performance telemetry.

Credential Storage

Credentials you enter (such as UniFi or Synology login details, or a UniFi API key) are stored exclusively in the iOS Keychain with kSecAttrAccessibleWhenUnlockedThisDeviceOnly, meaning they are protected by hardware-backed encryption, never sync to iCloud, and remain inaccessible while the device is locked. LANtern sends them only to the console or NAS address you configured: logins to sign in, and a UniFi API key with each request to that console. The app does not send them to Ramses Works or Anthropic. HomeKit access uses native iOS permissions and requires no stored credentials. Network and smart home data is fetched in real-time and not persisted on our servers unless you choose to include it in an in-app report. Conversation history stays on your device, is excluded from iCloud and device backups, and can be exported or deleted in Settings > Privacy. Photos you attach are kept with it for up to 30 days unless you turn off Keep attached photos in history. Voice preferences and settings are stored locally on-device.

On-Device Protections

LANtern includes additional safeguards that run entirely on your device:

  • Read-only by default. Every UniFi console, Synology NAS and HomeKit home you connect starts at the Read-only Access level, where LANtern can look but can’t change anything. Only you can raise it, per system, to Ask or Auto, and raising it needs Face ID, Touch ID or your passcode. See Read-only by default for what each level allows.
  • Biometric-protected Keychain items. When you turn on biometric lock, sensitive items (your BYOK Anthropic API key and console passwords) are stored with a biometric-bound access control. The protection invalidates automatically if your Face ID or Touch ID enrollment changes.
  • Step-up authentication for destructive actions. High-impact tools — controlling a HomeKit lock, door, or other accessory, running a HomeKit scene, restarting a network device, blocking or kicking a client, and deleting files on your NAS — require an immediate biometric or passcode prompt before they execute, in addition to the on-screen confirmation that shows you the exact action. At Read-only they don’t run at all.
  • Screen-recording blackout. Sensitive surfaces (credentials, message contents) are blacked out during iOS screen recording and AirPlay mirroring, so private content isn’t inadvertently captured.
  • Message redaction at the storage layer. Before any chat message is written to local SwiftData storage, a deny-list filter strips passwords, tokens, API keys, MAC and IP addresses, and authorization headers, so even your on-device history doesn’t retain these values.
  • Reports keep only what’s needed. Saved reports keep names, states, capacities, counts and times, never passwords, tokens, MAC or IP addresses, raw controller data, camera images, filenames or disk serials. When you confirm which network client a Home accessory is, LANtern keeps that link on this iPhone as keyed digests, with no MAC or IP address.

Network Communication and the App Privacy Report

LANtern connects directly to the controller addresses you configure and uses Apple’s HomeKit framework for accessories. We do not operate a relay for controller traffic or for your conversations. API calls to Claude AI are made directly from your device and are subject to Anthropic’s privacy policy.

You can check this yourself. On your iPhone, go to Settings > Privacy & Security > App Privacy Report and turn it on. It keeps the last seven days of activity; tap LANtern under App Network Activity to see each address the app contacted. These are all the addresses it can show, and what each one is for:

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.

Third-Party Services

LANtern integrates with the following third-party services:

  • Claude AI by Anthropic — natural language processing. When you chat, your messages (whether typed or spoken via voice input), any photos you attach, and the results of tool calls (including device names, IP addresses, MAC addresses, storage details, HomeKit room and accessory names) are sent directly from your device to Anthropic’s API for AI processing. Conversations are subject to Anthropic’s privacy policy.
  • Firebase by Google — opt-in analytics, crash reporting, and performance monitoring as described above; plus Firebase App Check, Firebase Installations, Firebase Remote Config, and the Cloud Functions, Secret Manager and Firestore behind getlantern.ai/getkey and getlantern.ai/report, as required app infrastructure. Data is handled according to Firebase’s privacy documentation.
  • Apple — Siri, Shortcuts, Spotlight, HomeKit, App Attest, in-app purchases and speech recognition run as part of iOS, as described above. Apple handles them under its own privacy policy.

Website Analytics

This website uses Google Analytics (via Firebase) to measure usage such as page views, link and button clicks, and visit duration. Collection is gated behind your cookie consent choice. If you accept, Google Analytics sets cookies with a random visitor ID so visits from the same browser can be counted together. We do not collect your name or email through Google Analytics. Separately, this website uses Firebase App Check with Google reCAPTCHA Enterprise to protect its forms from abuse; it runs regardless of your cookie choice and is governed by Google’s privacy policy.

Changes to This Policy

We may update this policy from time to time. Changes will be posted on this page with an updated effective date.

Your Privacy Rights

Depending on where you reside, you may have rights regarding your personal data, including the right to know what data we hold, the right to request deletion, and the right to opt out of certain data uses. LANtern is designed to keep most app data locally on your device, but Ramses Works may maintain contact-form submissions, integration votes, and in-app reports as described above. To make any privacy request, contact us at hello@getlantern.ai. California residents may also contact us to exercise rights under the CCPA. Maryland residents may exercise rights under the Maryland Online Data Privacy Act (MODPA).

International Data Transfers

When you use LANtern’s AI features, your query text is processed by Anthropic (anthropic.com), whose servers are located in the United States. By using LANtern, you acknowledge that your query text may be transferred to and processed in the United States. Anthropic’s processing is governed by their Data Processing Agreement and Privacy Policy.

Contact

Questions about this policy? Contact us at hello@getlantern.ai.