KetoCypher is built so we cannot read your food log, weight, biometrics, or any other entry you make. This policy describes the few things we do see, and the architectural reason we don't see the rest.
Effective: June 21, 2026.
To run an account and (optionally) a cloud backup, the server stores:
The server does not see your food log entries, weight, heart rate, sleep, glucose, steps, electrolyte totals, ratings, fasting sessions, custom foods, recipes, or any other data you enter in the app. Those values are encrypted on your device with a key derived from your password (Argon2id) before they ever leave it.
Everything you enter, everything Health Connect returns to the app, and everything KetoCypher computes from those values, stays on your phone in an encrypted local database (SQLCipher). Single-signal insights and correlations are computed on-device. We do not see what your sleep is, what your blood glucose was, or which foods you logged.
If you connect Google Health Connect, KetoCypher reads weight, sleep, heart rate, blood glucose, and steps locally to pair them with your food log. We do not store, transmit, or process those readings on our servers. Health Connect runs inside Android's sandbox; the data flows app-to-app on your device.
You can revoke individual signal permissions at any time in Android Settings → Health Connect → KetoCypher.
If you submit your email on the landing page waitlist, we store the address and a tag indicating the source (the landing page) in our database. We use it only to notify you when the Android beta opens. To remove yourself, reply to the confirmation email or write to [email protected].
We use Cloudflare Web Analytics, which is cookieless and does not track individuals across sites. It records aggregate page-view counts and approximate location at the country level. No personal profile is built.
KetoCypher is not directed at children under 13 and we do not knowingly collect data from them. If you believe a child has signed up, write to [email protected] and we will remove the account.
Account data and (for Premium Backup users) encrypted backup blobs are stored on infrastructure hosted in the United States. Cloudflare handles the public web edge.
You can:
.kcbak file from inside the app. It is still encrypted with your master key.If you are in the EU/UK, the GDPR/UK GDPR rights of access, rectification, erasure, restriction, portability, and objection apply. The architecture (we cannot read your data) means that for most categories there is no plaintext to access, rectify, or port from our side; the export inside the app is the only complete copy.
If we add or change a subprocessor in a way that affects this policy, we will update this page.
If we materially change how the app handles your data, we will update the "Effective" date above and call out the change at the top of this page. Continued use after a change means you accept the updated policy.
General questions: [email protected]. Privacy, account, or data requests: [email protected].