Meal Planner AI : What to Eat Last updated: July 19, 2026

Effective with the release of version 1.3.2

This Privacy Policy explains how Creative Adventures Lab ("we", "us", "our") collects, uses, discloses, and protects information in connection with the Meal Planner AI : What to Eat mobile application (available on the App Store and Google Play as "Meal Planner AI : What to Eat", also referred to as "What to Eat" or "the App"). It also describes your rights under applicable data protection law, including the EU General Data Protection Regulation ("GDPR") and the California Consumer Privacy Act ("CCPA").

Please read this policy carefully. By installing or using the App, you acknowledge that you have read and understood it.

What's New (Version 1.3.2)

• Corrected the database-access and AI Edge Function authentication claims to match what's actually enforced (Section 7, and the matching claim in Section 8's Art. 32).
• Corrected the Google Pub/Sub webhook verification claim, it depends on a server-side configuration value (Section 2.3).
• Corrected the household dietary-data claim, a per-profile version and a separate aggregated household-wide version are both sent to the AI (Section 2.4).
• Removed an inaccurate 90-day purchase-receipt retention claim, receipt identifiers are deleted immediately with the rest of your account (Section 6, Art. 17).
• Corrected the list of server-side fields, it now includes the Privacy Policy acknowledgment version and timestamp (Section 2.2, Section 6).
• Corrected the onboarding preview flag's storage location, it's stored alongside your other local content, not the secure keychain(Section 3).
• Added a new rule: custom and free-text fields may only be used for meal planning, not for unlawful content (Section 2.4; Terms of Use, Section 4 and Section 8.2).
• Named Supabase explicitly as the processor handling purchase-verification and webhook data (Section 2.3).
• Removed an inaccurate claim that IP address is stripped from AI requests, it was never part of that payload to begin with (Section 2.4).
• Described the plan_generation_usage table's own access model, distinct from the users and userEntitlements lockdown (Section 7).
• Your allergies, ingredient dislikes, and favourite ingredients now personalise AI plans, including custom ones you type (Section 2.4).
• Cost estimation can now use the AI when you tap "Estimate cost" on a meal (Section 2.4).
• We now scan free text for obvious personal information before sending it to the AI (Section 2.4).