Most privacy pages are written by lawyers, for lawyers. This one isn’t. We’re going to walk through each row of the card above and explain, in human language, what we do and don’t do — and why.
Network requests — updates only
Luna makes exactly one kind of outbound request: a check, once a day, to see whether there’s a new version. It hits a static JSON file on our server. The server logs the request with your IP address (which it has to — that’s how the internet works) and discards the log after 24 hours.
We don’t see what tone you picked. We don’t see when the app is open. We don’t see whether you used it for ten seconds or ten hours. The update check carries no device ID, no user ID, no telemetry payload. It’s a single HTTP GET with the current version number in the query string, so we know whether to tell you a new build exists.
You can turn the update check off entirely in settings. The app will keep working forever, just without the “new version available” banner.
Tracking SDKs — none
Most apps you have installed contain between four and twenty third-party libraries whose job is to phone home about you. Google Analytics. Facebook Pixel. Mixpanel. Amplitude. Crashlytics. Branch. Adjust. Segment. The list is long and the behaviour is always the same: every tap, scroll, and screen view goes to someone else’s server, where it’s joined to every other app’s data about you.
Luna contains zero of these. We don’t use a single tracking SDK. We don’t have a “product analytics” dashboard. We don’t know which features you use most. This is a constraint we accepted on purpose — it means we have to decide what to build by talking to people instead of by watching them. We think the software ends up better that way.
Account required — no
You bought Luna. That’s the entire relationship. There is no sign-up, no email verification, no account recovery, no password. The app does not know who you are. It cannot, because we never asked.
The one exception is purchase: Stripe needs an email address to send your receipt and to handle a refund if you ask for one. That email lives in Stripe’s vault, not ours. We can look it up when you write to us, but we don’t sync it into a CRM, and we don’t email you marketing — ever. If you opt in to the build-log newsletter, that’s a separate, explicit choice, and one unsubscribe link removes you completely.
Source available — at v1.0
When Luna 1.0 ships, the full source code goes up on GitHub under a source-available licence. You’ll be able to read every line of what we do, audit the network calls yourself, and verify that the binary on the App Store was built from the code we published. We’re not open-sourcing it in the you-can-fork-and-sell-it sense — Luna stays a small commercial project — but you’ll be able to see exactly what you’re running.
Before 1.0, the code is still being reshaped weekly. Once it stops moving, it goes public. A third-party audit by a German security firm will go up alongside it.
Crash reports — opt-in only
When an app crashes, the operating system can offer to send the developer a small report — a stack trace, the device model, the OS version. This is genuinely useful for fixing bugs. It’s also a tiny stream of personal data leaving your phone.
We don’t turn crash reporting on by default. The first time Luna crashes (we hope it doesn’t, but software is software), you’ll see a one-tap prompt asking whether you’d like to send the report. If you say no, nothing leaves your device. If you say yes, we get the stack trace and nothing else — no list of apps installed, no location, no identifier. You can change your answer anytime in settings.
If you delete Luna, there is no “your data” for us to delete. We never had any. That is the point.
Questions, or things we missed
We’re two people. If something here is unclear, or you spotted a gap, write to privacy@luna.appand one of us will answer. We’ll update this page rather than send boilerplate.
If you’d like the same promises in legal language for a compliance review, we can produce a formal data-processing statement on request. For most people, this page is enough.