←

Privacy Policy

Effective date: April 30, 2026

Lad is a calorie and macro tracking app that helps users log food through typed descriptions, scans, barcode lookups, menu scans, and saved items. This Privacy Policy explains what information Lad collects, how it is used, where it is stored, and which third-party services may receive information when the app is used.

1. Information We Collect

Account information

Lad requires account sign-in. When you create or access an account, Lad may collect your email address, authentication information, and account identifiers provided through Supabase authentication.

Beta signup

If you join the Lad beta list on the website, Lad collects your name and email address so beta access can be coordinated and a TestFlight invitation can be sent.

Food and nutrition information

Lad may collect food descriptions you type, food entries you save, saved foods, saved menus, selected menu items, barcode scan data, calorie and macro estimates, recipes, weight logs, water logs, and goal-related information.

Photos and scan information

When you use scanning features, Lad may process food photos, nutrition label photos, barcode scans, and menu photos. Food and label images are used for analysis. Menu images may also be saved locally on your device so you can reopen scanned menus later.

Profile and onboarding information

Lad may collect onboarding and profile information such as name, age, sex or gender, height, weight, activity level, goals, target weight, calorie settings, macro goals, and preferences. This information is used to calculate and personalize calorie and macro goals.

Feedback

If you submit feedback in the app, Lad may collect your feedback text and associate it with your account email or user ID for support and product improvement.

API keys

If you enter API keys, such as Groq or USDA API keys, Lad stores them securely in the device Keychain and uses them to make requests to the relevant services. Your Groq API key is sent to Groq as part of requests to Groq.

Analytics and diagnostics

Lad may collect app usage events, feature usage, account events, onboarding events, scan events, goal events, and similar analytics. Lad may also generate diagnostic logs during app use. These are used to improve reliability, understand feature usage, and fix bugs.

2. How We Use Information

Lad uses collected information to:

  • create and manage your account;
  • calculate calories, macros, goals, and food estimates;
  • analyze typed meals, food photos, nutrition labels, menus, and barcodes;
  • save foods, menus, recipes, weight logs, water logs, and preferences;
  • personalize the app experience;
  • manage beta signup requests and TestFlight invitations;
  • provide feedback and support;
  • improve app performance and reliability;
  • understand which features are being used.

3. Information Stored on Your Device

Lad stores certain information locally on your device, including food entries, saved foods, saved menus, recipes, macro goals, user profile data, weight logs, water logs, preferences, local settings, API keys, and authentication sessions.

API keys and authentication sessions are stored in the iOS Keychain. Other app data may be stored using local iOS storage such as SwiftData or UserDefaults.

4. Information Sent to Third-Party Services

Lad uses third-party services to provide core app functionality.

Groq

Lad may send typed meal descriptions, food images, nutrition label images, menu images, menu text, barcode-derived product context, goal-related inputs, and other analysis inputs to Groq to generate calorie estimates, macro estimates, menu parsing, titles, and related outputs. If you provide a Groq API key, that key is sent to Groq in request headers.

USDA FoodData Central

Lad may send food search queries and related food text to USDA FoodData Central to retrieve nutrition data. If you provide a USDA API key, it may be sent with USDA requests.

Open Food Facts

Lad may send barcode values to Open Food Facts to look up product names, ingredients, serving sizes, and nutrition data. Requests may include basic app-identifying User-Agent information.

Supabase

Lad uses Supabase for account authentication, email OTP login, session handling, user profiles, onboarding data, preferences, analytics events, and feedback submissions. Supabase may receive your email address, authentication tokens, user ID, profile information, preferences, feedback, and analytics events.

PostHog

Lad uses PostHog analytics to understand app usage and improve the product. PostHog may receive usage events, account identifiers, email address for email sign-in, onboarding properties, scan events, nutrition-related event properties, goal events, and automatic app lifecycle events.

Google Sheets

Feedback submitted through the app may be forwarded through a backend function to Google Sheets, including feedback text, submission time, and user email. Beta signup submissions from the website may also be stored in Google Sheets, including the submitted name and email address, submission time, and source page.

Apple services

Lad uses Apple platform features such as camera access, photo picking, microphone access, speech recognition, local notifications, and authentication-related system services where applicable.

5. Photos and Images

Food photos, nutrition label photos, and menu photos may be sent to external AI services for analysis. Ordinary food and label photos are used for analysis and are not intended to be permanently stored by the app. Menu photos may be stored locally on your device as part of saved menu functionality.

6. Health and Nutrition Information

Lad processes nutrition, diet, weight, water, and goal-related information. This information may be personal or sensitive. Lad is designed as a calorie and macro tracking tool and does not provide medical advice, diagnosis, or treatment.

7. Data Sharing

Lad does not sell user data. Lad does not use advertising identifiers or ad tracking based on the current app implementation.

Lad shares information only as needed to operate the app, including with services used for authentication, analytics, feedback, barcode lookup, nutrition lookup, and AI analysis.

8. Permissions

Lad may request:

  • Camera access for food scans, label scans, barcode scans, and menu scans;
  • Photo library access for importing menu images;
  • Microphone access for dictation;
  • Speech recognition access for voice input;
  • Notification access for local reminders.

Lad does not currently use location tracking, HealthKit, contacts, advertising tracking, or payment information.

9. Data Retention and Deletion

Lad stores app data locally on your device and may also store account, profile, preference, analytics, and feedback data through Supabase and related services.

The app includes local deletion or reset tools, but local deletion may not remove every type of data from every location. For example, some account/session data, saved menus, recipes, or server-side data may remain unless separately removed.

The app currently does not provide an in-app account deletion flow. To request deletion of account-related or server-side data, contact support at ladappsupport@gmail.com.

10. Security

Lad uses iOS Keychain storage for API keys and authentication sessions. No system can guarantee complete security, but Lad uses platform-provided storage mechanisms where appropriate.

11. Children

Lad is not intended for children under 13. If you believe a child has provided personal information, contact support at ladappsupport@gmail.com.

12. Changes to This Policy

This Privacy Policy may be updated as Lad changes. Updates will be posted on this page with a revised effective date.

13. Contact

For privacy questions, support requests, or deletion requests, email: ladappsupport@gmail.com