Skip to content

Security

How Git A protects your code.

Every repository is private: only the people you add can see it, not even the other members or admins of your organization. These are the facts of this release, stated exactly.

  1. 1Where your data is kept

    Your repositories, issues, activity, logs and build files stay in the region your organization chose, and the region cannot be changed later. Available now: India (Mumbai); more regions are coming. Your account details (name, email, sign-in IP addresses) and billing details are kept separately by Git A, today in India.

  2. 2Who runs it

    You choose who runs your organization: Git A on the cloud you pick, your own cloud account, or your own servers. Available now: Git A on AWS. Your own cloud account, your own servers and more clouds are coming.

  3. 3Encryption

    Everything sent between you and Git A is encrypted. Secrets you give us (webhook, two-factor, Actions and integration secrets) are stored encrypted. Passwords and access keys are stored only in a form that cannot be turned back into the original. Repository content, issues and activity are not separately encrypted by Git A in this release.

  4. 4Your code never runs on our servers

    Your builds and tests (Git A Actions) run on your own computers, called runners. Git A’s servers never run your code.

  5. 5Agent keys

    Each agent gets its own key that can do only what you allow: which repositories it may change and whether it may put changes on main by itself. You can give a key an end date: when it passes, its access stops automatically. You can see what each agent did, and switch a key off at any time.

  6. 6Approvals before production

    Environments such as dev and production can require a person to approve before anything is deployed to them. Every deployment is kept in a history you can check.

  7. 7Staff access

    The Git A team can open your organization’s repositories only in an emergency, with a temporary pass that works for your organization alone and lasts at most 24 hours. Every such access is written to your organization’s audit log (the record of who did what), and its owners get an email. The team works from India.

  8. 8Recovery

    If the server fails, you lose at most the last 24 hours of changes: we keep a copy of the server every day, in the same region. We aim to have the service back within 4 hours. We do not offer an uptime guarantee yet.

  9. 9Compliance

    SOC 2 Type II and ISO 27001: on the roadmap, not certified today.

10Who handles your data (subprocessors)

The companies that handle your data for us, and the country where they do it. A data processing agreement is being prepared with our lawyers and is not available yet.

Responsible disclosure

Found a security problem? Email the address in our security contact file. Please give us reasonable time to fix it before you publish it.

Related: Privacy · Terms · Pricing