Privacy Policy

Last updated: 29 October 2026 · Version 2026-10-29

This notice explains how myChef (“we”, “us”) collects, uses, shares and stores personal data when you use our website, mobile apps, web booking, WhatsApp, email, and the myChef app inside ChatGPT. The controller is the Brazilian company whose legal name is Mychef App Plataforma Digital LTDA.

This policy explains our data practices and your rights under Brazil’s Lei nº 13.709/2018 (LGPD). Section 8 explains the myChef app in ChatGPT, including its tool inputs and outputs.

1. Who is the controller

Controller: myChef, operated by Mychef App Plataforma Digital LTDA (razão social as registered with Receita Federal)
CNPJ: 59.718.921/0001-37
Address: Rua Francisco Rocha, 198, Batel, Curitiba/PR, CEP 80420-130, Brazil
Privacy and LGPD requests: contato@mychef.com.br

myChef is a marketplace that intermediates bookings between customers and independent personal chefs. We decide why and how personal data is processed on the platform. Chefs who receive your booking details process that data to deliver the service you requested.

To exercise any right in this notice, email contato@mychef.com.br with the subject “LGPD”. We handle requests within the applicable legal deadlines and explain any information we must retain.

You may also petition the Autoridade Nacional de Proteção de Dados (ANPD): gov.br/anpd.

2. What this policy covers

This policy covers our collection and sharing of data with payment and other service providers. Those providers also explain their own processing in their privacy policies. Chefs’ own websites and conversations they conduct independently outside myChef are subject to their own data practices.

3. Data we collect

We only collect what the product needs. Fields marked sensitive are treated under LGPD Art. 11.

3.1 Account (mobile app)

Created when you sign in with Google, Apple, or (in internal builds) email, via Firebase Authentication.

• Full name
• Email
• Firebase user id
• City you serve or live in
• Language and timezone
• Profile photo (optional)
• Cuisine preferences (customers)
• Notification topics you turn off
• Stripe and Pix customer ids we create for you
• Device platform and Firebase Cloud Messaging token (push)

We do not store your Google or Apple password.

3.2 Customer booking (website, app, ChatGPT, WhatsApp)

• Name, email, WhatsApp-capable phone
• Service date and time
• Guest / lunch-box / student quantity
• Chef, package, add-ons, cleanup, groceries, voucher code
• Service address: street, number, neighbourhood, complement, city, state, CEP
• Optional geocode (lat/lng) derived from that address
• Menu notes, event notes, guest notes
• Attribution: UTM tags, gclid, fbclid, landing page, referrer, GA client/session ids, IP, user agent
• Consent time, source and policy version (ChatGPT bookings)

3.3 Dietary information (sensitive)

Only if you type it:

• Dietary restrictions (vegan, vegetarian, pescatarian, dairy-free, nut-free, halal, kosher, paleo, keto)
• Food intolerances (lactose, fructose, histamine, FODMAP, salicylate, caffeine, MSG, sulfite, gluten-sensitive, casein)
• Free-text notes (allergies, preferences, occasion)

These fields can reveal health information or religious beliefs. We use them to arrange the meal, inform the chef, and generate booking summaries and preparation checklists using OpenAI as described below. If entered in the web booking form, they can also appear in the private session recordings described in section 3.9. We do not use dietary information for ads. Only share information needed for the meal; you can leave these optional fields empty and contact us about how to communicate an essential food restriction.

3.4 Payment

• Card payments go through Stripe. We store the PaymentIntent id and client secret. Card number, CVC and expiry stay with Stripe.
• Pix goes through Asaas. To issue a charge we send your name, email and CPF. We store the Asaas customer and charge ids, QR / copy-paste payload, and payment status.
• The ChatGPT app never asks for card numbers, CPF or Pix keys. Payment always happens on myChef’s own pages.
• Apple Pay / Google Pay, when offered in the app, are processed by those platforms and Stripe.

3.5 In-booking chat (app and web manage page)

• Text (up to 2,000 characters on the web)
• Images, audio, video and files you attach
• Sender id, time, booking id

Web chat is stored in Google Cloud Firestore. App media is stored on Amazon S3. We block phone numbers and emails in web chat so contact stays on the platform.

Microphone, camera and photo library are used only when you choose to record or pick a file.

3.6 Reviews

Rating and optional written review of a chef. Approved reviews appear on the chef’s public profile (first name / display context). We may send review text to OpenAI for automated moderation and delete reviews that break our rules.

3.7 Chef-only data (app)

If you become a chef we also collect:

