We download a bare clone of your repositories using that token. A bare clone involves downloading only the diffs and does not check out a working tree. Eventually, these stats get written to our database. No code is persisted at any point in the process. The service that initially cloned your repositories gets its container destroyed.

As a cloud service provider, our controls and processes demand the highest level of trust and transparency. Waydev’s information, security practices, policies, and procedures are suitable to meet the SOC 3 trust principles criteria for security, availability, and confidentiality. Waydev has highest level of security measurements against any potential security breach.

This ensures that all data transmitted to Waydev is done over a secure protocol, and allows our customers to maintain strict authentication and access security using Git provider tokens.

We use Stripe (www.stripe.com) for all credit card and payment information processing. Stripe has been audited by a PCI-certified auditor and is certified to PCI Service Provider Level This is the most stringent level of certification available in the payments industry.

All card numbers are encrypted at rest with AES-256. Decryption keys are stored on separate machines. None of Stripe’s internal servers and daemons are able to obtain plaintext card numbers; instead, they can just request that cards be sent to a service provider on a static whitelist. Stripe’s infrastructure for storing, decrypting, and transmitting card numbers runs in separate hosting infrastructure, and doesn’t share any credentials with Stripe’s primary services (API, website, etc.).