Privacy Policy

What do we collect from website guests (who are not logged in)?

Guests can only participate in anonymously chatting. Of the messages that are sent, only the last 10 messages will be temporarily stored, to be shared with newly connected clients. These messages are also broadcasted to all connected clients.

It is possible for a guest to change some settings which are stored in cookies. The only setting that is stored as a cookie currently is the selected background.

What cookies do we use?

Other values are stored as a cookie as well. The cookies are only stored with consent of the user. A list of all the used cookies:

  1. lastupdateviewed: this indicates the version of the site the user had visited the last time. Its purpose is to present the user with the changelog when the website is updated.
  2. clickedmarkarea: this stores whether or not the user has ever clicked the mark area button before. The purpose is to have a popup with info the first time the user tries to use this.
  3. mysession: this stores the session token such that the website knows who the user is. This is not used for guests.
  4. discordseen: this value is set to true after the user has seen the bobbing arrow at the Discord link button. When this value is true, upon loading the page, the arrow is no longer displayed.
  5. background: this value stores which background the user has selected.

What values do we store about users on our site?

User data

Users have to login through Google. The first time a user logs in, we store their google id as identification for future logins. We store their email address for communication when a user is banned, or must be notified of a change in our Privacy Policy. We store when their account has been created such that it is visible to any user on their profile page as a public interest. We store the timestamp of when the user last either placed a pixel on our canvas, or sent a message in the chat. We store whether or not the user is a moderator or not to distinguish between them and allow for use cases to only be available for moderators. We store whether or not the user is banned to limit the actions of banned users. We store when premium on an account expires such that the bought goods are no longer available after that time. We store how much the user has of our fictional currency “PixelPoints” such that we can reward users with this currency and this can be spent in our shop. This currency is not a property of the user and we are not responsible for any changes that are made to it. Finally, we store the valid session ids of a user on our site such that they can keep being logged in.

Pixel changes

As users can place pixels on the canvas, we log these changes. For each change we store the rgb-values, the x and y-position, timestamp, user id of the user that placed it and whether or not it was reverted. We store this with the goals that users can check who placed a pixel, know what color a pixel at a given position is, when a pixel was changed, to see who contributed on a drawing and to make timelapses. Moderators can revert changes of a user as a way to deal with griefing. This way, the data can be used as dataset to automatically detect griefing in the future.

Marked areas

Users can decide to mark an area. For an area we store the boundaries of the area, when it was marked and by whom. The user is also able to give it a title. The user who created the area marking, is able to freely delete it at any time.

Users can also leave comments on a marked area. For these comments, the id of the marking is stored, as well as the user id of the user who created the comment, timestamp and body of the comment such that other users can view them.

Custom colors

When a user purchases a custom color at the shop, we need to store the rgb values that the user has selected and relate them to the user’s id.

What data do we share with third parties?

Nothing. We don't specifically share any data with third parties. We do however, consider the data as free for public use. For example, anyone is allowed to see the pixels that have been placed, and by whom.