Privacy Policy

Potluck by Savor — no account, minimal anonymous usage data

Potluck requires no account and does not collect your name, email address, or profile information. The web version creates a random identifier in your browser so we can count spins and understand a few basic Potluck actions. It is not linked to a Savor account or to a personal profile.

What we collect — Savor

Savor requires an account to save and manage your recipes. When you use Savor we collect:

• Google profile — when you sign in with Google we receive your display name, email address, and profile picture from Google.
• Email address — if you register with email and password, we store your email for authentication only.
• Your username — displayed alongside recipes you share to the community feed.
• Recipes you save — stored in your personal recipe box on our servers.
• Recipes you choose to share — visible to other Savor users in the community feed.
• Savor Pro purchase status — if you buy Savor Pro through a subscription or one-time lifetime purchase, we receive the purchase and entitlement status from RevenueCat and Google Play. We never see your payment card details.

We do not collect your real name (beyond what Google provides), phone number, location, contacts, or any other personal information.

What we collect — Potluck by Savor

Potluck has no accounts and no sign-in. We do not collect your name, email address, phone number, or a Savor profile.

On the Potluck website, your browser creates a random local identifier. We send that identifier with random-recipe requests and a small set of product events such as visits, spin milestones, recipe opens, and Potluck/Savor link clicks. This lets us count spins and understand whether the product is being used. The identifier is not linked to a Savor account or to information that directly identifies you.

The web page also sends recently seen recipe IDs with a spin request so the server can avoid immediate repeats. Those IDs describe recipes, not you. Clearing this site's browser storage resets the local Potluck identifier.

The Android app keeps its Potluck history and weekly choices locally on your device. Normal network requests still reach our server to fetch recipe data and may include standard technical request information such as IP address and user agent in infrastructure logs.

Camera and scan

Savor's scan feature lets you photograph physical recipe cards and cookbooks to import them into your recipe box. When you use this feature:

• Your camera is accessed only when you actively initiate a scan.
• Images are processed on-device using ML Kit OCR to extract text.
• Where needed, extracted text is sent to our server for recipe parsing. The image itself is never sent to or stored on our servers.
• Processed text is not retained after your recipe has been imported.

Push notifications

With your permission, Savor may send you push notifications about your recipe activity and community updates. Notifications are optional — you can enable or disable them at any time in your device settings. We do not use notifications for advertising.

How we use your data

Savor uses your data solely to provide the service:

• Your email and Google profile authenticate you and keep your recipe box synced across devices.
• Your username is displayed alongside recipes you share to the community feed.
• Shared recipes are displayed in the community feed as you intended.
• Savor Pro purchase and entitlement status unlocks Pro features in the app.

Potluck's anonymous web identifier and basic event data are used only to operate the random-recipe service, count spins, diagnose problems, and understand basic feature use. They are not used to build an advertising profile.

We do not sell your data. We do not use your data for advertising. We do not share your data with third parties except the infrastructure providers listed below.

Third-party services

We use a small number of trusted services to run the apps:

• Firebase Authentication (Google) — handles sign-in for Savor. Your email and Google profile are stored with Firebase.
• MongoDB Atlas — stores your recipes and account data on our behalf.
• Railway — hosts our server that both apps communicate with.
• RevenueCat — manages Savor Pro purchase entitlements. RevenueCat receives purchase and subscription status and purchase history via Google Play. We never receive your payment card details.
• Expo / EAS — used to deliver over-the-air app updates. No personal data is transmitted.

Each of these services has their own privacy policy. We have chosen providers who take data seriously and do not use your data for their own advertising or profiling.

Data retention and deletion

You can delete your Savor account at any time from within the app (Settings → Privacy & Data → Delete Account). This permanently deletes your account, email address, and all saved recipes immediately.

Recipes you have shared to the community feed remain as anonymous contributions after account deletion — your username is removed but the recipe stays. This is intentional so the community isn't disrupted when someone leaves. If you want a specific shared recipe removed, contact us.

Potluck does not maintain a user account or personal profile to delete. Anonymous operational and product-event records are not linked to a known person or Savor account.

Children's privacy

Our apps are not directed at children under 13. We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, contact us and we will delete it.

Your rights

Depending on where you live, you may have rights regarding your personal data — including the right to access, correct, or delete it. To exercise any of these rights, contact us at the address below. We will respond within a reasonable timeframe.

Changes to this policy

If we make material changes to this policy we will update the date at the top of this page. Continued use of the apps after changes constitutes acceptance of the updated policy.

Questions about this policy? support@getsavor.recipes