Bowli is published under the Aquarel Labs brand in Ireland. This policy covers the website, beta waitlist and iPhone app. Account and profile information is stored remotely; Free food history stays on your device.
1. Account and profile information
Supabase processes your email, authentication credentials and sessions, plus limited name or photo details from Apple or Google if you use their sign-in services. Bowli never receives your Apple or Google password. Your account ID, name, date of birth, height, weight, biological sex, activity, optional body-fat and step estimates, preferences and current calorie and macro targets are saved in your account profile in Supabase. Some profile information may be health-related data.
2. Food history and search
Meals, amounts, resolved nutrition values and historical daily targets are stored on your iPhone, scoped to your account. Bowli does not upload Free food history or provide cloud restoration. CSV exports are readable copies, not backups that Bowli can import. Food search checks the bundled library first. A missing query may be sent through the authenticated Cloudflare API to USDA FoodData Central. Shared results are cached for up to one hour using a query hash without your account ID; Bowli application logs do not store raw search text. Your profile and meal history are not sent to USDA.
3. RevenueCat and subscription records
RevenueCat remains active to check entitlements and support restoration and management of existing subscriptions, even when new paid offers are hidden. It receives your Bowli account ID, purchase and receipt information, subscription status and the technical app/store information needed to operate the service. RevenueCat also provides subscription reporting. Bowli does not send it your food history or nutrition profile, email or name, and does not enable advertising-identifier collection or advertising integrations. Apple handles payment information.
4. Why information is used
We process information to create and secure your account, save your profile, calculate starting estimates, deliver food search, manage existing subscriptions and respond to support requests. The lawful bases include providing the service, legitimate interests in security and reliability, legal obligations and consent where required. Health-related information requires an appropriate legal basis under applicable law. We do not sell or rent personal data or use it for third-party advertising.
5. Service providers
Current providers are Supabase for authentication and profile storage; Cloudflare for the API, security and caching; USDA for remote food results; RevenueCat and Apple for subscription records; Apple or Google for optional sign-in; and Vercel for website hosting and aggregated web analytics. They process information under their terms and privacy notices. We may disclose information when required by law or for a business reorganisation with appropriate safeguards.
6. Waitlist, website analytics and support
The waitlist stores your email, signup time, source, consent-notice version and coarse device platform. It does not store the full browser User-Agent. We use these details for beta access and occasional product updates; contact us to unsubscribe. Vercel Web Analytics measures pages, approximate region, referrer, browser, operating system and device type. We do not send waitlist emails to analytics. Support messages are processed to respond. The native app does not send meal-logging events to a product-analytics service.
7. Retention and deletion
Account and profile data remain while the account is active. Settings lets you initiate account deletion with a typed confirmation. A completed deletion removes the Supabase account/profile and RevenueCat customer record, then removes that account’s local food history, targets and drafts on this iPhone. If cleanup fails, the app keeps a pending receipt and asks you to retry. Clearing local history alone keeps your account and remote profile. Signing out hides history without deleting it. Apple subscriptions are not cancelled by account deletion; manage them with Apple. If you signed in with Apple, follow the app’s instructions to remove Bowli access from your Apple Account when needed.
8. Your choices and rights
You can edit your profile, export or clear local food history and initiate account deletion in the app. Copies you exported, Apple device backups and records on other devices remain under your control and are not removed remotely by Bowli. We keep support and security records only as reasonably needed; legal retention requirements and provider backup schedules may apply. Depending on where you live, you may have rights to access, correct, erase, restrict or receive data, object to processing or withdraw consent. Contact us for requests or help. EEA residents may complain to their supervisory authority, including Ireland’s Data Protection Commission. Waitlist details remain until you unsubscribe or they are no longer needed for beta access and launch updates.
9. Security, cookies and international processing
We use encrypted connections, account-scoped access controls and restricted server credentials. No system is completely secure. The website stores a functional language cookie and does not use advertising cookies. Vercel Web Analytics does not use persistent cross-site tracking cookies. App sessions are stored securely on your device. Bowli is operated from Ireland; providers may process data elsewhere. Required transfer safeguards may include adequacy decisions, standard contractual clauses and provider data-protection agreements.
10. Adults and policy changes
Bowli is intended for adults aged 18 and over. Contact us if a minor has provided information so we can investigate and remove it. We will publish policy updates with a revised effective date and give appropriate notice of material changes.
11. Contact
For support, privacy requests or waitlist removal, email support@bowli.mobile. Never send passwords, login codes or payment-card details.