Snappy Logo

Snappy

Get Started

Privacy Policy

Last updated: September 14, 2026

Overview

Snappy ("we", "us", or "our") is committed to protecting your privacy. This policy explains how we collect, use, share, and protect your information when you use the Snappy mobile application and related websites (the "Service"). We do not sell your personal information.

1. Information We Collect

Account Information

Email address, name, and profile photo provided through Clerk authentication. If you use Sign in with Apple or Google, we receive the identity details those providers share with us.

Recipe & Content Data

Recipe titles, ingredients, cooking steps, nutritional information, recipe images (stored on Cloudflare R2), source URLs and video platforms (for example TikTok, Instagram, YouTube), meal planning data, grocery lists, and folders.

Preferences & Settings

Measurement system preference, cooking skill level, nutrition preferences, and notification preferences.

Purchase & Subscription Data

Product identifiers, purchase status, entitlements, and restore events from Apple In-App Purchases via RevenueCat. We do not receive your full payment card details.

Usage & Analytics Data

App events (for example recipe generation, meal planning, shopping list actions, onboarding, and paywall interactions), device type, operating system, app version, language/locale, session information, IP address, and device identifiers (such as IDFV). When you are signed in, analytics may be linked to your account ID and may include email or name when we associate them for product analytics.

Advertising & Attribution Data

If you grant permission through Apple's App Tracking Transparency (ATT) prompt, advertising identifiers (such as IDFA) and related campaign/attribution signals may be collected to measure ads and conversions. If you deny ATT, we do not enable advertiser tracking for that purpose.

Diagnostics & Support

Crash/error information and any details you send when contacting support.

2. How We Use Your Data

  • • Account management: Create and maintain your account
  • • Recipe generation: Process videos/content to extract and generate recipes using AI
  • • Content storage: Store and deliver recipes, meal plans, and grocery lists
  • • Personalization: Tailor experiences based on preferences and usage
  • • Subscriptions: Process purchases and restore entitlements
  • • Analytics: Understand product usage, funnels, and retention to improve Snappy
  • • Advertising measurement: Measure and optimize ad campaigns and attribution
  • • Support & safety: Respond to requests and prevent abuse

3. Analytics

We use PostHog for product analytics and related measurement. PostHog may receive event data, device and session information, IP address, and—when you are signed in—identifiers that can link usage to your account (and, where configured, contact details such as email).

Analytics is used to operate and improve Snappy. It is not sold. We may expand the events and properties we send to PostHog over time as we add more product instrumentation (similar to our other apps); those uses remain covered by this section.

4. Advertising, Attribution & Tracking

We use the Meta (Facebook) SDK and related advertising/attribution tools (including Apple AdServices / SKAdNetwork where applicable, and RevenueCat device identifiers for purchase attribution) to measure installs, app events, and campaign effectiveness.

On iOS, if we access data that Apple defines as "tracking," we request permission via the App Tracking Transparency prompt. You can change this later in iOS Settings → Privacy & Security → Tracking.

If you deny tracking permission, we may still process limited non-tracking measurement allowed by Apple and Meta, and we still use first-party analytics as described above.

5. Third-Party Services

We share limited data with trusted providers that help run Snappy:

Clerk

Authentication and account identity.

Cloudflare R2

Stores and hosts recipe images. Images are removed when associated content is deleted.

OpenAI

Processes content needed to generate recipes (for example titles/descriptions extracted from source media).

RapidAPI / media extraction providers

Extract video or page metadata from social platforms when you import a recipe source.

RevenueCat

Subscription and purchase entitlement status with the App Store.

PostHog

Product analytics as described above.

Meta Platforms

Advertising measurement and attribution.

Apple

Sign in with Apple, In-App Purchases, and platform services.

Neon / PostgreSQL & hosting providers

Store app data and host our APIs/websites (for example on Vercel).

6. Data Security

  • • Data in transit protected with HTTPS
  • • Accounts secured through Clerk
  • • Recipe images stored on Cloudflare R2 with access controls
  • • Database access restricted to our backend

7. Data Retention & Deletion

Your data is retained while your account is active. When you delete your account in the app:

  • • Your account identity is removed via Clerk
  • • Recipes and related app data are deleted from our database
  • • Associated recipe images are removed from Cloudflare R2
  • • Limited technical logs or analytics records may remain for security, fraud prevention, or legal compliance; where feasible we de-identify them so they are no longer reasonably linked to you

Purchase records retained by Apple or RevenueCat may persist according to their rules and are not fully controlled by us.

8. Your Rights & Choices

  • • Access / correct: Update account details or contact us
  • • Delete: Delete your account in the app, or contact support
  • • Export: Request a copy of your recipes/data where reasonably available
  • • Tracking: Manage ATT permission in iOS Settings
  • • GDPR / CCPA: If you are in the EEA/UK or California, you may have additional rights. Contact us to exercise them

9. Children's Privacy

Snappy is not directed to children under 13. We do not knowingly collect personal information from children under 13. If we learn that we have, we will delete it.

10. International Transfers

We and our providers may process data in the United States and other countries. Where required, we rely on appropriate transfer mechanisms.

11. Changes to This Policy

We may update this policy from time to time. The "Last updated" date at the top will change when we do. Continued use of Snappy after an update means you accept the revised policy.

12. Contact Us

Privacy questions or data requests:

We aim to respond within 7 business days.

EU & CCPA: If you are in the EU/EEA/UK (GDPR) or California (CCPA), you may have additional rights. Contact us for those requests.