RecipeHub Privacy Policy
Effective date: April 13, 2026
App: RecipeHub (“we”, “us”)
Developer: Pavan
Contact: ichilupa@gmail.com
This policy describes how we collect, use, and share information when you use the RecipeHub mobile application (including native builds built with Capacitor) and related services. By using RecipeHub, you agree to this policy.
Account and authentication
You can sign in with Google or Apple through our authentication provider (Supabase). Each provider may share with us what they allow for that sign-in method—typically including a unique user ID, and often name, email address, and profile photo URL when available. We do not handle your Google or Apple password.
Browsing without an account
You may choose to continue without signing in for a limited preview of public content. In that case we do not create an account tied to you; we may store a simple preference on your device (for example in browser or app storage) so the app remembers that you chose guest browse.
Profile
We store a display name and optional avatar URL in your profile so other users can see who created a recipe. You can edit your display name in the app.
Content you create
We store recipes you add (for example title, description, ingredients, instructions, prep/cook times, servings, tags) and associate them with your account.
Favorites
We store which recipes you have saved as favorites so we can show them to you and keep them in sync when you use the service while signed in.
Activity / notifications
When another user interacts with content in a way the app treats as notifiable (for example favoriting a recipe you authored), we may create an in-app notification for you (such as who acted and which recipe). You can view these in the Activity section of the app.
Technical / device data
The app runs as a native build using Capacitor and may use platform features such as in-app browser flows for sign-in, app lifecycle handling, keyboard, status bar, splash screen, and haptics as supported by your device. Apple, Google (for sign-in), and our hosting provider may process standard device, connection, and system information as part of normal operation (for example secure connections and OS-level services).
We do not integrate a separate third-party analytics SDK in the app as described in this policy. If that changes, we will update this policy.
We use the information above to:
Create and maintain your account
Show and sync your recipes and favorites
Display your profile name (and optional avatar) to other users
Deliver in-app notifications about activity relevant to your recipes
Operate, secure, and improve the service
Comply with law and respond to valid requests
We do not sell your personal information.
Other users
Recipes you publish are visible in the community experience for other users of the service. Your display name (and optional avatar) may appear with recipes you post. How favorite counts or relationships appear to others depends on how the product is configured in the backend; design this subsection to match your Supabase RLS and UI (e.g. if aggregate favorite counts are public on recipe cards, say so briefly).
Service providers
We use Supabase for authentication, database storage, server-side logic (such as account deletion), and related infrastructure. Data is processed according to Supabase’s terms and privacy practices: https://supabase.com/privacy
Google
Google sign-in is subject to Google’s policies: https://policies.google.com/privacy
Apple
Apple sign-in is subject to Apple’s policies: https://www.apple.com/legal/privacy/
We may also share information if required by law or to protect rights, safety, and security.
We retain your information while your account is active and as needed to provide the service.
You may delete your account from the app (for example via Profile), which triggers a server-side deletion flow for your auth user and associated data as implemented in our backend, subject to technical and legal limitations (for example logs retained by providers for a limited time).
You may also contact us at ichilupa@gmail.com to request deletion of your account or personal information; we will respond in line with applicable law.
We use reasonable measures appropriate to the nature of the service (including authentication controls and encrypted connections in transit). No method of transmission or storage is 100% secure.
RecipeHub is not directed at children under 13 (or the minimum age in your jurisdiction). We do not knowingly collect personal information from children. If you believe we have, contact us and we will take appropriate steps.
Your information may be processed in countries where our service providers operate (including where Supabase hosts your project). Those countries may have different data protection laws than your own.
Depending on where you live, you may have rights to access, correct, delete, or export your personal information, or to object to or restrict certain processing. Contact ichilupa@gmail.com to make a request.
We may update this policy from time to time. We will post the new effective date at the top. Continued use of the app after changes means you accept the updated policy (unless applicable law requires a different approach).
Questions about this policy: ichilupa@gmail.com
Developer: Pavan