Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Privacy policy #1

perborgen opened this issue Feb 12, 2019 — with GitSpeak · 0 comments

Privacy policy #1

perborgen opened this issue Feb 12, 2019 — with GitSpeak · 0 comments


Copy link

@perborgen perborgen commented Feb 12, 2019 — with GitSpeak

We’re dedicated to keeping your data safe, and we only collect information you explicitly share with us.

If you have questions which aren’t answered in this document, don’t hesitate to reach out via email (, and we’ll get back to you as soon as possible.

Who is collecting the data?

The data is collected via and via the GitSpeak desktop app, both of which are owned and operated by the Norwegian corporation Scrimba AS.

What data is being collected?

We do not store your source code when you connect a local repository to the GitSpeak app. Nor do we access your source code via GitHub.

However, if you record a codecast in GitSpeak, we'll need to store the code files you open during the codecast, so that other team members can watch the screencast. In the future, we plan to add an option for not even storing code files when recording a cast. This will, naturally, require the viewer to also have the local repository connected to GitSpeak when viewing the codecast, so that GitSpeak can fetch the code from a local version of the repository.

The only personal data we collect is the data you give access to GitSpeak in the authentication process. For a GitHub repository, this includes metadata on members, issues, pull requests, milestones, but not the source code. For a GitHub organization, this includes basic metadata on the organization's repositories and members.

When a user signs up on GitSpeak using GitHub auth we'll store the user's mail address and any other public metadata shared on GitHub. This can include your bio, location, website and whatever extra information you have shared publicly on GitHub.

We’re also Google Analytics for tracking inside the app. This data is also pseudo-anonymized. We’re not sending any personal information to Google Analytics, and we have turned of IP tracking to comply with GDPR.

What is the legal basis for processing the data?

The legal basis for processing your personal data is your consent when signing up for GitSpeak.

Will the data be shared with any third parties?

Our data is stored on a dedicated server operated by OVH SAS, and it is located in Canada. OVH undertakes to abide by its obligations in accordance with the aforementioned regulations, particularly the GDPR.

Google Analytics data is stored by Google Analytics. They are committed to complying with the new legislation and will collaborate with partners throughout this process.

We're using AWS (US) via EmailOctopus in order to send out notification emails and newsletters.

How will the information be used?

The information is only used to provide you with the best possible experience inside the GitSpeak app. We will never sell any of your data.

How long will the data be stored for?

The data will be stored until the owner asks us to delete it.

What rights does the data subject have?

You can at any given time ask us to delete your data, and we’ll fullfill your request without questions. Simply email us at

How can the data subject raise a complaint?

If you want us to delete your data please send an email to hello[@scrimba]().com and we’ll delete it.

@perborgen perborgen changed the title GitSpeak Privacy Policy Privacy Policy Feb 12, 2019
@perborgen perborgen changed the title Privacy Policy Privacy policy Feb 12, 2019
@Pistus Pistus added the documentation label Oct 3, 2019 — with GitSpeak
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants