You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 23, 2023. It is now read-only.
I could not find documentation concerning the possible cookie consent necessary when using gitcdn.xyz. Does it gather data (or rely on services) that would require a specific mention in a privacy policy ? For instance, as it relies on CloudFlare, I expect there should be something.
The text was updated successfully, but these errors were encountered:
That's a fair point- As I'm Australia based (and we don't have cookie consent policy laws) it hadn't crossed my mind to add one.
Only Cloudflare's cookies are added, so I'll consult their policy and add a statement to GitCDN.
That said, the only page that would need it is the GitCDN homepage (and I'll add it to the README as well), it's up to the end users to add cookie consents to their products.
I'll make a spot that specifies exactly what people implementing resources will need to know though.
I understand about the homepage. But the issue was also about usage of the CDN in other products. It is difficult to understand whether it adds a cookie in the background even when the user does not go to the homepage of gitcdn
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I could not find documentation concerning the possible cookie consent necessary when using gitcdn.xyz. Does it gather data (or rely on services) that would require a specific mention in a privacy policy ? For instance, as it relies on CloudFlare, I expect there should be something.
The text was updated successfully, but these errors were encountered: