@@ -5,18 +5,20 @@ receiving visits from European Union residents.
55
66These new restrictions make it more illegal to use Google Fonts directly. This proxy is a plug-and-play
77replacement for Google Fonts that can be hosted on a custom domain to proxy Google Fonts and thus comply
8- with GDPR (as no personal data will be transfered to Google Fonts).
8+ with GDPR (as no personal data will be transferred to Google Fonts).
99
1010This image only relies on nginx and its substitution module: it's extremely fast, privacy friendly and
1111production ready.
1212
13+ > The latest version is based on https://github.com/trajano/google-fonts-proxy-docker .
14+
1315## Usage
1416
1517Once setup (for instance at Citipo we run an instance on https://fonts.citipo.com ), all requests done to
1618the configured URL will be forwarded to Google Fonts with the same exact URL path and CSS responses
1719will be altered on-the-fly to change fonts files reference to use your own domain.
1820
19- ** This forwarding will be done fully anonymously so that the client IP and personnal data won't ever
21+ ** This forwarding will be done fully anonymously so that the client IP and personal data won't ever
2022be transmitted to Google.**
2123
2224Once deployed, you can use the service by directly replacing the Google Fonts URL with your own:
@@ -27,27 +29,26 @@ Once deployed, you can use the service by directly replacing the Google Fonts UR
2729<link href =" https://fonts.citipo.com/css2?family=Assistant:ital,wght@0,400;0,700;0,800;1,400;1,700" rel =" stylesheet" crossorigin =" anonymous" />
2830```
2931
30- > In compliance to Google Fonts Terms of Service, this proxy doesn't cache the fonts locally, it only transfers
31- > the requests (https://github.com/google/fonts/issues/1637 ).
32-
3332## Setup
3433
3534With docker-compose:
3635
3736``` yaml
38- version : ' 3'
39-
4037services :
4138 fonts :
42- image : docker.pkg.github.com /citipo/docker-google-fonts-proxy/alpine
39+ image : ghcr.io /citipo/docker-google-fonts-proxy
4340 ports :
4441 # You can use a proxy (like https://github.com/nginx-proxy/nginx-proxy)
4542 # to provide SSL
4643 - ' 80:80'
4744 environment :
4845 # The host you use for fonts: references to Google Fonts
4946 # will be replaced to this host in CSS files
50- - FONTS_HOST=fonts.citipo.com
47+ FONTS_HOST : fonts.citipo.com
48+ volumes :
49+ # The fonts and CSS files will be cached locally in this directory for 30 days
50+ # in order to avoid sending too many requests to Google Fonts
51+ - ' ./storage:/data/nuts'
5152` ` `
5253
5354With Docker CLI:
@@ -56,17 +57,17 @@ With Docker CLI:
5657docker run -d \
5758 -p 80:80 \
5859 -e FONTS_HOST=fonts.citipo.com \
59- docker.pkg.github.com /citipo/docker-google-fonts-proxy/alpine
60+ ghcr.io /citipo/docker-google-fonts-proxy
6061```
6162
6263## For developers: what to tell you Data Protection Officer?
6364
64- Your Data Protection Officer (the person responsible of GDPR in your company) may be curious about the details
65+ Your Data Protection Officer (the person responsible for GDPR in your company) may be curious about the details
6566of this tool, especially given the amount of media coverage the latest Google Fonts GDPR issues had.
6667
6768To answer their questions, you can explain that this tool * anonymizes data* (in the GDPR meaning): it transforms
6869personal, indirectly identifiable data into fully anonymous requests towards Google. As long as you host this
69- service in your own infrastructure, no personal data is ever transfered to Google (or any other intermediate).
70+ service in your own infrastructure, no personal data is ever transferred to Google (or any other intermediate).
7071
71- Data anonymization (which is different from pseudonymization) ensures that the data transfered to Google isn't
72+ Data anonymization (which is different from pseudonymization) ensures that the data transferred to Google isn't
7273covered by GDPR, thus not being a compliance issue.
0 commit comments