Privacy Policy

Last updated: 20-10-2026 · Applies to the Table mobile app (Android and iOS), the web app at app.mytablerecipes.com and the website at mytablerecipes.com

This policy explains what information Table ("we", "us", "the App") collects when you use our recipe app and website, how we use it, who can see it, who we share it with, and the choices you have.

The short version: your recipes are private unless you choose to share them, we only use outside services to run the app (never for advertising), we don't sell your data, and you can delete your account yourself at any time (§4.2).

1. Information We Collect

1.1 Account information

• Email address — used to create your account, sign you in, confirm your address, and reset your password.
• Name — optional. Shown to people you share a household or a recipe book with (§2).
• Password — if you sign up with email, we store it only as a one-way cryptographic hash. We never store or see your plain-text password. Accounts made with Apple or Google have no password.
• Email confirmation — you can use Table right away, before confirming your email. We send a 6-digit code to confirm it; you need a confirmed email only to invite people (to a book or your household) and to share recipes on Discover.
• Preferences — your color theme, whether you want new recipes shared on Discover, which book you've pinned to your Library, and whether you've dismissed the "Get started" card.

1.2 Signing in with Apple or Google

If you choose Sign in with Apple or Sign in with Google, the provider sends us a signed token that we verify. From it we keep:

• the provider's account id for you (a random identifier, not your email), so we recognize you next time;
• your email address, which the provider has already verified. With Apple you can choose "Hide My Email", in which case we only receive an Apple relay address;
• your name, if the provider shares it (Apple shares it only the first time you sign in, and only if you allow it).

If an account with the same verified email already exists, the sign-in is linked to that account. For Sign in with Apple we also store a token Apple issues to us; we keep it only so that, when you delete your account, we can tell Apple to revoke Table's access (§4.3).

On the website, the Google and Apple sign-in buttons load scripts from Google (Google Identity Services) and Apple (Sign in with Apple JS). These scripts are loaded only on the sign-in and sign-up screens, and only Google or Apple receive what you enter in them. Your use of their sign-in is also covered by Google's and Apple's own privacy policies.

1.3 Recipes, photos, notes and books

• Recipes you create, edit, import, save or add to favorites: title, description, ingredients, steps, servings, cooking time, categories, source link and image.
• Photos you add to a recipe.
• Notes you write on a recipe, and the labels and tags you use to organise your recipes.
• Recipe collections ("books") you create, with their titles, descriptions and covers, and who you've shared them with.

1.4 Importing a recipe

When you import a recipe from a link (by pasting it, or by sharing it to Table from another app):

• Websites: our server fetches the page and reads the recipe from it. The website sees a request from our server, not from your device.
• Instagram, TikTok and Facebook: we use outside services to fetch the public post the link points to — its caption, cover image and video, and, where available, a transcript of what is said in the video (§5).
• The recipe text we read is processed with AI (Anthropic's Claude) to tidy up ingredients and steps, check them against the source, and translate them if needed. For social posts, candidate cover images (the post's cover and a few frames from its video) may also be sent so the AI can pick the best photo of the dish. To take those frames, your device loads the post's video directly from the platform (for example Instagram), which can see your IP address, as it would if you watched the video there.
• We keep a private copy of what the import read (the page's recipe data, or the post's caption and transcript) together with the recipe. It is never shown to other users or returned by the app; it lets you use "Re-read source" later without fetching the post again.
• We also store a short import check on the recipe (lines worth double-checking, or lines held back because the source didn't back them up). Only the person who imported the recipe can see it.

1.5 Households, the weekly plan and the basket

If you plan meals, or join or create a household:

• Household: its name, its members and their roles, and a standing invite link.
• Weekly plan: which recipes are planned for which breakfast, lunch, dinner or weekly extras, with servings and who added them.
• Recent changes: who added, removed, moved or resized which dish, and when.
• Basket: the shopping list built from the plan, which lines were ticked off and by whom, items typed in by hand, and staples you keep at home.
• Planning settings: which meals to plan, how many dishes per meal, and the usual number of servings.
• Recipe books shared with the whole household.

1.6 Reports, blocks and feedback

• If you report a Discover recipe, we store the recipe, the reason, any details you write, and that the report came from you, so we can review it.
• If you block a creator, we store that, so their recipes stay out of your Discover feed. We don't tell the creator who reported or blocked them.
• If you send us feedback from the app, it is emailed to our support inbox together with your account email so we can reply. It is not stored in the app's database.

1.7 App usage data

We record a small set of first-party usage events tied to your account, with no other details attached: for example that you signed up (and how: email, Apple or Google), confirmed your email, saved or imported a recipe, created a book or household, joined one, wrote a note, started a plan or planned a new week, opened the basket, started cook mode, shared an invite link, chose a Discover setting, or dismissed the "Get started" card. When you sign up we also note which platform you used (web, Android or iPhone), the campaign tag on the link that brought you to Table if there was one (for example "pinterest"), and your answer to "How did you hear about Table?" if you give one. We use them to understand which features are used, which channels bring people who keep using Table, and whether people keep planning week after week, and to improve the app. Cook mode keeps your screen on while it is open; that needs no permission and sends nothing to us.

On our marketing website (www.mytablerecipes.com) we use Vercel Web Analytics to count page views. It sets no cookies and reports only aggregated numbers (such as pages viewed, referring site, country and device type); it does not build a profile of you. It is not used inside the app.

We do not use any third-party advertising or tracking SDKs, we do not track you across other apps or websites, and we do not sell your data.

1.8 Technical data

Like any online service, our servers receive your IP address and basic request information when the app talks to them. We use the IP address briefly for rate limiting (to stop abuse), and our hosting provider keeps short-lived server logs for security and troubleshooting.

1.9 Device permissions (mobile app)

• Photos and camera: on Android, Table requests no camera or photo-library permission. When you add a photo, the system photo picker opens and Table only receives the one photo you pick. On iOS, the system picker lets you choose from your photo library or take a new photo; iOS asks for your permission only if you choose to take a photo (or if it needs access to your library), and Table only receives the photo you pick. Photos are uploaded only when you attach one to a recipe.
• Sharing to Table: when you share a link to Table from another app (for example Instagram or a browser), Table receives only what you share.
• Table does not use your location, contacts, microphone or advertising identifier, and does not send push notifications.

1.10 Payment information

If you subscribe to Table Premium, your purchase is processed entirely by the Apple App Store or Google Play — we never see or store your card number. Subscription status is managed on our behalf by RevenueCat, which we use to verify your entitlement across devices and the web. RevenueCat identifies your subscription using your Table account id, not your name or email. We store your plan, which store it was bought through, the product, renewal and expiry dates, and whether there is a billing issue, plus counters for plan limits (such as imports this month).

1.11 Cookies and local storage

The app does not use cookies. Your sign-in session, a cached copy of recently viewed data (so the app opens quickly and works on a poor connection) and small preferences (such as dark mode or your unit preference) are kept in your browser's or device's local storage. This stays on your device; it isn't used to track you across other sites, and we don't set any advertising or analytics cookies. Signing out clears your session.

2. Who Can See What

• Your recipes are private by default. Only you (and the people you share a book with, below) see them in the app.
• Discover is opt-in. If you turn on sharing to Discover, the recipes you add from then on are published to Discover; you can also publish or unpublish a single recipe in the recipe editor. Turning the setting off keeps new recipes private but does not unpublish recipes already shared — unpublish those one by one. If you turn Discover on before confirming your email, your recipes are kept private until you confirm it, and are published then. A Discover recipe shows its content (title, description, photo, ingredients, steps, categories and source link) and how many people saved it. It does not show your name or email: creators on Discover are anonymous. Sharing to Discover requires a confirmed email.
• Recipe links. Every recipe has its own web address. Anyone who has the link to a recipe — for example because you shared it — can open it and see its content, even without a Table account and even if the recipe isn't on Discover. The link doesn't show who you are. Your notes, tags and import check are never shown through a link.
• Photos are stored at hard-to-guess web addresses; anyone who has a photo's address can open it.
• Shared recipe books. Members of a book see its recipes, each other's names and email addresses, the notes members write on recipes in that book, and the book's activity (who added or removed a recipe, joined, left or renamed the book). You can add people by their email address or with an invite link. Anyone with a valid book invite link can see the book's title, description, cover, number of members and recipes, and the inviter's first name (or the first part of their email address), and can join.
• Households. Household members see each other's names and email addresses, the shared weekly plan and basket, who ticked or added what, and "Recent changes" (who added, removed or changed which dish). Books shared with the household are shared with every current and future member. Anyone with the household invite link can see the household's name and its members' first names (or the first part of their email address), and can join. The household owner can reset the link at any time.
• We (the people who run Table) can access account data when needed to operate the service, answer a support request, review a report or enforce our Terms.

3. How We Use Your Information

• To provide the app — storing, syncing and showing your recipes, books, plan and basket, and sharing them with the people you choose.
• To sign you in, confirm your email address, and keep your account secure.
• To send account emails: your confirmation code and password-reset links.
• To help you get started: a welcome email when you sign up and up to three short tips in your first two weeks, only about the steps you haven't tried yet (saving a first recipe, planning a meal), and one question asking what got in the way. Turn these off with the link in each email or in Profile › Tips by email. We don't send advertising or third-party marketing emails.
• To import recipes you ask us to import, including AI-assisted cleanup, checking and translation.
• To manage Table Premium and enforce plan limits.
• To review reports and keep Discover free of abuse.
• To understand feature usage and improve the app, using the first-party events in §1.7.

We do not use your data for advertising, and we do not sell it.

4. Data Retention and Deletion

4.1 How long we keep things

• Your account and content are kept for as long as your account exists.
• Email confirmation codes expire after 10 minutes, password-reset links after 1 hour.
• Rate-limit records (which may contain your IP address) are short-lived and cleaned up automatically.
• Deleting a recipe removes it from your library and from Discover, and its link stops working. People who had already saved it keep their copy, so we keep the recipe itself in our database for them. If you want a recipe you created fully erased, contact us (§10).

4.2 How to delete your account

You can permanently delete your account yourself, at any time, without contacting us:

• In the app: go to Profile › Account, scroll to Danger zone and tap Delete account.
• On the web (no app needed): sign in at app.mytablerecipes.com/profile?tab=account and use Delete account in the Danger zone.
• To confirm, enter your password — or, for an Apple or Google account, type DELETE. Deletion takes effect immediately; there is no waiting period.
• If you can't sign in, email support@mytablerecipes.com from the address on your account and we will delete it for you.

4.3 What deletion removes, and what stays

• Removed: your email, name, password hash, preferences, Apple/Google sign-in links, your personal library, notes, personal tags, favorites, book and household memberships, reports you filed, blocks, and your subscription record and usage counters.
• Apple: if you used Sign in with Apple, we ask Apple to revoke Table's access before the account is deleted.
• Your private recipes are deleted, with their ingredients, steps, notes and the private copy of their import source, unless someone else still keeps them (they saved it, or it is in a shared book that passes to another member). Recipes you published to Discover remain on Discover, and saved copies stay with the people who saved them, without any link to you. If you want those erased as well, or the photos you uploaded removed from storage, contact us (§10).
• Books: if you own a shared book with other members, ownership passes to another member first so the collection isn't lost for them; a book with no other members is deleted with your account.
• Households: you are removed from your household. The plan, basket and staples stay with the remaining members, and entries in "Recent changes", book activity and the basket are no longer linked to you. If you were the only member, the household's plan and basket remain in our database without any link to you.
• Usage events (§1.7) are kept only as anonymous counts: they are unlinked from you.
• Copies in our database provider's automated backups are removed when those backups expire (typically after 1 day). Records Apple, Google, RevenueCat or we must keep by law (for example for tax) are kept for as long as that law requires.

4.4 Subscriptions

Deleting your account does not cancel an active Table Premium subscription, and does not refund it. Cancel it yourself in your Apple App Store or Google Play account settings, before or after deleting your account — we can't cancel a store subscription for you.

5. Third-Party Services We Use

We rely on a small number of infrastructure and service providers to operate Table. They process data on our behalf, and we do not permit them to use your data for their own purposes.

Several of these providers process data outside the country you live in, including outside the European Economic Area (EEA), for example in the United States. See §9 if you're in the EEA, UK, or Switzerland for how those transfers are safeguarded.

6. Security

We use industry-standard measures to protect your information, including encrypted connections (HTTPS) between the app and our servers, hashed password storage, verified sign-in tokens, and access controls that limit private recipes, books, households and plans to the people they're shared with. Treat invite links like a key: anyone who has one can join. No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.

7. Children's Privacy

Table is not directed at children. You must be at least 13 to create an account, or older where local law sets a higher age for using online services on your own (in that case you need permission from a parent or guardian). We do not knowingly collect personal information from children under 13. If you believe a child has given us personal information, contact us and we will delete it.

8. Your Rights

Depending on where you live, you may have the right to:

• Access the personal data we hold about you
• Correct inaccurate data
• Request deletion of your data
• Receive your data in a portable format
• Object to or restrict certain processing

Much of this you can do yourself in the app — edit your profile and recipes, make recipes private, leave a household or book, or delete your account entirely (§4.2). For a copy of your data or anything else, contact us using the details in §10; we'll respond within one month. If you're in the EEA, UK or Switzerland, see also §9.

9. Additional Information for Users in the EU/EEA, UK, and Switzerland (GDPR)

9.1 Who is responsible for your data

The data controller responsible for your personal data is Table. Contact details are in §10.

9.2 Our legal basis for processing

We do not use your data for automated decision-making or profiling that produces legal or similarly significant effects on you.

9.3 International data transfers

As listed in §5, some of our service providers may process data outside the EEA, including in the United States. Where that happens, we rely on appropriate safeguards recognized under GDPR, such as the EU–US Data Privacy Framework where the provider is certified, or the European Commission's Standard Contractual Clauses, as provided in each vendor's standard data processing terms.

9.4 Your GDPR rights

In addition to §8, you have the right to:

• Withdraw consent at any time, where we rely on consent as the legal basis (this doesn't affect processing we already carried out based on consent before you withdrew it)
• Object to processing based on our legitimate interests (§9.2)
• Lodge a complaint with your local data protection supervisory authority, or the supervisory authority where we are established, if you believe we've processed your data unlawfully

9.5 Retention

We keep your data only as long as your account exists, subject to the exceptions in §4 (recipes that stay available for people who saved them, backups that expire after a short period, and records we must keep by law).

10. Contact Us

Questions about this policy or your data, or a request to access, export or delete it? Contact us at support@mytablerecipes.com.

11. Changes to This Policy

We may update this policy from time to time. We'll update the "Last updated" date above when we do, and for significant changes we'll let you know in the app or by email. Continued use of the app after a change means you accept the updated policy.