← Back to MealTrackr

MealTrackr Privacy Policy

Last updated: 20 September 2026

Who runs MealTrackr

MealTrackr is developed and operated by Hamza el Osrouti under the developer name Hamzie Dev.

I am responsible for the personal data described in this policy.

Your data stays on your device

MealTrackr does not require an account.

Your food logs, water entries, saved foods, favourites, nutrition targets and settings are stored locally on your device. I do not receive or keep a server copy of this data.

The goal calculator also runs locally. Information such as age, height, weight, sex selection, activity level and your goal is only used on your device to calculate your targets.

MealTrackr uses your device language, date and time where needed. It does not request access to your location, contacts or microphone.

Local MealTrackr data is not separately encrypted by the app, so its protection also depends on your device security and backup settings.

Barcode scanning and food search

If you allow camera access, MealTrackr can use your camera to scan barcodes. Photos and video are not stored or uploaded. You can enter a barcode or food manually instead.

Barcode lookup checks your saved foods first. If no local match is found and an online Food Data API is selected, the barcode is sent to that provider. Online food search sends your food-name and brand search terms to your selected Food Data API and combines the results with saved foods.

An online provider receives the request content and normal connection information, such as your IP address. MealTrackr identifies the app making the request but does not attach your name, email address, account ID or device ID to lookups or searches.

You can choose Local only during setup or in Settings to prevent online food requests. The available choices and their specific data practices are explained under Food Data API choices below.

Product contributions

When supported by your selected Food Data API and enabled in MealTrackr, adding or correcting a barcoded product may submit:

Your diary, water history, goals, name, email address and any MealTrackr account identifier are not included. Product information may become public; do not enter personal information into product fields.

You can disable contributions during setup or in Settings. This stops future submissions but does not remove information already submitted to your selected Food Data API. Selecting Local only also disables contributions.

Provider-specific contribution defaults, recipients, authentication and relay processing are explained below.

Backups and deletion

MealTrackr can export your food logs, water entries, saved foods, goals and settings as a readable JSON backup.

Backups are not encrypted by MealTrackr and are not sent to me. You choose where they are saved or shared.

Importing a backup may replace existing MealTrackr data as explained in the app.

Older backups that do not contain water data leave your existing water data unchanged.

Your local data remains on your device until you delete or replace it.

Settings allows you to:

Clearing logs also removes water entries. Deleting saved foods does not remove foods already recorded in your diary.

Your operating system or another service may separately keep backups. Deleting data inside MealTrackr does not remove copies stored elsewhere or product information already submitted to your selected Food Data API.

Analytics and advertising

MealTrackr currently contains no advertising networks, behavioural analytics, tracking pixels or dedicated crash-reporting service.

I do not sell your MealTrackr data or use it to build advertising profiles.

Your device platform or app store may independently process information such as downloads, purchases or diagnostics under its own settings and privacy policy.

Contact and support

If you contact me, I receive your contact address, message and any attachments you choose to send.

This information is used to respond to you, investigate problems and handle privacy requests. It is not used for advertising.

Please avoid sending your diary or other sensitive information unless it is actually needed to resolve your request.

General support correspondence and attachments are deleted within 7 days after the request has been resolved.

The support mailbox is hosted by HEO Systems in the European Union.

Contact:

mealtrackr [@] hamzie.net

Business correspondence

Business correspondence, such as partnership discussions, is handled separately from normal support.

It is kept only for as long as needed to manage the business relationship.

Records that legally have to be retained are kept for the required statutory period and deleted when that requirement ends.

Where GDPR applies, ordinary business correspondence is processed based on legitimate interests in managing business relationships. Information that must legally be retained is processed based on the relevant legal obligation.

Your rights

MealTrackr does not have user accounts and I do not keep a server copy of your diary.

The limited personal data I may process, such as short-lived IP logs or support emails, is handled as described elsewhere in this policy and is deleted according to the stated retention periods.

Where applicable, you can still contact me about any personal data I hold about you or object to its processing.

