Who we are
Table for Two is operated by Wilson Matsuo (“we,” “us,” or “our”). This policy covers the Table for Two app, its companion experiences, and tablefortwo.fyi. For privacy questions or requests, email privacy@tablefortwo.fyi. For app help, email support@tablefortwo.fyi.
This policy explains information we collect, why we use it, who receives it, and the choices available to you. Features and availability may differ between app versions and subscription plans.
Information we collect
- Account and profile information: account identifiers, name, email address (including an Apple private relay address if you choose it), Sign in with Apple identifiers, profile photo, account status, and account creation and activity dates. A guest session also has a technical identifier and can store app content on our backend.
- Your kitchen content: recipes, source URLs, ingredients, instructions, photos, imported text and files, folders and cookbooks, meal plans, shopping lists, notes, saved searches, and cooking or nutrition preferences. Preferences may include dietary restrictions, allergies, or other information you choose to enter.
- Household and sharing information: kitchen membership, roles, invitations, share links, and content you share with other people.
- AI feature information: prompts, recipe context, conversation content, selected photos or document text, dietary preferences, and other inputs used to extract, suggest, explain, edit, price, or illustrate recipes.
- Subscriptions: purchase and transaction identifiers, purchased products, subscription status, renewal or expiration information, and the account or kitchen entitled to paid features. Apple handles your payment details; we do not receive your complete payment card number.
- Technical and usage information: IP address, app and device information, app interactions, onboarding and cooking events, crash and diagnostic reports, timestamps, request identifiers, account and family identifiers, usage limits, AI provider/model and token counts, response status, latency, and estimated processing cost. Some backend logs also include email or Apple account identifiers and error details.
- Communications: messages and attachments you send to support or privacy contacts, and information needed to answer you or send service notices.
How we use information
We use information to provide and sync your recipes and kitchen, support offline use, manage accounts and invitations, deliver the features you request, manage purchases and access limits, respond to support and privacy requests, diagnose crashes and failures, understand feature use, prevent abuse, protect the service, and meet legal obligations. We may send transactional messages about your account or changes affecting your data.
We do not sell personal information or share it for cross-context behavioral advertising. We do not use Apple Health information for advertising, marketing, or data brokerage.
Cloud AI, imports, and generated content
Cloud-assisted features send the relevant inputs through our backend to external processing providers. These features include recipe extraction from links, text, photos, or documents; nutrition and ingredient analysis; recipe chat and edits; meal suggestions; some ingredient and grocery decisions; and image generation. Image generation may run automatically as part of adding a recipe without a photo.
Google Gemini receives relevant recipe content, prompts, conversation context, preferences, and images for AI tasks. Exa receives source URLs to retrieve page content. Pixazo receives image prompts, such as a dish name, cuisine, and ingredients, to generate recipe illustrations. Some structured decision tasks use Impossibl’s Laya, with a fallback through Vercel AI Gateway to the Jev model; these receive relevant task context and candidate choices, such as ingredients, recipe steps, units, or grocery search options.
Some supported tasks run on the device using Apple’s frameworks. On-device processing for one task does not mean all app processing stays on your device. External websites and image hosts also receive ordinary network information when their content is retrieved.
Only use imported material that you have the right to process. Avoid putting unnecessary personal or sensitive information into prompts, recipe photos, or documents. Provider retention and processing depend on the applicable service and account configuration; we do not promise that every AI provider has zero retention or that all requests are excluded from provider model improvement. Contact us for questions about a particular feature.
Apple Health
If you enable Apple Health integration and grant permission, Table for Two can write dietary energy, protein, carbohydrates, total fat, fiber, sugar, sodium, cholesterol, and saturated fat to Apple Health when you log food. Entries can include the recipe title, servings, and time. The app requests access to the corresponding dietary data types.
Our HealthKit integration operates through Apple Health on your device. We do not upload records obtained from Apple Health to our recipe database, cloud AI services, advertising services, or analytics providers. Recipe nutrition estimates and dietary preferences entered in Table for Two are separate app content and may be processed in the cloud as described above.
You control Health permissions in Apple Health or your device settings. Turning off the integration stops future app activity but does not erase entries already saved in Apple Health. You can review or remove those entries in Apple Health. Deleting a Table for Two account does not itself delete Apple Health records.
Location and grocery estimates
With your permission, the app obtains a location for finding a nearby Kroger store. It uses Apple’s geocoding services to resolve a postal code. The grocery lookup sends the postal code and store or product search information to Kroger; our app does not send raw coordinates to Kroger or our recipe database. Apple may process location information to provide geocoding under its own privacy practices.
Store and price results can be cached on your device. You can turn grocery estimates off in the app and revoke location permission in device settings. Price estimates are informational and may be incomplete or out of date.
Photos, files, microphone, and speech
When you choose a profile image or import a recipe, selected photos, file contents, or extracted text may be processed locally, uploaded to our storage, or sent to cloud processing services as needed for that feature. Photo access does not give us a reason to collect unrelated pictures.
Hands-free cook mode uses your microphone and Apple speech recognition when you enable listening. The app requests on-device recognition when supported. If it is not supported, Apple’s speech services may process audio remotely. We do not store cook-mode microphone recordings on our backend. You can stop listening in cook mode and revoke microphone and speech permissions in device settings.
Services that help us operate
We use service providers for the purposes described in this policy. These include:
| Provider | Purpose and relevant information |
|---|---|
| Google Firebase / Google Cloud | Authentication, database and file storage, backend processing, app usage analytics, crash reporting, and operational logs. Account, kitchen content, device/usage, and diagnostic information. |
| Apple | Sign-in, purchases, Health, device permissions, speech and geocoding, platform features, and iCloud Mail for messages sent to us. |
| RevenueCat | Purchase verification and subscription management, using app user identifiers, transaction and entitlement information, and associated SDK diagnostics. |
| Google Gemini, Exa, Pixazo, Impossibl, and Vercel AI Gateway / Jev | The AI, extraction, image, and decision processing described above, with task-specific content and technical request information. |
| Amazon and Kroger | The optional or feature-specific Alexa and grocery services described above. |
| OpenAI Sites and Cloudflare | Website hosting, delivery, domain services, and infrastructure request/security information. |
| Resend | Delivery of configured transactional service notices, including recipient addresses and message contents. |
We may also disclose information when necessary to comply with law, respond to lawful requests, investigate abuse, protect people or rights, or carry out a business transfer with appropriate privacy protections. We do not authorize our service providers to use Apple Health data for advertising.
Retention and deletion
We keep information for as long as reasonably needed to provide the service, maintain your account or shared kitchen, address support and security needs, and meet legal obligations. Retention depends on the kind of information and your use of the service.
Our scheduled cleanup rules target expired share links; monthly AI usage buckets older than six calendar months; unlinked, inactive guest accounts after at least seven days where eligible; Alexa authorization codes older than a day; recent Alexa recipe records and past daily meal plans older than about 30 days; and unreferenced recipe images after a grace period. Inactive free kitchens can become eligible for deletion after two years, with an advance notice period of at least 30 days when a contact address is available. Timing depends on job execution, eligibility, delivery, and operational conditions; these are not guarantees that every copy disappears at those exact times.
Use the app’s Delete Account action or see account deletion instructions. Deletion removes your authentication account, profile and user records, profile photos, associated share-link records, and relevant account usage records through our deletion process. When other people remain in a shared kitchen, kitchen content stays available to them. If you are the last member, the shared kitchen and its associated content are also scheduled for removal through the deletion flow.
Some information can remain in operational/security logs, provider backups, financial records, or records needed for legal compliance and abuse prevention. Reserved invitation codes may remain to prevent code reuse. Third-party records and copies saved by other people are subject to their own handling. Storage cleanup can be asynchronous or require follow-up after a failure; contact us if you believe information remains unexpectedly. Removing the app or clearing local data does not delete the server account, cancel a subscription, or erase Apple Health data.
Your choices and privacy requests
You can edit content and preferences, manage kitchen membership, stop using optional integrations, revoke device permissions, and delete your account. For assistance accessing, correcting, exporting, or deleting information, email privacy@tablefortwo.fyi. Tell us what you need and which account is involved; do not send passwords or payment card details. We may request reasonable verification before acting.
Depending on where you live and which laws apply, you may also have rights to restrict or object to processing, receive a portable copy, withdraw consent for future consent-based processing, appeal a decision on a request, use an authorized agent, or complain to a data protection authority. We will handle applicable requests within legally required periods and will not unlawfully discriminate against you for exercising your rights.
Where European or UK data protection law applies, the legal bases relevant to our processing include providing the service you request, legitimate interests in operating and securing it, compliance with law, and consent where required (including for optional sensitive-data processing). Withdrawing consent does not affect prior lawful processing. You may contact us to discuss the basis for a particular use.
International processing and security
We and our providers may process information in the United States and other countries where infrastructure operates. Privacy laws may differ from those in your location. Where required, transfers must use an applicable legal mechanism and safeguards. Contact us for information about safeguards relevant to your data.
We use access controls, authenticated backend requests, and encrypted network connections to help protect information. No service can guarantee absolute security. Keep your account and devices secure and let us know about a suspected security issue at support@tablefortwo.fyi.
Children and policy changes
Table for Two is a general-audience cooking app and is not directed to children under 13. Where a higher minimum age or parental consent is required by applicable law, that requirement applies. If you believe a child has provided information without appropriate permission, contact us so we can investigate and address it.
We may update this policy as features or practices change. The effective date appears on this page. We will provide additional notice or request consent when a material change requires it. Contact Wilson Matsuo at privacy@tablefortwo.fyi with questions.