Privacy policy

Public website recipe previews

When you request a recipe preview on thepantryai.com, The Pantry sends your dinner idea and selected chef to OpenAI to create the recipe. It sends the resulting recipe details to OpenAI to create its picture. If you choose voice input, your recording is sent to OpenAI for transcription. Recording begins only after you use the microphone control and grant your browser microphone access.

The public preview does not read your private kitchen or attach your account details, saved pantry, journal or conversation history. It runs only when you ask for a preview or transcription. This policy covers AI features on the website and in the app.

What you choose to share

Your account can contain your name, email address or phone number, sign-in details, pantry items, shopping lists, receipts, food photos, recipes, meal plans, cooking progress, journal entries, messages, and preferences you save. Allergies and dietary needs may reveal sensitive information. Manual pantry tools and saved recipes remain available without using AI features.

We use this information to provide the features you request, keep your kitchen in sync and secure sign-in. Technical requests also include information such as IP address, browser or device details, and operational logs.

Activity analytics

We use first-party analytics to understand visits, feature usage, returning users and failures across our website and hosted app. Records contain page categories, action names, response codes, timing, a random browser identifier and, when signed in, your account identifier. They do not contain messages, recipes, receipts, photos, dietary details, raw IP addresses or full URLs. A first-party cookie recognizes a browser for up to 90 days; session storage groups activity until 30 minutes of inactivity.

Analytics are stored in Supabase and available only to approved Pantry administrators. Events expire after 90 days. Account deletion removes linked analytics. You can turn off activity analytics below; a signed-in choice also applies to confirmed kitchen action records. We honor Global Privacy Control and Do Not Track. Operational security and the records needed to provide your kitchen remain separate.

Sign in with Google

When you choose Continue with Google, Google shares sign-in information with Supabase, our authentication provider. This includes your Google account identifier, name, and email address, and can include profile information such as your profile picture when Google provides it. Supabase stores this information in your authentication record. The Pantry uses it to verify your sign-in, connect your account to your kitchen, and show your name, email address, and sign-in method in Account & profile.

This connection requests basic identity information, not access to your Gmail messages, Drive files, or calendars. The Pantry does not receive your Google password. You can request account deletion in Account & profile; this includes removal of your Supabase sign-in record through the deletion process described below.

AI and voice

Before AI uses your information, we show a short OpenAI disclosure beside the existing action. Using that action records your permission before information is sent or recording begins. Permission is separate from signing in and from the device’s camera or microphone permission. You can withdraw it below without deleting your kitchen.

The public homepage preview uses your dinner idea or voice recording without reading your private kitchen. Its full recipe stays in a temporary draft for up to 24 hours. Choosing Continue in the app carries that recipe into the existing signup and kitchen flow.

When you use an AI feature, OpenAI receives the photos, receipts, messages or voice you submit and the relevant pantry items, recipes, preferences, allergies and conversation context needed for AI recipe creation, photo understanding, cooking chat, transcription, generated images and live voice. Reading your personalized answers aloud sends that text to OpenAI. Optional cooking research sends a reduced cooking query to OpenAI’s web search service.

When available, browser speech recognition supplies dictation or live captions through your browser or device speech service. That service may receive microphone audio under its own terms. Recording starts only after you use a microphone control and grant your browser or device microphone access.

OpenAI states that API data is not used to train its models by default unless the customer opts in. OpenAI retention varies by feature and account settings. See OpenAI’s API data controls. You can stop voice recording with the app’s controls. Information already sent to a provider cannot be recalled by stopping a recording.

Services that help run the app

• Supabase: account authentication, kitchen records, messages and media storage.
• Vercel: hosting, delivery and server execution, including technical request information.
• Resend and Twilio: sign-in and invitation email, and phone verification when you choose those methods. They receive the address or phone number and delivery information needed for that message.
• Google Workspace: email you send to our support address, including your contact details and the information you choose to include.
• Wikimedia Commons: optional food-photo search sends a food or dish query, and image requests retrieve public reference photos. Images retain their source and license information.
• Cooking timer alerts: local timer notifications can be scheduled on your device with system permission. Remote push reminders are disabled in this release.

Photos and shared links

Kitchen photo uploads and newly generated personal images use private storage. Access requires your current kitchen membership. Public stock images and illustrations can be viewed by anyone. A receipt can contain information beyond food purchases; crop or cover details you do not want analyzed.

Before you create an account, your photos, receipts and kitchen work stay in a private temporary workspace for 24 hours. Signing in saves that work and its images into your kitchen. Photos and receipts you choose to scan are also sent to OpenAI for analysis. Expiry or resetting the guest session removes guest access immediately; daily cleanup removes expired drafts and temporary images, with retries if a service is unavailable.

When you create a cooking or shopping link, anyone with that link can access the shared content. Kitchen invitations give access according to the selected membership. Other kitchen members may retain contributions you made together. Review what you share and revoke links when they are no longer needed.

Public shared text is checked on our server for clearly abusive content. Recipients can report a link or block its publisher in their browser. Reports contain the selected reason and any note you choose to provide. We use keyed network fingerprints to reduce duplicate reports without storing your raw address in the report. Reports, decisions and limited publisher restrictions help us investigate concerns and prevent repeated abuse. A report alone does not remove a link. Removing a link stops future access through The Pantry; it cannot recall a copy someone already kept.

Storage, deletion and your choices

Sign-in and account security use cookies. Your browser or app can also keep local kitchen snapshots, unsent changes and cooking progress. Sign out on shared devices, and clear website or app storage if you want to remove local copies.

You can edit or delete kitchen items, conversations and saved preferences using the app’s controls. To delete your account, open Account & profile, choose Delete account, review what will remain in shared kitchens, then confirm. If you own a shared kitchen, follow the ownership instructions first. Some operational records, backup copies and service-provider records may remain under their retention processes or legal obligations.

For a privacy question or a request you cannot complete in the app, contact chef@thepantryai.com. Tell us the account email or phone needed to find your account. Never send your password, verification code, or complete payment details. We may need to verify the request before changing or disclosing account information.

Changes to this page

We will update this page when data handling changes. The effective date above identifies the current policy. You can review it from the website, sign-up process and Account & profile.