• Display name, bio, photo, gallery, menus, plates, prices, add-ons, weekly availability, cancellation policy
• Service city and commute fee
• Identity verification: CPF or CNPJ, phone, residential address, Pix key, photo of ID front and back, selfie
• Payout details (Pix / CPF)

ID photos and the selfie are used only to verify that you are a real person who can receive payouts. They are not published.

Chefs can send menu or bio text through our writing helpers. That text is sent to OpenAI to enhance, shorten, expand or translate. We do not send your ID photos to OpenAI.

We also send public chef profile and menu text to OpenAI to generate translations and numerical representations used to match searches. Content moderation can send submitted profile, menu, review or chat text and images to OpenAI to check for prohibited content and contact details.

3.8 Location (app)

With permission, GPS is used to suggest your city during sign-up. If you refuse, we can approximate city from IP. Location is not used to track you in the background. Booking addresses are stored because the chef has to go there.

3.9 Website and cookies

• Pages viewed, clicks on book / chef / experience buttons (Google Tag Manager GTM-MTTL7HDC and Google Analytics)
• First-touch cookie mychef_attr (30 days, domain .mychef.com.br): UTM parameters, gclid, fbclid, landing URL, referrer. This is copied onto the booking lead so we know which campaign found you.
• Essential cookies for the booking session (CSRF, locale, visitor token)
• Embedded YouTube video: the player can load when its section approaches the viewport and can start muted playback. Google/YouTube receives technical connection and playback information; the privacy-enhanced embed domain does not prevent all requests to Google.

Web booking recordings and heatmaps. When enabled, myChef records interactions with the booking form: page layout changes, clicks or taps, scrolling, steps visited, timing, device type, viewport size, language and the associated booking lead. These recordings reconstruct the form; they are not camera recordings or videos of your device.

Visible form values can be recorded before you submit the reservation, including name, email, phone, address, date, quantity, groceries budget, voucher and dietary notes or selections. Passwords, hidden fields, payment credentials and the private booking link are excluded from the recording. Recording stops when the reservation succeeds; payment, confirmation, booking management, chat and review pages are not recorded by this feature.

Authorized myChef managers use these recordings and heatmaps to investigate errors, understand incomplete bookings and improve the form. Recordings are kept in private myChef storage, with the retention described in section 6. This feature has no separate opt-out switch in the form; clearing analytics cookies does not disable it. You can contact contato@mychef.com.br to request access or deletion, object to this processing, or arrange assistance before entering information in the form.

3.10 App analytics and diagnostics

In release builds the app sends:

• Screen views and named product events, including a hashed Firebase installation id — Amplitude
• App-open / conversion events — Meta (Facebook) SDK; Android may read the advertising id
• Crashes, performance traces and breadcrumbs — Sentry (US ingest) and Firebase Performance
• Remote config flags — Firebase Remote Config

3.11 WhatsApp and email

If you write our WhatsApp number we store the conversation, your phone, name, city, occasion, guest count and any dietary notes you send, as a lead (source = whatsapp).

We send transactional email (booking created, pay reminder, paid, chef confirmed, reminder, finished, cancelled, refused) through Amazon SES. Some marketing / ops emails include a 1×1 open pixel.

You can stop booking follow-up emails from the unsubscribe link on those messages.

3.12 ChatGPT app

See section 8. We receive the arguments ChatGPT sends when it calls a myChef tool, including searches before a booking starts. Creating a booking lead requires a separate agreement to share contact details and receive booking follow-ups. The lead stores ChatGPT attribution, a visitor token derived from the MCP session, and consent details.

3.13 Automatically collected

IP address, user agent, timestamps, language, and server logs needed to run and secure the service.

3.14 Search matching and booking assistance using AI

• Search matching: when you use a free-text chef search, we send that search text to OpenAI’s embeddings API to match it with chef profiles. We cache the numerical representation of the search under a key derived from the text. The cache currently has no automatic expiry. You can search by city, service and cuisine without supplying free text.
• Booking summaries and preparation checklists: we send OpenAI the service type, menu title and description, menu/event/guest notes, dietary restrictions and intolerances. A preparation checklist can also use the weekday, start time, cleanup and grocery choices, whether food is included, and the grocery budget. Generated text is stored with the booking. Names, email addresses, phone numbers and street addresses are not dedicated fields in these requests, but information you put in free-text notes can be included.
• Moderation, translation and chef writing tools: we use the submitted content described in sections 3.5–3.7 to moderate content, translate it and assist with writing.

These API requests are separate from using the myChef app inside ChatGPT. They can occur for website and mobile bookings too. Please do not put unrelated personal details in search text or booking notes.

