How we handle access to your store
Giving an outside team access to your store is a real decision. Here is exactly what we ask for, what we never ask for, and how access ends.
What we commit to on every engagement
Least access first
We list the exact permissions we need in writing before you invite us, and start read-only wherever the platform allows it.
Our own staff accounts
You invite us as a staff or collaborator account. We never ask for your login, and we never share accounts.
No payment permissions
We never need billing, payouts, or payment settings, and we ask you to leave them off our accounts.
You add the secrets
We never ask you to email passwords or API keys. When a key is needed, you enter it yourself in the settings screen.
Approval before changes
Audits are read-only. Before any change, you get a written plan and we wait for your OK.
Changes you can undo
We take a backup or checkpoint before changing anything, and keep a written log of what we changed and when.
AI tools stay supervised
When we connect AI assistants to your store, writes are off by default and every write needs a person to approve it.
Your data stays yours
Customer data stays in your systems. We do not sell or share it, and we only export what the work needs, with your agreement.
Access ends with the work
At the end of an engagement we remove our accounts and send you a list of everything we had access to.
How access works on a typical engagement
You get our list
A short written list of the accounts and permissions the work needs, and why.
You invite us
Staff or collaborator invites from your side. You stay in control of every account.
We work read-only
The audit and planning happen without changing anything.
You approve changes
Each change comes with a written plan, a checkpoint first, and your sign-off.
We hand back the keys
Accounts removed, a written access list, and documentation that stays with you.
SOC 2 and ISO 27001 controls, already running
Controls in place
We run a security program built to the SOC 2 Trust Services Criteria and ISO 27001 Annex A across our own products and operations.
Evidence collection underway
We are collecting the evidence an independent auditor needs. We will post our SOC 2 report and ISO 27001 status here once the audits are complete.
Policies on request
Our information security policies are available under NDA. We also help other companies build the same program.
Security questions we get
Are you SOC 2 or ISO 27001 certified?
Not yet. Our SOC 2 and ISO 27001 controls are in place and we are collecting audit evidence. We will not claim either until an independent auditor has signed off.
Do you need my Shopify password?
No. You invite us as a staff or collaborator account with only the permissions we list. You can remove it at any time.
Will you have access to payments or payouts?
No. We never need billing, payout, or payment settings, and we ask you to leave them off our accounts.
Will you sign our NDA?
Yes. Send it with your first note and we will sign before we see anything private. We also have our own mutual NDA if you prefer.
What happens if a change breaks something?
We take a checkpoint before every change, so we restore it, tell you in writing what happened, and fix the cause before trying again.
Do AI tools get to change my store on their own?
No. Our AI setups are read-only by default, and any write action needs a person to approve it first.
Where is the work done?
Broke Hold is a US company based in New Jersey.
Tell us what you are working on
Send a short note and get a written answer within one business day, with a fixed price if there is work worth doing. No calls needed.