Dashboard

Security & Trust

What's actually protecting your store, in plain language.

Everything on this page is true today, not aspirational. If you're evaluating whether to trust this connector with your store, this is the page that should answer that.

Your Shopify credentials are never exposed

Your store's access token is encrypted before it's ever stored, and it's never sent to Claude, never visible to your team, and never appears in any log. When Claude needs to act on your store, the connector decrypts it internally, uses it for that one request, and nothing else ever sees it.

Nothing changes without your confirmation

Every action that would actually modify your store - a refund, a price change, an inventory adjustment - requires you to explicitly confirm it first. Claude describes exactly what it's about to do, in plain language, before anything happens. A confirmation can't be reused or replayed to trigger the same action twice, including under a network retry - this has been directly tested, not just assumed.

Every action is logged, to a real person

Because every team member has their own individual login (see Team Management), your Activity log can tell you exactly who did what, and when - not just "something happened." This is visible to you in your dashboard at any time.

Access is isolated per person and per store

If you remove someone from your team, their dashboard membership and future Claude authorization are revoked immediately: their Hydra login and consent sessions are deleted, and their consent grants are marked revoked. Current connector access tokens are JWTs with a one-hour lifetime, so a connection that already has a token may keep working until that token expires; treat that as a known revocation window, not a mid-session hard kill.

Your store's data is also fully isolated from any other business using this same connector - there is no scenario in which another company's data could appear in your account, or yours in theirs.

This app is Shopify-approved for protected customer data

Shopify requires a formal approval process before any app can access order and customer information, given how sensitive that data is. This connector has completed that review and is approved.

Resilience

If Shopify itself is having issues, the connector is designed so that a problem affecting one store doesn't affect any other store using the connector - each store's connection is fully isolated from every other store's, including under heavy load or failure conditions.

Who else is involved

We use a small number of specialized services to run this product, each handling a specific, limited part of the system:

ServiceWhat it's used for
SupabaseYour account login and core data storage
ShopifyYour store's commerce data
Ory HydraManaging Claude's access permissions
ResendSending account and invite emails
UpstashRate-limiting protection
SentryError monitoring, so issues get caught quickly

None of these services have access to your Shopify credentials directly - that encryption and access boundary is enforced by the connector itself, not delegated to any of them.

Questions

If your team's security review needs more detail than this page covers, reach out - we're glad to answer specific questions directly.

Was this page helpful?

Your feedback helps keep this documentation accurate and useful.

On this page