Privacy at a glance
The app is a local-first food and fitness journal. Version one has no developer-operated backend, remote database, analytics SDK, advertising SDK, crash-reporting SDK, or tracking technology. jdbeue does not receive your meals, health information, photos, workouts, weight, or in-app activity.
Information handled on your device
Depending on the features you use, the app may store:
- Meal, serving, calorie, macronutrient, and nutrition-label details.
- Selected images, thumbnails, recognized text, and local analysis results.
- Workout sessions, exercises, sets, repetitions, weight, effort, and notes.
- Hydration, creatine, body-weight, goals, preferences, and local profile details.
This information provides the logs, trends, targets, summaries, capture review, and export features you choose to use.
Apple Health
Apple Health access is optional and read-only. With permission, the app may read steps, active energy, exercise time, workouts, body mass, resting heart rate, and dietary energy, protein, carbohydrates, and total fat. Health information is processed locally, is not written to Apple Health, and is not sent to jdbeue.
Camera, photos, speech, and device authentication
These features are optional and used only when you invoke them. Camera captures and images selected through Apple’s system photo picker are copied into private local storage. On-device speech recognition may turn optional food dictation into text; the audio is not saved. Apple’s Local Authentication framework can protect the private photo roll, while the app receives only whether authentication succeeded.
On-device analysis
Apple Vision features may recognize text and barcodes, classify images, isolate foregrounds, detect poses, compare local visual features, and use supported camera-depth signals. On supported devices, Apple’s on-device Foundation Models may refine capture results. These operations do not send your content to jdbeue.
Storage, sharing, and security
Structured records and app images are stored in the app’s local container with iOS data-protection controls. Version one does not use CloudKit or app-level iCloud sync. Data leaves the app only when you deliberately export it and select a destination in the iOS share sheet. No storage method is completely risk-free, so protect your iPhone with a strong passcode.
Retention, export, and deletion
Local records remain until you delete them, use Delete Data & Sign Out, or remove the app. Export Data creates a JSON file for you to save or share. Delete Data & Sign Out removes local records, app images, temporary exports, preferences, connected-data state, and the current local session. It cannot delete source photos, Apple Health records, or export copies you already shared.
Because version one has no account server, there is no server-side app account or cloud record for jdbeue to delete.
Support communications
If you email support, jdbeue receives the address, message, and attachments you choose to provide and uses them only to respond, troubleshoot, prevent abuse, and meet legal obligations. Support data is never uploaded automatically by the app.
Children and health information
The app is not presented as a children’s app or a medical device. It does not provide diagnosis, treatment, emergency guidance, parental monitoring, or medical care.
Changes and contact
This policy may change when app features or data practices change. A revised policy will show an updated effective date here.
Privacy questions: support@jdbeue.com