Privacy Policy
Last updated November 4, 2026 · Version 2026-11-04
The short version
- Without an account, your kitchen stays on your phone and isn't sent to us. With one, family kitchens sync for their members, and your private kitchen syncs as a Premium cloud backup.
- Free voice becomes text on your phone, and its recordings stay there. Premium voice, when it launches, sends the parts where you name foods to Google's speech service only after you agree.
- Reading a recipe photo or a short recipe video, Stocky's suggested amounts and Ask Stocky send that photo, video, recipe or question to Google's Gemini AI. We don't add your name, email, diets or kitchen, but whatever is in what you send goes with it. Our servers keep a record of each read or question for about 90 days (for videos, with the recipe it read), not your photos, questions or answers, unless you report an answer, which we keep about 90 days to review. A recipe read from a public video with Premium can be kept up to 180 days for others who import that post.
- Diets and allergies are optional, shared with a family only if you agree, never used for ads and never added to what we send to AI.
- Star-rating totals are public. The owner account that runs our servers can see what's stored there; here's how we use that.
- When ads launch, the free version will show them; Premium won't. Advertisers never get your kitchen, recipes, voice, diets or family content.
- No analytics or crash-reporting tools of our own (Google's barcode scanner sends its own technical metrics; see below).
- Delete your account in the app or from our website.
Who we are
Stock & Savor LLC, a Washington limited liability company ("we", "us"), makes the Stock & Savor app for tracking the food in your kitchen, cooking with it and planning meals with your family. This policy covers the app and this website. Today, accounts and everything that uses our servers are open only to invited testers. Features that aren't available yet are marked "when it launches".
What stays on your phone
Without an account, what you add is saved on your phone and isn't sent to us. The app still goes online to open the recipe pages and posts you import (see below) and to download the public star-rating totals from our cloud storage. That download shows Google your IP address and a code for each imported recipe link whose totals it checks, but no account details or kitchen contents. No recipe video is sent to AI while no account is signed in. When the app opens it also starts Google's Firebase services, which check with Google Play (on iPhone, Apple) that this is the real app; that check shows Google your IP address and the device check result, not your kitchen.
Even with an account, these stay on your phone only: imported recipes' full text and photos (your account keeps each title and link; a recipe you share with a family kitchen also keeps a copy there for up to 90 days), recipe notes, personal meal plans, Cook Mode progress and cook history, spoken recipe drafts, taste preferences, Stocky's suggestions, voice recordings for replay, food reminders and cooking timer alarms.
With an account, your phone also keeps a copy of your kitchens so the app works offline. When you leave a family kitchen or are removed from it, the app deletes its saved copy of that kitchen's food, places and place photos from your phone. Signing out doesn't remove your copy from the phone; deleting your account does (see Deleting your account), and so do clearing the app's data and uninstalling.
Phone backups
Your phone's backup (Android's backup and new-phone transfer, or iCloud and computer backups on iPhone) copies the kitchen you keep without an account, its recipes and their photos, meal plans, cook history and settings. It leaves out diets and allergies, everything the app keeps for a signed-in account (its kitchen copy and unsent changes, recipes, meal plans, recent voice words and problem reports waiting to send), the app's sign-in, voice recordings and temporary files. If a backup brings a sign-in back anyway, the app signs it out the first time it opens. Backups follow your phone's settings, go to your own Google or Apple account, and aren't erased when you uninstall the app.
The app also keeps a small record on your phone of which versions of these policies, the Terms and Ask Stocky's consent were agreed to and when, with the account ID for each account that agreed. Deleting an account on this phone removes its entries; a phone backup made earlier may still include them.
What we keep when you have an account
| What | Why, and who sees it |
|---|---|
| Email, the name you choose, your password (held in scrambled form by Google's sign-in service) or your Google sign-in, which shares your name and email with us, and when the account was made and last signed in | To sign you in. We email you only to verify your address or reset your password; Google's sign-in service sends those emails. |
| Your private kitchen: foods, amounts, dates, places, custom foods, the grocery list and your recipe book (catalog recipes, and imported recipes' titles and links) | Premium cloud backup and sync across your phones. In the app, only you see it (the people who run our servers can reach stored data, as described below). |
| Family kitchen content: food, places, the grocery list, recipe book and shared recipe copies, meal plans, meal requests (for a catalog recipe or one shared with that kitchen, named by its shared title), votes and comments | Synced for the kitchen's members, who all see it (see Family kitchens). |
| Your star ratings and "made it" marks | Linked to your account. Totals (counts and averages, no names) are public: anyone on the internet can download them, not only app users. If you're the first to rate an imported recipe, its title and link are saved with its totals. An imported recipe link gets a public total only after at least three people have rated it, so no one person's stars show, and the rating files can be fetched one by one but not browsed as a list. |
| Diets and allergies, only if you save them | To mark or hide recipes and, if you share them, warn your family (see below). |
| Place photos, only when you choose "Share with My Kitchen" | So that kitchen's members can see where things are kept. |
| For each phone that allows notifications (up to 10): a push token, a random ID the app makes for that phone, and whether it's Android or iPhone; and your notification settings. Your phone makes no notification token until you sign in, and asks to delete it when you sign out (if the phone is offline, it tries again the next time it opens). Google's Firebase also keeps its own installation ID under its own rules. | To send family notifications and "recipe ready" notices to your phones (see Notifications). |
| Records of AI reads, suggestions and Ask Stocky questions (counts, times and outcomes; Ask Stocky records keep no questions or answers, and video records keep the recipe read), and any Ask Stocky answer you report (your question, the answer, the changes it suggested and your reason) | To apply monthly and daily limits, prevent abuse, review reported answers and, for videos, avoid reading the same post twice (see AI reads). |
| Agreement records: which version of these policies and the Terms, and of Ask Stocky's consent, your account agreed to, when you tapped it on your phone and when our server recorded it (the latest of each kind and a history of up to 20 agreements) | To show what you agreed to and when. |
| Problem reports you choose to send | To look into voice mistakes (see Problem reports). |
| Technical data: Google's logs of requests to our servers, which normally include your IP address and app details, and our own server logs, which record what happened (like counts and error codes) but not your content | To run sign-in and our servers and keep them secure. Kept 30 days. |
| While the app is in testing: your tester approval and any test plan | To let invited testers use our servers. Test plans aren't paid subscriptions. |
Signing in never uploads a phone-only kitchen unless you choose to copy it.
Who at Stock & Savor can see your information
- The account that runs our Google Cloud project, held by Stock & Savor's owner, can read everything stored on our servers and in their logs, including the list of accounts.
- Admin accounts can read the problem reports people send, with the sender's account name, and play their recordings.
- Our admin tools show each account's AI-read history (counts, times and a code for each post read) and let us set limits. When one account sends many video reads, admins' phones get an alert with the start of its account ID and the count; the alert is kept for 90 days, or until that account is deleted.
We use this access only to run and fix the app, keep it secure and prevent abuse, handle problem reports and your requests, and when the law requires it. We don't browse kitchens, recipes, comments or diets for any other reason.
Family kitchens
People join a family kitchen with an invite code or QR code and their own account. Invite codes are eight characters, work once and expire after 7 days; invite records are deleted 30 days after they expire, and when you delete your account your name is removed from the ones you made or used. A copied code is marked sensitive, so Android leaves it out of clipboard previews. Before you join, the app shows the name the family will see and lets you change it, and the family's Head Squirrel is told who joined. Members see:
- the kitchen's content, with the writer's name on meal requests, votes and comments;
- each member's name and role (Head Squirrel, Squirrel, Chipmunk or Visiting Squirrel, explained in our Terms). The name is your account's name, or a nickname for that family set by you or the Head Squirrel;
- a Visiting Squirrel's leaving date;
- former members' names and nicknames (the Head Squirrel also sees a list of former members), until a former member deletes their account;
- for each food, a code for the account that last changed it. The app doesn't show it, but members' phones receive it;
- diets and allergies only of members who chose to share them with that family.
If your account has no name, the part of your email before the @ is used. Member records saved before October 30, 2026 may hold your whole email, which members' phones can read. Please set a name.
If you leave, what you added stays with the kitchen. When a Squirrel accepts your meal request, "Requested by" with your name and note is added to the family's plan and stays there. Deleting your account removes your name from the member list (views then show a generic name), but names already saved in comments, meal requests, "Requested by" notes, change records and members' phones stay while those are kept.
Diets and allergies
Allergies and some diets (like halal or kosher) can reveal your health or beliefs, so we take extra care:
- We collect them only if you choose to save them. Change or clear them any time.
- They're used only to mark recipes that list those foods, hide those recipes if you choose, and, if you share them, warn your family on recipes and meal requests.
- A family kitchen sees them only if you agree to share them with it. Sharing starts off and stops when you turn that family's Share with This Family Kitchen switch off, leave, or clear all your choices. Members' phones don't save them.
- They're never added to what we send to AI services or put in notifications, never used for ads, given to advertisers or sold.
- On your phone they're saved in a file that phone backups leave out (see Phone backups).
Our Consumer Health Data Privacy Policy has the details.
Voice
The app uses the microphone only while a voice screen is open (adding food, creating a recipe or adding to the grocery list by voice, or practicing in the tutorial), and only after you tap to start. It stops when you leave the app and never listens in the background.
Free voice, on your phone
Your phone's own speech service (from Google or Apple) turns speech into text on the phone. The app requires on-device recognition, so voice isn't offered on phones that can't do it, and it gives the speech service your food and place names as hints, on the phone. We don't send the audio anywhere unless you attach it to a problem report.
When you add food or create a recipe by voice, the recording is kept on your phone so you can replay it for up to 24 hours; grocery list and tutorial voice keep no recording. Expired recordings are deleted the next time you use voice, so they can stay longer on a phone you don't use. Voice recordings, the words heard in the last 24 hours and problem reports waiting to send aren't in phone backups.
Problem reports
When voice gets something wrong, you can tap Report and send it. A report includes the words heard, the item, your note, the app version, your phone's system version and language and, on Android, its model and speech service. On Android you can also turn on "Send My Recording" to add up to 30 seconds of the recording. It starts off, and the app remembers your last choice on that phone. On iPhone the switch isn't shown and no recording is sent. When Premium voice is in use, the report also includes what it heard.
Admins read reports with your account's name and can play the recording. Recordings are deleted after about 30 days (about 14 days after the report is closed, if sooner) and the text after about 90 days. A reply from us may quote the words you reported and waits up to about 90 days for your app to collect it. A report that can't be sent yet is retried for up to 7 days; it stays in the app's files until they're next rewritten or your account's files are cleared. In admin test tools, an administrator can also send a diagnostic report with the phrase, what the app understood and technical details, kept about 90 days.
Premium voice, when it launches
Today only our own admin accounts can use it, for testing. It works the same way now and at launch:
- It's optional and starts off. Turning it on shows a "Use Premium Voice?" screen that explains what's sent; it stays off unless you tap Use Premium Voice. If what that screen says changes, the app asks again. Switch back to on-device voice any time in Account.
- When you tap Stop after adding food by voice on Android, the app sends the parts of the recording where you named foods, with long pauses cut, to Google Cloud Speech-to-Text (Chirp), which returns text.
- Google is our processor under its Cloud Data Processing Addendum and handles the audio in the United States. Its terms say it uses the audio to improve its services only if we opt in to data logging, and we won't.
- Our servers don't save the audio (we keep only a daily request count, to limit use), and we never use your voice to identify who's speaking, build a voice profile or target ads.
- Someone talking near your phone at that moment may be included.
Notifications
Every notification asks to be treated as private: if your phone hides sensitive notification content on the lock screen, Android shows only the app's name until you unlock. The notifications the app sets itself never name a food or recipe in their title, and a locked iPhone set that way shows only the title. If your phone shows all content, everything shows.
Set on your phone, with nothing sent to us:
- Food reminders name up to three foods in their text. Turn on Hide Food Names in reminder settings to leave them out.
- Cooking timers and reminders say "Time's Up" or "Time to Stir", with the recipe and timer in their text.
- Import notices say a recipe is ready to review or couldn't be imported.
Sent from our servers (push), following your Show Meal Names setting:
- Family meal requests and comments. With Show Meal Names off (the default), they say only who did what, like "[name] asked for a meal". Turn it on to show the meal, comments and reasons too.
- Recipe ready. When our servers finish reading a recipe video, a notice says "Your recipe is ready to review". It names the recipe only if Show Meal Names is on. It carries the post's link either way, so a tap opens the review.
Push notifications pass through Google's Firebase Cloud Messaging (and, when push launches on iPhone, Apple's push service). With Show Meal Names off, a push carries no meal name, recipe name or comment, in what it shows or in the data sent with it.
Photos, barcodes, links and posts
- Place photos stay on your phone unless you choose "Share with My Kitchen". A shared photo is made smaller and its hidden details (like location) are removed first. If you stop sharing or replace one, the kitchen loses access at once; the uploaded copy is deleted after seven days, and we can recover deleted files for seven more. Members' phones may keep copies they downloaded.
- Barcodes are read and looked up on your phone, in USDA FoodData Central and Open Food Facts data built into the app. No pictures are kept. On Android, barcodes and invite QR codes are read on your phone by Google's ML Kit and Google Play services; Google says these send it technical performance and usage metrics (not your pictures) and may download updates. On iPhone, the camera system reads invite codes.
- Recipe links. Your phone reads the recipe straight from the site, saying it's Stock & Savor's recipe importer and sending no cookies, so the site sees a visit from your phone's IP address, not from us. If the site turns that away, your phone loads the page once, out of sight, the way its built-in web browser would: that runs the site's own scripts, which can include its ads and trackers, while the page loads. Its cookies and storage are cleared before and after, you can't sign in there, and the app keeps only the recipe. You're never shown the site, and the app never answers a site's check that you're human. The recipe's photo is downloaded the same way (for Instagram, from instagram.com) and kept on your phone, never uploaded. Recipes a family member shares come onto your phone the same way, on their own while you're on Wi-Fi (on Android, also while the app is closed).
- Social posts. For a post you share from Instagram, TikTok, YouTube, Facebook or Pinterest, the app reads its public page the same way, without your account on that site, and uses its caption (for YouTube, the title and description). TikTok returns a cookie of its own, which the app sends back when it fetches that video; no cookie of yours is sent.
Apart from the AI reads below and the titles, links and family copies described above, we don't receive the pages or posts you import.
AI reads
These features send content to Gemini, Google's AI, which acts as our service provider. We don't add your name, email, saved diets or kitchen to what Gemini receives, but anything personal inside the photo, video, recipe or question you send goes with it, so leave those details out. Google Cloud's terms for these services say Google doesn't use this content to train its AI models without our permission. Google may keep it for a limited time, for example to cache answers or check for abuse, as its terms describe.
Recipe videos
- When an Instagram reel's or a TikTok's caption has no recipe or no steps, and the video is 8 seconds to 3 minutes long, AI can read the video. Free accounts are asked "Read the Video?" first and get 5 reads a month. With Premium, videos are read automatically, without asking.
- Our servers download the post's public video from Instagram or TikTok (from Google Cloud, as Stock & Savor, with nothing about you) and send it, with the caption's title and ingredients, to Gemini on Google Cloud Vertex AI, which writes out the recipe it sees and hears. For a YouTube Short whose description has no recipe, Gemini is given the public Short's link and watches it; nothing is downloaded from YouTube. Longer videos and ordinary YouTube videos are never sent: their caption or description is used.
- If our servers can't, your phone downloads the video and sends it to Gemini through Firebase AI Logic. Videos are read only while an account is signed in.
- We keep a record of each read for 90 days, with the recipe it read and a code made from the post's link with a secret key of ours, so only we can match it to the post, and monthly totals (counts and recent times) for about 13 months.
- With Premium, the recipe read from a public post is also kept for up to 180 days and given to anyone else who imports the same post, so it isn't read twice. It doesn't name you, but while your read's record exists (90 days, or until you delete your account) we could match the two through the post's code.
Recipe photos (Premium)
The one to three photos you choose are made smaller and have their hidden details (like location) removed on your phone, then are sent through our servers to Gemini on Vertex AI, which copies out the recipe and marks lines it isn't sure of. Our servers don't keep the photos or the recipe, only a record of each read (pages, size, result, how many lines were unsure and whether it was handwritten) for 90 days, and monthly totals for about 13 months.
Photo of Groceries, when it launches
Only our team's test builds have it today. It sends up to three photos, or one video clip up to about a minute, through our servers to Gemini, which lists the groceries it sees for you to confirm; we keep the same kind of read record as for recipe photos. A clip is first made smaller as a picture-only copy, with its sound removed and the details the camera saved with it (like when and where it was recorded) blanked. A clip the phone can't clean this way isn't sent.
Stocky's suggested amounts (Premium)
When you tap Ask Stocky, the recipe's title, servings, ingredient lines and steps are sent through our servers to Gemini to suggest amounts for lines that give none. Suggestions are saved on your phone, marked as Stocky's, and become part of the recipe only if you tap Use. Our servers keep only a record of each request (how many lines, how many suggested) for 90 days, and monthly totals for about 13 months.
Ask Stocky (Premium)
When you ask Stocky a question about a recipe you're writing, the recipe as it is on your screen (its name, ingredient lines and steps) and your question are sent through our servers to Gemini on Vertex AI, with instructions we write, and its answer comes back to your phone. Nothing about your account, kitchen, family or diets is added, but whatever you type in the question is sent as written, so leave out anything personal. Stocky's answers are marked as AI, and its suggested changes are made only if you tap Use. Unless you tap Report, our servers don't keep the recipe, your question or the answer: only a record of each question (where you asked, how many lines, how long the question was, whether it was answered) for 90 days, and monthly and daily totals for about 13 months. Before your first question, the app shows a short AI notice you agree to, and our server checks for it with each question. If you tap Report on an answer, the question, the answer and the changes Stocky suggested are sent to us for review, with which AI model answered, and kept about 90 days. Before an answer reaches you, our server checks its temperatures, storage times and safety promises against USDA guidance and replaces anything that doesn't match; it keeps only whether that happened, never the words. Deleting your account deletes these from our servers.
Ads in the free version, when they launch
The free version will show ads from an advertising partner we'll name here first. Premium has no ads. This is how ads will work at launch:
- The partner's code collects advertising and app set IDs, IP address and approximate location, device and app details, app and ad interactions (like launches and taps), and crash and performance data, to show and measure ads and prevent fraud.
- It never gets your kitchen, recipes, voice, diets, family content, name or email from us.
- Where the law requires (as in the EEA, UK and Switzerland), we'll ask before the ad service stores or reads identifiers on your phone, even for non-personalized ads. Without consent, you'll see limited ads that don't use them, or none.
- In US states with privacy laws, opt out of personalized ads in Account → Privacy Choices, or with Global Privacy Control where the law recognizes it. You can also reset your advertising ID.
- We don't sell your information for money, but some US state laws count personalized ads as "selling" or "sharing" it. The opt-out covers that.
- We won't use the data of anyone we know, or should know, is under 18 for personalized or targeted ads, or sell or share it. Nobody we know is under 13 sees ads.
- Ads are filtered for a family food app (no alcohol, gambling, dating, weight-loss or supplement ads).
Coming features
Phone AI features will be optional and off by default, and use your phone's own AI model, so what they read stays on your phone (its maker may download or update the model). We don't use your information to train AI models.
Estimated dates are worked out on your phone from USDA FoodKeeper guidance built into the app; working one out sends nothing. If the food is synced, its saved date syncs with it.
Who processes your information
| Service | What it does, and where |
|---|---|
| Firebase Authentication (Google) | Signs you in and sends verification and password-reset emails. May process data wherever Google operates. |
| Google Sign-In | "Continue with Google" on Android. Shares your name and email with us. |
| Cloud Firestore, Cloud Functions and Cloud Storage (Google Firebase) | Store and sync account data, shared photos, problem-report recordings and the public rating totals, and run our servers. United States (Iowa). |
| Google Cloud Logging | Keeps our server logs for 30 days. May process data wherever Google operates. |
| Firebase App Check, with Google Play Integrity (Android) and Apple App Attest and DeviceCheck (iPhone) | Checks that requests come from a genuine copy of the app on a real phone. Run by Google and Apple. |
| Firebase Cloud Messaging (Google) | Delivers push notifications. May process data wherever Google operates. |
| Apple Push Notification service | Delivers push notifications to iPhones, when push launches there. |
| Google Cloud Vertex AI and Firebase AI Logic (Gemini) | Read recipe videos and photos (and grocery photos, when that launches), suggest amounts and answer Ask Stocky questions. May process data wherever Google operates. |
| Google Cloud Speech-to-Text (Chirp) | Premium voice, when it launches (today our admin accounts only). United States. |
| Google Play | Delivers the app and may deliver its recipe photos; will handle subscriptions when they launch. |
| Our billing provider, if we use one | Manages subscriptions, when paid plans launch. We'll name it here first. |
| Our advertising partner | Ads, when they launch. It also uses ad data under its own policy. |
| Our website host | Delivers this website. |
Recipe websites, Instagram, TikTok, YouTube, Facebook and Pinterest aren't our service providers. Your phone, and for video reads our servers, fetch their public pages and videos as described above, and each site handles those visits under its own policy.
Google describes its handling in Google's Privacy Policy and Firebase's privacy page. We may also disclose information if the law requires it, to protect someone's safety, or in a sale or merger, where this policy keeps applying.
How long we keep it
Times below are when records become due for automatic deletion; cleanup runs in the background, so removal can finish a little later.
| Information | Kept |
|---|---|
| Your account and private kitchen | Until you delete them or your account |
| Family kitchen content | While the kitchen exists. Meal requests clear two days after their day; comments stay until their writer, the Head Squirrel or a Squirrel removes them; a shared recipe copy stays up to 90 days after it was last saved, or until its link is removed. |
| Removed foods and change records | Removing a food hides it, but its details stay in sync records until the kitchen is deleted. Change records can include comment or grocery list text; newer comment records are deleted after 30 days, others stay while the kitchen exists. |
| Family notifications | Deleted two days after they're sent or dropped |
| Notification registrations | Until you sign out on that phone, sign out everywhere, the phone stops accepting notifications, an eleventh phone replaces it, or you delete your account |
| Records of AI reads, suggestions and Ask Stocky | Each read's or question's record about 90 days (for videos, with the recipe read and the post's code); reported Ask Stocky answers about 90 days; daily and monthly totals about 13 months; deleted with your account |
| Agreement records | While your account exists; deleted with it |
| Invitation records | About 30 days after the code expires; deleting your account removes your name and account ID from invitations that stay with a kitchen |
| Diagnostic reports from admin test tools | About 90 days |
| Voice recordings on your phone (for replay) | About 24 hours, removed the next time voice is used |
| Limits, blocks and invitation-attempt records, and the last "sign out everywhere" time | While your account exists; deleted with it |
| A recipe read from a public video with Premium | Up to 180 days, also after you delete your account |
| Alerts about heavy video-read use | 90 days, or until the account they name is deleted |
| Problem reports | Recordings about 30 days (about 14 days after the report is closed, if sooner); text about 90 days; a reply waiting for your app until it's collected, about 90 days or your account is deleted |
| Rating totals, and an imported recipe's title and link saved with them | While we offer ratings, also after you delete your account (your own stars are removed, and if you were a recipe's only rater, its title and link go too) |
| Server logs | 30 days |
| Deleted files (place photos, problem-report recordings) | Recoverable by us for 7 days after deletion. Our database has no backups; deleted records can be read back for up to an hour. |
| Deleted-account records | Your account ID and the deletion date, kept with no end date so the account can't be used or refilled by mistake |
| Sign-in data after you delete your account | Google says it's removed from Firebase's live and backup systems within 180 days and that sign-in IP logs are kept for a few weeks |
| Anything saved only on your phone | Until you delete it, clear the app's data or uninstall (phone backups may keep copies) |
Daily cleanups delete eligible data in batches, so deletion can take longer, especially during a backlog.
Deleting your account
Delete your account in the app at Account → Account & Security → Delete Account, or through our account deletion page, which lists exactly what is removed and what stays. In short: your sign-in, private kitchen and its photos, ratings, diets and allergies, notification registrations, problem reports, AI-read records and alerts about your account are removed from our servers. What you added to family kitchens stays with them, under a nameless former-member record; the records in the table above marked "also after you delete your account" stay for their time; and, while the app is in testing, your tester approval stays. On the phone you delete from, the app signs out and removes what it kept for the account, including its kitchen copy, recipes, meal plans, diets and allergies, recent voice words and unsent problem reports. Your other phones do the same the next time they open signed in to it. The kitchen you keep without an account, downloaded recipe photos, cook history and the phone's settings stay until you clear the app's data or uninstall. A Head Squirrel first hands over or closes a family kitchen others are in. Deleting your account doesn't cancel a Google Play subscription.
Your choices and rights
Wherever you live, you can change your information in the app, choose what your family sees, turn off notifications and delete your account. Ad choices and a Premium voice switch arrive when those launch. Email us for a copy of your account data (no in-app export yet) or to correct or delete it. We reply within 30 days (if a request is complex, we may take up to 45 more days and will tell you why), may confirm it's you through your account's email, and won't treat you differently for asking.
US states, including California
Depending on your state, you can also opt out of "sale", "sharing" and targeted ads (Account → Privacy Choices once ads launch, or Global Privacy Control) and limit use of sensitive information, which we use only for what you asked, like diet warnings. We collect identifiers (email, IP address, and account, device, push and, when ads launch, advertising IDs), account and kitchen content, audio (problem-report recordings you send, and Premium voice when it launches), photos and videos you ask us to read, diets and allergies you save, and, through ads when they launch, approximate location and app and ad interactions. You can use an authorized agent. To appeal a refusal, reply to it; you can then contact your state attorney general.
EEA, UK and Switzerland
| Purpose | Legal basis |
|---|---|
| Your account, sync, family kitchens, notifications, Premium, and the photo and video reads and suggestions you ask for (or, with Premium, that run automatically) | Our contract with you |
| Diets and allergies, Premium voice, personalized ads, and storing or reading identifiers on your phone for any ads | Your consent (explicit for diets and allergies), which you can withdraw any time |
| Security, preventing abuse (including read limits and alerts), problem reports you send, keeping a read recipe so the same post isn't read twice, and showing non-personalized ads once any needed consent is given | Our legitimate interest in a safe, working app and paying for the free version |
| Answering lawful requests | Legal obligation |
Information is processed in the United States and, for services like Firebase Authentication, Cloud Messaging, Cloud Logging and Gemini, wherever Google operates, under Google's standard contractual clauses or the EU-US Data Privacy Framework (with its UK and Swiss extensions). You can also restrict, object to or move your data, and complain to your local data protection authority.
Children
Accounts are for people 13 and older. In the EEA and Switzerland, you must be 16 unless your country sets a lower age (13 to 15). Before you make an account, the app asks your birth month and year and checks them on your phone against the age for the region your phone is set to (16 if it names none). It keeps only the result on your phone (a "too young" answer for 24 hours) and never keeps or sends your birth month or year. With Continue with Google, the age check repeats on that phone until someone passes it once. "Chipmunk" is a role with limited permissions, not an age. We don't knowingly collect information from children under 13. If you think a child has given us information, contact us and we'll delete it.
Security
Information is encrypted between your phone and our servers, and when Google stores it. Our servers check that you're a member of a kitchen before showing or changing anything in it. No system is perfect; if a breach affects you, we'll tell you as the law requires.
This website
This website has no ads, analytics or cookies. Our host receives your IP address and browser details to deliver its pages. The pages load fonts from Google Fonts, which receives your IP address.
Changes
If we change this policy, we'll update the date above. If a change is significant, we'll say so in the app before it takes effect.
Contact
Questions or requests about privacy: privacy@stockandsavor.app.