Broklya
Privacy & data
This notice covers the broklya.com website and its private-access flow. Broklya is in closed beta, so the notice will evolve as the product and public launch model are finalized.
Updated 21 August 2026
What the website receives
For waitlist access we receive the email address, platform preference, locale, selected market/currency and, if you choose to answer it, one product-interest category. For invitation claims, the access service receives the invite code and email needed to validate and attach access. The website does not use access email as a marketing-newsletter subscription.
Product analytics
The site records a small set of interaction events such as landing views, invite or waitlist opens, successful access steps, install-page actions and whether a Broklya FAQ question matched. These events are intentionally designed not to contain email addresses, invite codes or the text you type into the public Broklya FAQ.
Infrastructure
The website is hosted on Vercel and the access flow uses the shared Broklya Supabase backend. Hosting and backend providers may process normal technical request data needed to operate, secure and troubleshoot the service.
Mobile app data
The mobile Broklya app can process additional account, nutrition, meal, image, weight, activity and AI-analysis data. This website notice is not a substitute for the final mobile-app privacy notice that will accompany public distribution.
Your data requests
During closed beta, use the account/data controls available in the app. If the relevant control is not available, use the beta support channel associated with your invitation and describe the request without posting secrets or access codes publicly.
Anonymous measurement IDs
To count unique website visits and sessions without attaching analytics to an email or Broklya account, the site stores random browser and session identifiers. It can also record a coarse acquisition category such as direct, search, social, referral or sanitized UTM source/medium/campaign values. We do not store the referring URL in these product events.