Security and data
Amazon SP-API security: what we can touch, and what we never do.
VSENK connects to your Amazon accounts only through Amazon's official Selling Partner API (SP-API) and Ads API, with permissions you grant and can revoke. We never scrape, never automate Seller Central in a browser and never ask for your password. This page explains exactly what we access, why, and how to switch us off.
- Official APIs only
- Read-only audit
- Stop switch
- NDA before data
Last reviewed
- Amazon SP-API Read Read · FBM tracking upload
- Amazon Ads API Read reports Read reports
- Shopify / Walmart Read Read · inventory levels
- QuickBooks / Xero Read or exports Draft entries only
- Warehouse or 3PL Viewer or exports Order push
- Supplier email None Follow-ups from your alias
Read-only everywhere. Nothing we do can change an order, a listing or your books.
The short version
Six rules we work by.
If one of these would be broken to finish a task, the task does not get done that way.
- 01
Official APIs only
Amazon SP-API and Ads API, and each platform's own API. No scraping, no browser automation of Seller Central, no shared logins.
- 02
Least privilege
Each workflow gets only the permissions it needs. Every permission is listed in your scope document before you grant it.
- 03
Read-only first
The audit runs on read-only access. Write access is added one action at a time, during a build, where a workflow needs it.
- 04
People approve money and listings
Purchase orders, refunds, listing changes and unusual journal entries always wait for a person.
- 05
Agents identify themselves and stop
Every action is logged under a named agent, and one switch stops every workflow.
- 06
NDA before data
We sign an NDA before we see anything, and work under a written data policy you can read.
Access, system by system
What we connect to, how, and how you cut us off.
This is the default. Your scope document lists the exact permissions for your accounts before you grant any of them.
| System | How we connect | During the audit | After a build | How to revoke |
|---|---|---|---|---|
| Amazon Seller Central | SP-API app you authorize | Read-only roles | Only the roles a workflow needs, such as FBM tracking upload | Manage Your Apps in Seller Central |
| Amazon Ads | Ads API, authorized by you | Read reports | Read reports. We do not manage campaigns | Remove the app from your Amazon account permissions |
| Shopify | App with scoped access | Read scopes | Inventory and fulfillment scopes where needed | Uninstall the app in Shopify admin |
| Walmart Marketplace | Marketplace API keys or delegated access | Read | Inventory updates where needed | Revoke the key or delegate in Seller Center |
| QuickBooks Online or Xero | App connection or bookkeeper exports | Read-only scopes where offered, otherwise exports | Draft journal entries for review | Disconnect the app in QuickBooks or Xero |
| Warehouse or 3PL | Portal API, viewer login or exports | Viewer or exports | Order push for FBM routing | Disable the user or key in the portal |
| ShipStation | API key | Read | Label purchase inside your shipping rules | Regenerate the API key |
| Slack or email | App in one channel, or a sending alias | Posts the daily alert | Posts alerts and approval requests | Remove the app or the alias |
Menu names change. If a revoke path above has moved, the platform's help center has the current one.
Agents and the stop switch
Every agent says who it is. One switch stops them all.
Amazon's agent policy, in force since 4 March 2026, expects automated tools to identify themselves and to stop when asked. We build every workflow that way.
- Every action is logged under a named agent, with the time and the API used.
- Our API requests carry our app's name, and messages our agents send say they are automated.
- Each workflow has its own switch, and one master switch stops everything.
- A stopped workflow holds its pending drafts and does nothing until you turn it back on.
Policy summaries: EcomCrew, Feb 2026 · SellerSprite.
- Replenishment + PO draftsDaily 06:00Running
- Settlements to QuickBooksOn each settlementRunning
- Ticket triage + reply draftsEvery 15 minRunning
Run logagent: vsenk-ops
Try it: stop one workflow, or all of them.
Human in the loop
Money and listings always wait for a person.
Automations do the routine work. People make the calls that cost money or touch your catalog.
See the full approval rules- Purchase orders
Drafted by the automation, sent only after you approve.
- Listings and prices
Any change waits for you, with the reason attached.
- Refunds, replacements and replies
Drafted with order context, sent by a person.
- Reimbursement cases
Evidence assembled automatically, filed by a person.
Data handling
What we keep, where, and for how long.
Set out in our written data policy, which we send before any access is granted.
- What we store
- Only the fields a workflow needs, such as SKUs, quantities, settlement lines and PO data. Buyer names and addresses only where a workflow cannot run without them, such as FBM routing.
- Buyer personal data
- Requested through Amazon's restricted data process and handled under Amazon's Data Protection Policy and Acceptable Use Policy for SP-API developers.
- Where it lives
- In a US region of our cloud provider.
- Encryption
- Encrypted in transit with TLS and at rest.
- Retention
- Kept only while a workflow needs it, and deleted at the end of the engagement or on request.
- AI models
- Your data is not used to train AI models.
People and process
- NDA signed before we see any data
- Named accounts for every team member, with multi-factor sign-in
- Only people assigned to your account can access your data
- Access removed the day someone leaves your account or our team
- Delivery team in Dhaka, Bangladesh. Calls in US business hours
If something goes wrong
- We pause the affected workflows with the stop switch.
- We tell you what happened and what was touched.
- Where Amazon data is involved, we report to Amazon as its Data Protection Policy requires.
- We fix the cause, write it up and only then turn the workflow back on, with your OK.
Certifications
We do not hold SOC 2 or ISO 27001 certification today, and we will not imply that we do. We answer security questionnaires and share our data policy and scope documents before access is granted.
Do you need my Seller Central password?
No. You authorize our app through Amazon's Selling Partner API, with the permissions listed in your scope document. We never ask for passwords and never log in to Seller Central through a browser.
Can we revoke your access?
Yes, at any time and without asking us. You can remove our app authorization in Seller Central under Manage Your Apps, and disconnect us from Shopify, Walmart, QuickBooks or Xero from their own settings.
Do you see buyer personal data?
Only where a workflow needs it, such as a ship-to address for FBM routing. That data is requested through Amazon's restricted data process and handled under Amazon's Data Protection Policy.
What happens if an automation goes wrong?
It stops. Every workflow has a stop switch, logs each action, and sends anything unusual to an analyst instead of acting on it. Money and listing changes never happen without an approval.
Are you SOC 2 certified?
No. We do not hold a third-party certification today. We share our written data policy, scope documents and security questionnaire answers before any access is granted.
Who on your team can access our data?
Only the named people assigned to your account, each with their own login. Access is removed when someone leaves your account or our team.
Read-only to start. Your call after that.
The Ops Leak Audit runs on read-only access under an NDA. You see every permission before you grant it, and you can revoke all of them at any time.
- Read-only access
- NDA before data
- US-hours calls