1. At a glance
| Area | Summary |
|---|---|
| Hosting | Amazon Web Services (AWS), London region, across two availability zones |
| Encryption | TLS 1.2 or higher in transit, AES-256 at rest, backups included |
| Sign-in | Passkeys, two-factor authentication and backup codes for dashboard accounts |
| Backups | Daily, with point-in-time recovery for the last 7 days |
| Card payments | Taken on a PCI DSS Level 1 certified payment page |
| Data protection | Registered with the ICO, reference ZC160169 |
2. Hosting
The platform runs on Amazon Web Services in the London region (eu-west-2), across two availability zones. The production database, file storage and backups are all held in London.
Our application servers run as containers behind load balancers. The production database runs with a standby in a second availability zone, which takes over automatically if the first fails.
A small number of supporting services process limited data outside the United Kingdom. Each one is named, with its purpose and location, on our Sub-processors page, and section 11 of our Data Processing Addendum sets out the safeguards that apply.
3. Encryption
- In transit: all traffic to the platform and to every storefront is served over HTTPS, using TLS 1.2 or higher. A custom domain gets its own certificate automatically.
- At rest: the production database, its backups, the cache and file storage are encrypted at rest with AES-256.
- Passwords and secrets: passwords are hashed with bcrypt and never stored in readable form. Two-factor secrets, and the credentials you give us for couriers, manual payment methods and supplier stock feeds, are additionally encrypted with AES-256-GCM.
4. Signing in and access
- Dashboard accounts: passkeys, two-factor authentication with an authenticator app, and one-time backup codes. Repeated failed sign-ins from one source are limited, and every failed sign-in is logged.
- Roles: each person signs in with their own account and a role that limits what they can see and change. Every request is checked against the store or supplier account it belongs to.
- Activity log: changes to orders, products, prices, customers, settings and team members are recorded with who made them and when. Store activity is kept for 180 days, and user, role, permission and security events for two years.
- Our own staff: access to production systems is limited to the engineers who need it. Console sign-in to the hosting account requires multi-factor authentication, and every action in that account is recorded in an audit trail. When our support team opens a store to help, that access is marked in the store’s activity log.
See the sign-in and team controls in the product on our security features page.
5. Network protection and monitoring
The production database cannot be reached from the public internet. A web application firewall rate-limits traffic in front of the application, AWS Shield Standard protects against network-level attacks, and AWS GuardDuty watches the hosting account for threats.
Alarms on error rates, response times, server health, database load and unusual traffic reach our engineering team in real time, and application errors are tracked as they happen. Service status is published at status.orbitcommerce.net.
6. Backups and recovery
The production database is backed up automatically every day, and its transaction logs are captured continuously, so it can be restored to any point in the last 7 days. An extra snapshot is taken before every production release. Backups are encrypted and held in London.
A release that fails its health checks is rolled back automatically. Our availability targets are set out in the Service Level Agreement.
7. How we build and release
Every change to the platform is reviewed by a second engineer and has to pass automated tests before it can be released. Dependencies are checked for known vulnerabilities, and every change is scanned for secrets. Credentials are held in a secrets manager, never in code, and production is kept separate from our test environments.
8. Card payments
Orbit Payments takes card details on a PCI DSS Level 1 certified payment page provided by Stripe. Card numbers never reach our servers or your store’s database, so stores that take cards this way normally fall under the lightest PCI self-assessment.
9. Data protection
Orbit Commerce is the trading name of Orbit Technologies Limited, company number 07259336. We are registered with the Information Commissioner’s Office, reference ZC160169.
For the personal data in a store, such as its customers and their orders, the store is the controller and we are its processor. The Data Processing Addendum is the contract that covers this, and it forms part of our Terms of Service.
Our Sub-processors page lists every provider that handles personal data for us, with what it does and where. Our Privacy Policy sets out what we keep and for how long.
Requests from individuals to see or erase their data are handled through the store that holds it, with our help where it is needed.
If we become aware of a personal data breach affecting a store’s data, we tell that store without undue delay, and in any event within 72 hours, as section 9 of the Data Processing Addendum sets out.
10. Questions and reporting a concern
If your IT or compliance team needs something that is not covered here, or you want to report a security concern, email support@orbitcommerce.net. We answer security questionnaires on request.