Luma

Privacy Policy

Updated October 21, 2026 · Luma 1.0 · Developer: Rodion Kukartsev

Information on your device

Your food diary, goals, age, sex, height, entered and imported weight, water, intermittent fasting sessions, analysis history and small copies of selected photos are stored in the app on your device. They may be included in device backups managed by Apple and you. If iCloud is on, this information — except analysis history and photos — syncs between your devices signed in with the same Apple ID through your private iCloud database. Apple stores it under your account; we cannot access it. You can turn this off in Settings → your name → iCloud. We do not receive a copy of your diary or your Apple Health data on our server.

Camera, photos and Apple Health

The camera is used only when you ask for it. The system photo picker gives the app only the image you select. Optional Apple Health access lets Luma read your weight only; Luma does not write data to Apple Health. You can change these permissions in iOS Settings and Apple Health.

AI food analysis

Only after separate consent, the selected image and the note you typed are sent over HTTPS to Luma's server, then to OpenRouter and the OpenAI model provider for an approximate estimate of calories and macronutrients for each food and drink in the photo. The request also includes your device's language setting (for example, en-US) so the result is written in your language. Notes may contain dietary information, so do not enter medical details, documents or other unnecessary personal information. You can decline and keep your diary manually.

The image is resized and re-encoded without its original metadata. Our server processes the photo, note and result in memory, does not save them or the request body to disk and does not keep HTTP access logs. OpenRouter requests are routed only to endpoints with a Zero Data Retention policy and with data collection for training disallowed. Processing takes place on the providers' infrastructure and may happen in other countries. Providers handle technical request and billing metadata under their own policies: OpenRouter Privacy Policy, OpenRouter Zero Data Retention and OpenAI Privacy Policy. We do not use your photos for advertising or to train our own models.

Server access and abuse prevention

On the first analysis, the server issues a random token that is stored in the device Keychain. The server keeps a one-way hash of it and an expiry date of up to 90 days, plus short-lived request counters that limit load and costs. Counters are kept for up to two days, and expired records are deleted automatically. We do not ask for your name, email, advertising identifier or a permanent hardware identifier for this.

Your IP address is needed for the network connection and is used temporarily in server memory, for about an hour, to rate-limit token issuance. Infrastructure providers may process connection details to operate and secure their services.

Deletion and choices

No photo is sent before you consent. You can delete diary and scan entries in the app. In Goals → Privacy and Support you can delete the server identifier and its counters, together with the token in the Keychain; the next analysis creates new access. Aggregate, non-identifying service counters remain for up to two days to prevent abuse. Deleting the app removes its local data but not records in Apple Health. A Keychain token may survive deleting the app, so use the button inside Luma to remove server access first. You manage existing device backups.

Ads, analytics, purchases and children

Version 1.0 is free, with no subscriptions, ads or third-party analytics SDKs. We do not track you across apps and websites. Luma is intended for adults aged 18+ and does not provide medical advice.

Contact and changes

For privacy and support questions: rodionangeles@gmail.com. If you contact us by email, we receive your address and message in order to reply; please do not send unnecessary sensitive information. We will update this policy if our data handling changes.