Security
What we protect, and how
DataShift sits between your trading partners, your ERP and your carriers, so it holds credentials and documents that matter. This is what we do about that, in plain terms.
Credentials are encrypted field by field
The keys that connect DataShift to your ERP and your carrier accounts are encrypted with Google Cloud Key Management before they are stored, using keys we manage in the same cloud. Two-factor secrets are protected the same way.
Sign-in and access
- Sign in with Google or with an emailed link, and turn on two-factor authentication with an authenticator app and backup codes.
- Roles decide who can see and change what, from reading orders to editing mappings. You can create your own roles.
- Every request is checked against your business's workspace and the person's role before anything is returned.
A record of what happened
Changes to settings, access and documents are written to an audit log you can read, so you can answer “who changed that, and when” without asking us.
Where it runs
DataShift runs on Google Cloud in Sydney (australia-southeast1).
Payments
Card payments are taken by Stripe. Card numbers never pass through DataShift's servers.
The live demo is safe to click
The live demo runs on a fictional distributor's data, is read only, and each visitor's session is separate, so nothing you do in it changes what anyone else sees.
Questions
If your security team has a questionnaire, or you want to know something that isn't here, write to hello@datashift.com.au or tell us what you need. We will answer what we can and say plainly what we can't.