The public website
The public Ask Gabriel website uses Plausible Analytics to understand aggregate traffic and page performance. Our current Plausible setup is designed to work without analytics cookies and does not build individual advertising profiles.
Product analytics
To see how people use the public website, we set two first-party cookies on askgabriel.com: gab_vid, a random visitor ID kept for a year, and gab_sid, a visit ID that ends after 30 minutes without activity. Two more, gab_ft and gab_lt, remember the campaign that first and most recently brought you (utm tags, Meta’s ad click ID, the referring site, and the landing page). Our database records the pages you view, what you tap, and how far you scroll under that ID. PostHog, our analytics provider, keeps its own ID for the same visitor in a cookie and in browser storage and records sessions with everything you type, chats, lab readings, and account details hidden. None of this runs on links that carry a private code, and PostHog never runs in an account area or on the Gabriel Shop. Turning off “Product analytics and session recordings” in “Your privacy choices” removes our visitor cookies and stops PostHog in this browser.
Advertising
On our public marketing pages, the Meta pixel helps us measure our ads on Facebook and Instagram. These include our pages about topics such as chronic conditions, longevity, women’s health and men’s health. It can set Meta’s cookies (_fbp, and _fbc after an ad click) and sends Meta the page you visited and basic browser and device details. Our server sends Meta the same events through Meta’s Conversions API, with those cookies and a hashed copy of our visitor ID, and tells Meta when a website visitor joins the waitlist, creates an account, starts a first conversation, or pays for a Gabriel Shop order (never what was ordered or what it cost). The pixel never runs on checkout pages, our care catalogue, the Gabriel app, or anything after you sign in. On the Gabriel Shop, where the bag and checkout are part of the shop’s own page, it sends only your visit and your taps to join, ask Gabriel or open the app, and we never send Meta your name, email, phone number, health information, or what you buy. To turn it off, use “Your privacy choices” at the bottom of any page or turn on Global Privacy Control in your browser.
The signed-in product
When you sign in to a Gabriel product, we may use cookies or local browser storage that are necessary for authentication, security, session continuity, and preferences. Blocking this storage can prevent account features from working correctly.
Services you choose to open
Payment providers, mapping services, social networks, and other third-party sites may use their own cookies after you open or interact with them. Their policies govern that activity.
Your controls
You can remove or block cookies in your browser settings. Essential account features may stop working if you block required session storage. “Your privacy choices” at the bottom of any public page has two switches, ad measurement (the Meta pixel and Conversions API) and product analytics and session recordings. Your choices are kept in this browser’s storage and in two small cookies (gabriel-ads-optout and gabriel-analytics-optout) so our server can respect them too.
Questions about privacy?
Read the shared Gabriel privacy policy or contact us with a specific question.