Per-tenant isolation
Every merchant’s data lives in its own isolated Postgres schema. One store can never reach another’s conversations, configuration, or knowledge base.

Security isn’t a feature we bolted on — it’s how ShopSifu is built. Merchant and shopper data is isolated, encrypted, and access-controlled from the ground up.
Every merchant’s data lives in its own isolated Postgres schema. One store can never reach another’s conversations, configuration, or knowledge base.
Shopify OAuth tokens are encrypted at rest with AES-256. All traffic is served over HTTPS (TLS 1.2/1.3), and data in transit between our services is encrypted.
Access to production systems is restricted to a limited number of authorized personnel, and sensitive tenant lifecycle events are recorded in an audit log.
Conversation content is surfaced to our team only through a linked support ticket — never browsed at will. Your shoppers’ chats aren’t an open book.
We never sell your data, and we never use your conversations or catalog to train third-party models. It’s yours, used only to serve your store.
Chat widget requests are authenticated with a per-merchant publishable key and validated against your store’s origin before anything is answered.
Trusted sub-processors
We rely on a small set of vetted providers to run ShopSifu. Each handles only what its role requires.
Deletion on request. We honor Shopify’s data-erasure webhooks — when a shop or a customer requests redaction, the relevant data is deleted. Because each merchant lives in its own schema, removing a store removes its data wholesale.
Found a vulnerability? We investigate every report and work with you to resolve confirmed issues promptly. Reach the security team directly — please don’t disclose publicly until we’ve had a chance to fix it.
Questions about how we handle your data? We’re happy to walk you through it.
See also our Privacy Policy for full detail on data handling.