forked from the-turing-way/the-turing-way
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request the-turing-way#3724 from aranas/3716-add-data-usag…
…e-statement 3716 add data usage statement
- Loading branch information
Showing
2 changed files
with
33 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
(data-usage)= | ||
# TTW Book Data Usage | ||
|
||
We want to understand and optimise the use, geographical reach, and findability of _The Turing Way_ book. | ||
It is possible through information such as how many people currently use the book, which chapters are they interested in, from which countries are they able to access our resources or where we are not currently findable or accessible. | ||
Therefore, we are collecting some data on our website activities, which we describe in this document. | ||
|
||
For example, we are keen to understand data on website traffic as it helps with assessing and reporting impact through different channels. | ||
Data on search terms people use to find the website can help us understand readers' needs and preferences. | ||
With this knowledge we can better tailor our content to be useful. | ||
|
||
See our ongoing discussions [on GitHub](https://github.com/the-turing-way/the-turing-way/discussions/3713) around which insights could help improve the content quality. | ||
|
||
For the above reasons, we are currently using Google Analytics to track traffic on our website and [Cauldron](https://cauldron.io/) to track activity on our GitHub repository. | ||
|
||
## User Awareness Statement - Google Analytics | ||
Google Analytics is [problematic](https://piwik.pro/blog/is-google-analytics-gdpr-compliant/). | ||
We are working on using an open-source, GDPR-compliant analytics tool like [Matomo](https://matomo.org/) or other ethical analytics tools instead. | ||
|
||
For now, we have configured Google Analytics to be as GDPR-compliant as possible: | ||
|
||
- Our data retention settings are set to the minimum duration possible (2 months). | ||
- All advertising features are disabled. | ||
- We do not send user IDs to Google. | ||
- We do not share any collected data with Google beyond what is required of us to ["maintain and protect the Google Analytics service."](https://business.safety.google/adsprocessorterms/) | ||
- Note that, in the latest Google Analytics version, IP addresses are now anonymized per default. | ||
|
||
By implementing these measures, we hope to somewhat mitigate the adverse effects of Google Analytics while we transition to a better tool. | ||
If you would like to get involved in this discussion, please head over to the GitHub issue linked to this document. | ||
|
||
For other related questions, please reach out to _The TuringWay_ team by emailing [turingway@turing.ac.uk](mailto:turingway@turing.ac.uk). |