BigBricey is an invite-only adult beta. It is designed so you can use a nickname or pseudonym while keeping long-term fitness, nutrition, and wellness records private to your account.
BigBricey uses random internal account identifiers, signed sessions, server-only service credentials, account-scoped database queries, rate limits, and access/mutation auditing. Data travels over HTTPS. The hosting and database providers report encryption for stored customer data. No Internet service can promise perfect security, and the beta is still subject to ongoing review and testing.
Service providers process data only for product functions: Google for sign-in, Vercel for hosting, Supabase for the private database, OpenRouter and the selected model provider for AI requests, and USDA/Open Food Facts for food lookups. Chat text needed for an AI answer is sent to the configured AI service. A food photo is sent only when you choose photo analysis; the image is used to create a review draft and is not added to your ledger or account history.
When voice dictation is available, your browser or device vendor may process microphone audio to produce text. BigBricey receives only the transcript you choose to send.
You can change your nickname, companion settings, onboarding answers, memories, and logged records in the app. In You → Your data & privacy, you can record a full-export request or prepare a deletion request. Deletion is not automatic: the request is verified and reviewed to avoid erasing the wrong account.
Account and health records are retained while your beta account is active so long-term trends remain available. A verified deletion request starts the controlled deletion process. Limited security, audit, legal, and provider-backup records may be retained where reasonably necessary. A final written retention schedule and incident-response process are launch gates before a larger commercial beta.
BigBricey currently accepts adults age 18 and older only. It is not marketed to children.
Questions or privacy requests: use the controls inside your signed-in account or contact the operator who invited you. A dedicated public privacy contact is required before wider enrollment.