HelpSecurity and privacy
Security and privacy
Where your apps and data live, how builds and apps are kept apart, how secrets, tokens and payments are protected, and what Orbits keeps about your visitors.
Where your data lives
Orbits runs in one region: Abuja, Nigeria (abj-1). Your builds, your running apps, your static sites, their logs and your team's data are all kept there. There is no other region to choose.
Your code is kept apart
Orbits treats every customer's code, build steps included, as untrusted:
- Builds run isolated. A build runs in a sandbox of its own, as an unprivileged user, with no access to Orbits' credentials and no way to reach Orbits' own systems. It can reach the internet, to download packages.
- Apps run isolated too. A running app can reach the internet (to call your database or another API), but not Orbits' own systems.
- What builds leave behind is checked. Cached files coming back from storage are only unpacked as plain files and folders, with their paths and sizes checked.
- The workflows endpoint is off the internet.
/.well-known/orbits/workflowsis blocked on every address, and each call to it carries a per-deployment key. See workflows.
Secrets
- Environment variable values are encrypted before they're stored, with a key kept apart from the data. A variable marked sensitive is write-only: no screen, API call or
orbits env pullever returns it. Revealing a readable one is a line in the activity feed, which names the key, never the value. See environment variables. - Credentials Orbits holds for you are encrypted the same way: a GitLab or Bitbucket connection, a Slack connection, a Microsoft Teams workflow address, webhook signing secrets, your two-factor secret.
- When Orbits clones your repository from GitHub, it uses a short-lived credential limited to that one repository, with read access only.
- Nothing secret is written to logs by Orbits. What your own app prints is kept as printed, so don't print secrets.
Tokens and passwords
Orbits signs you in without passwords: by a sign-in link sent to your email, or with GitHub, GitLab or Bitbucket.
- Sessions, sign-in links, API tokens, invite links and recovery codes are stored only as hashes. Orbits can check one, but can't show it again or hand it to anyone. That's why an API token and your recovery codes are shown once.
- Two-factor with an authenticator app, and ten one-time recovery codes.
- Team security rules: owners and admins can require two-factor, limit sign-in methods, sign people out after a set time and choose who can invite.
- API tokens reach one team, can be limited to one project and to reading, expire if you choose, and can never manage tokens, members, security rules or billing.
- Someone outside a team gets "not found" for anything of that team's, so a team's projects and names aren't given away.
Payments
You pay for Pro on Flutterwave's hosted page. Card and bank details are typed there only: Orbits never sees or stores a card number. It keeps the card's brand, last four digits and expiry, and a token from Flutterwave for renewals. A payment counts only once Orbits has checked it with Flutterwave for the right amount. See paying for Pro.
Invoices hold the payer's email address and are kept for good, as the record of money taken.
Previews
Production is public. Previews can be protected, from the project's settings:
- With a password. Visitors see a password page; a right password is remembered for 12 hours, and changing the password asks everyone again.
- Team members only. Visitors are sent to sign in to Orbits, and only members of the project's team get through.
Protection is checked on every request to a preview. See previews.
Your visitors
Runtime logs keep what you need to debug, not more: query strings are never stored, visitors' IP addresses are masked, cookies and authorization headers are never read, and only a few request headers are kept. Logs are deleted after 7 days. See runtime logs.
Analytics and Speed Insights use no cookies and store no IP addresses or browser strings. A visitor is a hash that changes every day, so nobody can be followed from one day to the next or across projects. See Analytics.
Feature flags report which ids were checked as the first 16 characters of their SHA-256, never as they were. See feature flags.
What Orbits sends out
- Webhooks (alerts and integrations) go only to
httpsaddresses on the public internet, don't follow redirects, and are signed with your secret, so you can check they came from Orbits. See integrations. - Slack gets permission to post and to list channels. It can't read your messages.
- Email goes to the team's owners, admins and members for the events the team turned on. See notifications.
When you delete things
- Deleting a project deletes its deployments, environment variables and alerts.
- Deleting a team disconnects its Git providers first, then deletes its domains, projects, activity, members and invites. A Pro plan ends with it. See deleting a team.
- A deleted environment variable can be restored for 10 minutes, then it's gone.
Reporting a problem
If you think you've found a security problem, contact us through pantechdynamics.com/contact and say it's about security. See getting help.