Agents get exactly the access they’re given

Who is asking

• Every agent identifies itself with an HTTPS address it controls. The store fetches its metadata and public keys from there, and checks the signature on every request to start or renew a Session.
• Session tokens are bound to a key the agent holds (DPoP). A copied token doesn’t work without that key, and each proof is accepted once.
• Tokens, codes and assertions are stored only as hashes. An agent’s per-store user ID is never stored in the clear.
• Fetching an agent’s documents refuses private and local network addresses, caps the size and follows a limited number of redirects.

What a customer agrees to

• Account access needs the customer’s approval, given on the store’s own sign-in page. The page names the agent and the domain it publishes from, and lists what it is asking for in plain words.
• The agent never sees the customer’s password.
• Access lasts 90 days. The customer can end it at any time from My Account, and gets an email whenever a new agent connects.
• Changing the account’s password or role disconnects every agent at once.
• Administrator and shop manager accounts can never be connected. That is checked at sign-in and again on every request.

What an agent can’t do

• Pay. The customer checks out on the store.
• Use a Session token to reach WordPress or WooCommerce’s own APIs. Tokens authenticate Agent Adapt’s endpoints only.
• Read another customer’s order. A missing order and someone else’s get the same answer.
• From its own browser: open the dashboard or the login page, change account details or payment methods, or check out.
• In Pro, change anything without a proposal the customer can read first. Refunds and address changes need the customer’s approval of that exact version.

What the store controls

• Block any agent. It is refused from its next request, everywhere.
• With Pro: switch actions off, cap an agent’s access, or accept only agents you approve. Policy can only narrow what agents may do.

Data

• Agent Adapt sends no data about your store or your customers to us, or to any analytics or advertising service.
• It records what agents do in your own database, for your own reports: the event, the agent, the time, and the product or order involved. Events are deleted after 90 days by default.
• It never records tokens, proofs, passwords or the contents of conversations.
• The only outside requests it makes are to the agents themselves, to check who they are. See Privacy.

Reporting a problem

If you think you’ve found a security issue in Agent Adapt, email [email protected]. Please don’t share it publicly until it’s fixed. We read every report.