Privacy Policy

Information you store in the Service

To provide menu planning, household approvals, invoicing, and related features, we store information you submit—for example account credentials, client and household profiles, recipes, menus, invoices, and agreement records. If you are a chef, you are responsible for having a lawful basis to collect information about your clients and for telling them how their data is used, as described in our Terms of Service.

This product data is used to run the Service. It is not sold to advertisers and is not uploaded to ad platforms as customer lists.

Usage analytics (with your consent in the browser)

When you allow analytics cookies in our cookie settings, we use PostHog to collect limited, pseudonymous information about how you use the website and chef product—for example which pages you visit, product actions such as starting a trial or sending a menu, and coarse usage buckets (not raw counts of your recipes or clients).

We identify chef accounts in analytics using an internal account ID only—not your email or name. We configure analytics so event properties do not include your clients' or households' names, contact details, dietary or health information, or other content you store for menu work.

We do not use session replay, screen recording, or heatmaps. Analytics is event-based only.

Optional analytics does not run on real client service pages (menu approval links, household portal, or agreement signing). See our Cookie Policy.

Product and billing events (server-side)

Separately from browser cookies, our servers may send pseudonymous product events to PostHog when certain account milestones occur—for example when a trial ends, a subscription is activated or canceled, or a menu is approved through a client link. These events use your internal account ID and coarse flags (such as whether you had sent a menu), not client names or menu content. This helps us measure product health and billing funnels reliably even if you close your browser during checkout.

Marketing and advertising (with your consent)

When you allow marketing cookies, we use tools such as Google Ads and Meta Pixel to measure whether our ads lead to trials or subscriptions. We fire standard conversion events only. We do not pass contact details, client records, or custom parameters containing user content. We do not use enhanced matching or upload customer lists from your account data.

Cookies and similar technologies

We use cookies and browser storage for sign-in, security, saving your cookie choices, and—when you consent—for analytics and advertising. Our interactive product demo at /sample/client-menu is a marketing preview with fictional data, not a real client menu; optional cookies may apply there with your consent. Details are in our Cookie Policy.

Payments and integrations

Stripe processes subscription payments and, when you enable it, client invoicing through Stripe Connect. Payment card details are handled by Stripe, not stored on our servers.

If you connect Google Calendar, cook-day events (including household name and service address you already store in the product) are sent to your Google account to create calendar events. That data is not sent to PostHog or ad platforms.

An active CookDaysubscription may include a map listing on PersonalChefFinder, operated as a related service. Profile data you choose to publish there is governed by that service's terms and your directory settings.

Service providers

We use service providers to host and operate the Service. They process data on our instructions and only as needed to provide their function. Main providers include:

• Vercel — application hosting
• Neon — database
• Neon Auth — authentication
• Stripe — payments and billing
• PostHog — product analytics (US region; see their privacy policy)
• Google — advertising measurement (when you consent)
• Meta — advertising measurement (when you consent)
• Resend — transactional email (where configured)

We may update providers as the product evolves and will update this policy when practices change materially.

Retention and deletion

We keep account and product data while your account is active. If you cancel without deleting, we may retain data for a limited period (see our Terms). You can export your data or delete your account from Chef Settings or the subscribe screen; deletion removes recipes, clients, menus, and related data from our primary database.

Analytics events already sent to PostHog may be retained there for a period according to PostHog's settings and our configuration. They are pseudonymous and do not include client content. Contact us if you need help with a privacy request related to analytics data.

International transfers

We are based in the United States. Service providers may process data in the U.S. or other countries. Where required, we rely on appropriate safeguards such as standard contractual clauses offered by providers.

Children

The Service is not directed at children under 16, and we do not knowingly collect personal information from them. Contact us if you believe a child has provided information to us.

Your rights

Depending on where you live, you may have rights to access, correct, delete, export, or restrict certain processing of your personal information, and to object to or withdraw consent for optional analytics or marketing. You can change cookie choices anytime via Cookie settings in the site footer. Rejecting optional cookies does not block use of the Service.

To exercise other rights, email privacy@personalchefapps.com with the subject line “Privacy request.” We may need to verify your identity before responding.

Changes

We may update this policy from time to time. We will post the new version here with an updated date. Where required, we will ask for renewed consent for new uses of cookies or tracking (for example by updating our cookie preference version so you can choose again).