Who we are
Our website address is: https://galwaygamejam.com.
This policy also covers our official Galway Game Jam Discord server.
What personal data we collect and why we collect it
Discord Server – Policy for Child Protection
(Updated 18th Jan 2022)
When you join our official Galway Game Jam Discord server, we have a sign up process which requires you to accept our server rules, including verifying that you are at least 18 years of age. We have a zero tolerance for minors on the server. However if a minor is found to be on the server, they are in breach of our policy. We will take steps to remove their user account from our community server and prevent them from joining again.
If you have children interested in game jams, we suggest looking into events and communities that are developed for children such Global Game Jam Next and CoderDojo.
When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.
If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.
If you leave a comment on our site you may opt in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.
If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.
Embedded content from other websites
Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
We use Google Analytics on our site to determine usage and other statistics.
Who we share your data with
Apart from the analytics provider and automated spam checker we do not share your information with any other third party.
We store our files on popular Cloud Storage providers – Google Drive and Dropbox. For more information please see their respective privacy and data policies.
How long we retain your data
If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognise and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.
What rights you have over your data
If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Where we send your data
Visitor comments may be checked through an automated spam detection service.
Your contact information
How we protect your data
We restrict access to data to the administrators of the website, and moderators of the Discord Server only. Volunteers and members have no access.
What data breach procedures we have in place
What third parties we receive data from
What automated decision making and/or profiling we do with user data