We do not sell personal data.

4. Why we use the data

If you refuse contact or address data we cannot complete a booking. If you refuse dietary data we still book, but the chef will not know your restrictions.

5. Who receives the data

5.1 People on the platform

• The chef you booked receives your name, phone, email, address, date, package, add-ons, dietary information and chat. They need this to cook at your home.
• You see the chef’s public profile, packages, ratings and approved reviews.
• myChef operators see leads and bookings to support you, stop fraud and pay chefs.

5.2 Service providers and other recipients

Providers process data to deliver the functions listed below. Some also process information for their own legal, security and account obligations. OpenAI operates ChatGPT separately from its API services used by myChef.

5.3 Legal and corporate

We disclose data if required by law, to defend a claim, or to a buyer if the company is sold (they must honour this notice).

Chefs are independent contractors, not myChef employees. After we share booking data with a chef so they can perform the service, they are responsible for how they handle it offline.

6. How long we keep it

A link or session expiring does not delete the underlying data. The periods and deletion conditions below distinguish access windows from storage. Where a record has no fixed automatic deletion date, we say so rather than promise that it disappears when a booking ends.

Deleting your app account clears its name and email, unlinks its sign-in and Stripe customer identifiers, removes the profile picture reference and hides the chef profile. It does not erase all related data: booking and lead records, messages, uploaded files, reviews and records held by providers may remain, and may still contain personal information. To request broader erasure, including information supplied through ChatGPT without an app account, email contato@mychef.com.br. We will explain what can be removed and any information that must be retained, including the reason and applicable period.

7. Your rights and controls

Under LGPD Art. 18 you can ask us to:

1. Confirm that we process your data
2. Access it
3. Correct it
4. Anonymise, block or delete data that is excessive or processed off this notice
5. Port it
6. Delete data processed on consent
7. Tell you who we shared it with
8. Tell you that you may refuse consent and what happens if you do
9. Revoke consent

How to do that in the product

• App account: open your profile, choose Delete account, read the notice and confirm. Steps and retention limits are at mychef.com.br/en/deleting-accounts.
• App profile: edit name, photo, city, dietary preferences, notification topics.
• Web booking emails: unsubscribe link on the message, or the booking manage page.
• Cookies: browser settings. Blocking analytics cookies does not stop a booking. Blocking all cookies will break the booking form.
• Location, camera, microphone, photos, advertising id: device settings. The app still works; city suggestion, camera photo, voice notes or some ads measurement may stop.
• ChatGPT: you can decline to share contact details or create a booking, omit optional dietary fields, and stop using or disconnect myChef in ChatGPT. Disconnecting does not delete existing myChef records; request that separately by email. Manage conversation deletion through ChatGPT’s own controls.
• Free-text search: omit query and use city, service and cuisine filters to avoid sending free-text search content to the embeddings API. For a deletion request concerning a search cache entry, provide the search phrase and approximate date so we can locate it.
• Web booking recordings: request access, deletion or assistance by email. The current form does not have an individual recording toggle; browser analytics-cookie controls do not disable this first-party feature.
• Push: OS notification settings, or disable topics in the app.

Email contato@mychef.com.br if the in-product control is not enough. We may ask you to confirm the email or phone on the account.

8. ChatGPT app, MCP tools and the OpenAI plugin

This section explains what myChef receives, stores and returns when you use its tools in ChatGPT. The rest of this policy also applies when you continue to our website or use the mobile app.

8.1 How the connection works

When ChatGPT calls a myChef tool, it sends a request to https://app.mychef.com.br/mcp. There is no myChef account login for this connection. Unauthenticated does not mean anonymous: search text, contact details, addresses and other arguments can identify you.

Typical order:

search_chefs → get_chef → get_chef_availability → quote_booking → start_booking (consent) → reserve_booking → you open payment_url in a browser.

list_service_cities is only for “where do you operate?” or an ambiguous city name.

We do not receive your ChatGPT thread. We receive the tool name and the arguments the model sends. If the model copies something you said into an argument (a city, a name, an address), that is when it lands with us.

OpenAI processes the chat itself under OpenAI’s privacy policy. That processing is OpenAI’s, not ours.

8.2 What we collect on every MCP call

