Who operates CookMyWeek
CookMyWeek is currently operated personally from the Netherlands (EU). CookMyWeek is not currently operated through a separate company or trading entity.
For privacy or personal-data requests, contact privacy@cookmyweek.com.
Information you give us
When you join early access, CookMyWeek may collect your email address, optional first name and country, consent record, and acquisition information such as UTM campaign fields. The Real-Week Check runs in your browser and shows its result before you provide an email. If you then ask for the printable blueprint and early-access updates, CookMyWeek may store the answers and diagnostic labels you selected or generated alongside your email and campaign attribution.
When you apply for the private beta, CookMyWeek may also collect the household-planning information you submit, such as who is eating, difficult nights, cooking availability, food restrictions, planning challenges, leftover habits and what would make the beta useful to you.
Why we use it
Early-access information is used to manage the pre-launch list and send product or marketing updates only after the subscriber confirms marketing consent through double opt-in. Real-Week Check information submitted with an email may be used to understand recurring planning-pressure patterns and improve the product and pre-launch experience.
Private-beta application information is used to review applications, send a transactional receipt confirming that the application was received, contact applicants about the beta, understand whether CookMyWeek can support real weekly constraints, and improve the product and onboarding. Permission to contact you about a beta application is separate from optional ongoing marketing consent. Applying for the beta does not subscribe you to marketing.
Analytics and cookie choices
CookMyWeek can be configured with Cloudflare Web Analytics and Google Analytics 4. Optional analytics do not load until you choose Allow analytics. Choosing Necessary only keeps optional analytics disabled. When optional analytics are configured, you can reopen Analytics settings in the footer at any time and change that choice.
No advertising or remarketing tags are included in this release.
Service providers
The implemented site architecture uses Cloudflare Pages and Pages Functions for hosting and server-side form handling, Cloudflare Turnstile for bot-abuse protection, Supabase for pre-launch lead and application storage, and Brevo for transactional beta-application receipt email plus consented pre-launch email and double opt-in. Transactional application receipts do not add applicants to the marketing list. Brevo subscription and unsubscribe events are synchronized back to Supabase through a secured server-to-server webhook.
Security and abuse prevention
Public forms use a honeypot and Cloudflare Turnstile. Turnstile tokens are verified server-side before a submission may create lead data or trigger email. Supabase and Brevo server credentials are used only by server-side Cloudflare code and are not exposed to the browser.
Retention and deletion
CookMyWeek keeps early-access and beta-application data only for as long as it is needed for the purposes described above, consent management, security, or applicable legal obligations. Marketing subscribers can use the unsubscribe link in marketing email. You can ask about access, correction or deletion of your personal data at the privacy contact above.
Your choices
You can decline optional analytics, change analytics preferences later, decline optional marketing consent when applying for the beta, unsubscribe from marketing email after subscribing, and contact us about your personal data.