Privacy Policy

1. Information We Collect

When you use IntakeLens, we collect information you provide directly and information generated as you use the service. Categories include:

  • Account information: email address, authentication identifier (user ID), and (for social sign-in) name and profile picture from Google or Apple
  • Profile information: name, age, sex, height, weight, activity level, dietary preferences, allergies, health goals, and — for users who enable medication reminders — medication names, dosages, schedules, and adherence logs (taken / missed / skipped). Medication data is treated as sensitive health data and is never sent to AI providers; it is stored only in your private account row with row-level security.
  • Health and body metrics: weight history, biometric measurements (height, age, sex), activity level, and explicit health-data consent status recorded before AI personalisation
  • Usage content: food diary entries, recipes, favourites, uploaded food photos and videos, voice recordings used for voice logging, planned meals, and achievements
  • App activity: in-app search history (food and recipe queries), feature usage, and engagement metrics
  • Subscription and payment information: subscription tier, renewal date, plan changes, and a transaction identifier from our payment processor (Paddle). Full card numbers are entered into Paddle's checkout overlay and never reach IntakeLens systems — we are out of PCI-DSS scope for cardholder data.
  • Support content: tickets and messages you send through the Contact page
  • Device and technical data: browser or device type, language, time zone, and rate-limiting metadata

2. How We Use Your Information

We use your information to:

  • Provide personalised nutrition tracking, meal plans, and recommendations
  • Analyse food photos and videos using AI to estimate nutritional content
  • Calculate calorie and macro targets based on your profile
  • Track your progress, streaks, and achievements
  • Process subscription payments and deliver paid features
  • Send reminders and notifications you have opted into
  • Respond to support requests and improve service quality and AI accuracy

3. Data Storage & Security

Your data is stored in a managed PostgreSQL database with row-level security policies that ensure each account can access only its own data. All data is encrypted in transit (TLS) and at rest. Uploaded images and audio are stored in secure object storage with access controls. Before any food photo, voice recording, or text prompt is sent to an AI provider, identifying EXIF metadata (including GPS and device information) is stripped server-side, and account identifiers such as your user ID, email address, and name are never included in the prompt — AI providers receive only the content needed to produce a nutritional estimate. Explicit consent is recorded before health and biometric data is used for AI-driven recommendations, and this consent can be withdrawn at any time in Settings. If we become aware of a security incident that affects your personal data, we will notify the Saudi Data & AI Authority (SDAIA) within the period prescribed by the PDPL Implementing Regulations where the incident meets the notification threshold, and we will notify affected users without undue delay where the incident is likely to result in significant harm — together with any steps you can take to protect yourself.

4. Service Providers (Named Sub-processors)

IntakeLens uses the following named third-party service providers to operate the app. Each provider processes data under its own privacy policy and, where applicable, a data processing agreement with us. None of these providers is authorised to use your data for its own marketing or profiling purposes.

  • Supabase Inc. (Frankfurt, Germany) — managed PostgreSQL database, authentication, object storage for photos and voice recordings
  • Cloudflare Inc. (global edge) — content delivery network, serverless API functions, DNS, and DDoS protection
  • PostHog Inc. (EU region — Frankfurt, Germany) — product analytics used to measure how visitors move through signup, onboarding, and trial-start so we can identify and fix friction points; receives event names, page paths, UTM parameters, and after sign-in the Supabase user ID; configured to capture only the explicit events we instrument (no autocapture, no session replay, no cross-site tracking)
  • OpenRouter Inc. (United States) — AI gateway used to route photo-analysis, voice-to-log, meal-suggestion, recipe-generation, and daily-insight requests to downstream model providers
  • Google LLC / Gemini (United States) — vision and text models invoked through OpenRouter for food-photo and voice-log analysis
  • OpenAI LLC (United States) — language models invoked through OpenRouter for meal suggestions and text generation
  • Anthropic PBC (United States) — Claude models invoked through OpenRouter for higher-quality insights (Pro tier)
  • Meta Platforms, Inc. (United States) — Llama-family open-weight models invoked through OpenRouter as part of the multi-model fallback for meal suggestions and recipe generation
  • Paddle.com Market Ltd (United Kingdom / United States) — merchant of record for web subscription checkout, invoicing, and tax handling
  • Spoonacular (United States) — recipe and nutrition data API used for the in-app blog; receives non-personal recipe data requests
  • USDA FoodData Central (United States) — public food-nutrition database; receives anonymous search queries
  • Open Food Facts (France, community-run) — public food-product database; receives anonymous barcode and search lookups
  • api.cobalt.tools (community-run) — used to convert a user-submitted recipe video URL into a downloadable file; only the submitted URL is sent, with no account identifier
  • Soro (trysoro.com, United States / European Union) — embedded community blog provider used to render featured nutrition articles inside the app; receives anonymous article-fetch requests including IP address, user agent, and the embed token configured for this app
  • Google LLC / Apple Inc. (sign-in only) — authenticate you when you choose "Sign in with Google" or "Sign in with Apple" and share a minimal profile (email, name, avatar) with us

5. Data Sharing

We do not sell, rent, or share your personal information with third parties for their own marketing purposes. We disclose data only to the service providers listed above, where required by law, or in connection with a business transfer (merger, acquisition, or asset sale) subject to notice to you.

6. Your Rights

