Cookie Policy
Last updated: April 8, 2026
This Cookie Policy explains how StorePilot uses cookies and similar tracking technologies, the distinction between the Platform dashboard and the WordPress Plugin, and what obligations arise for website owners ("Clients") using the Plugin.
1. What Are Cookies?
Cookies are small text files stored in your browser to enable functionality such as staying logged in, remembering preferences, or tracking usage patterns. Similar technologies include localStorage, sessionStorage, and browser fingerprinting.
2. Cookies on the StorePilot Dashboard
The Platform dashboard (at dashboard.store-pilot.net) uses a minimal set of cookies for authentication:
| Name | Type | Purpose | Duration |
|---|---|---|---|
wpel_access_token | Functional / Necessary | Stores the JWT access token to keep you logged in | 15 minutes |
wpel_refresh_token | Functional / Necessary | Allows silent token renewal without re-entering credentials | 7 days (HttpOnly, Secure) |
These cookies are strictly necessary for the Platform to function and do not require consent under the ePrivacy Directive.
No third-party analytics, advertising, or social media cookies are used on the Platform dashboard.
3. Storage Used by the WordPress Plugin on Client Websites
The StorePilot Plugin does not set HTTP cookies on visitors' browsers. Instead, it uses browser storage APIs:
| Storage Key | Type | Purpose | Duration |
|---|---|---|---|
wpel_visitor_id | localStorage | Unique anonymous identifier for each visitor | Persistent |
wpel_session_id | sessionStorage | Groups events (pageviews, errors) within one browser tab session | Until tab closes |
Is Consent Required?
This depends on applicable law:
- GDPR / ePrivacy Directive (EU):
localStorageused for analytics or behavioral tracking (session recordings, pageview analytics) typically requires prior informed consent. Error tracking for purely technical/security purposes may fall under "strictly necessary" depending on the scope. - CCPA (California, USA): Does not require opt-in consent but requires disclosure in the Privacy Policy and support for opt-out of "sale" of personal information.
- UK PECR: Similar to EU ePrivacy Directive.
Client Obligation: If session recording or pageview analytics is enabled, you must obtain visitor consent via a cookie/tracking consent banner before the Plugin initializes. You are solely responsible for this — the Platform does not manage consent on your behalf.
4. Third-Party Services Triggered by the Plugin
Depending on Client configuration, the Plugin sends data to:
| Service | Triggered By | Data Sent |
|---|---|---|
StorePilot Platform API (api.store-pilot.net) | All features | Errors, recordings, pageviews, leads |
| Client's own Amazon S3 (optional) | Session recordings | Compressed recording segment files |
No advertising networks, social media pixels, or retargeting platforms are embedded by the Plugin.
5. Implementing Consent on Your Website
To comply with GDPR/ePrivacy requirements, you should integrate the Plugin's initialization with your cookie consent solution.
Example using a consent callback:
// In your cookie consent tool's "accept analytics" callback:
window.StorePilot_CONSENT = true;
// The Plugin will check window.StorePilot_CONSENT before starting recording
// Configure this in: Dashboard → Sites → Settings → Privacy
Alternatively, you can conditionally enqueue the Plugin's JS only after consent is granted using WordPress's wp_enqueue_scripts hook based on a cookie set by your consent banner.
This approach can be configured in the Plugin settings under Settings → Privacy → Require consent before tracking.
6. How to Opt Out
For visitors of Client websites:
Contact the website owner. As the Data Controller, the website owner is responsible for honoring opt-out and erasure requests. They can use the Platform's right-to-erasure endpoint to delete your data.
For Clients (dashboard users):
The dashboard uses only strictly necessary authentication cookies. These cannot be disabled without breaking login functionality. You may delete your account to remove all associated data.
7. Changes to This Policy
We may update this Cookie Policy at any time. Changes will be reflected on this page with an updated date.
8. Contact
Questions about cookies: contact@store-pilot.net