This policy explains what data Hungrrry collects, why we collect it, who we share it with, and the rights you have over it. Questions: admin@gethungrrry.com.
1. What we collect
Account data: email address, hashed password, sign-in identifiers (e.g. Google OAuth subject), and the timestamp you accepted our terms.
Profile data: display name, handle, avatar, dietary preferences, allergens, and any other fields you fill in.
Content you create: cookbooks, saved recipes, notes, and photos you upload. We also record swipes (likes/dislikes/saves) so we don't show you the same recipe twice — they are not used to profile you or personalize ads.
Sharing & referrals: when you share a cookbook or invite link, we record visits to that link including a coarse fingerprint (user agent, referer, IP-derived region) so the owner can see referral activity and so we can prevent abuse.
Third-party recipe metadata: when you save a URL, we fetch and store its public title and og:image. We do not copy recipe text or the publisher's photos.
Technical logs: our backend records IP addresses, request timestamps, and error traces for security and debugging. These are retained on a short rolling window.
2. Why we use it
To run your account: authentication, password reset, email notifications you've opted into.
To power app features: your cookbooks, saved recipes, the Discover deck, and sharing. Swipes are only used to avoid re-showing recipes you've already seen — they don't drive personalization or recommendations.
To improve the product: aggregate, non-identifying usage patterns.
To prevent abuse, spam, and copyright violations.
3. Discover pool (on by default, opt-out)
By default, the public URLs you save are added to a backend pool used to seed Discover for other Hungrrry users. Only the public URL, page title, and og:image are shared — never your photos, notes, private cookbooks, or anything identifying you. You can turn this off at any time from your profile to stop all future contributions, or revoke an individual recipe by editing it and switching off "Share in Discover"— that recipe is then removed from the Discover pool on your behalf.
4. Who we share data with (subprocessors)
Lovable Cloud (Supabase): hosts our database, authentication, and file storage.
Email delivery provider: sends transactional email (sign-up confirmations, password resets, cookbook share invites). Only your email address and the message contents are passed through.
Image hosts: when Hungrrry displays an og:image for a recipe URL, your browser fetches it from the original publisher's server.
We do not sell your personal data, and we do not share it with advertisers.
5. Cookies and local storage
We use first-party cookies and local storage strictly to keep you signed in, remember your "remember me" preference, and store UI state (e.g. which onboarding cards you've seen). We don't use third-party advertising cookies or cross-site trackers.
6. Retention and deletion
Account data is retained while your account is active. You can delete your account at any time from the profile page, or email admin@gethungrrry.com to request deletion. Deletion removes your profile, cookbooks, saved recipes, and swipes. Backups are purged on a rolling schedule (typically within 30 days).
7. Your rights
Depending on where you live, you may have the right to:
Access the personal data we hold about you.
Correct inaccurate data.
Delete your data ("right to be forgotten").
Export your data in a portable format.
Withdraw consent for optional features (e.g. Discover contribution).
Lodge a complaint with your local data protection authority.
Hungrrry isn't directed at children under 13 (or under 16 in the EU/UK). If you believe a child has created an account, please contact us and we'll remove it.
9. International transfers
Your data may be processed in the United States or the European Union depending on the region of our hosting provider. Where required, we rely on Standard Contractual Clauses for cross-border transfers.
10. Security
Passwords are hashed; database access is restricted by row-level security so you can only read and write your own records. No system is perfectly secure — if you spot something, please report it to admin@gethungrrry.com.
11. Changes to this policy
We'll update the date at the top whenever this policy changes. Material changes will be announced in-app before they take effect.