Privacy Policy

This Privacy Policy applies to the Brie mobile app, website, and related services. In this policy, “Brie,” “we,” “us,” and “our” refer to the operator of those services, Lucera LLC.

Brie is a shared family meal-planning service. It helps households save attributed recipes, plan meals, build grocery lists, track cooking and nutrition information, and get assistance while planning or cooking.

• Account information: your name, email address, profile image, sign-in provider, and account identifiers.
• Household information: household names, invitations, membership, and the people with whom you choose to share a household.
• Meal-planning information: recipes, original source links and attribution, weekly plans, grocery lists, favorites, serving choices, prep tasks, and cooking progress.
• Preferences and nutrition information: dietary preferences, allergies or restrictions, meal feedback, nutrition targets, and food or macro logs you choose to provide.
• Content you submit: recipe text, links, cookbook pages, PDFs, photos, package labels, food photos, voice requests, and messages sent to Brie or support, and feedback you submit through the website. The feedback form may also include an optional reply email and campaign link tags.
• Purchase information: your Brie plan, subscription status, renewal state, paid-through date, and Apple transaction identifiers. Website subscriptions also involve Stripe customer, checkout, invoice, and subscription identifiers. Stripe receives your name, email, billing address, and payment details to process website billing. Apple and Stripe do not provide Brie with your full payment-card details. Billing information is not sent to AI providers as part of your subscription purchase.

When you use Brie, we and the services that host Brie may receive technical information such as your IP address, device and app version, browser type, request timestamps, session activity, and diagnostic or error information. We use this information to secure, operate, and troubleshoot the service.

The website feedback form uses Cloudflare Turnstile to prevent spam. Brie's servers also use a hash of the visitor IP to limit repeated submissions; the feedback record does not contain the IP.

Brie uses essential session tokens, local app storage, and similar technologies to keep you signed in and remember product state. We do not currently use third-party advertising trackers.

When enabled, we use PostHog in its US-hosted service to understand website visits, App Store link clicks, setup, recipe imports and edits, meal planning, grocery use, cooking, nutrition feature actions, reminders, and return visits. We measure time the app is in the foreground and estimate active time from interaction and speech activity. We also record action counts, completion, failures, response timing, and whether an action used touch, Text, Voice, Siri, or a connected assistant. Website analytics use an anonymous local identifier, public campaign tags, and the referring website’s domain. App activity uses an opaque Brie account identifier and a hashed household identifier. Verified purchase events use the opaque account identifier. We use these reports to understand conversion, household planning activity, and retention. PostHog receives network requests and the limited event metadata needed for these reports; our event configuration removes IP fields and disables location enrichment.

These analytics do not include your name, email, recipes, allergies, nutrition logs, messages, voice recordings, private invitation links, or payment-card details. Session recording and automatic interaction capture are disabled. Website analytics respect Do Not Track and Global Privacy Control when your browser sends them. We use these reports to improve Brie and evaluate acquisition, not to target ads across other companies’ apps or websites.

• Authenticate accounts and keep sessions secure.
• Operate shared households, meal plans, recipes, and grocery lists.
• Process recipe sources and user requests, including with automated and AI-assisted tools.
• Personalize suggestions using the household preferences and feedback you provide.
• Estimate nutrition and support optional nutrition logging.
• Send sign-in links, invitations, security notices, and support replies.
• Protect Brie, prevent misuse, diagnose problems, and improve reliability.
• Comply with law and enforce our Terms.

If you sign in with Google, Brie receives the basic profile information you authorize Google to provide, such as your name, email address, profile image, and a stable account identifier. We use Google user data only to create, authenticate, secure, and display your Brie identity.

Brie does not use Google user data for advertising, sell it, or use it to train general-purpose AI models. Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

If you sign in with Apple, Brie receives the account identifier and any name or email information you choose to share. Apple may provide a private relay email address instead of your personal address. We use that information for the same account and security purposes.

You can review or revoke provider access in your Google or Apple account settings. Revoking provider access does not by itself delete information already stored in your Brie account.

Learn more about Google’s requirements in the Google API Services User Data Policy.

Brie does not sell personal information.

• Your household: information you add to a shared household is visible to the members of that household as needed to collaborate on meals, groceries, and cooking.
• Service providers: we use providers for cloud hosting, database and file storage, authentication, email delivery, recipe and media processing, product analytics, and AI features. They may process information only to provide their services to Brie. We require them to handle the information only for the specified services and to protect it under standards no less protective than this policy, as applicable.
• Recipe sources: when you ask Brie to import a public link, the source site or processing provider may receive the usual web request information needed to retrieve it.
• Safety and legal reasons: we may disclose information when reasonably necessary to comply with law, protect people or the service, investigate abuse, or enforce our agreements.
• Business changes: information may transfer as part of a merger, financing, acquisition, reorganization, or sale of assets, subject to appropriate confidentiality and notice obligations.

Brie's built-in AI assistance uses OpenAI and TypeSafe AI. Before sending your information to these providers, Brie asks you to review the sharing details and explicitly allow it. Creating an account, accepting these terms, joining a household, or purchasing a plan does not by itself grant this permission. In the iOS app, AI consent is collected during account setup after sign-in, before new-household setup. Existing household members can access saved content without granting AI permission.

