Cookie and Storage Policy
1. Introduction
This Cookie and Storage Policy explains how LoopHQ (operated by PROXYGIST LLC, doing business as LOOP) uses cookies and similar browser storage technologies on our website, in our dashboard application, and in the chat widget that our customers embed on their websites.
For a full picture of how we handle data, please also read our Privacy Policy.
2. What We Use
2.1 Authentication Cookies (Strictly Necessary)
When you log in to your LoopHQ dashboard, we set HTTP-only session cookies through our authentication provider. These cookies keep you signed in, prevent unauthorized access to your account, and are required for the dashboard to function.
- Purpose: Authentication and session management
- Type: Strictly necessary, HTTP-only
- Duration: Session-based, refreshed automatically while you are active
- Can be disabled: No — disabling these cookies prevents you from logging in
2.2 Chat Widget Local Storage
The LoopHQ chat widget that businesses embed on their websites uses your browser’s localStorage and sessionStorage to make the conversation experience continuous across page loads.
Stored in localStorage (persists until you clear it):
- Conversation history (the messages exchanged between you and the Loop agent during a conversation)
- Widget display preferences (open/closed state)
- Whether you have engaged with the widget before
Stored in sessionStorage (cleared when the browser tab closes):
- The ID of the most recently viewed conversation
- Per-conversation unread message counts
Important: Conversation history is also stored on LoopHQ’s servers (see Privacy Policy § 3.3). The localStorage copy exists to make the widget feel continuous — for example, so reopening the widget after a page refresh shows the same conversation.
Conversation data stored in localStorage stays in your browser. Server-stored conversation data is governed by Privacy Policy § 10.
2.3 Page Analytics
Our hosting provider collects page-level analytics for the LoopHQ website (loophq.dev) — including page views, navigation paths, and performance metrics. This collection does not rely on cookie-based tracking and does not include information that identifies you personally.
On our public marketing and account pages (e.g., loophq.dev/, /solutions, /pricing, /signup, /login, /legal/*, /unsubscribe), we also use Microsoft Clarity and PostHog to capture aggregated session behavior — page sequences, scroll depth, click activity, anonymized session replays, web vitals, and product-improvement events — for the purpose of improving the website. Both tools set first-party cookies to maintain session continuity (Clarity uses cookies typically named _clck and _clsk; PostHog uses cookies typically named ph_* and __ph_*) and may use additional first-party storage. Both tools automatically mask all form input, so typed content is not recorded. PostHog operates in identified-only mode, meaning anonymous visitors do not receive a persistent profile until they sign up for an account.
Neither Microsoft Clarity nor PostHog runs on the embedded LoopHQ chat widget that appears on our customers’ websites, in our authenticated dashboard, or on our APIs. Microsoft and PostHog act as sub-processors for this analytics collection — see our Sub-Processors page.
2.4 Rate-Limiting Identifiers
To protect the Service from automated abuse, we use a transient cache that records recent IP addresses and visitor identifiers in order to enforce abuse-prevention limits. These identifiers are stored only briefly and are not used for advertising or analytics.
3. What We Currently Do Not Use
- No advertising or marketing cookies. We currently do not run ad networks, retargeting pixels, or behavioral advertising trackers.
- No social media tracking pixels. We currently do not embed Facebook Pixel, LinkedIn Insight Tag, X/Twitter Pixel, or similar trackers on our website.
- No cross-site tracking cookies. We currently do not set or receive cookies that follow you across other websites.
- No session-recording inside the chat widget. We currently do not run Hotjar, FullStory, or comparable services inside the embedded chat widget. Microsoft Clarity and PostHog, described in Section 2.3, run only on our marketing and account pages and are automatically configured to mask form input.
Because we do not currently use marketing or cross-site tracking cookies, the LoopHQ website does not currently display a cookie consent banner. The cookies and storage described in Section 2 are either strictly necessary or are first-party storage used for the specific purposes listed.
If we introduce any advertising or tracking technology in the future, we will update this Cookie Policy in advance and (where required by law) introduce a consent or opt-out mechanism appropriate to the jurisdictions affected.
4. Third-Party Storage on Customer Sites
When the LoopHQ chat widget is embedded on a customer’s website, the localStorage and sessionStorage described in Section 2.2 are written toyour browser by the widget code, not by the customer’s website. The customer (the business operating the agent) acts as the data controller for the conversation that takes place on its site. The customer is responsible for any additional cookie or consent obligations that apply to its own website, including any region-specific consent banners required for visitors in jurisdictions outside the United States.
5. Managing Cookies and Local Storage
You can clear cookies and local storage at any time through your browser’s settings. Most browsers also let you block all cookies, block third-party cookies, or be prompted before any cookie is set.
Quick links to browser instructions:
- Chrome: Settings → Privacy and Security → Clear browsing data / Cookies and other site data
- Safari: Preferences → Privacy → Manage Website Data
- Firefox: Settings → Privacy & Security → Cookies and Site Data
- Edge: Settings → Cookies and site permissions
Note that clearing the LoopHQ authentication cookies will sign you out of the dashboard. Clearing chat widget local storage will reset your conversation history on a customer site (the server-side conversation record may still exist; see the Privacy Policy for retention and deletion).
6. Changes to This Policy
We may update this Cookie and Storage Policy from time to time as our use of cookies and storage evolves. Material changes will be communicated through the LoopHQ dashboard and reflected in the updated “Last Updated” date and version number.
7. Contact Us
Questions about this Cookie and Storage Policy can be sent to:
PROXYGIST LLC, doing business as LOOP
Privacy inquiries: privacy@loophq.dev
General inquiries: support@loophq.dev
Website: loophq.dev