Privacy Policy
Britt’s Bistro Café and BBRS
Effective date: October 26, 2026
October 26 update: added information about connected User Input profile collection and its use for suggestions and filtering.
About this policy
This policy explains how information is handled when you use brittsbistrocafe.com, its connected BBRS features, or contact Britt’s Bistro Café. For privacy questions or requests, contact brittsbistrocafe.mealplanning@gmail.com.
Information you provide
We receive information you submit when creating or using an account, requesting services, communicating with us, or entering website content. Depending on the features you use, this can include your name, username, email address, account identifiers, membership status, recipes, ingredients, instructions, notes, preferences, service requests, and order, invoice or payment-reference information.
If you include dietary, allergy or health information in a message or recipe note, it becomes part of what you submit. Include only information relevant to your request. Do not send passwords, full payment-card numbers or government identification documents through ordinary messages.
Website information and cookies
The website and services used to operate it can receive technical information such as IP addresses, browser and device details, requested pages, referring pages, request times and cookies. WordPress and membership features use cookies for account access and website operation. The website also includes Metricool analytics, WooCommerce order-attribution features, Google Fonts and WordPress emoji resources. External resources can receive technical request information when loaded. Metricool tracking and WooCommerce order attribution are disabled on the connected Create Recipe, My Cookbook, Recipe Viewer and User Input pages; those pages also suppress outgoing referrer information.
You can manage cookies through your browser. Blocking cookies or external resources may affect sign-in or other features. We have not verified automatic handling of Do Not Track or Global Privacy Control signals. A browser privacy setting should not be treated as a guarantee that every external service stops processing information.
How information is used
Information is used to operate accounts, check membership access, save and retrieve submitted content, respond to questions, provide requested services, maintain order and service records, understand website use, troubleshoot problems and investigate misuse or security issues.
The currently connected BBRS cookbook functions support saving, listing, viewing and editing recipes. The connected User Input page also loads and saves available user-provided measurements, activity, reported conditions and stages, allergies and intolerances, GLP-1 tracker display preference, and food and lifestyle preferences for suggestions and filtering. These entries may reveal health information; no diagnosis is inferred.
The connected cookbook and profile service
WordPress handles account and membership access. Connected cookbook and profile requests pass through ngrok to a privately operated database using Supabase software. Requests can include account identifiers, email and membership assertions, and recipe or profile information needed for the requested action. This use of Supabase software is not the same as using Supabase’s hosted cloud service.
The connection uses authenticated requests and encrypted transport. This does not mean the network-service provider is technically unable to process information passing through its service.
At the October 25, 2026 review, the ngrok account used for this connection has Full Capture disabled and a 24-hour Traffic Inspector metadata-retention window. This describes that specific setting, not a promise that all website information, provider records or cookbook data is deleted within 24 hours.
Services and access
Services used to operate the website and respond to customers include website hosting, ngrok, the privately operated database, Gmail for business email, and analytics or attribution tools. Authorized website administration and technical support may require access to operate, maintain or troubleshoot the service. Private cookbook and profile access is checked through account and membership controls.
Information sent through Facebook or another communication platform is also handled under that platform’s practices. Information posted in community areas may be visible to others who have access to those areas.
Payments arranged through PayPal, Venmo or Cash App are processed by the respective provider. Review its privacy information for details. Other linked websites and services have their own practices. This policy does not represent that every listed payment method is integrated into website checkout.
Retention
Account, cookbook, profile, correspondence and transaction-related records are maintained as part of operating the service. There is no single deletion period stated here for every record type. Retention depends on the record’s purpose, ongoing account or service needs, security and administrative needs, and applicable obligations. Hosting and other providers may maintain operational records under their own retention controls.
Cancelling a paid membership should not be assumed to delete all associated information. Contact us to request review of the information associated with your account and deletion where appropriate.
Your questions and requests
Email brittsbistrocafe.mealplanning@gmail.com to ask about information associated with your account, request access or correction, request deletion, or discuss a privacy concern. We may need information sufficient to verify that the request concerns your own account. Requests are reviewed in light of the information involved, the systems holding it and applicable obligations. This policy does not promise immediate deletion of every record.
Security and changes
We use account-access restrictions and technical safeguards, but no website, storage system or transmission method can be guaranteed completely secure. Updates to this policy will be posted on this page with a revised effective date. Material changes will be identified in the updated notice. The policy should be reviewed when new features or information-handling practices are introduced.