This document is not yet effective. Everock’s operator details and final legal terms must be completed before it is used as an agreement or production notice.
Cookies and browser storage
Cookies are small values a browser sends with matching requests. Local storage persists values for an origin, while session storage is scoped to a browser tab’s session. Everock uses these technologies for account access, interface preferences, and supported SDK identifiers.
This draft covers the current implementation. Authentication providers and enabled integrations can introduce their own storage. The final production inventory must identify actual cookies, providers, purposes, and lifetimes before this policy becomes effective.
Current implementation inventory
SDK storage belongs to the instrumented application’s origin; visiting a documentation page does not itself install the SDK in your application.
| Storage | Purpose | Duration / scope |
|---|---|---|
| Authentication cookies | Maintain signed-in access and supported authentication flows. Names and lifetimes depend on the configured auth provider. | Provider configuration; browser domain and path rules apply. |
| everock-landing-appearance · local storage | Remember light or dark appearance on the public website. | Persists until cleared or replaced. |
| theme · local storage | Remember the selected dashboard and documentation appearance. | Persists until cleared or replaced. |
| everock.sid · session storage | Associate SDK events with the current browser-tab session in an instrumented application. | Browser-tab session. |
| everock.device · local storage | Associate SDK evidence with a browser installation where device identification is used. | Persists until cleared or replaced. |
Essential functions and optional collection
Authentication storage supports signed-in functions. Appearance storage remembers an interface choice. SDK telemetry and replay must be assessed separately according to their purpose and the law applicable to the customer’s application.
Do not infer a blanket cookie exemption or consent from this inventory. When permission is required, the application must obtain it and initialize the SDK with the appropriate capture categories disabled until that permission is recorded. The SDK does not display a consent banner automatically.
Your choices
- Use your browser’s site-data controls to inspect or remove cookies and local or session storage.
- Change the appearance control to replace the saved theme preference.
- Use your application’s consent interface to withdraw optional capture permission where applicable.
- Remember that clearing authentication cookies signs you out, and clearing SDK identifiers can create a new session or device identity.
Third-party technologies and changes
This page does not assert that advertising pixels or a particular marketing analytics provider are installed. Any additional nonessential tracking must be documented and controlled before activation. Embedded third-party content may follow the third party’s own policy.
The customer operating an instrumented website is responsible for its own notices and consent choices. Questions about this inventory or future changes can be sent using the Privacy topic in the contact form.
