Cookie Policy

1What cookies & similar technologies are

Cookies are small text files placed on your device by a website you visit. They let a site remember your actions and preferences over time. This policy also covers similar technologies that perform comparable functions but work differently, so it helps to be precise:

• 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) — like 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: cookies travel with requests and expire; localStorage stays in the browser and is read by scripts on demand. Both are covered by consent law where they are not strictly necessary. Throughout this policy, OpsIQ means the platform operated by Nabtech Digitalnet Limited (nabtech.co).

2Why we use them

On this marketing site we use a small number of cookies and similar technologies to:

• Keep the site secure and working — 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.

3The four cookie categories

We organise cookies and similar technologies into four standard categories. Only the first is exempt from consent; the other three are set only with your permission.

These four categories are the same baseline model that OpsIQ's own consent product ships with — and which our customers can rename or extend on their own sites (see Section 11).

4Cookies we set on this site

Below is a realistic, generic inventory for this PHP-based SaaS site. Exact names may evolve, but the purpose and category are authoritative. We do not list cookies we do not set.

Third parties such as our CDN or payment processor may also set cookies in specific contexts — see Section 10.

5Local storage on this site

This site uses a small amount of localStorage for interface state that doesn't need to travel with every request. Because it isn't a cookie, it has no expiry and is read only by scripts on this page:

• UI state — e.g. whether you dismissed a notice, or a remembered tab — so the interface behaves consistently between visits.
• Consent mirror — a copy of your consent choice may be mirrored to localStorage alongside the cookie_consent cookie, so client-side scripts can honour it without a round-trip.

Clearing site data in your browser removes these values. None of this local storage is used to track you across other websites. The OpsIQ widget on customer sites uses localStorage differently — see the next section.

6The OpsIQ widget & localStorage on customer sites

When the OpsIQ chat widget is embedded on one of our customers' websites, it uses localStorage — not third-party tracking cookies — to keep:

• a visitor identifier, so a conversation can continue across page loads and return visits;
• session / UI state, such as whether the widget is open or minimised.

Using localStorage here means the identifier is scoped to that customer's site and is not silently broadcast to other domains the way a third-party cookie can be. In this context OpsIQ acts as a data processor on behalf of the customer (the website operator), who is the controller. The customer is responsible for the consent banner shown on their own site; OpsIQ provides the tooling (Section 11) to capture and enforce those choices. See our Data Processing Addendum for the processor terms and our Privacy Policy for the controller/processor split.

7Consent & how we ask

Strictly necessary cookies are exempt from consent because the site cannot operate without them. Everything else — Preferences, Analytics and Marketing — is non-essential and is set only with your consent.

When you first visit, a consent banner lets you:

• Accept all — enable every category;
• Reject non-essential — keep only strictly necessary cookies;
• Preferences — choose each category individually.

Your choice is recorded in the cookie_consent cookie (with a mirror in localStorage) so we don't ask again on every visit, and you can change it at any time (Section 8). We keep a record of consent decisions so we can demonstrate, if asked, that consent was freely given — see Section 12 on retention.

8Managing or withdrawing consent

You stay in control. You can change or withdraw your choices at any time, and withdrawing consent is as easy as giving it:

• Consent preferences: reopen the preferences panel from the banner control to turn categories on or off, or to withdraw consent entirely. Changes take effect immediately for future capture.
• Browser settings: most browsers let you block or delete cookies and clear local storage for a site. Note that blocking strictly necessary cookies may break sign-in and other core functions.

When you withdraw consent for a category, we stop setting new cookies in that category. Existing non-essential cookies are expired or cleared on your next interaction.

9Do-Not-Track & Global Privacy Control

Some browsers and extensions can send an automated privacy signal:

• Global Privacy Control (GPC) — a standardised signal indicating you opt out of sale/sharing of personal information.
• Do-Not-Track (DNT) — an older browser header expressing a preference not to be tracked.

Where your browser sends a GPC or DNT signal, we treat it as a request to opt out of non-essential and marketing cookies, and we will not set those categories unless you later explicitly consent through the banner. Because there is no single industry standard for honouring DNT, we apply it on a best-effort basis alongside GPC.

10Third parties & sub-processors

Some functionality relies on trusted third parties that may set their own cookies under their own privacy and cookie policies:

• Cloudflare — CDN and DDoS protection; may set a security cookie to identify trusted web traffic.
• Payment processors (Stripe / Paystack / PayPal) — set cookies during checkout for fraud prevention and to complete a transaction.
• Embedded media — where a page embeds external video or maps, the provider may set cookies.

For a full list of the sub-processors OpsIQ relies on to deliver the service, and how we handle personal data overall, see our Privacy Policy.

11Children

This website and the OpsIQ product are intended for businesses and are not directed at children. We do not knowingly use cookies or similar technologies to build profiles of children. If you believe a child has provided personal information through our site, contact us at [email protected] and we will delete it.

12Using OpsIQ's consent product on your own site

Beyond the cookies on this marketing site, OpsIQ ships its own cookie-consent platform that customers deploy on their websites to obtain and enforce visitor consent. It is a separate product capability — and it is what we use ourselves. For our customers it provides:

• Admin-defined categories — define your own categories, rename them, and decide exactly what counts as strictly necessary for your site.
• Per-category enforcement that actually stops capture — when a visitor declines Analytics, OpsIQ truly stops capturing analytics for that visitor. Consent is enforced at the data layer, not merely hidden in the UI.
• 20+ banner designs — transparent, solid and gradient styles you can brand to match your site.
• Group-domain sharing — a single consent choice can be honoured across a group of related domains you operate.
• A consent ledger — a durable record of who consented to what and when, so you can demonstrate compliance.

Customers configure and brand the banner from their OpsIQ admin, and it is delivered through the OpsIQ widget. The legal responsibility for the consent experience on a customer's site rests with that customer as controller. Learn more on the Consent & GDPR page.

13How long we keep consent records

We retain a record of your consent decisions for as long as needed to demonstrate that consent was validly obtained, and to honour your stored preference, after which records are purged on a retention schedule. The cookie_consent cookie itself typically persists for up to 12 months before you are re-prompted. You can clear it sooner via your browser, and any new visit re-establishes your preference through the banner.

14Changes to this policy

We update this Cookie Policy when our use of cookies or similar technologies changes. The Effective date at the top reflects the current version. Material changes are posted on this page, and where required we will refresh the consent banner so you can review your choices.

15Contact

Questions about cookies or this policy: [email protected]

See also our Privacy Policy, Consent & GDPR page, Data Processing Addendum and Compliance overview.

This document is provided for transparency and does not constitute legal advice. Customers in regulated industries should review it with their own counsel before deployment.