Plain-English Summary
What this page covers
- The current audited site uses only strictly necessary session cookies and small functional sessionStorage items tied to login and UI state.
- The current audited site does not show analytics cookies, advertising pixels, marketing tags, or similar non-essential tracking code.
- Because no non-essential tracking is currently in use, the site does not show a cookie consent popup today.
- If non-essential analytics, A/B testing, ads, or marketing tags are introduced later, this notice and any required consent flow should be updated before release.
Overview
NICKNOW currently uses cookies and browser storage mainly to keep authenticated sessions working and to support short-lived login and UI state. In the current audited site implementation, those technologies are necessary or functional rather than advertising or analytics technologies.
Current Cookies And Storage
| Name | Category | Duration | Purpose |
|---|---|---|---|
| Customer dashboard session cookie | Strictly necessary | Up to about 24 hours per session configuration | Used for Discord-authenticated dashboard sessions. In code the actual name comes from the configured customer cookie name and is prefixed with __Host- in production. |
| Admin monitor session cookie | Strictly necessary | Up to about 24 hours per session configuration | Used only for the private owner/admin monitor. The code uses nicknow.sid locally and __Host-nicknow.sid in production. |
| sessionStorage: nicknow:auth-pending | Functional browser storage | Until the login flow completes or browser data is cleared | Used to complete the Discord OAuth popup flow on the customer website. It is not used for analytics or advertising. |
| sessionStorage: nicknow:flash | Functional browser storage | Until the message is shown or browser data is cleared | Used for one-time status and error banners in the customer site UI. It is not used for analytics or advertising. |
No Non-Essential Tracking Today
The current audited site does not show analytics scripts, advertising tags, cross-site pixels, heatmaps, chat widgets, or similar non-essential tracking code. For that reason, the site does not currently present a cookie consent banner.
Related Third-Party Requests
Even without analytics cookies, NICKNOW may still involve third-party requests that are part of core product delivery. Examples include:
- Discord OAuth requests during sign-in.
- Server-side Discord API calls for guild, member, role, and configuration data.
- Discord CDN image requests when avatars or guild icons are shown.
- Cloudflare edge routing/protection if used in the documented production deployment.
The current public pages do not load a remote Google Fonts dependency or a comparable third-party font host.
Future Changes
If NICKNOW later adds non-essential analytics, experimentation tooling, advertising technology, marketing tags, or similar tracking, this notice and any required consent mechanism should be updated before those technologies go live.
The same applies if future payment or marketing flows introduce new browser-side tracking or new storage categories that do not exist in the current audited implementation.
Managing Storage
You can usually control cookies through your browser settings, but blocking strictly necessary cookies may stop login or dashboard features from working.
You can also clear browser session storage to remove the temporary nicknow:auth-pending and nicknow:flash values.
For privacy questions about the current storage behavior, contact [email protected].