How this is kept safe

Shopify tokens

• The access token for your store stays on the server. It is never sent to the browser and never appears in a URL.
• Tokens are refreshed automatically through Shopify's token exchange, and a call that comes back unauthorised is retried once with a fresh token rather than failing quietly.
• Uninstalling revokes Shopify access. Aiders processes the uninstall notification to disable the store; webhook delivery and running tasks are handled separately.
• Token refresh and authentication failures are recorded for investigation. Alert delivery depends on the configured monitoring connections.

Tenant isolation

Store records are scoped to a tenant. Access requires an authenticated store membership or an authorized platform-support role. Shared account and platform records have separate access controls.

The application enforces that scoping, and row level security is switched on in the database for the tables the dashboard reads directly.

The review gate on knowledge

The agent can only quote from a knowledge base that belongs to your store. Anything pulled in from your site or your product catalogue lands in a review queue as pending, and a pending entry is never embedded and never retrievable. A person publishes it or rejects it.

A rejected entry is kept as rejected rather than deleted, so the next crawl cannot propose the same thing again.

Spending controls

The controls that stop an agent from being expensive are in the code, not in a prompt. A prompt can be argued with.

• A refund ladder. A full refund is refused until the cheaper rungs have been walked first.
• A cash ceiling per store. Above it a refund is never paid out automatically, it queues for a person.
• No second payout on the same order, and no extra money to a customer with a recent chargeback.
• Sandbox scenarios use separate test records. Explicitly authorized playground tests against real Shopify orders can perform real actions; they must not be treated as a no-effects sandbox.

Who can get in

The owner is currently the sole production operator and has confirmed multi-factor authentication on Shopify, GitHub, Cloudflare, Supabase and the operational email account. Service credentials are restricted to the backend.

What we do not claim

We are pre-launch and we would rather be accurate than impressive. We hold no SOC 2 report and no ISO 27001 certificate. We have not commissioned a penetration test. We do not promise an uptime figure and we do not claim your data stays inside the EU, because some of our providers are in the United States.

When any of that changes it will say so here, with the date it changed.

Reporting a vulnerability

Email support@aiders.app with what you found and how you found it. A person reads it and answers within one business day.

Please do not test against a live merchant's store or against data that is not yours. We will not take legal action over research done in good faith and reported to us before it is published. There is no bounty programme yet, and we will say so here when there is.