Privacy Policy

1. Information we collect

We collect information you provide, information created when you use the Service, and limited technical information needed to operate the Service. We do not sell your personal information, and we do not use advertising SDKs or third-party marketing pixels in the app or site as built today.

Account and profile

• Account identifiers: Clerk user ID, email address, and username (derived from your account).
• Name: name associated with your Clerk account; optional display name you set in profile settings (synced with the mobile app).
• Optional profile fields: phone number and birthday, if you choose to add them in settings.
• Authentication data: session and sign-in information managed by Clerk (including social or email sign-in you choose through Clerk).

Content you create or import

• Recipes (titles, ingredients, steps, timing, source URLs, notes, nutrition-related fields we derive or you confirm).
• Cookbooks/folders, favorites, meal calendar plans, and grocery lists.
• Recipe cover and folder cover images you upload.
• Videos you upload (for example MP4) or video URLs you submit (currently TikTok URL import where supported), plus related job metadata such as transcripts, OCR text, thumbnails, and extracted recipe drafts.

Purchases and entitlements

• Web subscriptions: Stripe customer and subscription identifiers and status (for example customer ID, subscription ID, price ID, subscription status) stored on your profile to unlock Pro features.
• iOS in-app purchases: Apple subscriptions managed through RevenueCat. We receive webhook events (for example purchase, renewal, expiration) keyed to your Clerk user ID and store entitlement fields such as plan tier, billing source, and whether the Apple entitlement is active. Payment card details are handled by Apple / Stripe — we do not store full card numbers.

Technical and usage information

• Server logs and security-related request metadata as typical for hosting (for example IP address, timestamps, and error diagnostics collected by our hosting provider).
• Aggregated product analytics via Vercel Analytics and Speed Insights on the website (performance and usage metrics; not used to build advertising profiles).
• Limited on-device preferences in the browser (for example localStorage flags for UI dismissals or grocery category overrides).

2. How we use information

• Provide, secure, and improve the Service (accounts, recipes, planning, sync across web and iOS).
• Authenticate you and enforce access controls (including database row-level security tied to your user ID).
• Process subscriptions and unlock Pro features on web (Stripe) and iOS (Apple via RevenueCat).
• Import and extract recipes from URLs or videos (including server-side AI processing described below).
• Estimate or match nutrition information using USDA FoodData Central data and, when needed, server-side AI estimation for unresolved ingredient lines.
• Respond to support or privacy requests you send us.
• Detect abuse, debug failures, and maintain service reliability.

3. How we share information (service providers)

We share information with processors that help us run HomeRecipe. They receive only what is needed for their role. We do not claim that we “never share data with third parties,” because these providers process data on our behalf:

• Clerk — authentication and account management (including session cookies).
• Supabase — database, file storage (recipe covers, videos), and authorization using your Clerk session.
• Stripe — web checkout, billing, customer portal, and related webhooks.
• RevenueCat and Apple — iOS in-app subscriptions; RevenueCat notifies our servers at /api/webhooks/revenuecat so we can sync Pro access.
• Vercel — hosting the website and related infrastructure, plus Analytics / Speed Insights.
• OpenAI — server-side processing for video transcription, recipe extraction from video content, and optional nutrition estimation when USDA matching is incomplete. Recipe content and related media-derived text may be sent to OpenAI for these features.
• Tavily — Pro web recipe search queries (search terms you enter) when that feature is used.
• USDA FoodData Central — server-side lookups to match ingredients to public nutrition data (queries are food descriptions / IDs, not your password).
• Recipe URL import service — our scraping service fetches public recipe pages you ask us to import (JSON-LD / HTML extraction; not an LLM in the current importer).

We may also disclose information if required by law, to protect rights and safety, or in connection with a business transfer (for example a merger), subject to applicable law.

4. AI and automated processing

Certain features send content to AI providers on our servers (not in your browser):

• Video recipe import: audio transcription (Whisper) and structured recipe extraction from transcript/OCR text.
• Nutrition: when an ingredient line cannot be confidently matched to USDA data, we may use an OpenAI model to estimate macros or suggest a match.
• On-device / worker OCR (Tesseract) may run in our video processing pipeline to read on-screen text from frames.

Static webpage URL import scrapes structured recipe data from the page you provide; that importer does not currently call an LLM. We do not use your content to train our own foundation models. OpenAI’s processing is subject to OpenAI’s terms and data policies for API customers.

5. Cookies and local storage

Authentication cookies and session material are managed by Clerk. We do not create a separate custom auth cookie, and we do not store passwords in cookies. The website may also use browser localStorage for non-essential UI preferences (for example dismissing a banner or remembering grocery category overrides on that device).

6. Retention

• Account and profile data are kept while your account remains active.
• Free-tier user recipes generally expire after 30 days and move to Trash unless you upgrade.
• Items in Trash are permanently deleted after 7 days.
• Meal calendar entries older than about 90 days are purged by scheduled cleanup.
• Billing and entitlement records are retained as needed to provide Pro access, prevent fraud, and meet legal/accounting requirements.
• Video processing jobs and stored media are retained to provide the feature and for operational debugging; you can delete associated recipes/content in-product where available.

7. Security

We use industry-standard protections appropriate to our stack, including HTTPS in production, Clerk-managed authentication, Supabase access controls (including row-level security keyed to your Clerk user ID), and secret keys kept on the server. No method of transmission or storage is 100% secure.

8. Children’s privacy

HomeRecipe is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us information, contact us and we will take appropriate steps to delete it.

9. Your choices and rights

• Access and update: you can view and edit optional profile fields in Settings, and manage password/security through Clerk account management.
• Delete content: you can delete recipes and cookbooks in the product (Trash retains them briefly, then permanent deletion).
• Account deletion: the in-app Settings page does not by itself delete your Clerk account. To delete your account and associated personal data, use Clerk account controls where available and/or email us at cristian@ageitosdigital.com. We will help delete or de-identify account data we control, subject to legal retention needs (for example billing records).
• Marketing: we do not run an in-product marketing email list in the current codebase. If that changes, we will update this policy.
• Depending on your location (for example EEA/UK or California), you may have rights to request access, correction, deletion, or information about sharing. We do not sell personal information. To exercise rights, contact cristian@ageitosdigital.com.

10. International transfers

We and our processors (including Clerk, Supabase, Stripe, RevenueCat, OpenAI, Tavily, and Vercel) may process data in the United States and other countries. If you use HomeRecipe from elsewhere, your information may be transferred to those locations. Where required, we rely on appropriate safeguards offered by those providers.

11. Changes to this policy

We may update this Privacy Policy from time to time. We will post the updated version at https://homerecipe.co/privacy and revise the “Last updated” date above. Continued use of the Service after changes means you accept the updated policy.

12. Contact

Questions or privacy requests: cristian@ageitosdigital.com

Service: HomeRecipe · Website: https://homerecipe.co