Privacy Policy
How NADA handles local app data, website visits, barcode lookups, purchases, sharing and support messages.
Last updated
This policy covers the NADA website and mobile app. It explains which information stays on your device and when an external service receives personal data.
Who is responsible
NADA TECHNOLOGIES LTD is the data controller for the personal data described in this policy where NADA decides how and why it is used.
NADA TECHNOLOGIES LTD is registered in England and Wales under company number 17108376. Its registered office is 71-75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ. Contact founder@notadietapp.com.
App data kept on your device
NADA stores food logs, nutrition history, daily totals, goals, custom foods, saved barcode foods, local barcode corrections, portions, favourites, recipes, preferences and settings on your device. NADA TECHNOLOGIES LTD does not receive this information through an app account or cloud nutrition service.
You can export your records or use the app's full local deletion control. NADA cannot recover locally deleted records.
If device backup is enabled, Apple or Google may include app data in an operating-system backup. NADA does not receive or control those backups. Use your device or platform settings to manage them.
Website visits
The website is a static site delivered by Render through its content delivery network. Your browser sends technical request data such as your IP address, browser and device information, requested path and request time so the site can be delivered and protected. Render's static-site service does not provide NADA with request logs.
The website does not use advertising trackers or general audience analytics. It does not set advertising or analytics cookies. A light or dark theme choice is saved in your browser's local storage until you clear it.
Support messages
If you email NADA, we receive your email address, message, attachments and related delivery information. We use this information to answer you, keep a record of the issue, protect the service and deal with legal claims where necessary.
Do not send payment card details, passwords, full nutrition exports or medical records. If you choose to include health information, we use only the minimum needed to answer your request. You may withdraw permission for that use by contacting us, although this may limit the help we can provide.
Barcode lookups
When you scan a barcode, NADA may send the barcode and normal internet request data to Open Food Facts to retrieve product information. A product image may also be retrieved for display. NADA does not send food logs, goals, recipes, nutrition history or local corrections with a barcode request.
Purchases and restores
Apple or Google processes the payment through your store account. NADA does not receive your payment card details.
RevenueCat manages product offerings, purchase validation, Pro entitlement and restore requests. It may receive an anonymous app user identifier, purchase history, receipt and transaction data, product and entitlement details, app version, store, platform, locale and country information needed for those purposes. NADA does not send food logs or other nutrition data to RevenueCat as customer attributes.
Purchase information may also be used in RevenueCat's customer history and purchase reports so NADA can manage entitlements and understand purchase performance.
Links, photos, exports and recipe sharing
Links open through your browser. The browser and destination receive the information normally sent with a web request.
If you choose a saved image to import a recipe QR code, the operating system provides the selected image to NADA. Where the platform supports it, NADA uses a system picker instead of asking for access to your whole photo library.
Exports and shares begin only when you choose them. NADA gives the selected file or content to the system share sheet. The app or person you choose then controls the copy it receives.
A NADA recipe QR link stores the recipe in the link fragment. Browsers do not normally send that fragment to the website when loading the fallback page. A person who receives the QR code or link can keep and copy its contents.
What NADA does not collect
NADA does not provide a cloud account for nutrition history. It does not store nutrition records on a NADA server, sell personal data, use advertising networks, or include a general analytics or crash-reporting SDK.
Why we use personal data
We use the following UK data-protection bases:
| Purpose | Lawful basis |
|---|---|
| Delivering and protecting the website | Legitimate interests in running a secure public website |
| Answering support messages and keeping issue records | Legitimate interests in supporting NADA and establishing or defending legal claims |
| Using health information you deliberately include in a support message | Your explicit consent, which you may withdraw |
| Validating purchases, providing Pro and restoring access | Performance of the purchase contract and legitimate interests in preventing fraud and managing entitlements |
| Keeping records required by tax, accounting or consumer law | Legal obligation |
| Running a barcode lookup, opening a link, choosing a photo, exporting or sharing at your request | Performance of the service you asked NADA to provide |
You do not have to send a support message. We need an email address and enough detail to reply. Purchase and entitlement data is required if you choose to buy or restore Pro.
NADA does not make decisions about you that have legal or similarly significant effects using automated processing.
Who receives personal data
Depending on the feature you use, recipients may include:
- Render for website delivery and security;
- NADA's email provider for support messages;
- Open Food Facts for barcode requests;
- Apple, Google and RevenueCat for purchases and restores;
- an app, service or person you choose through a link or share action; and
- professional advisers, insurers, regulators, courts or public authorities where reasonably necessary or required by law.
Where a supplier processes personal data for NADA, we require it to use the data for the agreed service and apply appropriate security and data-protection terms. Apple, Google, Open Food Facts and destinations you choose may also act as independent controllers under their own privacy policies.
Processing outside the UK
Some providers process personal data outside the UK. RevenueCat stores customer data in the United States, and its data-processing terms incorporate the UK Transfer Addendum for restricted transfers. Other transfers use UK adequacy regulations or approved contractual safeguards, such as the UK International Data Transfer Agreement or UK Transfer Addendum, where required. Contact us for information about the safeguard used for a particular provider.
Provider information is available from Render, Open Food Facts, RevenueCat, Apple and Google.
How long information is kept
- Local app data remains on your device until you delete it. Backup copies follow your platform's backup settings and retention rules.
- The website theme preference remains in browser local storage until you change it or clear browser data.
- Routine support correspondence is kept for up to 24 months after the issue is closed. Relevant records may be kept for up to six years where needed for a complaint, transaction, legal claim or legal obligation.
- NADA keeps purchase and entitlement records for as long as needed to provide access, handle a purchase issue, prevent fraud and meet legal obligations. Apple, Google and RevenueCat also keep records under their own terms and retention rules.
- NADA does not keep website request logs supplied by Render for this static site.
When a retention period ends, we delete or anonymise information unless the law requires it to be kept.
Deletion and permissions
Use NADA's full local deletion control to remove nutrition records from the device. Manage operating-system backups through your Apple or Google settings. Deleting local data or uninstalling the app does not cancel a store subscription.
You can withdraw photo access through device settings and can stop future barcode lookups, links, exports and shares by choosing not to start those actions. For personal data held by NADA or RevenueCat on NADA's behalf, email founder@notadietapp.com. We may need information that identifies the relevant purchase or anonymous app user record.
Your data-protection rights
UK data-protection law may give you rights to access, correct, erase or restrict personal data, receive portable data, and object to its use. The rights that apply depend on the information and lawful basis. Contact founder@notadietapp.com to make a request. We may ask for information needed to verify your identity.
Your right to object
You may object to processing based on legitimate interests. Tell us what you object to and why. We will stop unless there are compelling lawful grounds to continue or the information is needed for legal claims. You can always object to direct marketing. NADA does not currently send marketing email.
You may complain to the Information Commissioner's Office or another supervisory authority that applies where you live.
Children
NADA is not directed at children. A parent or guardian should review its use and store settings where the user cannot enter these terms or make privacy choices under local law. Contact us if you believe a child has sent personal data to NADA.
Security
NADA limits the personal data it receives and uses suppliers with contractual and security commitments. Internet transmission and device storage still carry risk. Keep your device, store account and exports secure.
Changes to this policy
We update this page when NADA's features, providers or legal duties change. The date above shows the latest revision. We will give additional notice where the law requires it.
Contact
Questions? Email founder@notadietapp.com.