Privacy Notice

1. Controller and local-first approach

Omer Yildirim is the developer, provider, and data controller of the DietMaxx mobile app under Turkish Personal Data Protection Law No. 6698. DietMaxx is designed as a privacy-first, zero-server, local-first mobile app. Omer Yildirim does not create a central user account, collect email, password, or authentication credentials, or remotely access app data stored on your device.

Management, storage, and protection of data processed in the app primarily take place on the device where the data is entered.

2. Data processed

Profile and physical data may include a name or profile label, date of birth or age, height, weight, sex preference, body measurements, goals, and training type, intensity, and schedule entered by the user.

Nutrition and wellness data may include meals and food logs, macro values, water and caffeine records, sleep and recovery inputs, digestive comfort, personal sensitivities, symptom records, and user notes.

The app may store local notification preferences, the version, language, and timestamp of accepted legal documents, a manually entered city, and a profile image if selected by the user.

3. Purposes and storage

Data is processed to calculate personalized calories and macros, plan meals, create hydration targets, display nutrition and recovery records, provide digestive wellness context, and run local reminders selected by the user.

Profile, log, setting, and consent records are stored in SQLite- and MMKV-based local storage allocated to the app on the device. DietMaxx does not promise central cloud backup or cross-device synchronization for this data.

4. Notifications and device permissions

The app may request notification permission for meal, hydration, recovery, and wind-down reminders. Reminder schedules and preferences are stored on the device and can be disabled in the app or operating-system settings.

If the user selects a profile image, photo-library access is requested only to use the image chosen by the user in the app.

5. Network connections and third parties

A city manually entered by the user may be sent to Open-Meteo geocoding and weather services to obtain city suggestions and weather data. Coordinates returned by the service are used only to request weather for that city. Health data, food logs, and detailed profile records are not included in these requests.

App download, updates, premium purchases, subscription validation, restoration, and management are handled through Apple App Store or Google Play infrastructure. DietMaxx does not access payment-card details.

The current mobile app does not use centralized authentication, product analytics, or remote crash-reporting systems.

6. Retention, security, and data loss

Local data may remain on the device until the user edits it, runs Reset All Data, the operating system clears app data, or the app is removed.

Loss, theft, or failure of the device, deletion of the app, or clearing local storage may cause permanent data loss. Device-access security and operating-system backup preferences remain under the user’s control.

7. Rights and acceptance records

Users can view and correct data through profile and log screens and can delete local user data and acceptance records by running Reset All Data.

The accepted document version, language, and acceptance time are stored on the device as an acceptance snapshot so the consent and acceptance chain can be verified. The User Rights Procedure explains how these rights are exercised.