KeySkope
KeySkope / Documentation
Documentation

Cookies, storage and analytics

How KeySkope uses browser storage and measures activity.

Optional website analytics

With your permission, KeySkope sends page-view, signup-click and contact-form-open events to its own service. Events contain an approved public page path, the event type, a broad traffic channel such as Google, LinkedIn or direct, and the domain name of the referring website. Page views also carry a random browser identifier that this site creates in your browser when you accept. The identifier is not derived from your device, network or any account and does not identify you personally; it lets platform administrators count distinct consenting browsers, returning browsers and the pages each browser viewed. Query strings, fragments, full referring URLs, form contents, names, email addresses and IP addresses are not part of these records. We retain daily aggregate totals and individual page-view records for 90 days.

Your choice

Optional website analytics are off until you accept. Use Analytics preferences at the bottom of any public page to accept or reject them later. A Global Privacy Control or Do Not Track signal disables optional analytics. Your choice, together with the browser identifier when you accept, is stored in this browser under ks_analytics_consent_v1 for up to 180 days. Clearing browser storage removes them. Rejecting stops future events, removes the identifier from this browser and asks our service to delete the page-view records stored under it. Aggregate totals are kept but cannot be associated with a browser or a person.

Portal storage

The portal uses session storage for sign-in state, including the current authentication token and signed-out marker. It also uses local storage to remember the sidebar preference. These features are separate from optional website analytics. The identity provider may use cookies on its sign-in domain to maintain authentication.

Operational records

Signup requests, contact requests, successful portal activity and security audit records support operating the service. Platform administrators can see aggregate activity and tenant onboarding state. Rejecting website analytics does not disable these service records. The 90-day limit above applies to website analytics counters, not customer or security records.

Network requests

Hosting infrastructure handles IP addresses and request metadata to deliver the site and protect it from abuse. The analytics collector temporarily uses a source IP in memory for rate limiting but does not write it into the analytics tables. Some pages load fonts from Google Fonts. KeySkope does not install an advertising pixel or external analytics service.

Questions

Use the contact form on the homepage for questions about these features. This page documents storage and analytics behavior; it is not a complete privacy notice or terms of service.

A clearer place to start

Know your access.
Focus your next review.