Privacy Policy — KetoPulse Pro
This Privacy Policy explains how the KetoPulse Pro iOS application (the "App") collects, uses, and shares information. KetoPulse Pro is a separate application from the original KetoPulse app and has its own policy. By using the App you agree to this policy.
The short version. KetoPulse Pro is anonymous by default — there is no sign-up, name, or email required. We do not show ads, we do not use affiliate links, and we do not sell your personal information. Meal text and photos you submit are sent to our backend to generate AI analysis.
1. Information we collect
| Category | Examples | Why |
|---|---|---|
| Anonymous identifier | A randomly generated device-based ID (anonymous Firebase auth) | To associate your check-ins and subscription with your device, and for support requests |
| Check-in content | Meal descriptions you type or dictate, and photos of meals you choose to submit | To generate AI estimates of macros and ketosis state |
| Usage & diagnostics | App events (e.g. check-in started/completed), crash reports, performance data | To keep the App reliable and improve it |
| Subscription data | Purchase/restore status and entitlement (via Apple & RevenueCat) | To unlock and manage your subscription |
| Attribution data | Install attribution and, with your permission, the advertising identifier (IDFA) | To understand which campaigns bring new users |
We do not request your contact list, precise location, health records, or social accounts. Your individual check-in history is stored locally on your device.
2. App Tracking Transparency (ATT)
On iOS, the App asks for your permission before accessing the advertising identifier (IDFA) for attribution. If you decline, the App still works; we simply do not use the IDFA. You can change this any time in iOS Settings → Privacy & Security → Tracking.
3. AI analysis & third-party AI (Google Gemini)
To estimate your meal's macros, keto score, and ketosis state, the App sends the meal content you choose to submit — the meal text you type or dictate, or the meal photo you capture or upload — together with minimal context (time zone, language, and coaching-tone preference) over an encrypted connection to our backend, which calls Google's Gemini AI model to generate the result.
We ask for your consent inside the App before any data is sent to the AI. The first time you start an analysis, the App shows a screen that discloses what is sent and who it is sent to, and no data leaves your device unless you agree. We do not send your name, account, email, contacts, precise location, health records, or advertising identifier — the App is anonymous.
Your submissions are used only to generate your analysis and to operate and debug the service; they are not used to build an advertising profile of you. Google processes this data as our service provider under its own terms and privacy commitments, which provide a comparable level of protection.
4. Voice check-ins & the microphone
You can log a meal by speaking instead of typing. This is optional: the App asks for microphone and speech-recognition permission the first time you use it, and every other feature works without granting it.
Audio is transcribed to text using Apple's Speech framework. On devices and languages that support on-device recognition, the audio never leaves your device. Where on-device recognition is not available, iOS may send the audio to Apple's speech-recognition service for transcription, under Apple's own privacy policy; we do not control or receive that audio.
We never send your audio to our servers or to Google. Only the resulting text reaches our backend, and only if you then submit the check-in for AI analysis — at which point it is treated exactly like text you typed (see section 3). Recordings are not stored on your device after the transcription finishes.
5. Third-party services
We rely on the following processors, each under their own terms and privacy policies:
- Apple — App distribution and in-app purchases.
- Google Firebase — anonymous authentication, analytics, crash reporting, and remote configuration.
- Google Gemini (via our backend) — AI analysis of meal text and photos.
- RevenueCat — subscription management.
- AppsFlyer — install attribution and marketing measurement.
Each processor receives only the data needed to provide its service, acts on our instructions, and is bound by its own privacy terms providing a comparable level of protection for your data.
6. How we use information
- To provide the core features: check-ins, scores, ketosis tracking, and progress.
- To operate, secure, debug, and improve the App.
- To manage subscriptions and provide support.
- To measure marketing performance in aggregate.
7. Sharing
We share information only with the processors listed above to provide the service, or where required by law. We do not sell your personal information and we do not share it for cross-context behavioural advertising.
8. Data retention
Check-in history lives on your device and is removed when you delete the App. Backend logs and analytics are retained only as long as needed to operate the service and are then deleted or aggregated. You may request deletion of data associated with your anonymous identifier (see Contact).
9. Your choices & rights
- Decline tracking via the ATT prompt or iOS Settings.
- Delete your local data by deleting the App.
- Request access to or deletion of data tied to your anonymous ID by emailing us.
- Manage or cancel your subscription in your Apple ID Account Settings.
10. Children
KetoPulse Pro is not directed to children under 13 (or the minimum age of digital consent in your region) and we do not knowingly collect their data.
11. International users
Your information may be processed on servers located outside your country. We take reasonable steps to protect it consistent with this policy.
12. Changes
We may update this policy from time to time. Material changes will be communicated through the App or this page, and the effective date above will be updated.
13. Contact
Email: support@ketopulse.app