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.
Privacy contact: our designated privacy contact for access, correction, deletion, and other data requests (including under Canada's PIPEDA) is reachable at 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, photos you upload, and star ratings you give recipes. We also record swipes — right swipes are an interest signal that lands a recipe in your Saved list, and left swipes skip it; adding a recipe to a cookbook is the actual save. Swipes and ratings are not used to build an advertising profile or to target ads.
Public activity: if you mark a cookbook public, follow another creator, or like a public cookbook or creator recipe, the relationship and counts may be visible to other Hungrrry users and may appear on discovery surfaces such as /public-cookbooks and /discover. Private cookbooks, private cookbook saves, and swipes are never shown to other users.
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 also extract the recipe's ingredient list from the page and store it so we can (a) match recipes against other users' allergies and dietary restrictions, and (b) let you add ingredients to your grocery list. Ingredients are shown to you when you build a grocery list from a saved recipe, but we do not republish them publicly. We do not copy recipe instructions, body 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.
To decide what to show you in Discover. Specifically: recipes you've already swiped on are excluded so you don't see them again; recipes you skipped stay suppressed unless you choose to include them; recipes you've saved or added to a cookbook may be resurfaced in Discover so they don't get lost, and recipes from cookbooks you've made public or shared may be given resurfacing priority; star ratings adjust resurfacing — 1★ recipes are excluded, 2★ are heavily deprioritized, 3★ is neutral, and 4★/5★ remain eligible; and your dietary preferences, allergies, dislikes, and hide-alcohol setting filter out recipes that don't fit. This is deterministic, rule-based filtering and ordering — not a machine-learning model, behavioral profile, interest graph, or prediction system, and it is never used for advertising.
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. We store the public URL, page title, and og:image, and we extract the recipe's ingredient list from the page so we can hide recipes from users whose allergies or dietary preferences would be violated, and so users who save the recipe can add its ingredients to their own grocery list. Ingredients are not exported or republished, and the source URL always points back to the original publisher. We never share 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)
Supabase (backend infrastructure provider, used through Lovable Cloud): 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. AI-assisted features
Some Hungrrry features use third-party AI models (reached through the Lovable AI Gateway) — for example, parsing a recipe URL into a structured recipe, generating short summaries, or classifying ingredients. When a feature uses AI, only the data needed for that specific request (e.g. the URL or text you submitted) is sent to the provider, and only for the duration of that request. We do not use your content to train AI models, and our providers are contractually prohibited from training on content routed through Hungrrry.
6. 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.
7. 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).
Some deleted information may remain temporarily in backups, security logs, or audit records where required for security, legal compliance, or operational integrity.
8. 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.
10. International transfers
Hungrrry is operated from Ontario, Canada. Your data may be processed in Canada, the United States, or the European Union depending on the region of our hosting and infrastructure providers. Where required, we rely on Standard Contractual Clauses or equivalent safeguards for cross-border transfers.
11. 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.
12. 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.
For copyright, impersonation, safety, or abuse reports, contact us through our Abuse & Legal Requests page.