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.

If weekly planning is used, the shopping day, chosen template, targets and the profile preference needed for calculation at plan creation, seven days of meals and amounts, shopping list, preparation allocations, user-created foods and macros, and earlier plan revisions are stored on the device. Plans created earlier may contain a broader profile copy.

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.

Weekly plan data is processed automatically on the device to generate meal, shopping, and preparation suggestions from the chosen template and targets, recalculate remaining meals after food changes, and preserve history. Ordinary profile and preference data needed to provide the app features chosen by the user is processed under Article 5(2)(c) of Turkish Law No. 6698; health-related special-category data is processed under Article 6(3)(a) and the separate Explicit Consent for Health Data.

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 for as long as it is needed for the relevant feature. Replacing or removing an ingredient from a weekly plan does not erase past days or earlier plan revisions; these are kept to show plan and consumption history correctly. Delete Account & Data removes weekly plans, previous revisions, custom foods, and other local user records. Operating-system data clearing or app removal may also delete local records.

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 profile/account data, app data, and acceptance records by running Delete Account & Data.

The privacy-notice acknowledgement and separate acceptance/consent decisions for terms and health documents are stored on the device with the relevant document version, language, and time. The User Rights Procedure explains how these rights are exercised.