Security

How we connect to your Amazon account

• OAuth only, never your password. You authorize AMZ Vault through Amazon's own Login with Amazon flow, on Amazon's pages. We never see or store your Seller Central password.
• Least privilege. We request only the API scopes the platform uses - advertising and selling-partner data. Nothing broader.
• Revocable by you, at any time. You can disconnect from inside AMZ Vault or revoke the authorization directly in Seller Central. Either one cuts our access immediately.

How your data is protected

• Encrypted in transit. All traffic to AMZ Vault is served over HTTPS (TLS).
• Credentials encrypted at rest. Amazon refresh tokens are stored using authenticated symmetric encryption (Fernet), with the encryption key held separately from the database. Tokens are decrypted only in memory, at the moment an API call needs them.
• Passwords hashed, never stored. Account passwords are salted and hashed with an industry-standard algorithm. Sessions use secure, HTTP-only cookies.
• Encrypted storage. The database runs on managed infrastructure that encrypts storage at rest.
• Rate limiting on authentication and API surfaces to resist brute-force and abuse.

Who can see your data

• Strict tenant isolation. Every query in the platform is scoped to your account. Your data is never visible to another customer, and the advertising profile to seller account link requires an exact identity match - never a guess.
• Team access is explicit. You grant teammates access per account, and read-only stays read-only - a read-only teammate cannot stage, approve, or push any change.
• Support access is consent-first. Our support staff cannot open your account unless you grant it - a toggle on the Feedback & Support page (or through the AI connection). The grant is read-only, expires automatically after 7 days, and you can revoke it early at any time.
• The live demo contains zero real seller data. It runs on synthetic data for a fictitious brand - generated, not anonymized.

The approval gate

Every change the platform proposes - from an automation rule, a dashboard workflow, or the AI connection - is staged as a reviewable diff. You see exactly what would change, on which campaign or product, before anything happens. Nothing reaches Amazon until you confirm it, and staged changes you don't want are cancelled with one click. Automation rules only ever act on the campaigns you explicitly assign to them.

Automation rules are approved once, as a rule. When you create one you choose how it runs: queued for your approval every time, AI-reviewed with low-confidence cases escalated to you, analysis-only, or applied automatically on its schedule - because you approved that behaviour when you created the rule. Every change a rule makes is logged, and you can switch it back to manual or off at any time.

Every applied change is logged: what changed, what the value was before, where the change came from, and when. You can trace any number on your account back to the action that produced it.

Amazon's AI Agent Policy, in practice

Amazon's AI Agent Policy (effective March 2026) sets rules for automated systems that touch seller accounts: agents must identify themselves, never imitate humans, and honor Amazon's controls on agent access. AMZ Vault's AI connection meets that bar and adds a stricter standard of our own - human accountability:

• Human in the loop, enforced by architecture. No change the AI proposes reaches Amazon without a human approving it. The AI's write tools can only stage changes; the apply step is a separate, explicit confirmation that you make, and the AI cannot do both.
• The AI can never grant itself unsupervised execution. Automation rules have modes, including one that applies changes automatically once you've approved the rule itself - but the AI connection cannot create an auto-applying rule or switch one to automatic. Granting a rule that autonomy is a deliberate action you take in the app.
• Authenticated and scoped. The AI connection uses its own OAuth authorization (with PKCE), tied to your user account and your permissions. It can never see or do more than you can.
• Auditable. Every tool call that stages a change, and every confirmation that applies one, is recorded in the same change log as the rest of the platform.
• Stoppable. Disconnect the AI connector, cancel pending staged changes, or revoke the Amazon authorization - each takes effect immediately.
• We do not train AI models on your Amazon data. The AI works from your data to answer your questions; it does not learn from it.

The full tool inventory - every read and write the AI can perform - is public on the docs page. Of all of them, exactly one can change your Amazon account - and it won't run until you've been shown, in your own words, what you're approving.

Your data, your call

Ask us to delete your data, export it, or both. We confirm receipt of deletion and export requests within 2 business days and complete them within 30 days. The details are in our Privacy Policy, including the Amazon Data Addendum.

Found something?

If you believe you've found a security issue in AMZ Vault, email support@amz-vault.com and put “Security” in the subject line. A real person reads it, and reports like this go to the front of the queue.