Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit e14953f

Browse files
committed
Updates GitLens security information
Replaces the existing security information page with a more detailed and up-to-date version. Clarifies data collection, storage, and SOC 2 compliance for GitLens, providing users with a better understanding of data security practices.
1 parent 9f88866 commit e14953f

File tree

1 file changed

+28
-26
lines changed

1 file changed

+28
-26
lines changed

‎gitlens/GL-Security.md

Lines changed: 28 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,31 +1,33 @@
11
---
2-
3-
title: Security Information - Gitlens
4-
description: Data Security Information for GL
2+
title: GitLens Security Information
3+
description: Learn how GitLens secures your data, including collection, transfer, storage, and SOC 2 certification.
54
taxonomy:
65
category: gitlens
76

87
---
9-
## Information Collection/Storage
10-
Below is a chart outlining some basic security information regarding the type of data that we collect and how we store it remotely.
11-
12-
| Service | What information are we collecting | How is this information secured in the transfer| Where is this information stored | How is this information secured in storage |
13-
| --- | --- | --- | --- | --- |
14-
| Subscriptions | Billing info: name, payment type (credit card, paypal, ACH, etc.), last four digits of payment method, zip code, country, credit card type (mastercard, visa, etc.) | Encrypted with TLS | MongoDB Atlas | Encrypted at rest (AES-256) |
15-
| Launchpad | URLs of issues and pull requests ONLY for pin/snooze functionality | Encrypted with TLS | Postgres (RDS) | Encrypted at rest (AES-256) |
16-
| Cloud Patches | Info related to the patch (repo name/URL/provider/base branch name/etc.) + the patch content itself. | Encrypted with TLS | Patch info is stored in a Postgres database, patch content is stored in AWS S3. | SSE-S3, which uses 256-bit Advanced Encryption Standard (AES-256) |
17-
| Cloud Workspaces | Repository info: URL, provider, org name, repo name | Encrypted with TLS | MongoDB Atlas | Encrypted at rest (AES-256) |
18-
19-
## SOC2
20-
Gitkraken and it’s tools are now SOC 2 Certified! If you would like to request a copy of our SOC2 report, please visit our [Trust Center](https://trust.gitkraken.com/) to get the request process started. Please note that in order to provide a copy of the report, we will need you to sign an MNDA.
21-
22-
<div class="bbb-callout bbb--info">
23-
<div class="irow">
24-
<div class="ilogobox">
25-
<span class="logoimg"></span>
26-
</div>
27-
<div class="imsgbox">
28-
SOC 2 reports are only available for Business and Enterprise customers.
29-
</div>
30-
</div>
31-
</div>
8+
9+
<kbd>Last updated: August 2025</kbd>
10+
11+
## Data Collection and Storage
12+
13+
The table below outlines the types of data GitLens collects, how it is secured during transfer, where it is stored, and how it is protected at rest.
14+
15+
| Service | Data Collected | Secured in Transfer | Storage Location | Secured in Storage |
16+
|-----------------|--------------------------------------------------------------------------------|---------------------|------------------------------------------|--------------------------------------------------|
17+
| **Subscriptions** | Billing info: name, payment type (credit card, PayPal, ACH, etc.), last 4 digits of payment method, zip code, country, card type (Visa, Mastercard, etc.) | Encrypted with TLS | MongoDB Atlas | Encrypted at rest (AES-256) |
18+
| **Launchpad** | URLs of issues and pull requests (for pin/snooze functionality only) | Encrypted with TLS | Postgres (RDS) | Encrypted at rest (AES-256) |
19+
| **Cloud Patches** | Patch metadata (repo name/URL/provider/base branch, etc.) and patch content | Encrypted with TLS | Metadata in Postgres; patch content in AWS S3 | Metadata encrypted at rest (AES-256); patch content encrypted with SSE-S3 (AES-256) |
20+
| **Cloud Workspaces** | Repository info: URL, provider, organization name, repository name | Encrypted with TLS | MongoDB Atlas | Encrypted at rest (AES-256) |
21+
22+
---
23+
24+
## SOC 2 Compliance
25+
26+
GitKraken and its tools, including GitLens, are **SOC 2 certified**.
27+
If you would like to request a copy of our SOC 2 report, please visit our [Trust Center](https://trust.gitkraken.com/) to begin the request process.
28+
29+
Please note: an MNDA must be signed before we can provide a copy of the report.
30+
31+
<div class='callout callout--info'>
32+
<p><strong>Note:</strong> SOC 2 reports are only available for <strong>Business</strong> and <strong>Enterprise</strong> customers.</p>
33+
</div>

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /