Security at StorePilot
Last updated: September 16, 2026 · Questions: security@storepilothq.com
StorePilot connects to the systems that run your business, so security isn't a feature — it's the product. We designed it around two principles: read only what we need, and act only within the permissions and approvals you provide.
Information Security & Privacy Policy. Our formal, versioned policy is available as a document: Download the policy (PDF) — Version 1.0, effective July 28, 2026.
Controls & approvals
Consequential actions are approval-controlled. You can approve individual actions or explicitly enable supported recurring workflows within their rules and limits. Automation is not enabled simply by connecting a store. Workflow controls let you inspect activity and revoke recurring permission; actions and approval decisions are recorded for review.
Data protection
- Encryption in transit: all traffic uses TLS 1.2+.
- Encryption at rest: data and backups are encrypted with AES-256.
- Token vault: the OAuth tokens that connect your stores are held in a dedicated, encrypted secrets store — never in plaintext configuration or source control.
- Buyer-data minimization: supported operations may read buyer information and retain bounded conversation snapshots or operational records. Sensitive outbound message text and recipients are redacted from action audit records. See our Privacy Policy and deletion instructions.
- Retention & deletion: we keep only what's needed to operate the service, and honor deletion requests. Disconnect a store and its access is revoked.
Access & authorization
- Least privilege: each marketplace is authorized with the minimum scopes required — read-only wherever possible.
- You grant, you revoke: connect supported channels through their authorization or credential setup. Some workflows also use a signed-in browser through StorePilot Helper. You can disconnect connections and revoke their platform permissions.
- Tenant isolation: every customer's data and credentials are isolated per tenant.
- Source-aware reporting: live reads, saved reports, and document retrieval serve different purposes. Review source timestamps, coverage, and missing-data warnings for each report.
Operational security
- Approved account access: new customer emails require approval. Account setup and recovery verify an emailed code; customers sign in with a password. Passwords are stored as salted scrypt hashes. Administrative access is role-restricted and separate from customer access.
- Application and access logs retained for review of abnormal activity.
- A documented incident-response plan with defined roles, reviewed every six months: on a suspected compromise we revoke affected tokens, rotate keys, and notify affected customers and the impacted marketplaces within 24 hours of detection.
- Regular dependency and vulnerability review.
Sub-processors
Core service providers include the following. Model routing depends on deployment configuration; contact us for the provider and data-processing details applicable to your workspace.
| Provider | Purpose |
|---|---|
| Anthropic | Default AI model provider |
| OpenAI | Optional AI model provider when configured for the deployment |
| Render | Hosted application and database services |
| Resend | Transactional account and verification email |
Responsible disclosure
Found a vulnerability? We want to hear from you. Email security@storepilothq.com with details and we'll respond promptly. Please give us reasonable time to remediate before public disclosure.
A Data Processing Agreement (DPA) is available to customers on request. Enterprise customers can request our security documentation during onboarding.