Cookie Policy — OpsIQ
Cookie Policy
This policy explains how this website uses cookies and similar technologies, how the OpsIQ widget utilizes local storage on our customers' sites, and how OpsIQ's own cookie-consent product provides end-users with real, enforceable control.
Effective: June 22, 2026
Version: 2026.06
Reviewed by: OpsIQ Security
Essential Only by Default
Strictly necessary cookies are required to run the site. All other cookies wait for your consent.
Cookies vs. localStorage
We are precise about which technology we use and why, for each purpose.
GPC & DNT Respected
Browser opt-out signals are treated as a request to skip non-essential cookies.
Real, Enforced Control
- What cookies & similar technologies are
- Why we use them
- The four cookie categories
- Cookies we set on this site
- Local storage on this site
- The OpsIQ widget & localStorage on customer sites
- Consent & how we ask
- Managing or withdrawing consent
- Do-Not-Track & Global Privacy Control
- Third parties & sub-processors
- Children
- Using OpsIQ's consent product on your own site
- How long we keep consent records
- Changes to this policy
- Contact
1. What Cookies & Similar Technologies Are
In short, cookies are small files, and localStorage is browser storage. We use both; this policy explains which and why.
Cookies are small text files placed on your device by a website you visit. They allow a site to remember your actions and preferences over time. This policy also covers similar technologies that perform comparable functions but work differently:
- Cookies: Small files sent back to the server on every matching request. They can be first-party (set by this site) or third-party (set by another domain). They have an expiry and can be cleared by you at any time.
- Local storage (localStorage): Key/value data kept by your browser that is not automatically sent on every request. It has no built-in expiry and persists until cleared. The OpsIQ widget uses this for a visitor identifier (see Section 6).
- Session storage (sessionStorage): Similar to local storage but cleared when you close the tab.
- Pixels & beacons: Tiny image or script requests used to record that a page or message was loaded.
The key distinction is that cookies travel with requests and expire, while localStorage stays in the browser and is read by scripts on demand. Both are covered by consent law where they are not strictly necessary.
2. Why We Use Them
In short, we use cookies to keep the site secure, remember your preferences, and — only with consent — measure traffic and campaigns. We do not create cross-site ad profiles.
On this marketing site, we use a small number of cookies and similar technologies to:
- Keep the site secure and functioning — sign-in sessions, CSRF protection, load balancing, and remembering your consent choice so we don't ask on every page.
- Remember your preferences — such as currency/region, language, and theme.
- Understand aggregate traffic — privacy-respecting measurement of which pages are visited and how people find us.
- Measure marketing — only where you consent, to see which campaigns brought you here.
We do not use cookies to build advertising profiles about you across unrelated sites, and we do not sell personal information. Non-essential cookies are only set after you consent through the banner described in Section 7.
3. The Four Cookie Categories
In short, we categorize cookies into four standard categories: Strictly Necessary (always on), Preferences, Analytics, and Marketing (all opt-in). Only the first category is exempt from consent; the other three require your permission.
| Category | What It Does | 1st / 3rd Party | Typical Duration | Essential? |
|---|---|---|---|---|
| Strictly Necessary | Authentication, security (CSRF), load balancing, and remembering your consent choice. The site cannot function without these. | First-party | Session – 12 months | Yes (no consent needed) |
| Preferences | Remember choices you make — currency/region, language, light/dark theme — so the site feels consistent. | First-party | Up to 12 months | No (opt-in) |
| Analytics | Aggregate, privacy-respecting measurement of pages viewed, traffic source, and time on page, to improve the site. | First-party | Up to 13 months | No (opt-in) |
| Marketing | Measure the effectiveness of campaigns that referred you. Set only with consent. | First / third-party | Up to 13 months | No (opt-in) |
These four categories are the same baseline model that OpsIQ's own consent product ships with, and our customers can rename or extend them on their own sites (see Section 11).
4. Cookies We Set on This Site
In short, we provide a short, honest list: session/auth, CSRF, the consent state itself, preference cookies, and optional first-party analytics. Below is a realistic, generic inventory for this PHP-based SaaS site. Exact names may evolve, but the purpose and category
Was this article helpful?