Privacy and data
This page describes what LUNA stores, where, and who can read it. The published privacy policy is at runink.org/luna-privacy.
What is stored
Everything Luna keeps about you is written to your own partition of one encrypted store:
| What | Where it lives |
|---|---|
| Chat turns (text and voice transcripts), habit events, avatars, training and meal plans, body records, logged sets | Append-only journal streams, one per kind, per account |
| Long-term memory | A per-account vector index (hybrid vector + keyword search) that recalls earlier conversations |
| Sessions | A session table holding only a SHA-256 hash of each 12-hour session id |
| Avatar video loops (custom avatars only) | The object store’s media area, served through signed, expiring URLs |
The store is LUNA’s own store/appfs root. It is encrypted and sealed
under a key derived from the platform’s key-encryption key, and kept on
Runink’s self-hosted object storage, not a managed cloud database. Your
partition is keyed by a hash of your account, not the raw address,
because an address is personal data and shouldn’t appear in a storage path.
Who can read it
- Only you, through your session. Every request is checked against the session table and the allowlist. The data layer takes the account from the verified session and refuses a request that has none. It never falls back to a shared bucket.
- Only the aspects that need it. Before the model runs, the server decides which of your data goes into the prompt. Your health journal, body records and plans are included only for the trainer and nutritionist. The keeper gets your streak counts only (days in a row, and whether today is logged yet), never the values behind them. Your “inner context” is included only for counsel, trainer and nutritionist.
- No third-party AI provider. Chat, vision, speech-to-text, text-to-speech and embeddings all go to Runink’s own services. At startup the server checks that every one of those endpoints outside the cluster is encrypted, and runs only when they are.
- Conversation text is not logged. Server logs don’t contain your messages. The exception is a short excerpt, logged when the prompt-injection scanner flags a transcript, photo reading or plan text. Your email address is logged at sign-in.
Third parties the apps contact
The model side is fully sovereign. The client still reaches a few outside services:
| Contact | What it receives | When |
|---|---|---|
| Google Sign-In | Your identity at sign-in | Always |
| The device speech recogniser (usually Google’s on Android) | Your voice | Only on the STT fallback path |
| The device text-to-speech engine | The text of Luna’s replies | Every spoken reply on native builds, and the fallback on web |
| OpenStreetMap | Your IP address and the map area you view | While tracking an activity |
| GitHub (raw content) | Your IP address and which exercise image | When exercise images load |
| Open-Meteo | Coordinates coarsened to about 1 km | Only if you connect local weather (web build) |
Health Connect is not on this list. It is on-device, and Luna only reads from it.
Honesty markers you will see
- “not saved — Luna won’t remember this”: a reply that streamed but couldn’t be written to the journal. The conversation carries on, but that turn won’t be recalled later.
- “not verified”: a model proposal the judging ladder couldn’t confirm.
- A dash or “not reported”: a value Luna doesn’t have. It is never shown as zero.
Deletion
Records are kept until they are deleted on request; there is no automatic retention window. Removing an account from the allowlist revokes all of its sessions immediately, and its data stays in place until a deletion request.