How we protect your data

#Separate rooms, separate keys

Your data is not in one big database. Each kind of data lives with the service that owns it, in its own database:

• customer details (names, emails, phones, addresses, notes) in a dedicated vault on its own server, with its own encryption keys, unreachable from the internet;
• orders encrypted with the orders service's own keys;
• payment credentials and carrier credentials encrypted, and only ever shown masked;
• analytics with no personal data at all.

If one part ever had a problem, the walls around the others still stand.

#Only the right people

• Everyone signs in through one account system, with two-factor sign-in available to all.
• Every action checks the person's role and permissions in your organization, on the server, every time.
• DashForDevs staff need two-factor sign-in, always, and their access to your organization is recorded.

#Everything recorded, nothing exposed

Every service keeps an append-only log where each entry is chained to the one before it, so a deleted or altered entry is detectable. It records who did what to which record and which fields, never the values themselves. You can see your organization's trail under Organization → Logs.

#On the wire

Every connection is encrypted (HTTPS only). Our public API sits behind a web application firewall that blocks known attacks and floods.

#What you can do

• turn on two-factor sign-in, and require it for your team;
• give each person the smallest role that fits their job;
• never share a secret API key; if one leaks, rotate it at once (Developers → API keys);
• review Organization → Logs now and then.