Your log,
on a big screen.
Scan this with AlisLog. Your phone sends an encrypted snapshot of your history to this tab; the key stays in the code, and the relay holds the ciphertext for 24 hours without being able to read it.
- 01Open AlisLog → Settings → Web console
- 02Tap Scan the code and point it at this screen
- 03This page fills in. Re-open the app to refresh; it re-beams on its own.
The key is in the code
This page mints a random session id and an AES-GCM key. The key travels in the QR and in the URL fragment, which browsers never send to a server.
The relay can't read it
Your phone encrypts before it sends. The relay holds one ciphertext per session, signed by your phone, for 24 hours. Then it's gone.
Nothing is stored here
Decryption happens in this tab. Close it and the snapshot is gone. No account, no cookie, no login: the same rules as the app.
This session ended.
Either you disconnected, or 24 hours passed and the relay dropped the snapshot. Nothing was kept. Mint a new code whenever you like.
Calories
Weight
Supplements, water & fasts
Macros · daily average vs goal
The ledger
Decrypted in this tab with a key that only ever lived in the code you scanned. The relay holds one encrypted snapshot for 24 hours and can't read it. This site stores nothing; close the tab and the snapshot is gone.
AlisLog shows information computed from your own logs. It isn't medical or nutritional advice, and AI-estimated nutrition can be inaccurate; estimated items are marked.