Privacy Policy
Last updated: April 8, 2026
This Privacy Policy explains how StorePilot ("we", "us", "Platform") collects, uses, stores, and protects information when Clients use the Service, and what data the Plugin may collect about end-users on Client websites.
1. Who We Are
StorePilot is a SaaS analytics and monitoring platform. For the purposes of this Privacy Policy:
- We are the Data Processor — we process personal data on behalf of our Clients according to their instructions.
- The Client is the Data Controller — the website owner who installs our Plugin and sends data to our Platform.
- End-Users are visitors to the Client's website whose data may be collected by the Plugin.
2. Data Collected by the Platform
2.1 Account Data (Client)
When you register on the Platform, we collect:
| Data | Purpose |
|---|---|
| Email address | Account identification, notifications |
| Password (bcrypt hashed, never stored in plain text) | Authentication |
| Name (optional) | Dashboard display |
| Account creation timestamp | Internal records |
We do not store payment data directly — this is handled by our payment processor (if billing is active).
2.2 Site Configuration Data
When you add a WordPress site to the Platform, we store:
- Site name and domain
- API key (used to authenticate data from the Plugin)
- Storage configuration (S3 bucket credentials are stored encrypted)
- Notification settings (Slack webhook URL, Telegram token, SMTP settings — stored encrypted)
2.3 End-User Data Collected via the Plugin
The Plugin may collect the following data about visitors to the Client's website, depending on which features are activated:
| Category | Data Points | Feature |
|---|---|---|
| Technical | JavaScript errors, stack traces, error type | Error Tracking |
| Technical | PHP error messages, severity, file/line | Backend Error Tracking |
| Behavioral | Pages visited, time on page, session ID | Pageview Analytics |
| Behavioral | Mouse movements, clicks, scroll, keyboard input* | Session Recording |
| Identity | WordPress User ID (if logged in) | Error Tracking, Leads |
| Contact | Name, email, phone, delivery address | Lead Capture (WooCommerce) |
| E-commerce | Cart contents, cart total, order notes | Lead Capture |
| Network | IP address (used for geolocation, then may be stored) | All features |
| Device | User agent, browser, OS, screen size, language | Visitor Analytics |
| Location | Country code (derived from IP) | Visitor Analytics |
* Session Recording: Key press data is masked by default. The Plugin does not record passwords or payment card numbers. Clients are responsible for ensuring their session recording configuration is compliant with applicable law and their own Privacy Policy.
3. Legal Basis for Processing
We process data on behalf of our Clients (as Data Processor). The legal basis for processing end-user data is determined by the Client (Data Controller). Typically this will be:
- Legitimate interests — for error tracking and technical analytics;
- Consent — for session recordings, which require explicit cookie/tracking consent from the visitor;
- Contract performance — for lead data submitted through checkout forms.
4. Data Retention
| Data Type | Default Retention |
|---|---|
| JavaScript / PHP errors | Until manually deleted by Client |
| Session recordings | Until manually deleted or storage limit reached |
| Leads | Until manually deleted by Client |
| Pageviews | Until manually deleted by Client |
| Visitor profiles | Until manually deleted or erasure request processed |
| Account data | Until account deletion |
| Refresh tokens | 7 days (auto-expired and cleaned up daily) |
Clients may reduce retention periods or delete data at any time through the dashboard or API.
5. Data Storage & Security
- The Platform database is hosted on a dedicated server with restricted access.
- All data in transit is encrypted using TLS 1.2+.
- Session recording files are stored in S3 or on-server storage, depending on the Client's configuration.
- Sensitive credentials (S3 keys, SMTP passwords) are stored encrypted at rest.
- Access to the Platform database is restricted to production server infrastructure only — ports are not exposed to the public internet.
- Authentication uses JWT tokens with short expiry (15 minutes) and refresh token rotation.
6. Data Sharing
We do not sell, rent, or share end-user data with third parties for marketing purposes.
Data may be shared only in the following circumstances:
- With the Client — Clients have full access to data collected from their own websites.
- Storage providers — If the Client has configured Amazon S3, recording files are stored in the Client's own S3 bucket. We do not have standing access to third-party S3 buckets.
- Notification services — If the Client configures Slack, Telegram, or email notifications, event summaries are sent to those services according to the Client's settings.
- Legal obligations — If required by law, court order, or governmental authority.
7. Data Subject Rights (End-Users of Client Websites)
End-users of Client websites should direct privacy requests to the website owner (the Client), who is responsible for responding as Data Controller. The Platform provides tools to support:
- Right to Access — Clients can export visitor data from the dashboard.
- Right to Erasure — Clients can permanently delete all data for a specific visitor using
DELETE /api/v1/sites/:id/visitors/:id/data. This removes pageviews, recordings, leads, and anonymizes linked error records. - Right to Portability — Data can be exported via the dashboard API.
8. Cookies Used by the Platform Dashboard
The Platform dashboard (used by Clients, not end-users) uses:
| Cookie | Purpose | Duration |
|---|---|---|
wpel_access_token | Authentication JWT | 15 minutes |
wpel_refresh_token | Silent re-authentication | 7 days |
The Plugin installed on Client websites does not set cookies itself. It uses localStorage for the visitor ID and session ID. The Client is responsible for disclosing this in their cookie notice.
9. Changes to This Policy
We will post any changes to this Privacy Policy on this page and update the "Last updated" date. For material changes, we will send registered account holders an email notification.
10. Contact
Data Controller inquiries (Client accounts): contact@store-pilot.net
Data subject inquiries (end-users of Client websites): Contact the website owner directly.