Subject to the privacy laws that apply where you live, you have the right to:

  • Access and export your data (available in Settings → Data Export)
  • Correct inaccurate information in your profile
  • Delete your account and all associated data (Settings → Delete Account)
  • Withdraw consent for optional processing at any time
  • Object to or restrict certain processing of your personal data
  • Lodge a complaint with the competent data protection authority. Because we are based in Saudi Arabia and voluntarily comply with the Saudi Personal Data Protection Law (PDPL), you may direct complaints to the Saudi Data & AI Authority (SDAIA) — see https://sdaia.gov.sa for contact and complaint information. Residents of jurisdictions outside Saudi Arabia (including the EU/UK) may also have rights under their local data protection law and may complain to their national authority. You can exercise any of these rights by emailing [email protected] or through the Contact page in the app, and we will respond within 30 days.

7. Cookies & Local Storage

We use cookies and local storage in three categories. (1) Necessary — required for sign-in (Supabase Auth session), checkout (Paddle), and remembering your preferences (language, theme, units, dashboard visibility). These are always on; the app cannot function without them. (2) Analytics — product analytics (PostHog, EU region) measure how the app is used and where users encounter friction. PostHog runs through a same-origin reverse proxy at /ingest so requests stay first-party; we capture pageviews, custom events, and Core Web Vitals, never advertising identifiers, and do not build cross-site behavioural profiles. (3) Marketing — Google Ads tag fires conversion pings when you complete signup or subscription, used only to measure ad campaign effectiveness. You control Analytics and Marketing through the cookie banner shown on first visit and the "Cookie preferences" entry in Settings → About. We respect the browser "Do Not Track" signal and apply Consent Mode v2 regional defaults: visitors in the EEA, UK, and Switzerland start with all optional categories denied until they opt in; visitors elsewhere start with optional categories granted unless they opt out.

8. Data Retention

We retain your data for as long as your account is active. Specific retention periods are:

  • Diary entries, recipes, photos, voice recordings, and profile data: until you delete your account
  • Support tickets: up to 24 months after resolution, then deleted
  • Subscription and payment records: retained for the period required by applicable tax and financial regulations (typically 7 years)
  • Food-search cache: search query text is cached for up to 180 days with no account identifier attached, to speed up common lookups
  • Technical logs and rate-limit records: up to 90 days
  • When you delete your account, personal content is removed within 30 days; legally required records (payment history, abuse reports) are retained for the minimum period prescribed by law

9. International Data Transfers (Saudi PDPL + GDPR)

IntakeLens is operated by a data controller based in Saudi Arabia who voluntarily complies with the Saudi Personal Data Protection Law (PDPL), while our cloud and AI infrastructure operates globally. By using the app you are informed that your personal data will be transferred outside Saudi Arabia — specifically to Germany (Supabase / Frankfurt), the United States (OpenRouter, OpenAI, Anthropic, Paddle, Spoonacular, USDA, Soro), the United Kingdom (Paddle), and wherever else our named sub-processors operate — and is processed under safeguards aligned with Saudi PDPL Article 29. These safeguards include: (a) your explicit informed consent obtained at onboarding and retained in the account record; (b) purpose-limited processing (food analysis and account operation only, no secondary or advertising use); (c) contractual safeguards with each sub-processor equivalent to the PDPL Implementing Regulations; and (d) technical measures including TLS 1.3 in transit, encryption at rest, EXIF and PII stripping before AI dispatch, and row-level security at the database layer. Where the transfer additionally involves personal data of EU or UK residents, we rely on Standard Contractual Clauses and the supplementary safeguards described in our Transfer Impact Assessment, available on request at [email protected].

10. Children

IntakeLens is intended for users aged 18 and over and is not directed to children. We do not knowingly collect personal information from anyone under 18, and onboarding requires a date of birth that places the account holder at 18 or older. We do not currently use document-based age verification; if we discover or have reason to believe an account holder is under 18, we will suspend the account and delete the associated data within 30 days. If you believe a minor has created an account, please contact us at [email protected] and we will act promptly.

11. Changes to this Policy

We may update this Privacy Policy from time to time. For material changes that affect how we use your personal data, we will update the "Last updated" date above and post a notice on this page; we encourage you to review this policy periodically, and we will surface a notice in-app where feasible. Continued use of the service after we publish a material change constitutes acceptance of the updated policy; if you do not agree, you may delete your account at any time.

12. Contact & Data Controller

IntakeLens is operated by SoftSSlution, a sole-proprietor developer based in Saudi Arabia, which acts as the data controller for personal data processed through the app and voluntarily complies with the Saudi Personal Data Protection Law (PDPL). If you have questions about this Privacy Policy, wish to exercise your rights, or need to report a data incident, contact us at [email protected] or through the Contact page inside the app.

13. Lawful Bases for Processing

Where a privacy law such as the EU GDPR, UK GDPR, or Saudi PDPL applies to our processing of your personal data, we rely on the following lawful bases:

  • Your explicit consent — for health and biometric data used in AI personalisation, for push notifications, and for any processing of sensitive data
  • Performance of a contract with you — to create and maintain your account, deliver paid features, and provide the core food-logging service
  • Our legitimate interests — to prevent fraud and abuse, secure the service, measure aggregate service health, and improve AI accuracy (we balance these interests against your rights before relying on them)
  • Compliance with a legal obligation — to retain payment and tax records and to respond to lawful requests from authorities

14. Automated Decisions & AI

AI-generated nutrition estimates, meal plans, daily insights, and recipe extractions are advisory only. You always review, edit, and approve what is logged to your diary. We do not use AI to make fully automated decisions that produce legal effects or similarly significant effects on you (for example, we do not use AI to set your prices, approve or deny your subscription, or profile you for advertising). If you disagree with an AI estimate, you can correct or delete it at any time from the diary.

15. Affiliate Links & Amazon Associates

IntakeLens participates in affiliate marketing programs, which means we may earn a commission if you purchase products through links on our platform. As an Amazon Associate, IntakeLens earns from qualifying purchases. These commissions help support the development of the app and do not affect the price you pay.