Notice Details
Track the current cookie notice version and contact path.
Why Cookies Are Used
Browser-side storage is limited to legitimate service purposes.
- Keeping a signed-in user authenticated.
- Protecting sessions and preventing misuse.
- Remembering basic interface or consent preferences where enabled.
- Measuring service performance or usage only when that measurement has been explicitly approved for the relevant public surface.
Storage Technologies
The cookie notice should describe the main browser-side storage types in use.
- HTTP cookies used for authentication, session continuity, and security protections.
- Local or session storage used for limited interface state such as theme, consent, or other preference handling where enabled.
- Optional measurement identifiers only when the relevant public surface has explicitly enabled and disclosed that behavior.
Cookie Categories
Essential first, optional only with approval.
Cookie Inventory
The public notice should identify the current browser-side identifiers in use on this surface.
| Identifier | Type | Purpose | Default state |
|---|---|---|---|
| veridataops_cookie_preferences | Cookie | Stores the visitor's cookie preference choices for preferences and analytics. | Set after the visitor records a cookie choice. |
| netbox-source-reconciler-theme | Local storage | Remembers an allowed theme preference in the current browser when preference storage is enabled. | Only used after preference consent is enabled. |
| netbox-ingester-theme | Local storage | Legacy theme-preference key kept for older public-surface visits and migrated preference handling. | Read only when preference consent is enabled. |
| G-R7WXGD2XHR | Analytics identifier | Enables Google Analytics measurement for the public marketing surface. | Disabled until analytics consent is explicitly enabled. |
Duration And Third Parties
The notice should describe how long browser-side identifiers last and whether third parties receive them.
Managing Cookies
Visitors can manage browser storage through browser settings and the site consent surface.
Disabling strictly necessary cookies may prevent login, security, or application features from working correctly.
Where consent is required for optional analytics or similar non-essential storage, VeridataOps should provide a surface-appropriate choice before those identifiers are used.
Consent choices for public marketing analytics and preference storage can be changed through the site cookie settings surface, and older local theme keys can be cleared through normal browser storage controls.
Questions about browser-side storage, optional analytics behavior, or consent handling can be routed through privacy@veridataops.com.
Next Step
Use the live public surface as the review artifact.
When a customer or reviewer needs product-safe wording, point them at these URLs on veridataops.com and then attach deployment-specific evidence separately.