BeautyReply beta
Cookies & Local Storage
Effective 28 August 2026
This page describes cookies and browser storage technologies BeautyReply currently uses or may cause a visitor browser to load. It is a technical inventory for legal review — not a cookie consent banner.
1. BeautyReply dashboard (business users)
BeautyReply account session. When you sign in to the dashboard, BeautyReply stores session tokens in the browser (typically localStorage) so you remain signed in. These tokens are necessary for authentication.
Platform language preference. Your selected dashboard language may be stored locally or in your workspace profile.
No third-party advertising or analytics cookies were identified in the BeautyReply dashboard codebase at the time of this review. Verify production deployments before launch.
2. Embedded website widget (widget visitors)
localStorage. The widget stores a conversation identifier, optional visitor token (for human handoff polling), selected language, and temporary product configuration state. These are functional and not used for cross-site advertising.
sessionStorage. The widget may store that the AI disclosure notice was shown during the current browser session so it is not repeated unnecessarily.
hCaptcha. When configured, lead forms and signup flows may load hCaptcha, which may set its own cookies or use browser storage. Review hCaptcha's privacy policy for consent requirements in your jurisdiction.
Google Fonts. Dashboard pages may request fonts from Google. Font requests can involve IP address processing by Google. Consider self-hosting fonts if counsel advises minimizing third-party requests.
3. Shopify add-to-cart (beta, optional)
When enabled by a salon and embedded on a Shopify storefront, add-to-cart actions use Shopify's cart API on the merchant domain. Shopify may set or read its own cookies according to the merchant's Shopify configuration.
4. What may require consent (verify with counsel)
- hCaptcha on public forms if not strictly necessary in your jurisdiction
- Google Fonts if treated as non-essential third-party processing in the EU
- Any future analytics or marketing tools added before launch
5. Related documents
See also the Privacy Policy and Subprocessor List.
