Privacy Policy

Version 2026-04-26.v2 · Effective 26 April 2026

At a glance.
  • You give us your email, a password, and photos / descriptions of your meals. We use these to give you AI-generated nutritional feedback and a daily score.
  • Your photos and descriptions are stored by us in the UK / EU, on AWS, and analysed by OpenAI under their API business terms - not used to train OpenAI's models.
  • We do not sell your personal data, do not share it with advertisers, and do not use it to train any AI model.
  • You can export your data from Profile → Export, delete your account from Profile → Delete account, and contact our Data Protection Officer at privacy@aliqa.app.
  • Your health data belongs to you, not to us.
  • The score Aliqa shows you is AI-generated and approximate. You can edit any meal in the App and the score will recompute - that is your right to human review of automated decisions under UK GDPR Article 22.

1. Scope

This Policy covers the Aliqa Food-Log iOS app, the universal-link host at app.aliqa.app, the auth SPA at login.aliqa.app, and the marketing site at www.aliqa.app. It is written to satisfy:

  • Apple App Store Review Guidelines 5.1 (privacy) and 5.1.2 (data use and sharing);
  • the UK GDPR and the Data Protection Act 2018;
  • the EU GDPR (Regulation (EU) 2016/679), with French-specific notices expected by the CNIL;
  • Singapore's Personal Data Protection Act 2012 (PDPA), since Singapore is a launch market;
  • the California CCPA / CPRA for users in California; and
  • the Privacy and Electronic Communications Regulations 2003 (PECR) in the UK and the EU ePrivacy Directive (2002/58/EC).

This Policy is published in English; the English version is the legally governing version.

2. Who we are (the controller)

The data controller for the Service is Agile Projects Ltd, a company registered in England and Wales, trading as "Aliqa". Our registered office is at Langley House, 53 Theobald Street, Borehamwood, England, WD6 4RT, United Kingdom; you can reach the privacy team at privacy@aliqa.app (privacy-specific) or support@aliqa.app (general).

RoleContact
UK / EU privacy team (and Article 27 representative if later required)privacy@aliqa.app
Data Protection Officer (appointed voluntarily, given that we process special-category health data on a structured basis)privacy@aliqa.app, addressed to "Aliqa DPO"
Singapore PDPA Data Protection Officer under Section 11 of the PDPAprivacy@aliqa.app, addressed to "Aliqa DPO"
California CCPA / CPRA contactprivacy@aliqa.app

3. What we collect, why, and the lawful basis

We organise the personal data we hold about you into Default data (necessary to operate the Service for you) and Optional data (only if you choose to provide it).

3.1 Default account data

DataPurposeLawful basis (UK / EU GDPR)
Email addressAccount identity, login, transactional email, password resetContract performance - Art. 6(1)(b)
Password (stored as a bcrypt hash; never in plaintext)Authenticate youContract performance - Art. 6(1)(b)
Time zone, language preferenceShow the day boundary correctly, localise the UIContract performance - Art. 6(1)(b)
Legal-acceptance record (verbatim disclaimer text, Terms / Privacy / disclaimer version, age-attestation timestamp)Evidence of informed consentLegal obligation - Art. 6(1)(c); legitimate interests - Art. 6(1)(f)
Sign-up code (if used)Controlled beta accessContract performance - Art. 6(1)(b)
Admin scopes (internal staff only)Administrative authorisationLegitimate interests - Art. 6(1)(f)

3.2 Default food-log data - special-category data

The food-log data set inevitably reveals information about your diet, eating habits, and inferred metabolic patterns. Under UK GDPR / EU GDPR Article 9, dietary data combined with the AI-generated daily score is treated as data concerning health because, taken together, it can suggest a health condition or wellbeing trajectory. We therefore process this data only with your explicit consent under Article 9(2)(a) at signup.

DataPurposeLawful basis
Meal photos you uploadInput to the AI pipeline; your visible meal historyArticle 6(1)(b) contract + Article 9(2)(a) explicit consent
Manual meal descriptions and correctionsInput to the AI pipeline; your editable recordArticle 6(1)(b) + Article 9(2)(a)
AI-generated food items, tags, portion descriptorsCore output. You can edit any of these at any time; day scores recompute on edit. This is how we satisfy the right to contest an automated decision under UK GDPR Article 22.Article 6(1)(b) + Article 9(2)(a)
AI-generated daily scores, weekly reviews, recommendationsProvide the ServiceArticle 6(1)(b) + Article 9(2)(a)
Clarification questions and your answersImprove accuracy of the analysis for the meal you loggedArticle 6(1)(b) + Article 9(2)(a)
Frequent-foods / meal-guide preferencesPersonalise the experienceArticle 6(1)(b)
Streaks, badges, daily-score historyEngagement featuresArticle 6(1)(b)

