Draft: some details are still being confirmed.
Privacy Policy
App: Saucepan
Effective date: November 13, 2026
Last updated: October 24, 2026
This policy explains what information the Saucepan app and website collect, why, who we share it with, and the choices you have. We wrote it in plain English. If anything is unclear, email us at support@goldtechsolutions.net [[CONFIRM: support email, e.g. support@getsaucepan.com]].
The short version
- You can use Saucepan without an account. Your recipes, photos, lists, plans, and taste profile then stay on your device.
- Signing in is optional. You can sign in with Apple, an email code, a phone number code, Google, or Facebook. If you sign in, we store your library on our servers so it syncs, and you can use community features and Cook Together.
- AI runs on your device first. Saucepan uses Apple’s on-device intelligence where it can. Cloud AI (reading recipes your device can’t, nutrition estimates and ingredient swaps, and optional tag suggestions) runs only if you say yes first. It sends recipe text only, never your photos or personal details, through OpenRouter to AI hosts whose policies say they don’t keep it or train on it (Section 2).
- Fridge and pantry photos never leave your device.
- No ads. No tracking in the app. We don’t sell or share your personal information. Our website uses Google Analytics to count visits (Section 7).
- You can delete your account and server data in the app (Settings → Delete Account), however you signed in.
Who we are
Saucepan is made by Aaron Gold, doing business as Gold Tech Solutions [[CONFIRM: legal entity name, e.g. “Gold Tech Solutions LLC”]], located in the United States ([[CONFIRM: mailing address]]). In this policy, “we”, “us”, and “our” mean Gold Tech Solutions. For people in the European Economic Area, the UK, and Switzerland, we are the “controller” of your personal data.
This policy covers the Saucepan iOS app, its widgets, Share extension, Siri and Shortcuts actions, the Send to Your Inbox channels (Section 5), and our website at getsaucepan.com.
1. Using Saucepan without an account
Without an account, your recipes and other content stay on your device. We don’t receive your recipes, photos, lists, plans, notes, cooking history, search history, pantry, profiles for people you cook for, or taste profile. Cloud AI features need an account, so they’re not used either.
This data is stored in the app’s storage on your iPhone or iPad. It may be included in your device backups (for example, iCloud Backup), which Apple handles under its own privacy policy. If you delete the app, this data is deleted from the device.
The app still talks to our servers to download ingredient pictures, ingredient data, and app settings. Our servers see your IP address in their logs when it does (Section 3, Server logs).
Ingredient names we don’t recognize. When a recipe or grocery list has an ingredient name the app doesn’t know, the app may send that name to us, at most once a day, so we can add it to our ingredient list. It sends only the names, with no account, device ID, or recipe, and we keep only a count of how often each name was seen. This happens with or without an account. [[CONFIRM: add a switch to turn this off (e.g. Settings → Your Data & Privacy → Help Improve Ingredients) and name it here; today there’s no switch in Settings]]
Features that run on your device
| Feature | What happens |
|---|---|
| Reading recipes (Apple Intelligence) | On supported devices, Apple’s on-device Foundation Models read recipe text. The text stays on your device, unless Apple Intelligence can’t read the recipe and you’ve allowed Cloud Recipe Reading (Section 2). Some Apple Intelligence requests may use Apple’s Private Cloud Compute, which Apple runs and which does not share data with us. |
| Sorting recipes (Smart Organization) | Course, cuisine, and tag suggestions are worked out on your device first. What it learns from your library stays on your device. |
| Scanning recipe cards, cookbooks, and screenshots | Text is recognized on your device with Apple’s Vision framework. |
| Fridge and pantry photos (“What Can I Make?”) | Ingredients are recognized on your device. The photo is never uploaded. |
| Cooking videos you import | The app downloads the video to your device, reads on-screen text and transcribes the narration on your device, then deletes the video file. |
| Allergy and diet flags | Checked on your device against a fixed ingredient table. |
| Search, widgets, Spotlight, Siri | Indexed and handled on your device. |
Device permissions
Saucepan asks for these permissions only when you use a feature that needs them. You can change them anytime in iOS Settings → Saucepan.
| Permission | Why we ask | Does the data leave your device? |
|---|---|---|
| Camera | Scan recipe cards and cookbooks, photograph your fridge, take photos of dishes you made | No, unless you attach a dish photo to a recipe or post while signed in (see Section 3) |
| Photos | Import recipes from screenshots and attach photos to your recipes | Same as Camera |
| Add to Photos | Save recipe images you export | No |
| Microphone | Hands-free voice commands while cooking, and “Just Talk” | No. Audio is not recorded or sent to us |
| Speech Recognition | Turn your voice commands and video narration into text | Apple’s speech recognition runs on your device when your device supports it. On older devices, Apple may process the audio on its servers under Apple’s privacy policy. We never receive the audio |
| Reminders | Add your grocery list to Reminders | No |
| Alarms | Ring cooking timers even in Silent mode, like the Clock app | No |
| Notifications | Cooking timers and alarms, and (if signed in) community activity and recipes arriving in your Inbox | Timers are local. Other notifications use Apple’s push service (Section 3) |
[[TODO: when Apple Health logging ships (Saucepan+ "Nutrition and goals"), add a Health row here (what is written to and read from Apple Health, that it stays on the device, and that HealthKit data is never used for advertising or stored in iCloud by us), update Sections 3, 8, 10 and 12, the App Privacy labels, and OPEN_QUESTIONS Q33. Not built yet.]]
2. Cloud AI features (optional, only with your permission)
Saucepan can use a cloud AI model for three things. None of them run unless you agree, and all of them need you to be signed in.
| Feature | What it does | When it runs | What we send |
|---|---|---|---|
| Cloud recipe reading | Turns messy text (like an Instagram caption or a video transcript) into a clean recipe | On devices that can’t run Apple Intelligence, and on other devices as a backup when Apple Intelligence can’t read a recipe. Only if you’ve allowed Cloud Recipe Reading | The recipe text only, such as a caption, web page text, a video transcript, or text read from a screenshot, plus the source type, page title, and the creator’s handle if there is one. Up to 12,000 characters |
| Nutrition and swaps | Estimates nutrition per serving, suggests substitutes for ingredients you might be out of, and works out a lighter version of the dish | When you save a new recipe, change a recipe’s title, servings, or ingredients, or open a recipe that doesn’t have estimates yet. Only if you’ve allowed Cloud Recipe Reading | The recipe’s title, number of servings, ingredients (with amounts and notes), steps, and any nutrition the recipe already states |
| Tag suggestions | Suggests a course, cuisine, and tags when the on-device sorting isn’t sure | Only if you turn on Ask the Cloud When Unsure (off by default) | The recipe’s title, ingredient names, existing tags, total time, and a list of tags you already use |
With each request we also send your app language, so answers come back in it.
- We ask first. The first time cloud reading or nutrition estimates could be used, the app asks whether Saucepan may send the recipe’s text to a cloud AI service. One answer covers both cloud recipe reading and nutrition and swaps. If you say no, Saucepan reads recipes on your device instead and doesn’t show nutrition estimates or swaps. You can change your answer anytime in Settings → Your Data & Privacy → Cloud Recipe Reading. Tag suggestions have their own switch in Settings → Smart Organization → Ask the Cloud When Unsure.
- What we never send: photos or videos, including photos of people, your fridge, or your pantry. We don’t send your name, email, phone number, account ID, taste profile, allergies, or your own recipe notes.
- Who processes it: our server passes the text to OpenRouter, Inc. (openrouter.ai), which routes it to an AI model, currently DeepSeek V4 Flash. If we change models, we’ll update this policy. [[CONFIRM: the OPENROUTER_MODEL, OPENROUTER_PARSE_MODEL and OPENROUTER_ENRICH_MODEL secrets are unset or set to deepseek/deepseek-v4-flash-0731 in production]] The model is run by independent AI hosting companies that OpenRouter works with. Our requests tell OpenRouter to use only hosts whose policies say they don’t store prompts or use them for training. Our requests identify our app, not you.
- Where it’s processed: the hosts OpenRouter chooses may be outside the United States, including in China. [[CONFIRM: whether we restrict cloud AI to US-based hosts; if we do, replace this sentence with “Only hosts in the United States are used.”]]
- What’s kept: our server does not store the text or log it. OpenRouter keeps basic request records (such as time, model, and size) for billing [[CONFIRM: OpenRouter prompt logging is turned off on our account, and its retention for request metadata]]. The hosts we allow say in their policies that they don’t keep the text or train on it. [[CONFIRM: our requests use OpenRouter’s data_collection “deny” filter, not zero data retention (zdr); decide whether to add zdr, and whether “deny” hosts may keep prompts briefly, e.g. for abuse checks]]
- What you get back: a recipe you save is stored like any other recipe (on your device, and synced if you’re signed in). Nutrition estimates, swaps, and lighter versions are stored with that recipe in the same way. They are never copied into recipes you publish.
- They’re estimates. Nutrition numbers, swaps, and lighter versions come from an AI model and can be wrong. They’re not medical or dietary advice. See our Terms of Use.
3. If you sign in
Signing in is optional. You can choose how to sign in. Sign in with Apple is shown first. When you sign in, we collect the following.
Account information
What we receive depends on how you sign in:
| Sign-in method | What we receive and store |
|---|---|
| Sign in with Apple | A unique Apple user ID, your email address (which can be an Apple “Hide My Email” relay address if you choose), and your name if you choose to share it |
| Email code | Your email address. We email you a 6-digit code (and a sign-in link) to prove it’s yours. No password |
| Phone number code | Your phone number. We text you a 6-digit code through an SMS provider ([[CONFIRM: SMS provider, e.g. Twilio]]), which receives your number and the code to deliver it. Message and data rates may apply |
| Your Google account ID, name, email address, and profile picture link, as Google shares them with us | |
| Your Facebook account ID, name, email address (if your Facebook account has one), and profile picture link, as Meta shares them with us |
- Sign-in emails are sent by our sign-in service, Supabase [[CONFIRM: or a custom email sender, if one is set up]].
- Linked sign-ins. If you sign in with different methods that share the same verified email address (for example, Apple and Google), they are linked to the same Saucepan account automatically.
- Google and Facebook sign-in happen on their own sign-in pages. Their privacy policies apply to what they collect there. We don’t get your password and we don’t post anything to your accounts.
- Your profile: a handle, display name, bio, optional profile photo, optional website, and whether your account is private. We create your first handle and display name from the name Apple, Google, or Facebook shares with us. If there isn’t one, your handle starts as something like “cook_4821”. We never use your email address or phone number for them. You can change both anytime. Your handle and display name are public (Section 4).
Your synced library
When you’re signed in, your library syncs to our servers so it’s available on your other devices and is backed up. This includes:
- Recipes: title, ingredients, steps, notes, tags, ratings, favorites, source links, the original imported text, nutrition (stated or estimated), ingredient swaps and lighter versions, and photos you add
- Collections, who you share a collection with, their role (viewer or editor), and who added which recipe to it
- Your household: its name, who is in it, and who added or checked off each shared grocery item or planned meal
- Invite links you create (valid for 7 days)
- Grocery lists, meal plans, and cooking history (including your notes and dish photos)
Cook Together (shared collections and households)
If you share a collection or join a household, the people in it see your handle and display name, your role, and which recipes, grocery items, or planned meals you added or checked off. Someone can add you to a collection by your handle. A household can have up to 6 people. See Section 4 for what they can see.
Taste profile and people you cook for (sensitive)
Your taste profile can include allergies and intolerances, diets (such as vegan, halal, or kosher), dislikes, and goals. Profiles for people you cook for can include the same details about them, including children. These are separate from a Cook Together household (below).
- This information can reveal health information or religious beliefs, so we treat it as sensitive.
- It’s stored on your device. It syncs to our servers only if you’re signed in, and we ask you before syncing it the first time [[CONFIRM: build the sync consent prompt]] [[CONFIRM: taste-profile sync isn’t built yet (no server table; the Settings switch does nothing). If it doesn’t ship in 1.0, say it stays on your device, and remove the sync wording here and in Sections 8 and 12]].
- We use it only to show you fit badges and allergy flags and to keep it in sync across your devices. It is never sent to cloud AI.
- We never sell it, never use it for advertising, and never share it with other users, including members of your Cook Together household. Other people see whether a recipe “fits you” only on your own device.
- For profiles of people you cook for, please add only what’s needed (a first name or nickname is enough) and only with that person’s permission, or as their parent or guardian.
Community features
If you use community features, we store:
- Recipes you publish, posts (“I made this” photos and captions), comments, likes, saves, and follows
- Which published recipes you’ve cooked, how many times, and when (others see a count, and people who follow you may see your name; Section 4)
- Reports you submit and accounts you block
- In-app notifications (for example, “Maya liked your recipe”)
- A push notification token from Apple, so we can send community notifications and “New in your Inbox” alerts to your device. You can turn these off in iOS Settings.
Server logs
Like most online services, our hosting provider automatically records technical information when the app talks to our servers, such as IP address, time, request type, and error codes. We use these logs only for security, abuse prevention, and fixing problems, and they’re deleted automatically after a short period (see Section 10). We don’t deliberately log recipe text or message contents.
4. What other people can see
| What | Who can see it |
|---|---|
| Your private recipes, lists, plans, cooking history, taste profile, Inbox | Only you. People you invite to a shared collection can see the recipes in that collection, and editors can add their own recipes to it. People in your household can see the shared grocery list and meal plan (including who added or checked each item), and the recipes planned in it. You can leave a collection or household at any time; what you added to a household list stays with the household. [[CONFIRM: move synced private recipe photos to private storage before launch; see OPEN_QUESTIONS]] |
| Your handle, display name, and role in a shared collection or household | The other people in it |
| Your profile: handle, display name, photo, bio, website, follower counts | Anyone, even if your account is private |
| Recipes you publish | Depends on the setting you choose: Public (anyone, including on the web at getsaucepan.com), Unlisted (anyone with the link), or Friends (people who follow you) |
| Your posts | Everyone, or only approved followers if your account is private |
| Comments and likes | People who can see the recipe or post |
| Who you follow and who follows you | Anyone |
| That you cooked someone’s published recipe | People who follow you (for example, “Cooked by Maya and 2 other friends”), unless you’ve blocked each other. Everyone else sees only the total count |
| How you signed in, your email address, phone number | Only you. We never show them to other users |
When you publish a recipe, other people can save a copy to their own library. If you later delete your recipe or your account, we can’t remove copies other people already saved to their devices.
5. Importing from websites, social apps, and your Inbox
When you save a recipe from a website, Instagram, TikTok, or YouTube:
- Your device may load the page or video directly from that site. That site sees a normal request from your device (including your IP address) and handles it under its own privacy policy.
- If you’re signed in, our server may fetch the public post’s caption, creator handle, and thumbnail for you. We keep a copy of this public post information (the post’s address, caption, creator handle, and thumbnail) so repeat imports are fast. This copy is not linked to you or your account. [[CONFIRM: add a job that deletes cached posts after 7 days; today they are reused for 7 days but never deleted]]
- If a website refuses to open on your device, the app tries other ways to read it. If you’re signed in, as a last resort our server may fetch that public page for you. Your link is used for that one request and is not stored or logged. For pages that are still out of reach, the app may read a saved copy of the page from the Internet Archive (archive.org), which receives the page address. You can also open the page yourself inside the app. If you do, the app reads the page as you see it on your device, including anything you signed in to, and that page is not sent anywhere except through cloud recipe reading, if you’ve allowed it.
Send to Your Inbox (optional)
If you’re signed in, you can send recipes to Saucepan from outside the app. Set it up in Settings → Account & Sync → Send to Your Inbox. Each channel is off until you connect it.
| Channel | How it works | What we receive and store |
|---|---|---|
| You message a reel, post, or link to Saucepan’s Instagram account. Meta delivers the message to us through its Instagram Messaging API | Your Instagram-scoped user ID (an ID Meta creates for our account only), your Instagram username, and the links (or a link to the shared video), the caption, and any text sent with them | |
| You message a link or a typed recipe to Saucepan’s WhatsApp number. Meta delivers it through the WhatsApp Cloud API | Your WhatsApp ID (which is based on your phone number) and the links, any text sent with them, or the recipe text in the message | |
| You forward an email to your own private Saucepan address. Our email provider, Postmark, receives it and passes it to us | The links or typed recipe in the email and its subject line. Postmark processes the whole email, including the sender’s address. We don’t store the sender’s address |
- Connecting. To connect Instagram or WhatsApp, the app shows a one-time code that works for 10 minutes. You send it from your account, and that links it to your Saucepan account. Your email address is private and random. Anyone who knows it can send to it, so you can make a new one anytime and the old one stops working.
- Your Inbox. What you send waits in your Inbox on our servers until the app picks it up and reads it like any other import. When something arrives, we send a “New in your Inbox” notification to your device.
- Replies. Saucepan may reply in the chat to confirm it got your recipe, or to explain what it can’t use.
- Disconnect Instagram or WhatsApp anytime in the same Settings screen. Meta and Postmark handle messages under their own privacy policies.
6. Saucepan+ subscriptions
Saucepan+ is sold through Apple’s App Store. Apple processes your payment. We never see your card or bank details.
The app checks your subscription status with Apple on your device. [[CONFIRM: if we add server-side receipt validation, add: “If you’re signed in, we store your subscription status and Apple transaction ID with your account so Saucepan+ works on all your devices.”]]
[[CONFIRM: The app includes the RevenueCat SDK, which is used only if a RevenueCat key is set at build time. If it ships enabled, add: “We use RevenueCat, Inc. to manage subscriptions. RevenueCat receives your App Store purchase and subscription history and, if you’re signed in, your Saucepan account ID, so Saucepan+ follows your account across devices. It does not receive your payment details.” and add RevenueCat to Section 9. If not, delete this note.]]
7. Analytics, cookies, and crash reports
In the app
- Today, the Saucepan app has no third-party analytics, advertising, or crash-reporting tools, and it doesn’t use cookies. Any usage counters (for example, how many times you’ve used What Can I Make? this week, for the free limit) stay on your device.
- If you’ve chosen to share analytics with app developers in iOS Settings, Apple may send us anonymous crash reports and usage statistics. Apple controls this, and the data isn’t linked to you.
[[PLACEHOLDER: If we add a privacy-friendly analytics SDK to the app later (for example, TelemetryDeck), update this section before release: name the provider, list the events, state that data is anonymous and not linked to you, and update the App Privacy labels.]]
On our website
Our website, getsaucepan.com, uses Google Analytics 4, run by Google. We use it to count visits and see which pages people use, so we can improve the site. It’s only on the website, never in the app.
- What it collects: pages you view, how you got to the site (such as a link or search), your browser and device type, and your approximate location (country or city), worked out from your IP address. Google Analytics 4 doesn’t log or store IP addresses.
- Cookies: Google Analytics sets first-party cookies named
_ga(and_ga_<ID>) that tell repeat visits apart. They can last up to 2 years. - No advertising: we’ve turned off Google’s advertising features everywhere (Consent Mode settings
ad_storage,ad_user_data, andad_personalizationare denied). We don’t use the data for ads or share it with advertisers. - Europe, the UK, and Switzerland: analytics cookies are off by default. Google Analytics then sends only cookieless signals that can’t tell you apart from other visitors. [[CONFIRM: add a consent banner if we want analytics cookies for these visitors]]
- Your choices: you can block or delete cookies in your browser, or install Google’s opt-out add-on (tools.google.com/dlpage/gaoptout).
- Page addresses: Google Analytics doesn’t run on invite pages. On shared recipe, post and profile pages it receives only a generic address and title (like getsaucepan.com/r/:id), never the recipe’s link, its title, or anyone’s name.
- Pictures: recipe and profile pictures on shared pages load from our storage provider, Supabase.
- Our website host, Vercel, records standard request logs (such as IP address, time, and page) to run and protect the site.
8. How we use information, and our legal bases
We use your information only to run Saucepan and keep it safe:
| Purpose | Information | Legal basis (EEA/UK) |
|---|---|---|
| Provide the app, sign-in, and sync | Account info (including email, phone number, or Google/Facebook account details, depending on how you sign in), synced library | Contract (to provide the service you asked for) |
| Community features and Cook Together | Profile, published recipes, posts, comments, follows, shared collections and households | Contract |
| Sync your taste profile and profiles for people you cook for | Allergies, diets, dislikes, goals | Your explicit consent (you can withdraw it anytime) |
| Cloud AI features (recipe reading, nutrition and swaps, tag suggestions) | Recipe text, as listed in Section 2 | Your consent |
| Send to Your Inbox | Instagram or WhatsApp ID, Instagram username, message contents, your private email address | Contract (you connected the channel) |
| Push notifications | Push token, notification content | Consent (iOS permission) |
| Website analytics | Website usage, cookie ID, approximate location | Legitimate interests (understanding how the site is used), and consent where the law requires it for cookies [[CONFIRM WITH COUNSEL]] |
| Improve our ingredient list | Ingredient names the app doesn’t recognize, not linked to you (Section 1) | Legitimate interests (making ingredient matching work for everyone) |
| Safety, moderation, and preventing abuse | Reports, blocks, content, server logs | Legitimate interests (keeping the community safe) and legal obligations |
| Support | Your emails to us | Legitimate interests |
| Legal compliance | As needed | Legal obligation |
What we never do
- We don’t sell your personal information or “share” it for cross-context behavioral advertising.
- We don’t show ads.
- We don’t track you across other companies’ apps or websites, and we don’t use Apple’s advertising identifier.
- We don’t use your content or taste profile to train AI models, and we only use AI hosts whose policies say they don’t train on it.
- We don’t make automated decisions that have legal or similarly significant effects on you.
9. Who we share information with
We share information only with the companies below. Most are service providers that act on our instructions under contracts that limit how they use it. Apple, and Google and Meta when you sign in with them or message us through them, also handle your information under their own privacy policies:
| Provider | What they do | Data involved |
|---|---|---|
Supabase, Inc. (servers hosted on Amazon Web Services in the United States, Oregon region us-west-2) |
Database, sign-in, file storage, live updates, server functions, sign-in emails; pictures on shared web pages | Account info, synced library, community content, Inbox items, ingredient names we don’t recognize, server logs |
| OpenRouter, Inc. | Routes cloud AI requests to an AI host (only with your consent) | Recipe text, as listed in Section 2 |
| AI hosting companies chosen by OpenRouter (only ones whose policies say they don’t store prompts or train on them; may be outside the US) | Run the AI model (currently DeepSeek V4 Flash) | Recipe text, as listed in Section 2 |
| Apple Inc. | Sign in with Apple, push notifications, App Store payments, speech recognition, Apple Intelligence | As described in Apple’s privacy policy |
| Google LLC | Google sign-in (if you use it); Google Analytics on our website | Google account ID, name, email, profile picture link; website usage data and IP address (Section 7) |
| Meta Platforms, Inc. | Facebook sign-in (if you use it); delivering Instagram and WhatsApp messages you send to Saucepan (if you connect them) | Facebook account ID, name, email, profile picture link; Instagram or WhatsApp ID and message contents |
| SMS provider [[CONFIRM: e.g. Twilio Inc.]] | Texts your sign-in code (if you sign in with your phone number) | Phone number, sign-in code |
| Postmark (ActiveCampaign, LLC) [[CONFIRM: entity]] | Receives email you forward to your Saucepan address | The forwarded email |
| Vercel Inc. | Hosts getsaucepan.com | Standard web request logs |
We may also disclose information:
- If the law requires it, such as a valid court order. Where allowed, we’ll tell you first.
- To protect people, such as to prevent fraud, abuse, or harm.
- In a business transfer, such as a merger or sale. The new owner must honor this policy, and we’ll tell you before your information becomes subject to a different policy.
10. How long we keep information
| Information | How long |
|---|---|
| Data on your device | Until you delete it or delete the app |
| Account and synced data (including nutrition estimates and swaps stored with your recipes) | Until you delete it or delete your account |
| Items you delete while signed in | Marked deleted right away, then permanently removed after 90 days (so your other devices can catch up) |
| Deleted accounts | Removed from our live database right away. Removed from backups within 30 days [[CONFIRM: Supabase backup / point-in-time-recovery window]] |
| Cloud AI request text | Not stored by us. The AI hosts we allow say in their policies that they don’t keep it (Section 2). See Section 2 for OpenRouter |
| Sign-in codes | Expire within an hour, and work only once |
| Inbox items | Removed 7 days after the app picks them up. Items the app never picks up are removed after 30 days |
| Instagram and WhatsApp connections | Until you disconnect them or delete your account. Connection codes expire after 10 minutes |
| Your private Inbox email address | Until you make a new one or delete your account |
| Forwarded emails at Postmark | [[CONFIRM: Postmark inbound message retention on our plan]] |
| Cached public post info | Not linked to you. [[CONFIRM: up to 7 days once a cleanup job is added; today it isn’t deleted]] |
| Ingredient names we don’t recognize | Kept as counts until we add the name to our ingredient list. Not linked to you |
| Reports | As long as needed to handle them and keep the community safe, up to 2 years [[CONFIRM]]. Your link to reports you filed is removed when you delete your account |
| Server logs | Up to 30 days [[CONFIRM: Supabase log retention on chosen plan]] |
| Website analytics (Google Analytics) | [[CONFIRM: GA4 data retention setting, 2 or 14 months]]. _ga cookies last up to 2 years in your browser |
| Website request logs (Vercel) | [[CONFIRM: Vercel log retention on our plan]] |
| Support emails | Up to 3 years, then deleted [[CONFIRM]] |
11. Security
- All traffic between the app and our servers is encrypted (HTTPS/TLS).
- Our database uses row-level security, so each account can read only its own private data.
- Your sign-in session is stored in the iOS Keychain.
- Messages from Instagram, WhatsApp, and email are accepted only when they carry Meta’s or Postmark’s verified signature or password.
- Only Aaron Gold has administrative access to the servers [[CONFIRM]].
No system is perfectly secure. If a breach affects your personal information, we’ll notify you and the authorities as the law requires.
12. Your choices and rights
Everyone, wherever you live, can:
- See and export your data. Recipes can be exported from the app (Settings → Your Data & Privacy → Export My Recipes). For a full copy of what’s on our servers, email us.
- Correct your data. Edit your recipes and profile in the app.
- Delete your data. Delete individual items in the app, or delete your whole account in Settings → Delete Account. This works however you signed in. It permanently deletes your account (including your email address, phone number, and linked sign-ins), synced library, published recipes, posts, comments, likes, follows, photos, Inbox items, Instagram and WhatsApp connections, your Inbox email address, and push tokens from our servers. If you used Sign in with Apple, we also ask Apple to revoke Saucepan’s access. If you’re in a Cook Together household, it passes to the next member, and the grocery items and planned meals you added stay on its shared list and plan without your name. Recipes stored on your device stay there until you delete them or the app.
- Withdraw consent. Turn off Cloud Recipe Reading (which also stops nutrition estimates and swaps) or taste-profile sync in Settings → Your Data & Privacy, turn off Ask the Cloud When Unsure in Settings → Smart Organization, disconnect Inbox channels in Settings → Account & Sync → Send to Your Inbox, or turn off notifications in iOS Settings.
- Use the app without an account.
[[TODO: when Cookbook PDF export ships, add it to "See and export your data" (and say whether the PDF is made on the device). Not built yet.]]
To make a request, email support@goldtechsolutions.net. We’ll reply within 30 days (45 days where state law allows). We may need to confirm the request comes from you, for example by asking you to email us from the address linked to your account or to confirm in the app. We won’t treat you differently for using your rights.
If you’re in the EEA, UK, or Switzerland
You also have the right to restrict or object to processing, and to complain to your local data protection authority. Our servers are in the United States. Cloud AI requests may also be processed by AI hosts in other countries, including China (Section 2). When we transfer your data outside your country, we rely on our service providers’ Standard Contractual Clauses (and the UK Addendum) [[CONFIRM: DPAs signed with Supabase, OpenRouter, Google, Meta, Postmark, Vercel, and the SMS provider]]. Our EU/UK representative: [[CONFIRM: appoint an EU and UK Article 27 representative, or confirm not required]].
If you’re in California or another US state with a privacy law
In the past 12 months, we’ve collected these categories of personal information: identifiers (account ID, Apple, Google, or Facebook account ID, email address, phone number, handle, Instagram-scoped ID and username, WhatsApp ID, push token, and the website analytics cookie ID); personal records (name, email address, phone number); internet or electronic activity (community interactions, server logs, and pages viewed on our website); approximate location (country or city, from website visits); audio-visual information (photos you upload, and profile picture links from Google or Facebook); and sensitive personal information (health-related allergy and diet details, and diets that may reveal religious beliefs, only if you sync your taste profile). The sources, purposes, and recipients are described above.
- We do not sell or share personal information, and haven’t in the past 12 months. Google’s advertising features are turned off on our website.
- We use sensitive personal information only to provide the features you ask for, so there’s no need for a “Limit the Use of My Sensitive Personal Information” link.
- You can use an authorized agent to make a request. If we deny your request, you can appeal by replying to our decision; we’ll respond within 45 days.
Consumer health data (Washington, Nevada, and similar laws)
Allergy, intolerance, and some diet information may count as “consumer health data”. We collect it only from you, only to show allergy flags and fit badges and keep them in sync, and only with your consent. We don’t sell it, share it with third parties other than our hosting provider, send it to cloud AI, or use it for advertising. You can see, export, or delete it at any time as described above. Nutrition estimates describe a recipe, not you. [[CONFIRM WITH COUNSEL: whether a separate Consumer Health Data Privacy Policy page is required]]
13. Children
Saucepan is not directed to children under 13, and we don’t knowingly collect personal information from children under 13. You must be at least 13 to create an account (or older if your country requires it). If you believe a child under 13 has given us personal information, email us and we’ll delete it.
Profiles for people you cook for let an adult note a child’s allergies or diet. That’s information the adult provides. It stays on the adult’s device unless they turn on taste-profile sync, it’s never shown to other people (including members of a Cook Together household), and it follows the same rules as the rest of the taste profile.
14. Changes to this policy
If we make changes, we’ll update the “Last updated” date. If a change materially affects how we use your information, we’ll tell you in the app before it takes effect and, where required, ask for your consent again.
15. Contact
- Email: support@goldtechsolutions.net [[CONFIRM]]
- Mail: Gold Tech Solutions, [[CONFIRM: mailing address]]
- Web: https://getsaucepan.com/support