Trust Center
Everything your security team will ask, in one place
StoreOnCall watches live stores, so it is built to be safe to install and easy to review. Here is how it works, what it holds, and the documents your legal and security teams need.
The plugin and app can only read. Nothing is ever sent back to your store.
Counts and statuses only. Reports that look personal are refused.
Every connection uses HTTPS, through Cloudflare.
Store keys, API keys and sign-in links are stored one-way and shown once.
Google or Microsoft sign-in, and you can require it for the whole team.
Limit the dashboard and API to your office addresses.
Every sign-in and change, downloadable as a spreadsheet.
The database is backed up every day, on top of the host's own backups.
Data flow
What crosses from your store, and what never does
Documents
Policies and legal documents
Security reviews
Straight answers to common questions
What can StoreOnCall change in our store?
Nothing. The Magento plugin only reads and sends counts out; it accepts no commands. The BigCommerce app has read-only access to orders and store information. The checkout test never pays and deletes its cart.
What data leaves our store?
Counts and statuses: orders and payment outcomes per hour, background job, index, queue and cache status, unsent order email counts, extension versions and which setting paths changed (never their values). Never names, emails, addresses, phone numbers, IP addresses or payment details. Your developer can run bin/magento storeoncall:preview to see the exact report before connecting.
Where is our data kept?
On StoreOnCall's server, with the hosting company named on the Subprocessors page. The database is backed up daily. Raw plugin reports are kept for 3 days; hourly totals and incidents are kept so the dashboard and reports work.
Can we export or delete everything?
Yes. Owners can download all account data as a file and close the account from the Security page in the dashboard.
Do you have SOC 2 or ISO 27001?
Not yet. StoreOnCall is new, and we would rather say so. We will answer your security questionnaire in full and walk your team through how the product is built. Ask for a security review call.
Who do we contact about a vulnerability?
Email [email protected] with "Security" in the subject. Our security.txt has the details.
Need a security review call?
We will walk your team through the design and answer your questionnaire.