Privacy Policy

Your account: your name and email address from Google sign-in or Sign in with Apple. We never see your password and we do not request access to your Gmail, Drive or any other Google or Apple data. If you choose Hide My Email with Apple, we receive the private relay address Apple creates for you instead of your own.

Your table's content: recipes, pantry, meal plans, votes, grocery lists, favorites, Table-tested marks, invite codes, your table's name, and the store you shop at.

Health data: the allergies, intolerances and foods to avoid your table sets, and what we work out from them. See the Consumer Health Data Privacy Policy.

Agreements: when you accepted the safety agreement, confirmed you are 18 or older, and gave consent for health data.

Activity: which pages you open and a few actions (such as browsing The Commons or checking off a grocery item), when you sign in and were last active, and how many new dishes and photos your table made with AI. It is tied to your account and used to run limits, keep the Service working and improve it. We use no third-party analytics, advertising or tracking tools.

iPhone app sign-ins: for each phone signed in to the app, the phone's model name (such as “iPhone 15”) and when it was last used, so you can tell your sign-ins apart.

Store searches: when you look for a store, the zip code you type or, if you choose “use my location,” your location rounded to about 100 meters. We send it to Kroger to find stores and keep the search results, without your name or account, so we don't have to ask again. Your account keeps only the store you pick.

Purchases: if you subscribe to Full in the iPhone app, Apple takes the payment and we never see your card, billing address or Apple ID password. We receive the status of your subscription (which plan, whether it is in its free trial, when it renews or ends) and an anonymous subscriber id, so the app can unlock Full for your table. See RevenueCat below.

Messages you send us: if you email us, we keep the conversation as long as we need it to help you.

Technical basics: standard request logs (such as IP address and browser type) kept briefly by our hosting provider for security and reliability. Cookies are only the ones needed to keep you signed in and to complete invite links.

To run the Service: signing you in, showing your table its own kitchen, checking recipes against your table's restrictions, cooking up new recipes and dish photos with AI when you ask, sharing recipes to The Commons as described below, honoring invite codes, finding store prices, and enforcing plan limits. We also use it to secure, debug and improve the Service, and to contact you about it. That's all.

Your table's content is visible only to your table's members, with these exceptions, all by design:

• The Commons: new dishes your table cooks up with AI, and on Full, recipes you type in yourself (including their steps), are shared with every Cleared Table table, under your table's name. Never your email, and never your restrictions. A table admin can change the table's name in Settings.
• Invite links: someone who opens one of your invite links sees your table's name.
• Shared recipe links: when you tap Share on a recipe, anyone with that link can see the recipe: its title, photo, ingredients, time and servings, the directions for recipes your table wrote or cooked up, a link to the source for clipped recipes, and which common allergen groups it is free of. The page says only “Shared from a Cleared Table kitchen”: never your name, email, table name, restrictions or who shared it. Choose Stop sharing from the recipe's menu and the link stops working.
• Learn writers: if you apply to write for Learn, the profile you write (display name, headline, bio, credentials, city and state, link) and the articles you publish are visible to signed-in members.

Recipes clipped from other websites, your pantry, plans, votes, grocery lists, settings and restrictions stay private to your table.

These service providers run parts of Cleared Table for us. Each receives only what its job needs and may use it only to provide its service to us.

If you use the iPhone app, Apple handles its download and updates under Apple's own privacy policy. We do not sell personal information and we do not share it with advertisers or data brokers. We may disclose information if the law requires it or to protect the Service and its users.

• Your account, activity and sign-in history: while your account exists. They are deleted with your account.
• Your table's content: while your table exists. It is deleted when its last member deletes their account.
• iPhone app sign-ins: up to 180 days, or until you sign out or delete your account.
• AI usage counts: kept for our cost records, without your email, after your account is deleted.
• Database backups: kept by our database provider for disaster recovery and replaced within 30 days.
• Hosting request logs: kept briefly by our hosting provider.

You can export your table's data, leave your table, or delete your account yourself at any time in Settings, on the web or in the app. Deleting your account removes your membership, your activity and sign-in history and your app sign-ins at once, and replaces your name on things you leave at a shared table with “former member.” If you were the last person at your table, the table and everything on it, including the Commons recipes it shared, are deleted with it. We keep a record that a deletion happened, without your email. You can also email us and we will complete a deletion within 30 days.

You can ask for a copy of your data, corrections, or deletion at any time by emailing us. Depending on where you live, you may have more rights, including the right not to be treated differently for using them. We honor these requests wherever you live. We do not “sell” or “share” personal information as those terms are defined in California law. Health data rights, including how to appeal a decision, are in the Consumer Health Data Privacy Policy.

The Service is not directed at anyone under 18, and we do not knowingly collect their personal information. Accounts belong to adults, who confirm they are 18 or older when they first enter. Younger family members take part through an adult's account. If we learn someone under 18 holds an account, we will delete it.

Data is encrypted in transit, stored with reputable providers, and access is limited by the table model described above. No system is perfectly secure. If a breach affects your data, we will notify you, and the authorities where required, as the law requires.

If we make material changes, we will announce them in the app or by email and update the effective date above. We will update this policy before any new service provider receives your data.

BuildMyMap LLC, North Carolina. Privacy questions and requests: info@clearedtable.com.