GDRequests

PRIVACY POLICY

Effective date: 13th December 2022

Introduction:

I'm not going to bore you with the boring stuff. I'm going to talk about how this thing works, and what that means for your data. Of course, as with all parts of this site, how your data is used depends on how you use the site, so different parts of this policy will apply to you at different times. Therefore, I'd recommend you read this whole page.

All Users:

Just a quick disclaimer that by logging in via Twitch or YouTube, you accept to that site's terms and conditions, as well as their privacy policy.
To see Google's Privacy Policy, go here: https://policies.google.com/privacy
Or to see Twitch's, go here: https://www.twitch.tv/p/en/legal/privacy-notice/

Additionally, this site (as well as everything else on this domain) uses Cloudflare for security. Unfortunately, this does bring some more cookies into the mix, but I believe I have disabled everything I can in terms of tracking. To see the cookies that Cloudflare uses for security, see this page: https://developers.cloudflare.com/fundamentals/get-started/reference/cloudflare-cookies/

The cookies that those services use whilst you're logging in through their websites are out of my control. However, no tracking services have been deliberately put on this site. Only what is necessary for the site to function.
What does the site need to function? For everyone, this is simply any settings you've changed in the page settings, and any cached content through the service worker. There is no way to be tracked via this information.
Whilst logged in, IDs related to you will be stored in a session, which remains active until you log out or until enough time has passed. This session is used so you are not constantly pestered to login. But here's the part I'm proud of! This site does not store your access token! It's used, and then immediately forgotten!
Your only point of concern really should be that the server keeps track of your IP address as you browse for the site. But every site does that.

Viewers:

If you need to login to send a level, the ID associated with your connection is stored (so if you logged in via Twitch, your Twitch ID is saved, likewise with YouTube).
Other than that, and a timestamp of when you sent the level, only what you send is sent to the server. That's it. Nothing more.

Moderators:

So that you can moderate levels, a WebSocket connection is made to the servers. As part of this, a brief authentication window occurs, where your IP address, and user IDs are stored in a database for roughly twenty seconds. This is to prevent attackers from acting on your behalf and wreaking havoc on a stream.

Streamers:

As part of creating a page, you're given a Site ID. This ID is used to refer to you and your stuff within the site's database, as well as folders for any image content that you upload (profile pictures and banners). You can view what data is stored about you by going into “Settings”, then clicking on “Request Data” whilst you're logged in. Over there, you'll find your data is quite self-explanatory, but if you feel that something could be clarified, feel free to send me feedback.
Also, like moderators, so that you can get levels to play, a WebSocket connection is made to the servers. As part of this, a brief authentication window occurs, where your IP address, and user IDs are stored in a database for roughly twenty seconds. This is to prevent attackers from acting on your behalf and wreaking havoc on your stream.