RecipeTree

1. Information We Collect

When you use RecipeTree, we collect certain information to provide and improve our services:

Account Information: Your email address, name, and profile picture provided through authentication.
User Content: Recipes you create or save, grocery lists, and meal plans.
Usage Data: Information on how you interact with the App. We store the dates of authenticated activity and an aggregate API request count for each active day to measure daily, weekly, and monthly usage.
Download Attribution: When you use our app download link, we record a random click identifier, timestamp, campaign labels, destination store, coarse device category, coarse country, and referring website hostname when available. On Android, Google Play may return that click identifier and install timing so we can measure first opens and, after sign-in, attributed signups. Our download analytics do not retain raw IP addresses, full user-agent strings, advertising identifiers, or device fingerprints.
Device Identifiers: We collect Push Notification tokens (FCM tokens) to send you relevant updates.
Mobile Advertising Measurement: In our iOS and Android apps, the Meta App Events SDK records app activation or first-open events, completed account registrations, and server-verified subscription purchases. Purchase events include the product identifier, value, and currency. Meta also receives ordinary technical context generated by its SDK and the network request, such as app and device information, IP address, and an app-install-scoped anonymous identifier.
Payment Information: Processed securely through Stripe (on web) or via the Apple App Store / Google Play Store (on mobile); we do not store your full credit card details.

2. How We Use Your Information

We use the collected information for the following purposes:

To provide, maintain, and improve the App's features.
To personalize your experience, such as generating custom recipes.
To process payments and manage your subscription.
To communicate with you about updates, security, and support.
To analyze usage patterns to enhance App performance.
To understand which first-party marketing campaigns lead to app store visits, Android first opens, and signups.
To measure whether Meta advertising leads to app activations, registrations, and verified subscription purchases, and to improve and optimize those campaigns.

3. Information Sharing

We do not sell your personal information. We may share your data with trusted third-party service providers who assist us in operating the App:

Authentication Infrastructure: We use the Better Auth framework in our application and may share data with identity providers you choose (such as Google or Apple) to authenticate your account.
Payments: Stripe (web), Apple App Store (iOS), and Google Play Store (Android) process payments and subscriptions based on your platform.
AI Processing: Google Cloud Vertex AI processes recipe text/images and related prompts to provide AI-powered features.
Email Delivery: Resend is used to send account emails such as sign-in and verification messages.
Push Notifications: Firebase Cloud Messaging (FCM) is used to deliver push notifications to your device.
Advertising Measurement: Meta Platforms, Inc. receives the mobile app events and technical context described above so that we can measure and optimize RecipeTree advertising on Meta services. We do not send Meta your RecipeTree email address, account ID, name, recipes, meal plans, shopping lists, ingredients, or full store transaction identifier through this integration. Meta processes this information under its Privacy Policy.
File Storage and Hosting: Vercel services (including Vercel Blob) and other cloud hosting providers are used to host the application and store uploaded content such as recipe images.

4. Data Security

We implement industry-standard security measures to protect your data. However, no method of transmission over the Internet is 100% secure, and we cannot guarantee absolute security.

5. Your Rights and Account Deletion

You have the right to access, update, or delete your personal information. You can request deletion in either of the following ways:

In-app self-service deletion: Sign in, open Account settings, and use the Delete Account action in Danger Zone.
Public request page: Visit /account-deletion and follow the in-app deletion path, or email andrew@edulilo.com.

For email/manual requests, we may ask for verification before we process deletion.

RecipeTree configures the Meta SDK not to access Apple's Identifier for Advertisers (IDFA) or Google's Android Advertising ID (AAID), does not request Apple App Tracking Transparency permission, and does not use device fingerprinting. You can also manage how Meta uses activity from advertising partners through your Meta account's advertising settings.

6. What Is Deleted vs. Retained

When account deletion is completed, we delete account data from our active application database, including:

Profile and authentication data (name, email, profile image, linked auth accounts, and active sessions)
User content (recipes, meal plans, shopping lists, favorites, and social-sharing relationships)
Push notification token(s), purchase event records, local subscription records, and account-linked activity records

Some records may be retained in limited form:

Moderation/report records may be retained with user references removed where feasible.
Payment processors (such as Stripe, Apple App Store, and Google Play) may retain transaction records under their own legal and compliance obligations.
Secure infrastructure backups may retain data for up to 30 days before overwrite.
Individual download-click records are retained for up to 180 days. After that, they are deleted and only non-identifying daily campaign totals are retained.
RecipeTree retains only acknowledgement timestamps indicating that a registration or verified purchase was reported to Meta; those account-linked records are deleted with your account. Meta retains app-event data according to its own policies.

7. Deletion Timing

In-app self-service deletion is processed immediately after confirmation. Manual email/form requests are typically processed within 7 days after successful account ownership verification.

8. Changes to This Policy

We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last Updated" date.