Depending on the feature, information sent to OpenAI includes your messages, voice audio, submitted photos, food and package-label images, documents or cookbook pages, recipe text and links, and relevant household and member display names, recipes, meal plans, groceries, cooking progress, dietary preferences or allergies. Your own nutrition goals and food-log entries may be included when needed for your request. Permission belongs to the person using the feature; another household member's permission does not authorize access to your private nutrition history. Connection and request information is also processed to deliver the service.

OpenAI processes this information to answer requests, interpret recipe sources, help match foods and amounts, prepare recipe images and search information, and assist with planning, cooking, and nutrition estimates. Some requested recipe and nutrition work continues in the background. We check permission before dispatching new AI requests, including retries and queued processing. AI estimates should be reviewed and are not medical advice.

Saved-recipe search uses TypeSafe AI to judge how well recipes fit your request and meal. It receives your search, meal context, and eligible recipes' titles, descriptions, cuisines, meal types, tags, and ingredient wording. It does not receive photos, directions, nutrition, source URLs, or household profiles. Brie asks you to review the updated sharing details when a new AI provider is added.

You can review or withdraw AI consent in the iOS app under Settings → Privacy → AI assistance. This stops new covered requests and disconnects the active voice session on that device. A request already sent may finish, and withdrawing permission cannot recall information a provider already received. You must agree again before using AI assistance. Your saved content remains accessible, and account management, account deletion subject to household ownership requirements, and Apple subscription management remain available. Camera and microphone permissions are separate from AI-sharing permission.

We store your sharing choice, disclosure version, and acceptance or withdrawal timestamps with your account. Account deletion removes this record. Provider processing and retention are subject to the service terms and data-protection arrangements applicable to Brie; this policy does not promise anonymous processing or zero retention. We require service providers to process information for the specified services and provide protection no less protective than this policy. Contact support@withbrie.app for questions or deletion requests.

Guest cooking assistance asks for permission to send the guest's question or dictated text and the shared cook's recipes and progress to OpenAI. This permission applies to that guest interaction and does not grant access to a member's private nutrition data.

Connecting an agent is optional. You sign in to Brie, choose a household, and approve separate permissions to read recipes, save recipes, read groceries, add groceries, read shared plans and food preferences, or prepare and save reviewed meal plans. The agent may receive shared household content under the permissions you approve.

Recipe responses can include titles, descriptions, source links and creator attribution, servings, cooking times, ingredients, directions, recipe and version references, image availability, and estimated nutrition when available. Grocery responses can include item names, amounts, units, shopping categories, and checked status. Import responses include job references, progress, and details needed to complete the import. With planning access, responses can include shared household allergies and food preferences, serving defaults, planned dates, dishes, recipe versions and prep tasks. Planning proposals and their approval records are stored in Brie. These references let the agent retrieve the right content and avoid duplicate saves.

When you ask an agent to save a recipe or add groceries, Brie receives that content and stores it in the selected household. Approved plan proposals update the specified meals and rebuild their groceries. Recipe processing may use the same extraction, image, and nutrition providers used by Brie. The agent connection does not grant access to personal nutrition logs, payment details, account administration, or device controls. Built-in AI enrichment also requires your separate AI-sharing permission in Brie; connecting an agent does not turn it on.

We keep connection permissions, authorization credentials, and operation records to secure access, enforce your plan and usage allowances, and prevent duplicate writes. If you approve ongoing access, the agent can reconnect between conversations until the connection expires or is revoked. We do not send your Brie password or sign-in code to the agent.

You can review and disconnect agents on the Brie connections page. Disconnecting stops future access through that grant; requests already authorized may finish. It does not delete saved recipes or groceries, or remove content already received by the agent. The agent provider handles that content under its own privacy policy and settings.

We keep account and household information for as long as your account is active or as needed to provide Brie. We may retain limited records longer when reasonably necessary for security, fraud prevention, legal compliance, dispute resolution, backups, or enforcing agreements.

You can delete your account in the app under Settings, Account & household. A household member’s private account and nutrition history are deleted while shared household content remains for the other members. A sole household owner’s deletion also deletes the household and its shared recipes, plans, groceries, and history. An owner must transfer ownership before deleting an account when another signed-in member remains.

Account deletion cancels an active website subscription immediately. It does not cancel a subscription billed by Apple. Manage or cancel that subscription separately through Apple. Limited records may remain where reasonably necessary for security, fraud prevention, legal compliance, disputes, backups, or enforcing agreements.

• Update available profile and household information in the app.
• Review or withdraw AI consent in Settings → Privacy → AI assistance.
• Leave a household or ask its owner to remove your membership.
• Revoke Google or Apple access through the provider’s settings.
• Review and revoke connected-agent permissions on the Brie connections page.
• Delete your account from Settings, Account & household.
• Request access, correction, export, or deletion by emailing support@withbrie.app from the address associated with your account.

If you cannot access the in-app deletion control, use the email request above. See the support page for the information to include.

We use reasonable administrative, technical, and organizational safeguards designed to protect information. No internet service can guarantee perfect security, so please use care when choosing what to share and keep your sign-in methods secure.

Brie and its service providers may process information in the United States and other countries where they operate. Those locations may have different data-protection laws than your home jurisdiction.

Brie is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided information to Brie, please contact us so we can review and remove it as appropriate.

We may update this policy as Brie changes. We will post the revised policy here, update the effective date, and provide additional notice when a change materially affects your rights or how we use information.

Questions or privacy requests can be sent to support@withbrie.app.