COUNTERNEST

Cookie & Storage Policy

CounterNest · Nigeria

Updated 1 October 2026

Account cookies

CounterNest uses session and request-security cookies to support sign-in, guest management and protection against forged requests. Browser settings can remove or block these cookies, but account and management functions may then stop working.

Analytics storage on websites using a counter

The embedded counter stores a pseudonymous browser identifier in local storage under cn_visitor. It also reads cn_exclude, which lets a website owner exclude their own browser from measurement. Local storage remains until cleared or removed; it does not have a cookie-style automatic expiry.

A website owner must decide whether consent is required and, where it is, load the CounterNest script only after consent. The script itself is not a consent-management platform. Clearing browser storage changes the visitor identifier and may affect unique-visitor counts.

Browser notifications

Push notifications require browser permission and can be revoked in browser settings. Disabling notifications does not delete your CounterNest account.

Third-party and custom content

Administrators may add external content or scripts in isolated custom blocks. Those providers can make their own network requests and use storage subject to browser restrictions. The operator must update this notice and implement any required consent before enabling such integrations. CounterNest does not include advertising trackers in its default interface.

Managing your choices

Use your browser's cookie, storage and notification settings to review or remove permissions. Contact support@counternest.com for questions about CounterNest; contact the website owner about a counter embedded on their website.