You can withdraw your Article 9 consent at any time by deleting the relevant content (or your account) in Profile → Delete. Withdrawal does not affect the lawfulness of processing before withdrawal.

3.3 Notifications and email preferences

Push-notification tokens (APNs) if you opt in; email preferences (weekly review, daily score, meal reminders). We send transactional email (verification, password reset, weekly review, trial-end reminder, renewal reminder) to fulfil the contract. You can disable optional notifications in Profile → Notifications and Profile → Emails.

DataPurposeLawful basis
APNs push tokenDeliver opted-in notificationsConsent - Art. 6(1)(a); UK PECR; EU ePrivacy Directive
Marketing email opt-inSend product updates if you opted inConsent - Art. 6(1)(a)
Transactional email (verification, password reset, billing reminders)Fulfil the contract / comply with consumer-law reminder dutiesContract - Art. 6(1)(b); legal obligation - Art. 6(1)(c)

3.4 Subscription and billing data

When you subscribe through the Apple App Store, Apple processes the payment. We do not receive your credit-card number or full payment details. Apple shares with us a subscription status (active / trial / expired / cancelled), a receipt / transaction identifier tied to your Apple ID, and billing-lifecycle events (renewal, cancellation, refund, billing issue). We keep these so we know whether to grant you access. Lawful basis: contract performance - Art. 6(1)(b); legal obligation (tax / accounting) - Art. 6(1)(c).

3.5 Device and technical data

DataPurposeLawful basis
IP address, approximate region (recorded at our API gateway for a short period)Security, abuse prevention, geo-routingLegitimate interests - Art. 6(1)(f)
App version, OS version, device modelSupport and crash diagnosisLegitimate interests - Art. 6(1)(f)
Endpoint, latency, AI token-cost telemetry (no payload)Operate the Service efficientlyLegitimate interests - Art. 6(1)(f)

3.6 Data-export and deletion-history audit

We keep a short audit record of data-export and account-deletion events to evidence compliance.

3.7 What we do not collect

  • We do not request HealthKit, Motion & Fitness, Location, Contacts, or Calendar access. If we do in future, we will ask you separately and treat any HealthKit-derived data as Article 9 data; we will not use HealthKit data for marketing or share it with third parties.
  • We do not use advertising SDKs, third-party analytics that fingerprint users across apps, Facebook Pixel, Google Ads, or any IDFA-based attribution.
  • Our App Store "Data Used to Track You" declaration is None.
  • We do not process race or ethnicity, religious beliefs, sexual life or orientation, political opinions, trade-union membership, or genetic data.

3.8 EXIF metadata in your photos

Photos taken by your phone may contain EXIF metadata - including GPS coordinates, capture time, and device model. Our App strips GPS coordinates from photos before they leave your device; we keep the capture timestamp because it is needed to assign a meal to the correct day. If you upload a photo that we detect is not a photo of food or drink, we may delete it without notice, in line with §6 of our Terms of Use.

4. Sub-processors and where data is stored

We work with a small number of sub-processors. Each is bound by a written data-processing agreement (UK GDPR Article 28, equivalent EU/EEA, PDPA Section 26).

Sub-processorCountry of establishmentActivityData categoriesTransfer safeguard
Amazon Web Services EMEA SARL Luxembourg (operations in UK / EU regions) Hosting, RDS database, S3 meal-image storage, API gateway logging Account data, food-log data, photos, technical logs Stored in UK / EU; no transfer outside UK / EEA in the default flow
OpenAI Ireland Limited (and OpenAI OpCo, LLC for API processing) Ireland / United States Vision analysis (GPT-4.1 mini), tagger, scoring, weekly-review text generation. API only - OpenAI does not train its models on API inputs or outputs by default. Photos and meal descriptions; AI prompt/response content; an internal user identifier (not your email) EU‑US Data Privacy Framework; SCCs (2021/914) + UK IDTA Addendum
Apple Distribution International Limited Ireland (App Store EU); USA (APNs) App Store delivery, StoreKit billing, Sign in with Apple (if used), push notifications via APNs Apple ID transaction identifier, push token Apple-controlled; Apple's own Privacy Policy applies to data Apple holds about you
Transactional email provider UK / EU Sends verification, password reset, weekly review, trial-end and renewal reminders Email address, message content, delivery telemetry Stored in UK / EU

A change to this list is a material change to this Policy; we will notify you in advance under §10.

