Security at ShopSavvy
What we do to protect your account and the data you get from us, stated as facts you can check. If you need something that is not here, email business@shopsavvy.com.
Last reviewed
Where data is hosted
- ShopSavvy's API, website and database run on DigitalOcean in its San Francisco region (sfo3), in the United States.
- We do not offer EU or other regional data residency. The services listed under Sub-processors below run on their own infrastructure.
Encryption in transit
- shopsavvy.com and api.shopsavvy.com accept TLS 1.2 and TLS 1.3 and refuse TLS 1.1 and older.
- Plain HTTP requests are redirected to HTTPS.
API keys
- Data API keys are bearer tokens sent in the Authorization header.
- Keys are stored as hashes, not in plain text, so we cannot read a key back after it is issued. A new key's secret is shown once.
- You can create, regenerate and revoke keys yourself in the developer dashboard. Regenerating a key stops the old secret working immediately.
- Each account is limited to 1,000 requests per rolling hour per account; requests over the limit get HTTP 429 with a Retry-After header.
Webhooks
- Every webhook delivery is signed: the X-ShopSavvy-Signature header carries a timestamp and an HMAC-SHA256 of the timestamp and body, computed with your webhook's secret.
- Deliveries are retried up to five attempts, and each event carries a stable id so you can ignore repeats.
- Webhooks created in the developer dashboard must use an HTTPS URL.
What we store about API customers
- Your account (email address and sign-in), your API keys (hashed) and your subscription status. Card details are held by our payment processor, not by ShopSavvy.
- A log row per API request: key id, endpoint, method, response code, error code, credits used, timestamp, request id, IP address and user agent.
- Request log rows are deleted after about 13 months. Our web servers also keep standard access logs, which include request URLs.
Deleting your account
- Delete Account in your account settings erases the account in one step: the account record, API keys, request logs, webhooks, Business monitoring data and the other records tied to the account are deleted together in one database transaction. Data licensing purchase records are kept for tax and accounting.
- The same step cancels any active subscription, deletes your customer record at our payment processor (which keeps the payment records it is legally required to keep) and deletes your sign-in account.
- You can also ask by email at support@shopsavvy.com. We run the same deletion and reply when it is done.
- Database backups are complete copies. We keep the three most recent daily backups and one from the start of the month, so deleted data leaves the backups as newer ones replace them.
Licensed and API data contain no personal data
- Data API responses and Data Licensing exports contain product and offer data only: identifiers, product attributes, retailer, price, availability, condition and timestamps.
- They never contain user identifiers, names, contact details, location or behavioural data such as searches, scans or purchases. Licensed exports are produced from a fixed column whitelist.
Backups and recovery
- The production database is backed up daily to off-site object storage. Each backup is a complete, standalone copy, and older copies are only removed after a newer one has been verified as fully uploaded.
- Backups run every day, so a restore normally loses no more than the last day of changes.
- A documented rebuild of the production server from backups was tested end to end on a fresh server on 2026-07-30.
Sub-processors
- DigitalOcean: hosting, database and backup storage (US).
- Stripe: payments and billing.
- Google Firebase: account sign-in.
- Amazon Web Services (Simple Email Service): transactional email.
- Google Analytics: website analytics.
- Google Workspace: our support@ and business@ email, so anything you send us by email.
- Slack: our internal team messaging. Sales inquiries from our contact forms (name, email, company and message), website support chat messages and internal account alerts that name a customer account by email are posted there so a person follows up.
- OpenAI: when you import a product list into ShopSavvy for Business, the header row and first five rows of the file (each cell cut to 100 characters) are sent to detect which column holds the product identifiers.
- This list covers vendors that process personal data about Data API, ShopSavvy for Business, Search API and data licensing customers and people who contact us. Product and price data is not personal data.
Certifications
- ShopSavvy does not hold SOC 2 or ISO 27001 certification.
- For security questionnaires or contract terms, email business@shopsavvy.com.
Support and contract terms
- Every Data API and ShopSavvy for Business plan gets a first response from the team within one business day (Monday to Friday, US time). Email support@shopsavvy.com, or business@shopsavvy.com for contract and security questions.
- Paid business products are governed by the ShopSavvy B2B Terms at shopsavvy.com/terms/api: the Common Paper Cloud Service Agreement (version 3.0) with Delaware law, liability capped at the fees paid in the prior 12 months, and confidentiality obligations on both sides.
Reporting a security issue
- Email business@shopsavvy.com with "Security" in the subject. Please include steps to reproduce, and give us reasonable time to fix the issue before disclosing it.
Related: Pricing · Privacy policy · Terms of use · B2B Terms · security.txt