• Tool name and the arguments listed in 8.5
• An MCP session id (Mcp-Session-Id). It is not a password. It groups one conversation so we can reuse an unfinished ChatGPT lead instead of creating a duplicate, and so we can rate-limit that conversation. We derive a visitor token from it on start_booking.
• Technical request information, including IP address, request headers and timestamps, for delivery, rate limiting, security and troubleshooting. For server-to-server calls the IP may belong to OpenAI rather than your device.
• Diagnostic logs can include the tool name, session, lead or booking identifiers, error details and related context. We do not receive your full conversation, but errors or downstream booking diagnostics can contain values submitted through the tools.
• lang when the model sends it (pt, en or es) — that language is also used for our emails and WhatsApp after a lead exists.

We do not automatically receive your ChatGPT account email or credentials. We receive an email address if you provide one as customer_email. Tools do not request card details, CPF, Pix keys, passwords or other login secrets; payment details are entered on the external checkout.

8.3 When data starts being stored

start_booking requires contact_consent=true. Before that call the assistant must tell you, in that conversation, that your name, email and phone go to myChef, that we will contact you by email and WhatsApp about this booking, and must give you https://mychef.com.br/pt/privacy-policy/. Silence or earlier enthusiasm is not consent. If you decline, it must not call the tool; it should give you the chef’s public profile URL instead.

A ChatGPT lead is only reserved against a ChatGPT-created draft. The plugin cannot attach a web or WhatsApp lead.

8.4 Recipients, purpose, retention, controls

Purpose: find a chef, quote a price, take consent, create a lead, hold a slot, send you to pay on myChef, notify the chef.

Recipients: myChef and its hosting/storage providers process tool inputs and stored records. Authorized operators and the selected chef receive the information needed to manage and deliver the booking. Amazon SES, Meta WhatsApp and push providers deliver applicable notifications. OpenAI’s API receives free-text searches and the booking content described in section 3.14. Stripe or Asaas receives the information needed when checkout or a payment request is initiated on myChef, which can be before payment succeeds.

Data returned to ChatGPT: OpenAI receives tool results: public chef information and approved review text, quotes, availability, draft and booking identifiers, status, totals, and booking/payment/management links. The normal successful booking results do not repeat the customer’s email, phone or street address. Private booking links give access to the associated booking; do not publish or share them with people who should not have that access.

Retention: section 6 applies, including the absence of a fixed automatic deletion date for leads and search embeddings. The 7-day draft-link window and the payment deadline are not deletion periods.

Your controls: decline to create a lead or reservation; omit free-text searches and optional dietary information; stop follow-up emails using their unsubscribe link; disconnect myChef in ChatGPT; and email contato@mychef.com.br for access, correction or deletion. A myChef app account is not required to make a privacy request. Disconnecting or deleting a ChatGPT conversation does not cancel a booking or erase myChef’s records.

8.5 Current tool inputs and outputs

Request logs and rate-limit processing apply to every tool. The second column describes additional storage or booking effects.

These seven tools are the current surface. If we add or change a tool that takes or returns personal data, we will update this section and bump the policy version.

9. Mobile app — permissions and SDK list

Sign-in: Google Sign-In, Sign in with Apple, Firebase Auth.

Payments in the app: Stripe (card), Asaas (Pix + CPF), Apple Pay / Google Pay where available.

Third-party SDKs in the app: Firebase (Auth, Firestore, Messaging, Storage, Performance, Remote Config, Installations), Stripe, Amplitude, Meta SDK, Sentry, Google Sign-In, Sign in with Apple, Google Fonts (typefaces only).

10. Children

myChef is for people 18 or older. We do not knowingly collect data from children. If a child created an account, email us and we will delete it.

11. International transfers

Our primary operation is in Brazil. Hosts and processors in section 5 sit mainly in the United States. Transfers rely on LGPD Art. 33: contractual clauses with those vendors and the fact that the transfer is required to provide the service you asked for (Art. 33, IX, when applicable).

12. Security

TLS in transit. Access to production is limited to operators who need it. Passwords for Google/Apple stay with those providers. Card data stays with Stripe. ID images live in private object storage. No method is perfect; if we have a breach that risks you, we will notify you and the ANPD as the law requires.

13. Changes

If we change this notice in a material way we will update the date and version at the top and, when the law requires, tell you by email or in the app. Consent records preserve the time, source and version marker recorded when consent was obtained; changing this page does not rewrite historical consent records.

The Portuguese text at mychef.com.br/pt/privacy-policy is the version that governs for users in Brazil. This English page is a translation.

14. How to reach us

myChef · Mychef App Plataforma Digital LTDA
Rua Francisco Rocha, 198 — Batel
Curitiba/PR — 80420-130
CNPJ 59.718.921/0001-37
contato@mychef.com.br

Account deletion help: mychef.com.br/en/deleting-accounts.