Charlie is designed with security-first principles. No customer PII, no payment data, minimal attack surface.
Data governance
Shopify-resident data (never accessed by Charlie)
- Customer PII (names, emails, addresses)
- Payment and billing information
- Order details and transaction history
- Product, variant, and inventory data
Charlie-resident data
Charlie stores only operational configuration:
- Location settings
- Safety stock rules
- Session tokens
- Job tracking
Charlie contains no PII, no customer data, no payment information.
Data ownership
| Aspect | Detail |
|---|
| Storage | All merchant rules reside in Shopify metafields |
| Ownership | 100% merchant-owned |
| Portability | No proprietary formats |
| Uninstall | All data persists in Shopify |
Security controls
| Control | Implementation |
|---|
| Data isolation | Complete separation between merchants, database queries filtered by shop |
| Encryption | At rest and in transit |
| Webhook verification | HMAC signature verification for all Shopify webhooks |
| Minimal permissions | Read-only access except for metafields |
| GDPR compliance | Automated handlers for deletion and export requests |
Certification status
Charlie does not currently hold SOC2 certification. Mitigating factors:
- No customer PII stored in Charlie systems
- No payment data processed or retained
- Cloudflare (infrastructure provider): SOC2 Type II certified
- Shopify (platform): SOC2 Type II certified
Risk summary
| Risk | Assessment |
|---|
| Data breach exposure | Minimal — no customer PII in Charlie systems |
| Payment data risk | None — all transactions remain within Shopify |
| Vendor lock-in | Low — merchant-owned metafields, no proprietary formats |
| IT burden | Zero — no integration, maintenance, or technical debt |