You can also complain to your local data protection authority.

Your MealTrackr diary stays on your device, so I cannot remotely access, retrieve or delete it. You can manage that data directly in MealTrackr.

For information held by your selected Food Data API provider, your app store or another backup provider, contact that provider directly.

Children

MealTrackr is not intended for children under 13.

If you believe a child has sent personal information directly to me, contact me so I can investigate and address it.

Food Data API choices

You choose the Food Data API during setup or in Settings. The currently available choices are Local only and Open Food Facts.

Local only

Barcode matching and food search use only foods saved on your device. If a barcode is not saved locally, you can add the product manually.

No online barcode lookups, food searches or product contributions are sent. The contribution and relay controls appear switched off, greyed out and disabled. Manual food entry, your diary, water tracking, goals and local backups remain available.

Your data-source choice is saved on your device and included in backups. Contribution and relay preferences are remembered and resume if you select Open Food Facts again. Selecting Local only cancels pending requests where possible and prevents new requests; it cannot recall information already sent.

Open Food Facts

Open Food Facts is the default Food Data API. Barcode lookups and online searches go directly to Open Food Facts, which receives the request content, app identification and ordinary connection information, including your IP address. These lookups and searches do not pass through the MealTrackr relay.

Open Food Facts is a separate service governed by its own privacy policy.

Product contributions

Contributions are enabled by default when Open Food Facts is selected. They can be disabled during setup or in Settings.

The product fields listed under Product contributions are submitted for the public Open Food Facts database. Open Food Facts may retain and publish accepted contributions under its own policies. Disabling contributions or deleting local MealTrackr data does not delete those records.

By default, contributions go through the MealTrackr Contribution Relay. You can disable the relay while leaving contributions enabled; the app then attempts a direct, unauthenticated submission to Open Food Facts, which may reject it. Direct requests expose your connection information to Open Food Facts.

Turning off contributions or the relay does not disable barcode lookup or online search. Choose Local only to disable all Food Data API requests.

MealTrackr Contribution Relay

The MealTrackr Contribution Relay allows product contributions to use a shared Open Food Facts account without putting those credentials inside the app or requiring you to create your own Open Food Facts account.

When enabled, contributions follow this route:

Your device → MealTrackr Contribution Relay → Open Food Facts

The relay receives the product information being submitted together with normal connection information such as your IP address. It validates the request and forwards the contribution to Open Food Facts.

Product submissions and request bodies are not stored. They are processed temporarily in memory and discarded afterwards.

Limited security and network logs may contain:

These logs are only used for security, abuse prevention and troubleshooting. They are not used for advertising, analytics or profiling.

Logs are automatically deleted within 7 days, or earlier when they are no longer needed.

Product contents, request bodies and authentication credentials are not included in these logs.

The relay is hosted by HEO Systems in the European Union.

The relay also sends Open Food Facts a pseudonymous moderation identifier called app_uuid.

This identifier is derived from the connecting network address using a random secret created when the relay starts. It is not a permanent device or account ID and changes when the relay restarts. Multiple users may also share the same identifier when they connect through the same network or proxy.

Your original IP address is not forwarded to Open Food Facts in the submitted product fields or request headers.

Temporary rate-limit counters are kept in memory only and are not written to disk.

If the relay is selected but unavailable, MealTrackr does not silently switch to direct submission.

Legal basis for relay processing

Where GDPR applies, the limited connection information needed by the relay is processed based on legitimate interests in operating the service, preventing abuse and protecting the shared Open Food Facts account.

This information is not used for advertising or profiling.

You can disable contributions or the relay in the app and can contact me if you want to object to this processing.

Future changes

If MealTrackr introduces features such as cloud sync, payments, sponsorships or other new data processing, this policy will be updated before that processing begins.

The updated policy will explain what data is involved, which providers are used, how long information is kept and what choices you have.

Your diary will not automatically be enrolled in cloud sync.

The date at the top of this policy will be updated whenever the policy changes.