Below is a solid, App Store–ready Privacy Policy template for your QuickMealLog-style app (Siri meal logging → Firebase auth/storage → OpenAI-powered nutrition estimate). I wrote it to be accurate for a “minimal data” implementation; tweak any parts that don’t match what you actually do (especially analytics/crash reporting).
Effective date: January 25, 2026
QuickMealLog (“QuickMealLog,” “we,” “us,” or “our”) helps you log meals (including via Siri) and view/export your food log. This Privacy Policy explains what information we collect, how we use it, and your choices.
Meal entries and notes: Text you submit such as “bagel and cream cheese,” and any edits, tags, or notes you add.
Optional metadata you provide: If you add custom serving sizes, brands, or categories, we store what you enter.
Account identifiers: We use authentication to associate data with your account (for example, a Firebase user ID).
Basic device/app information: We may receive basic technical information needed to operate the app (e.g., app version, device type, OS version) and to troubleshoot issues.
To estimate calories and macros, your submitted meal text may be sent to our AI processing service providers (see “Third-Party Services” below). We may also use online sources to find nutrition information (for example, public nutrition databases or product nutrition pages).
We use your information to:
Provide the core service (log meals, estimate nutrition, display history, export CSV).
Authenticate you and keep your food log associated with your account.
Improve reliability and security (debugging, preventing abuse, monitoring for errors).
Respond to support requests (if you contact us).
We do not sell your personal information.
We share information only as needed to operate the app:
Service providers: We use third-party vendors to host infrastructure, store data, authenticate users, and process meal text for nutrition estimation. These vendors process data on our behalf and are required to protect it.
Legal requirements: We may disclose information if required by law, or to protect rights, safety, and security.
QuickMealLog relies on third-party services that may process data to provide the app:
Google Firebase (Authentication and Database): Used to sign you in and store your meal logs.
OpenAI (AI processing): Used to parse your meal text and help estimate calories/macros.
Apple (Siri/App Intents): If you use Siri, Apple’s systems handle voice recognition and intent invocation.
These providers have their own privacy practices. We encourage you to review their policies.
We retain your meal log data for as long as your account is active or as needed to provide the service. You can request deletion (see “Your Choices”).
We may retain limited records as required for legal, security, or fraud-prevention purposes.
Depending on the features available in your version of the app, you may be able to:
View and export your meal logs (e.g., CSV export).
Edit or delete meal entries within the app.
Delete your account / request data deletion by contacting us (see “Contact Us”).
We use reasonable administrative, technical, and physical safeguards designed to protect your information. No method of transmission or storage is 100% secure, but we work to protect your data.
QuickMealLog is not intended for children under 13 (or the minimum age required in your jurisdiction). We do not knowingly collect personal information from children.
Your information may be processed in countries other than where you live, depending on where our service providers operate. We take steps designed to ensure appropriate protections are in place.
We may update this Privacy Policy from time to time. If we make material changes, we will update the effective date and may provide additional notice in the app.
If you have questions or requests regarding this Privacy Policy or your data, contact:
Email: cazforshort@gmail.com
App name: QuickMealLog
If you use Analytics (Firebase Analytics) or Crash Reporting (Crashlytics), tell me and I’ll add a short section clarifying what’s collected and why.
If your app supports in-app account deletion, I’ll add the exact language Apple likes (“You can delete your account in Settings → Account → Delete Account…”).
If you paste your current Firebase/OpenAI usage (just high-level: Analytics yes/no, Crashlytics yes/no, any ad SDKs?), I’ll tailor this so it perfectly matches what you actually ship.