Security
Store data is operationally sensitive.
SmokeOps uses layered access controls and audit evidence while being honest about the responsibilities shared by the platform, the store owner, and the hosting environment.
Application controls
Organizations and stores are tenant-scoped. Owners, managers, and employees receive different capabilities, and an owner can narrow access by store. Platform administration is separate from customer-store navigation.
Passwords are one-way hashed, sessions are revocable, repeated login failures are rate limited, and production platform administration requires a second authentication factor.
Data handling
POS uploads and generated reports are stored outside the public web directory. Customer contact fields can be encrypted with a deployment-specific key. Destructive and high-impact workflows record actor, reason, time, and affected records.
Production requirements
Production mode requires HTTPS, secure cookies, a strong PostgreSQL credential, an encryption key, protected maintenance jobs, and a separate demo-signing secret. The operator must also configure encrypted database backups, retention, monitoring, and restore testing with the chosen hosting provider.
No unsupported claims
SmokeOps does not currently claim PCI, SOC 2, HIPAA, or other third-party certification. POS exports should exclude payment-card secrets. Report a suspected security issue through the customer support path immediately.