We may also disclose limited information to: professional advisers (lawyers, accountants, auditors) under confidentiality; public authorities if required by law or to protect rights, property, or safety; or a successor entity in a merger, acquisition, or insolvency (your rights will not be materially reduced).

We do not share your personal data with advertisers, data brokers, or any third party for their own marketing purposes.

5. How long we keep data

CategoryRetention
Account record (email, preferences)Until you delete your account, plus 30 days disaster-recovery window
Meal photos (S3) and food entries (DB)Until you delete them, or within 30 days of account deletion
AI analyses, day scores, weekly reviewsSame as the underlying meal
Clarification tasks, reprocess jobsUntil completed or abandoned, then 90 days
Transactional-email delivery logs30 days
API access logs30–90 days (security)
Marketing email preferences (where you opted in)Until you opt out, plus 30 days
Push-notification tokenUntil invalidated by Apple, or until you opt out
Billing records received from Apple7 years (UK / EU tax & accounting)
Data-export / deletion audit records2 years
Inactivity ruleIf your account has had no activity for 10 years, we will delete or fully anonymise it on a routine basis.

Aggregated, fully anonymised statistics (from which you cannot be re-identified, even by combination with other data we hold) may be kept indefinitely to improve the Service. We treat pseudonymised data (data linked to an internal user ID but stripped of direct identifiers) as personal data and apply the retention rules above.

6. Your rights

Wherever you live, we will honour the following requests to the extent we reasonably can:

  • Access - use Profile → Export data in the App for a ZIP of your data, or email privacy@aliqa.app.
  • Rectification - edit meal entries directly in the App; email us for account-level corrections.
  • Erasure - Profile → Delete account. You will be asked to re-enter your password. Your sessions are revoked immediately, your photos and food entries are scheduled for deletion, and the user row is tombstoned. Note: you must also cancel your iOS subscription separately in iOS Settings → Subscriptions; deleting the account does not stop Apple billing.
  • Restriction / objection - email privacy@aliqa.app.
  • Portability - the Export ZIP contains JSON files suitable for import elsewhere.
  • Withdraw consent - wherever we rely on consent (push notifications, marketing email, Article 9 health data, analytics cookies on the marketing site), you can withdraw it without affecting the lawfulness of prior processing.
  • Right to human review of automated decisions (UK / EU GDPR Article 22). The daily Aliqa score is solely automated and has no legal effect on you, but it is a significant output of the Service. You can (a) edit any input meal at any time and force a recompute, (b) ask us to manually review your score by emailing privacy@aliqa.app with a description and the day in question, and (c) ask us to delete the score for any day.

We will respond within 30 days (extendable by a further two months for complex requests, with notice). We may need to verify your identity before responding. If we refuse or restrict your request, we will tell you why and how to complain. You can complain to your local data-protection authority - see §6.2.

6.1 Singapore (PDPA)

If you are in Singapore, Agile Projects Ltd is the organisation responsible for your personal data under the PDPA. You have an access right (Section 21), a correction right (Section 22), and the right to withdraw consent to processing that relied on consent. You can complain to the Personal Data Protection Commission (pdpc.gov.sg). PDPA contact: privacy@aliqa.app (addressed to "Aliqa DPO"), Agile Projects Ltd, Langley House, 53 Theobald Street, Borehamwood, England, WD6 4RT, United Kingdom.

6.2 UK / EEA / France

Local supervisory authorities: UK - the Information Commissioner's Office; France - the CNIL; other EEA states - your national supervisory authority. French users can exercise their right to give post-mortem instructions regarding their personal data under Article 85 of the French Loi Informatique et Libertés; contact privacy@aliqa.app.

6.3 California (CCPA / CPRA)

You have rights under the CCPA / CPRA including the right to know, to delete, to correct, and to opt out of "sale" or "sharing". We do not sell or share personal information within the CCPA's meaning. Exercise rights at privacy@aliqa.app. We will not discriminate against you for exercising them. We honour the Global Privacy Control signal sent by your browser as a request to opt out of any future "sharing".

6.4 Children

The Service is not directed to children under 18 and we do not knowingly collect data from them. At sign-up we ask you to confirm you are at least 18. If you believe a child has signed up, email privacy@aliqa.app and we will remove the account.

