Skip to content
This repository has been archived by the owner on May 25, 2021. It is now read-only.

Add privacy policy (cont.) #27

Open
wants to merge 30 commits into
base: master
Choose a base branch
from
Open

Add privacy policy (cont.) #27

wants to merge 30 commits into from

Conversation

Hans5958
Copy link
Member

Continuation of #26, resolves #24.

@WorldLanguages, you do the merge as you are the project leader.

@Hans5958 Hans5958 changed the title Add privacy policy Add privacy policy (cont.) Sep 30, 2020
privacy.md Outdated Show resolved Hide resolved
privacy.md Outdated

## Information we collect

We collect a few different kinds of information about you, like what part of the world you are in, what pages you come to our website from, and what device and software you use. We also collect information about how you use our website. We might collect your Scratch username.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We might collect your Scratch username.

Any specific reason for this to not be specific enough? We don't collect usernames unless explicitly given by users, in the feedback page.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc @easrng

Copy link
Contributor

@Explosion-Scratch Explosion-Scratch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grammar fixes

privacy.md Outdated

## Information we collect

We collect a few different kinds of information about you, like what part of the world you are in, what pages you come to our website from, and what device and software you use. We also collect information about how you use our website. We might collect your Scratch username.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe change this We also collect information about how you use our website. We might collect your Scratch username. to this: We also collect your Scratch username (if you have one) and data about how you use ScratchAddons.com

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc @easrng

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good, but this isn't my pr anymore.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Explosion-Scratch I think it is "might" because it is an optional thing. Also, don't refer it as ScratchAddons.com. You can refer it as "our website" as stated on the first paragraph.

@easrng Just so you know, you can do a pull request that is directly to the privacy branch.

@Hans5958 Hans5958 force-pushed the master branch 2 times, most recently from 662c251 to b4acd86 Compare October 20, 2020 13:10
@GrahamSH-LLK
Copy link
Member

GrahamSH-LLK commented Oct 27, 2020

Up to date version (without merge conflicts): #41

# Conflicts:
#	assets/css/base.scss
#	site/faq.md
#	site/farewell.html
#	site/feedback.html
#	site/index.html
#	site/scratch-messaging-transition.html
#	site/welcome.html
Copy link

@williamhorning williamhorning left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did you delete the Welcome and Farewell pages? This makes no sense, otherwise, this is all good.

@Hans5958
Copy link
Member Author

Hans5958 commented Nov 9, 2020

That is really weird. Will try to resolve this.

@Hans5958
Copy link
Member Author

Hans5958 commented Nov 9, 2020

@wgyt735yt Fixed it. You can check it again if you want.

@williamhorning
Copy link

@wgyt735yt Fixed it. You can check it again if you want.

Thanks for doing it, can we merge this?

Copy link

@williamhorning williamhorning left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we merge this already? It works now, and is good.

@WorldLanguages
Copy link
Member

I'll work on this after v1.14.0 release

@WorldLanguages
Copy link
Member

Related: does anyone know of an analytics service that does not require us to ask for opt-in, unlike Google Analytics? That way, we could avoid the banner altogether. I believe GitHub recently did some changes like that as well - they only kept necessary cookies and removed the banner.

@cobaltt7
Copy link
Contributor

Related: does anyone know of an analytics service that does not require us to ask for opt-in, unlike Google Analytics? That way, we could avoid the banner altogether. I believe GitHub recently did some changes like that as well - they only kept necessary cookies and removed the banner.

Ocular uses Plausible, and they don't have a banner.

@WorldLanguages
Copy link
Member

I plan to remove all cookies from the website by the second half of May.
Cloudflare will be removing the only cookie it adds on May 10th: __cfduid
And all other cookies are related to Google Analytics.

We'll probably move to a self-hosted instance of Plausible, which does not use cookies. Possibly hosted by @jeffalo. And we'll have a page that will display at least some of the data Plausible collected publicly (not sure if we want everything public yet).

