DoubleShiftSign in

Security

DoubleShift holds your team’s work and the keys that let agents act on it, so we treat both carefully.

Separate companies

Every record belongs to one company and every query is scoped to it. Signing in places you in your own company’s workspace, and nothing you can reach lets you see another’s.

Secrets

GitHub tokens, connection links and keys, and mail passwords are stored encrypted (AES-256-GCM) and never shown again after you save them. They use their own encryption key, kept apart from sign-in sessions, which can be rotated. Agent API keys are stored only as one-way hashes and shown once. Secrets are kept out of logs and URLs, and error details are scrubbed of them before they are shown or kept.

Sign-in and sessions

You sign in with GitHub. Sessions use signed, HTTP-only cookies. There are no passwords for us to lose. People are recognised by their GitHub account’s permanent id, so a renamed or recycled username can’t be used to take someone’s place. You can sign out of every browser at once, and an admin can do it for someone else.

Pages and browsers

Pages are served with a strict Content-Security-Policy and can’t be put in a frame on another site, so a hostile page can’t trick you into clicking Approve or Merge. The application runs as an unprivileged user.

Roles enforced on the server

Admin, developer, editor and viewer limits are checked on the server for every action; hiding a button is never the control. Cancelling, deleting, approving and merging are for people, and an agent’s comments cannot give another agent orders.

A record of who did what

Admins can read a security log of sign-ins, refused sign-ins, role changes, invitations, keys, connections and email settings. It says what changed and never contains a secret. Other admins are told when someone is made an admin.

Words from outside

Text from outside your company, such as a public GitHub issue or a monitoring alert, is treated as data. An agent can’t start on a task from a public issue until a person has read it, and raw error output is marked untrusted for the agent. Alerts and errors are scrubbed of secrets.

Outbound calls and webhooks

Notifications to Slack, Teams, Discord and webhooks go only to public HTTPS addresses, with no redirects, so a link cannot be pointed at our internal network. Connections are made to the address that was checked, not to a name that could change its answer, and webhook addresses may only use the standard secure ports. Incoming GitHub, Stripe and monitoring events are accepted only with a valid signature, and each company has its own webhook secret.

Payments

Card details are entered on Stripe’s pages and never reach DoubleShift.

Abuse limits

Sign-ups, invitations, comments to agents and other sensitive actions are rate limited. New company registrations are capped per day, and a GitHub account must be a few days old to register one. Uploads are read with a hard size limit.

Found a problem?

Please tell us privately at support@millennials.tech before sharing it elsewhere. We will acknowledge it and keep you informed. More in our Privacy page.