Security and privacy

What the platform does today, and what we are not claiming.

Built into the product

Tenant and store isolation

Business data is scoped to a tenant and store from the verified request context. The server does not trust tenant or store ids sent in a request body, and isolation is covered by automated tests.

Roles and permissions

Owner, manager, staff, analyst and developer roles with per-module read and write abilities.

Scoped credentials for APIs and AI

API keys and MCP tokens carry explicit scopes, are stored as hashes, are shown once, and can be rotated or revoked.

Human approval for risky AI actions

MCP can only request product deletion. A person confirms it in the dashboard. Larger stock changes also need approval.

Audit trail

Consequential actions are recorded with the actor and source (dashboard, API, MCP or automation). Secrets are not logged.

Webhook and payment callbacks

Payment callbacks are signature-verified and rate limited.

What we do not claim

We do not currently claim SOC 2, ISO 27001, PCI or other certifications.
No payment gateway is live yet, so card data is not processed by the platform today.
MCP OAuth is planned; today MCP uses bearer tokens. Treat tokens as secrets.
When you connect a third-party assistant, data you allow it to read is processed under that provider's terms.

To report a vulnerability, use the contact form and choose the Security topic.