ChefFit App Privacy Policy

1. About this policy

For privacy questions, requests or complaints about ChefFit, email support@chef-fit.com. Please do not send passwords, verification codes or unnecessary medical records. The person responsible for the service is identified in Operator and contact.

2. Information used by the app

Weight, dietary needs, allergies, food logs and related targets can reveal health information. Only enter information that you want to use for these features. This notice explains processing; reading it or accepting our terms is not, by itself, a separate consent to health-data processing where such consent is required by law.

3. Accounts and local storage

The app requires an account. Unfinished onboarding drafts and some preferences are stored locally before and after sign-in. Clearing app storage, uninstalling the app or changing devices can remove that local information. Device or operating-system backup settings may affect local copies.

When you use an account, ChefFit synchronizes your profile, supported settings, meal plans, favorites, food logs and weight entries with our cloud service. The app also keeps an account-specific local copy and queues changes while offline. Signing out is different from deleting your account. Previous data saved on a device is imported into an account only through the app's explicit import flow.

Authentication sessions are stored on the device so you can remain signed in. ChefFit does not describe this local storage as end-to-end encrypted. Protect your device and sign out on shared devices.

4. Why we use information

We use information to provide and personalize the features you choose, provide and restore your ChefFit Plus subscription, calculate nutrition estimates, keep your plans and diary, synchronize account data, send account confirmation and recovery messages, secure accounts and services, and answer support and privacy requests. We do not use your food or health entries for advertising.

Product analytics: to understand which features are used and where people stop, the App Store version of the app sends a short, fixed list of events to PostHog: onboarding step numbers, the sign-up method, subscription screen views, purchase and restore taps with the chosen plan, which catalog recipe was opened, whether a meal was logged from a recipe or a plan, the number of meals in a generated plan, and screen names. These events are linked to your account identifier only. They never include your name, email, body measurements, weight, targets, allergies, meal contents or food diary. Session recording, automatic tap capture and location lookup from your IP address are turned off.

Crash reports: when the App Store version of the app has an error, it sends a technical report to Sentry. The report contains the error type and the location in the app's code, not your account identifier, email, entries or health information. IP addresses are not stored with crash reports.

Recipe search and filter input is processed in the app and is not sent to analytics. The app has no advertising integration and does not track you across other companies' apps or websites. Infrastructure providers may still process operational and security logs. We do not sell your app information or share it for cross-context behavioral advertising.

5. Service providers and disclosures

Providers receive the information needed for their role. Network requests can include IP addresses, request times, device/browser information and error or security information. We may disclose information when legally required or necessary to investigate abuse, protect rights or respond to a valid legal request, subject to applicable law.

6. International processing and security

The app database is in Ireland, and analytics and crash reports are stored in the EU. RevenueCat processes subscription records in the United States. The operator’s location is listed in Operator and contact. Email delivery, subscription management, support and provider infrastructure may process information in other countries, whose protections may differ from those in your country. Hosting the database in one region does not mean that all technical processing stays in that region. Applicable transfer requirements must also be met for the countries where the service is offered.

The service uses HTTPS and account-based access controls to help protect information. No network or storage system can guarantee absolute security. Contact us if you suspect unauthorized access to your account.

7. Retention and deletion

We retain active account information and synchronized entries while needed to provide the account and your saved features, unless you delete them or request account deletion. There is no automatic short expiry for your food or weight diary. Analytics events and crash reports are kept for the retention periods set in those services. We retain support correspondence only as needed to handle the request, maintain necessary records or meet legal obligations.

You can edit your profile and remove supported food or weight entries in the app. For permanent account deletion, open Profile, then Account & Data, then Delete account, and confirm. Deletion requires a connection and removes your authentication account and associated records from the active service. The device completing deletion also clears that account's app data and resets analytics on that device. Deleting your account does not cancel an App Store subscription; cancel it in your Apple Account subscription settings. Reset app data and Sign out are not substitutes for permanent account deletion.

Deletion cannot directly erase copies on another offline device, exported copies or operating-system backups. Provider backups and technical/security records, where retained, follow their applicable retention schedules and legal obligations; they are not all erased instantly by the in-app action. We do not use retained backup information as an active account. Contact support if you cannot access the deletion option or need help with remaining copies.

8. Your privacy choices and rights

You may change the information you enter, stop using optional features, remove local app data, or delete your account. Removing the app alone does not delete a cloud account.

Depending on applicable law, you may request access to, correction of, a copy of, portability of, or deletion of your information; object to or restrict processing; or withdraw consent for processing that relies on consent. Withdrawal does not undo earlier lawful processing. Send requests to support@chef-fit.com from your account address where possible. We may ask for proportionate verification and will respond within the period required by applicable law. You may also complain to your competent data-protection authority, including Morocco's CNDP where relevant. These rights may have legal exceptions.

9. Age eligibility

ChefFit's current service is for people aged 18 and over. It is not intended for children or teenagers, and its personalized calorie and weight features are not a children's nutrition service. If you believe someone under 18 has provided account or health information, contact support so we can investigate and address it. An App Store content rating does not change this service eligibility rule.

10. Changes and contact

We will update the effective date when this policy changes and give additional notice of material changes where required. Changes that require separate consent will not be authorized merely by changing this page. Contact support@chef-fit.com with questions. See also our App Terms of Use.

Operator and contact

ChefFit is operated by Elatrach Anass, an individual developer based in Morocco.
support@chef-fit.com