Security at Joggr

Joggr's authorization model is based upon the permissions you set in your Version Control System (VCS), such as GitHub. This means that if you remove access to a repository or organization in GitHub the user immediately loses access in Joggr to all documentation related to those entities.

Our application needs read & write access to your repository, since all of your documentation is stored in GitHub. When a user onboards they authorize access to GitHub and we make commits, open pull requests, and other operations on their behalf. All of our access is driven by the current authenticated user. We will never make changes to your code, only Joggr Doc markdown files.

Yes, we work with all of our clients to make sure they are GDPR compliant while using Joggr. We provide a Data Processing Addendum (DPA) that describes our Technical and Organizational Security Measures. For more information please contact our security team.

Joggr does not currently have a SOC 2 Type II attestation. We have a SOC 2 ready security program and are working towards a SOC 2 in the near future.

Joggr does not store personal credit card information for any of our customers. We use Stripe to securely process payments and trust their commitment to top-notch security. Stripe is a certified PCI Service Provider Level 1, which is the highest level of certification in the payments industry.

Yes, all data is encrypted at rest (AES-256) and in transit (HTTPS / TLS). Additional client-side encryption and decryption is utilized for senstitive data such as GitHub authorization tokens.

Yes, data is backed up in its entirety once per day and point-in-time recovery is enabled for up to 7 days.