7. Security

  • Passwords are hashed using bcrypt; we never see or store your plaintext password.
  • All traffic between the Apps and our API uses HTTPS / TLS 1.2 +.
  • Meal photos are stored in a private S3 bucket accessible only via short-lived pre-signed URLs scoped to your account.
  • Data is encrypted at rest in S3 and in our managed database, and encrypted in transit between every component.
  • Access to production systems is limited to a small number of named engineers via scoped IAM roles and multi-factor authentication.
  • Internal admin access uses SSO with MFA and IP-allowlisted entry points; production databases are configured so that engineers cannot directly read user-app content in normal operation.
  • We run automated vulnerability scanning and WAF rules at our API gateway.
  • Our team receives privacy and security training on joining and at least once a year.
  • We will notify affected users and the relevant supervisory authority of any security incident that is likely to result in a risk to your rights and freedoms, within 72 hours as required by UK / EU GDPR Article 33.

We commit reasonable, industry-standard technical and organisational measures to protect your personal data, but no internet service can be guaranteed completely secure.

8. Cookies and similar technologies

The marketing site www.aliqa.app uses Google Analytics 4 for aggregate traffic measurement only after you opt in via the consent banner; the default is reject all. The auth SPA and product SPAs use localStorage and a root-domain cookie on .aliqa.app for authentication - these are strictly necessary to keep you logged in across our subdomains. The iOS app does not set browser cookies; auth tokens are kept in the iOS Keychain. See our separate Cookies notice for the full list.

9. International transfers and the AI pipeline

Our primary infrastructure is in the UK / EU. Limited transfers to the United States occur for: meal analysis by OpenAI (the AI sub-processor that powers the vision, tagging, scoring, and weekly-review steps); delivery by Apple (App Store, APNs, StoreKit); and some support tooling.

RegionTransfer safeguard
UKUK Government data-bridge for the EU‑US Data Privacy Framework; UK International Data Transfer Addendum (IDTA) to the EU Standard Contractual Clauses; or the standalone UK IDTA
EEA / FranceEU‑US Data Privacy Framework; Standard Contractual Clauses (Module 2 / Module 3 as applicable); supplementary measures (encryption, identifier minimisation)
SingaporePDPA's transfer-limitation obligation (Section 26), met through written contracts with each sub-processor requiring a standard of protection comparable to that under the PDPA
Other countriesData is processed by the sub-processors listed in §4; by using the Service you consent to the international transfer described here, to the extent consent is required in your country

9.1 How the AI pipeline handles your data

When you upload a meal photo or description we send it to OpenAI through the OpenAI API:

  1. Your photo or description plus an internal user identifier (not your email) are sent over HTTPS / TLS to the OpenAI API.
  2. OpenAI processes the request and returns the analysis.
  3. OpenAI's API business terms state that OpenAI does not train its foundation models on API inputs or outputs. OpenAI may retain API content for up to 30 days for trust-and-safety purposes, after which it is deleted from OpenAI's systems.
  4. We do not use Your content (photos, food entries, scores, tags, recommendations) to train any AI model - ours or anyone else's.
  5. We may modify, replace or extend our AI sub-processor; doing so is a material change to this Policy under §10.

If you ever see an AI output you want a human to review, edit the meal in the App (see §6) or email privacy@aliqa.app.

10. Changes to this Policy

We post the new version at /legal/privacy.html and update the "Effective" date. For material changes - for example a new sub-processor that materially changes where your data goes, a change of lawful basis, a change in retention periods, a change in your rights, or a change that adds AI training on your data - we will: give at least 30 days' advance notice in the App and by email; highlight what has changed; where required by law, ask you to re-accept at next sign-in; and give you a window to delete your account without penalty before the change takes effect.

We bump the version string on every change so you always know which wording you accepted.

11. Marketing, profiling and "no surprises"

  • We do not use your meal photos, descriptions, scores or any health-derived data for marketing - to anyone, ever.
  • We do not profile users for advertising.
  • We do not make decisions with legal or similarly significant effect on you solely by automated means under UK GDPR Article 22(1). The daily Aliqa score is informational and educational and you can edit or delete the inputs at any time.
  • We do not use dark patterns to obtain consent. Reject-all is offered with the same prominence as Accept on our marketing-site cookie banner.

12. Contact

Privacy questions and rights requests: privacy@aliqa.app. General support: support@aliqa.app. Postal: Agile Projects Ltd (Aliqa DPO), Langley House, 53 Theobald Street, Borehamwood, England, WD6 4RT, United Kingdom.

If you are not satisfied with our response, you can complain to: in the UK, the Information Commissioner's Office at ico.org.uk; in the EEA, your national supervisory authority (in France, the CNIL at cnil.fr); in Singapore, the Personal Data Protection Commission at pdpc.gov.sg; in California, the California Privacy Protection Agency at cppa.ca.gov.

© 2026 Agile Projects Ltd (Aliqa). Version 2026-04-26.v2. Terms · Cookies · Medical Disclaimer.