Cookie Policy
Last updated: April 1, 2026
This Cookie Policy explains how MiserablyEmployed, LLC (“we,” “us,” or “our”) uses cookies and similar storage technologies in connection with the SessionSight platform (a product of MiserablyEmployed, LLC) and the sessionsight.com website. This policy is part of our Terms of Service and should be read alongside our Privacy Policy.
1. What Are Cookies
Cookies are small text files that a website places on your device (computer, tablet, or mobile phone) when you visit a page. They allow the website to recognize your device and store certain information about your session or preferences. Cookies may be “first-party” (set by the website you are visiting) or “third-party” (set by a domain other than the one you are visiting). SessionSight uses only first-party cookies and does not set any third-party tracking cookies.
In addition to cookies, websites may use other browser storage mechanisms such as localStorage, which stores data directly in the browser without an expiration date. Like cookies, localStorage is scoped to the origin domain and is accessible only by that domain.
2. Two-Tier Capture: What Accept and Decline Mean
The SessionSight SDK runs in one of two tiers. Which tier is active for a given visit determines what we capture and what cookies, if any, we set on the visitor’s device.
| Tier | When it runs | Cookies / Storage | What is captured |
|---|---|---|---|
| Anonymous tier | Before the visitor has clicked the cookie banner, after the visitor has clicked Decline, or whenever the browser sends a Global Privacy Control or Do Not Track signal | None. Per-tab identifiers are minted in memory only, never written to cookie or localStorage. | Pageview counts, referrer host, device class (mobile, tablet, desktop), aggregate click density, aggregate form analytics counters (starts, submits, abandonments, per-field retries), error counts, goal counts. No replay, no per-visitor row, no IP, no IP-derived geolocation. |
| Full tier | Only after the visitor has clicked Accept on the cookie banner (and Global Privacy Control or Do Not Track is not active) | ss_vid, ss_vtoken, ss_sid (see Section 3) and sessionsight_visitor_id localStorage entry. | Everything in the anonymous tier, plus session replay, per-visitor journey reconstruction, returning-visitor linking, identified goal revenue attribution, and country or region geolocation. |
The anonymous tier exists so that visitors who never click the banner, or who click Decline, are still counted in aggregate page-level analytics. It does not write anything to the device and does not process anything that the law treats as personal data: there are no persistent identifiers, no IP-derived data points, and no behavioural fingerprint that survives a tab close. Because there is no per-visitor row, requests under data subject access rights for anonymous-tier-only visitors return “no data on file” by definition: there is nothing personally identifiable to retrieve, and nothing to delete.
The full tier is the original SessionSight capture model. It writes the cookies and localStorage entries documented in Section 3 and produces a per-visitor record that the customer’s dashboard can query.
A visitor who switches from Accept to Decline (or to no answer) triggers an immediate flush of any buffered events, after which the SDK clears every persistent storage entry it had previously written and drops back to the anonymous tier.
3. Cookies Set by the SessionSight SDK
When a customer integrates the SessionSight SDK into their website, the SDK may set the following cookie and localStorage entry on the End User’s device. These are set on the customer’s domain (first-party) and are used solely for the purpose of identifying returning visitors across sessions.
| Storage Type | Name | Purpose | Duration | Classification |
|---|---|---|---|---|
| Cookie | ss_vid | Persistent visitor identification. Assigns a unique, anonymous identifier to each visitor so that SessionSight can correlate multiple sessions from the same browser. | 1 year | First-party, SameSite=Lax |
| localStorage | ss_vid | Backup visitor ID storage. Used as a fallback when cookies are unavailable or have been cleared, ensuring consistent visitor identification. | Persistent (until cleared by user) | First-party |
| Cookie | ss_sid | Recording session identifier. Used to associate server-side events with the active SessionSight recording session. | Session (cleared when the browser closes) | First-party, SameSite=Lax |
How the SDK Uses These Storage Mechanisms
The SessionSight SDK first attempts to read the visitor identifier from the ss_vid cookie. If the cookie is not present (for example, because the user’s browser blocks cookies or the cookie has expired), the SDK falls back to reading the value from localStorage. If neither storage mechanism contains an existing identifier, the SDK generates a new anonymous identifier and writes it to both the cookie and localStorage.
The ss_vid value is a randomly generated anonymous string. It does not contain any personal information such as names, email addresses, or IP addresses. Its sole purpose is to link multiple browsing sessions from the same browser so that analytics data can be accurately attributed.
Do Not Track and Global Privacy Control
When the SDK detects a Do Not Track (DNT) or Global Privacy Control (GPC) signal from the visitor’s browser, it suppresses the persistent ss_vid cookie and localStorage entry and uses an in-memory session identifier instead. The visitor’s session is still recorded, but they are not identified across separate visits.
No Third-Party Tracking
The SessionSight SDK does not set any third-party cookies. All cookies and localStorage entries are scoped to the customer’s own domain. SessionSight does not use cookies for cross-site tracking, advertising, or behavioral profiling.
4. Cookies and Storage on sessionsight.com
When you visit the SessionSight website (sessionsight.com) or use the SessionSight dashboard, the following first-party cookies and browser storage entries may be set:
| Storage Type | Name | Purpose | Duration | Classification |
|---|---|---|---|---|
| Cookie | better-auth.session_token | Authenticates your dashboard session after sign-in. | Session or up to 30 days for “remember me” sessions | First-party, HttpOnly, Secure, SameSite=Lax |
| Cookie | ss_vid | Persistent visitor identifier set by SessionSight’s own analytics SDK on our website. Same purpose and behavior as described in Section 3. | 1 year | First-party, SameSite=Lax |
| Cookie | ss_sid | Recording session identifier set by SessionSight’s own analytics SDK on our website. | Session | First-party, SameSite=Lax |
| localStorage | ss_vid | Backup of the visitor identifier when cookies are unavailable. | Persistent (until cleared by user) | First-party |
| localStorage | sessionsight-cookie-consent | Stores your cookie consent preference for this site. | Persistent (until cleared by user) | First-party |
| localStorage | sessionsight-theme | Stores your selected dashboard theme (light/dark). | Persistent (until cleared by user) | First-party |
| localStorage | ss-active-property | Remembers the most recently selected property in your dashboard. | Persistent (until cleared by user) | First-party |
Essential and Functional Cookies
The authentication cookie and dashboard preference entries above are necessary for the website and dashboard to function properly. They enable core functionality such as user authentication, session management, security protections, and remembering your preferences (such as theme and active property). Without these, certain features of the website or dashboard may not work correctly. Essential cookies cannot be disabled because they are required for the basic operation of the service.
Analytics Cookies (First-Party)
We use SessionSight’s own analytics product on our website to understand how visitors interact with our pages. This data helps us improve the user experience. Because we use our own product, these are first-party analytics cookies, and the data collected is processed in accordance with our Privacy Policy. No data is shared with third-party analytics or advertising platforms.
5. How to Manage Cookies
You have the right to decide whether to accept or reject cookies. You can manage your cookie preferences through your browser settings. Most browsers allow you to:
- View what cookies are currently stored on your device and delete them individually or in bulk.
- Block all cookies or only third-party cookies.
- Configure the browser to notify you when a cookie is being set, allowing you to accept or reject it on a case-by-case basis.
- Clear all cookies and site data when you close the browser.
To manage localStorage entries, you can use your browser’s developer tools (typically accessible via F12 or the browser menu) to view and delete stored data for specific websites.
Please note that if you disable or delete the ss_vid cookie and localStorage entry, SessionSight will treat subsequent visits as coming from a new visitor. This may affect the accuracy of visitor identification and analytics data for websites that use the SessionSight SDK.
For more information on managing cookies in specific browsers, consult your browser’s help documentation or visit allaboutcookies.org.
6. Customer Responsibility
SessionSight provides the SDK as a tool for website owners and operators (“Customers”). Customers are responsible for ensuring that they have obtained appropriate consent from their End Users before loading the SessionSight SDK on their websites, in accordance with applicable data protection and privacy laws (including, but not limited to, the EU ePrivacy Directive, GDPR, UK GDPR, CCPA/CPRA, and any other applicable cookie consent regulations).
Customers are responsible for implementing their own cookie consent banner or management platform and ensuring the SessionSight SDK is loaded only after appropriate consent has been obtained, where required by law. SessionSight may provide tools and configuration options to assist with consent-based SDK loading.
For guidance on implementing consent-based loading of the SessionSight SDK, please refer to our developer documentation.
7. Changes to This Policy
We may update this Cookie Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors. When we make material changes, we will update the “Last updated” date at the top of this page. We encourage you to review this policy periodically to stay informed about how we use cookies.
If we make changes that materially expand the types of cookies we use or the purposes for which we use them, we will provide prominent notice on our website or through other appropriate communication channels.
8. Contact Us
If you have any questions or concerns about this Cookie Policy or our use of cookies, please contact us:
- Email: [email protected]
- Legal inquiries: [email protected]
- Mail: MiserablyEmployed, LLC, 400 N Tampa St Ste 1550 PMB 200053, Tampa, Florida 33602-4719 US