Privacy Policy

Last updated: 27 September 2026

This policy explains how NutriFlow, the operator of joinnutriflow.com, handles information when you use our website, generate a meal plan or contact us. For privacy questions and requests, email redabrewer@gmail.com.

Information you provide

The plan builder requests your age, sex for calorie calculations, height, weight, optional target weight, activity level, goals, diet, meals per day, food budget and cooking preferences. You may also provide your first name, allergies, intolerances, dislikes, preferred cuisines and additional notes. Some of these details can reveal health information or religious dietary preferences. Only provide information needed for your plan; do not include medical records or other people's personal information.

How information is used

We use your inputs to calculate nutrition targets and generate the meal plan you request. Our Cloudflare Pages endpoint processes your profile and sends relevant profile details and targets to Cloudflare Workers AI, using the model configured for NutriFlow. We use support messages to answer questions, troubleshoot issues and handle purchase or privacy requests.

Where applicable data-protection law requires a legal basis, we process information to provide the service you request, meet legal obligations, and pursue legitimate interests such as security and support. Where consent is required for sensitive information, we request it before generation. You may withdraw consent by contacting us; this does not undo processing already performed.

Providers and technical information

Cloudflare hosts the website and processes AI requests. Google Fonts supplies fonts, and jsDelivr supplies browser libraries. These providers receive technical information such as IP address and browser/request information when your browser contacts them. Provider processing is governed by their applicable terms and privacy policies: Cloudflare, Google and jsDelivr.

If you purchase through an external checkout, the checkout provider identified there processes payment and billing details under its own privacy policy. Do not send card details to our support email. Our plan-generation endpoint does not collect payment-card information.

Storage and retention

The current plan builder does not save profiles or generated plans in a NutriFlow application database or in browser local storage. Inputs and results are held in the active page and processed during generation. Save your plan as a PDF if you want to keep it. Closing the page does not erase copies you downloaded or any provider-managed logs.

Hosting, security and AI providers may retain operational information under their own policies and settings. Support emails and any transaction records are retained as needed to resolve requests, maintain required business records and comply with law. Contact us to ask what information we hold about you or to request deletion; information required for legal obligations may need to be retained.

Cookies, sharing and international processing

The current application code does not set advertising cookies or include advertising analytics. Infrastructure and external checkout providers may use their own necessary storage or cookies. We do not sell profile information. We disclose information to providers needed to operate the service, or when legally required. Providers may process information outside your country, subject to applicable data-protection requirements.

Your choices and rights

You may leave optional fields empty or choose not to generate a plan. Depending on your location, you may have rights to access, correct, delete or obtain a copy of personal information, restrict or object to processing, withdraw consent, and complain to your local data-protection authority. Email [email protected] to exercise these rights. We may need to verify your identity, but do not send identity documents unless we explain why they are needed.

Children and changes

NutriFlow is intended for adults aged 18 and over. If a child has provided information, contact us so we can address it. We update this page when our practices change and revise the date above.