A chat widget runs on every storefront page, in every shopper's browser. Anything it ships to the browser can be read, copied and replayed by anyone who opens DevTools. So the first security question for a Magento AI assistant is not about the model. It is about what the widget can do on its own, and what the backend refuses to trust.
This post is a short buyer checklist, with the answers Claspwell gives for its Magento 2 / Hyvä assistant. Every answer below is the same claim we publish on our security page.
1. Does any secret ship to the browser?
Look at the page source and the network tab. If you can find an OpenAI key, a Magento integration token or an admin credential, the widget is a liability: whoever copies it can run up your bill or read your store data.
In Claspwell, the storefront only uses a public store key to start a session. The public key is not a secret and is not enough to do anything alone. OpenAI keys never ship in the browser, and secrets are never hardcoded or logged.
2. What stops someone reusing your store key on another site?
A public key is public by design, so the backend must check where requests come from. Claspwell issues session tokens only after origin validation, and the API uses CORS allow-lists for registered storefront origins. A copied key on an unregistered domain does not get a session.
3. Who decides which store a chat belongs to?
Multi-store Magento setups make this matter. If the browser can send store_id=2 and the server believes it, one store's catalog or chat history can leak into another.
Claspwell session tokens carry a verified store_id. Queries and chat history are scoped to that tenant, never taken from browser-supplied store identifiers alone. Each store or isolated store view is its own tenant.
4. What happens when a bot hammers the widget?
Every public chat endpoint gets scripted traffic sooner or later. Without limits, that traffic turns into model costs and slow answers for real shoppers. Claspwell applies rate limiting at three layers: per IP, per session and per store.
5. Where do your Magento credentials live?
The assistant needs catalog access, so somewhere a credential exists. It should never be in the storefront, and on the backend it should be encrypted. Claspwell stores OAuth and integration credentials encrypted at rest.
6. What does the model actually see?
Ask what personal data goes into each model call. Claspwell sends the model the question text, not unnecessary personal profiles. Visitor IPs are stored as hashes, conversations have a retention window (default target: 90 days), and there are deletion endpoints.
7. Which certifications does the vendor claim, and can they prove it?
A badge without an audit report is marketing. Claspwell does not claim SOC 2 or ISO certification. We publish isolation, encryption and retention details instead, so your team can check them against the integration.
A quick test you can run today
- Open your storefront with DevTools and search the loaded scripts for "sk-", "Bearer" and "token".
- Copy the widget snippet to a test domain and see whether it still gets answers.
- Change any store identifier in a request and check whether the answers change.
- Send a burst of messages and see whether anything pushes back.
If any of those tests surprises you, the widget is trusting the browser too much.
Next step
Claspwell is a catalog-aware AI sales assistant for Magento 2 and Hyvä, installed with you in typically 3 days to 1 week once scope and access are ready. Read the security details, see how the Magento 2 AI chatbot works, or request an integration.