We'll continue to use Cloudflare for now, so there's no other option but to let it "see" the IP addresses of our visitors (at some point of the chain, someone has to be able to do that of course). But using Cloudflare infrastructure, we could make it so other 3rd parties (GitHub Pages, Plausible, let me know if we can think of any other) don't get the full IP addresses of our visitors (or don't get them at all).

@GrahamSH-LLK
Copy link
Member

AFAIK plausible doesn't touch IPs. __cfduid doesn't show up on my site, so I think there's a way to disable it. Jeffalo should be able to add plausible easily, but if we want to use a cloud version, we'll have to pay. #65 would have worked for this purpose.

@WorldLanguages
Copy link
Member

AFAIK plausible doesn't touch IPs

It doesn't. But the server hosting Plausible can still get it. "Never trust the client" and "never trust the server", they say.

@GrahamSH-LLK
Copy link
Member

GrahamSH-LLK commented Apr 30, 2021

AFAIK plausible doesn't touch IPs

It doesn't. But the server hosting Plausible can still get it. "Never trust the client" and "never trust the server", they say.

I think we can trust Jeffalo not to log IPs?
I mean, we already have an Ocular addon, so we're screwed if he does.

@WorldLanguages
Copy link
Member

I think we can trust Jeffalo not to log IPs?
I mean, we already have an Ocular addon, so we're screwed if he does.

You have to optin into enabling the Ocular addon - but the moment the extension is installed, we immediately open ScratchAddons.com without explicit consent. Not the same.
Also, why not anonymize IP addresses if we can. We're going to use Cloudflare as a proxy anyway.

@williamhorning
Copy link

@WorldLanguages Cloudflare's proxy doesn't pass the real IP unless you tell it to
unless you enable the setting "True-Client-IP Header" under Network, even then you need the enterprise plan
or
you check the headers 'X-Forwarded-For' and 'CF-Connecting-IP'

@WorldLanguages
Copy link
Member

@wgyt Are you sure they can be disabled from settings? I was thinking of using a Cloudflare Worker
Also, completely removing the IP is unideal for analytics. We'd miss geolocation analytics, like how many % of our visitors are from the US (spoiler: a lot)

@williamhorning
Copy link

@wgyt Are you sure they can be disabled from settings? I was thinking of using a Cloudflare Worker
Also, completely removing the IP is unideal for analytics. We'd miss geolocation analytics, like how many % of our visitors are from the US (spoiler: a lot)

AFAIK 'X-Forwarded-For' and 'CF-Connecting-IP' are always on.

@GrahamSH-LLK
Copy link
Member

@wgyt Are you sure they can be disabled from settings? I was thinking of using a Cloudflare Worker
Also, completely removing the IP is unideal for analytics. We'd miss geolocation analytics, like how many % of our visitors are from the US (spoiler: a lot)

AFAIK 'X-Forwarded-For' and 'CF-Connecting-IP' are always on.

Spoiler alert: you can easily set up Nginx to de-obfuscate ips from behind cloudflare, so we have to trust whoever is hosting our server.

@williamhorning
Copy link

On my website, I use Cloudflare analytics and it works well. It uses 0 cookies, and gives a decent amount of data, including visits, page views, page load time, country data, the referer, host, path, and browser.

@WorldLanguages
Copy link
Member

Spoiler alert: you can easily set up Nginx to de-obfuscate ips from behind cloudflare, so we have to trust whoever is hosting our server.

I don't think anything is stopping us from setting up a Cloudflare Worker that anonymizes the X-Forwarded-For and CF-Connecting-IP headers. Those are what's used by Nginx to de-obfuscate IPs.

@williamhorning
Copy link

Spoiler alert: you can easily set up Nginx to de-obfuscate ips from behind cloudflare, so we have to trust whoever is hosting our server.

I don't think anything is stopping us from setting up a Cloudflare Worker that anonymizes the X-Forwarded-For and CF-Connecting-IP headers. Those are what's used by Nginx to de-obfuscate IPs.

I think you could anonymize those headers, but I have no experience with CF workers so 🤷🏻‍♂️

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Privacy Issue] Add a disclaimer about use of Google Analytics
7 participants