This policy explains what information Table ("we", "us", "the App") collects when you use our recipe management app and website, how we use it, who we share it with, and the choices you have.
If you join or are invited to a shared book, your name and email are visible to other members of that book, and actions you take in it (adding, editing, or removing a recipe) are visible to them in that book's activity log.
We record a small set of first-party product-usage events tied to your account — for example, that a recipe was saved, a book was created, or a note was added — to understand feature usage and improve the app. We do not use any third-party analytics, advertising, or tracking SDKs, and we do not sell your data.
| Permission | Why we ask |
|---|---|
| Camera | To let you take a photo of a recipe directly from the app. |
| Photo library | To let you choose an existing photo as a recipe image. |
| Internet | Required for the app to load and save your recipes. |
These permissions are only requested when you actively use the related feature, and photos are only uploaded if you choose to attach one to a recipe.
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, email, or payment details.
The app does not use cookies. Your sign-in session is kept using your browser's or device's local storage — not a cookie — purely so the app can tell you're signed in; it isn't used to track you across other sites, and we don't set any advertising or analytics cookies.
We rely on a small number of infrastructure and service providers to operate the app. We do not permit any of them to use your data for their own purposes.
| Provider | Purpose | What it sees |
|---|---|---|
| Vercel | Hosts our app and API | All traffic to the app passes through it |
| Supabase | Hosts our database | All account and recipe data at rest |
| Vercel Blob storage | Stores recipe images | Images you upload or import |
| Apple App Store / Google Play | Processes Table Premium payments | Billing/payment details for your subscription |
| RevenueCat | Manages and verifies your Table Premium subscription status | Your Table account id and subscription status — not your name, email, or payment details |
| Anthropic (Claude API) | AI cleanup and translation of imported recipe text | The ingredient/step text of a recipe you import |
| Apify | Extracts recipe data from Instagram, TikTok, and Facebook links you submit | The URL you submit and the public page content it points to |
| Our email provider (SMTP) | Delivers verification and password-reset emails | Your email address and the message content |
Several of these providers process data outside the country you live in, including outside the European Economic Area (EEA). See §8 if you're in the EEA, UK, or Switzerland for how those transfers are safeguarded.
We use industry-standard measures to protect your information, including encrypted connections (HTTPS) between the app and our servers, hashed password storage, and access controls that restrict shared-book data to members you've explicitly added. No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.
Table is not directed at children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, contact us and we will delete it.
Depending on where you live, you may have the right to:
Most of these you can already do yourself in the app — edit your profile and recipes directly, or delete your account entirely from Account → Danger zone (§4). For anything else, or if you're in the EEA/UK/Switzerland, see §8 below, or contact us using the details in §9.
The data controller responsible for your personal data is Table. Contact details are in §9.
| What we process it for | Legal basis (GDPR Art. 6) |
|---|---|
| Creating your account, storing and syncing your recipes/books, shared-book access | Performance of a contract — this is the service you signed up for |
| Recipe import (URL fetching, AI cleanup via Anthropic, video-link extraction via Apify) | Performance of a contract — carrying out the specific action you requested |
| Account verification, password reset, security emails | Performance of a contract |
| Table Premium subscription management via RevenueCat | Performance of a contract, and legal obligation (e.g. invoicing/tax records) |
| Rate limiting, fraud/abuse prevention, first-party usage events (§1.4) | Legitimate interests — keeping the service secure, reliable, and improving it, weighed against the low privacy impact (no third-party sharing, no ad tracking) |
We do not use your data for automated decision-making or profiling that produces legal or similarly significant effects on you.
As listed in §3, 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 European Commission's Standard Contractual Clauses, as provided in each vendor's standard data processing terms.
In addition to §7, you have the right to:
We keep your data only as long as your account is active, plus a short residual period needed to purge it from backups (typically 1 day after account deletion) and any longer period required by law (for example, billing records Apple, Google, or we must retain for tax purposes).
Questions about this policy or your data? Contact us at support@mytablerecipes.com.
We may update this policy from time to time. We'll update the "Last updated" date above when we do. Continued use of the app after a change means you accept the updated policy.