Draft. Not yet reviewed.
A plain summary of how your costing data is protected. It is a working draft and has not been reviewed. Please ask before relying on it.
Each organization's data lives in its own database schema rather than sharing tables with other customers, so one organization cannot read another's recipes or pricing.
Members hold roles that decide what they can see and change. Sign-in is protected by a challenge that blocks automated attempts, and sessions expire.
Traffic is encrypted in transit. Passwords are stored hashed, never in readable form.
If you believe you have found a security issue, contact us before disclosing it publicly and we will work with you on it.