Contact
Questions about an order? Email service@rhem.ai.
Current tracking settings
PostHog analytics starts only after you accept analytics in the cookie notice or enable it in Cookie preferences. It measures page visits, product interactions, signup actions and checkout progress. Our public website and campaign landing pages offer a separate choice for Meta advertising measurement. The browser Pixel starts only after you accept advertising. It can also measure a verified paid purchase on the campaign confirmation page. It does not load on private order pages or main-site confirmation pages.
You can reopen Cookie preferences from the footer at any time to change your analytics choice or withdraw advertising permission. Advertising can be enabled on public website and campaign pages. Rejecting either does not affect browsing or buying. We respect your browser’s Do Not Track setting; Global Privacy Control also prevents campaign advertising measurement.
Browser storage
Local storage named rhem-cookie-notice-v1 remembers your analytics choice and preference version. Your analytics choice is valid for 180 days, after which you are prompted again. The record remains in local storage until replaced or cleared. It contains no contact or payment information. Clearing browser storage removes it and displays the notice again.
Local storage named rhem-campaign-advertising-v1 remembers your separate advertising choice, its time and disclosure version, and whether a withdrawal still needs to reach our server. The version-2 choice expires after 180 days; the record remains until replaced or cleared. Earlier permission for server-only advertising does not enable the browser Pixel. When you accept advertising, an HttpOnly cookie named rhem_campaign_ads holds a random reference to an encrypted server consent record and expires after 180 days. We check that record and the original campaign checkout before allowing a purchase event. Withdrawal removes the cookie when the server request succeeds. Use Cookie preferences to withdraw permission; clearing local storage alone does not revoke the server record.
After a verified campaign purchase, local storage entries beginning rhem-campaign-purchase: remember its hashed event reference so reloading the confirmation page does not count it again. These entries contain no contact details, payment details or order-access credentials and remain until browser storage is cleared.
With analytics permission, PostHog stores random browser and session identifiers in browser storage (ph_ prefixed keys). A per-tab rhem:order-recorded: or rhem:reservation-recorded: entry prevents repeated confirmation views from counting again. Withdrawing permission removes these identifiers where the browser permits access.
Intercom Messenger loads on public pages for visitor support. Cookies with the intercom- prefix recognize your browser and maintain your chat session and conversations. We do not automatically send your account ID, name, email, or account creation date. You can clear these cookies through your browser settings; doing so may remove access to a previous conversation from that browser.
Local storage named rhem-feedback-shown-v1 records when the optional order-page feedback invitation or survey was shown, so automatic prompts are suppressed for 30 days. It contains only a timestamp, not your answer or contact information, and stays in your browser until replaced or cleared. The feedback link remains available even while automatic prompts are suppressed.
PostHog analytics
PostHog receives page paths, browser and device information, and the product interactions we measure. Network requests also disclose your IP address to PostHog. We remove URL query strings and fragments, exclude private order and admin pages, and do not send names, emails, form entries or payment references. With your permission, masked session recordings capture browsing on public product and editorial pages. Text and inputs are masked; forms, support chat, private order and confirmation pages are excluded. Console, network-body and canvas recording are disabled. Automatic click capture and person profiles remain disabled. Referrers include only the referring site, without its page path or query.
Withdrawing permission stops new analytics collection; it does not automatically delete events previously received by PostHog. Contact privacy@rhem.ai about your information. See PostHog’s privacy policy.
Optional Meta advertising measurement
With separate advertising permission on a public website or campaign page, the Meta browser Pixel sends PageView and ViewContent events, InitiateCheckout once per visit to a Rhem checkout entry page after advertising permission is granted, including when permission is granted on that page, and Purchase only when our campaign confirmation page verifies a paid order and the original consent. Purchase value is the product subtotal, excluding tax and shipping. Clicking a preorder button or visiting a confirmation URL does not by itself count as a purchase.
The Pixel can receive your IP address, browser information, page URL, referrer and Meta identifiers. It may set _fbp and _fbc cookies to recognize a browser and an ad click. Our explicit event parameters contain generic Rhem product details, currency, product subtotal and unique event identifiers; we do not add names, email addresses, delivery addresses, form answers or device conversations. Browser Pixel collection can include information in page URLs. The campaign payment-confirmation page removes its checkout reference from the address before loading the Pixel, and the Pixel does not load in the private order portal.
Withdrawing advertising permission stops new Pixel events in your browser immediately and asks our server to revoke the consent record so later purchase events are not authorized. We remove Meta cookies where browser access permits. If the server request fails, browser tracking remains off and we retry withdrawal when possible. Withdrawal does not automatically delete events Meta already received. Contact privacy@rhem.ai about your information. See Meta’s privacy policy.
Checkout, support, and content services
Intercom receives network and browser information and the pages where Messenger runs, along with messages or contact details you choose to provide in chat. See Intercom’s privacy policy. Messenger is not initialized on admin pages, private order pages, or payment-status pages.
Payment takes place on Stripe’s hosted checkout after you choose to buy. Stripe controls storage on its own pages; consult Stripe’s privacy policy. Your cookie notice acknowledgment here does not grant consent on Stripe’s website.
Website hosting and image or video delivery involve network requests to hosting and content providers. These requests can include your IP address and browser information. Social media links open those services only when followed. The separately consented Meta Pixel is described above.
Privacy questions
See our Privacy Policy for the website’s data collection and contact privacy@rhem.ai about your information.