From 1a96a065588d888af6e78828ad980a4657fabde7 Mon Sep 17 00:00:00 2001 From: Keiran Wilkinson Date: Thu, 5 Aug 2021 21:55:59 +0100 Subject: [PATCH 01/11] Adds a privacy policy - this needs to be completed --- privacy.md | 91 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 91 insertions(+) create mode 100644 privacy.md diff --git a/privacy.md b/privacy.md new file mode 100644 index 0000000..0478b30 --- /dev/null +++ b/privacy.md @@ -0,0 +1,91 @@ +--- +permalink: /privacy/ +layout: default +suffixes: + - Privacy, + - Assurance, + - Safeguards, + - Security, + - Us +title: Code of Conduct +--- + +# Privacy Policy + +CodeWith wants to be a friendly community where everyone feels welcome and safe at meetups and events. + +This code of conduct is to protect that atmosphere of inclusivity. It helps us all to understand the community’s shared values and provides clear guidelines on how we should behave. + +All attendees, speakers, hosts, and mentors must agree with this code of conduct. We must all cooperate to ensure a safe environment for everybody. + +## Summary + +We want to make sure that all CodeWith events are a harassment-free experience for everyone, regardless of gender, age, sexual orientation, disability, physical appearance, body size, race, or religion (or lack thereof). + +We should all listen and communicate respectfully, regardless of appearance or background. We do not tolerate harassment of participants in any form. + +Sexual language and imagery are not appropriate for any venue, including talks, parties, Twitter, Facebook, Eventbrite, our Slack channel, and other online media. + +CodeWith events are not for people to attend with the sole purpose of selling or recruiting. + +Anyone who breaks this code of conduct may be sanctioned or expelled from events at the organisers’ discretion. + +## The details +### No harassment + +We do not tolerate harassment at any CodeWith event. + +Harassment includes offensive verbal comments that relate to gender, age, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. + +We also have a general policy that we do not tolerate disruptive behaviour including repeated interruption, inebriation (or similar intoxication), fighting and open aggression. + +We expect anyone who we ask to stop any disruptive or inappropriate behaviour to do so immediately. + +If someone being at an event becomes a problem, we will take appropriate action, which may include a warning or expulsion without a refund (if applicable). + +### No selling or solicitation + +CodeWith is not a platform for anyone to send spam or broadcasts, nor is it for solicitation or job recruiting. Anyone who attends a CodeWith event with the sole purpose of selling products or goods will not be tolerated. + +Speakers who use their time to sell a particular product will also find their talk won’t be well received. It’s fine to mention that your company sells products, but talks should focus on its technical aspects. Encourage people to try it out – avoid solution selling. + +### No recruiting during events + +We want job seekers to find employment and for our attendees to be successful, but there is a right way to communicate. + +It may be appropriate for a recruitment company to sponsor refreshments and do a quick pitch to a relevant audience of potential candidates, but this is down to the discretion of the event organiser(s). Recruiting during an event without prior arrangement will be treated as a breach of this code of conduct. + +### What to do if you have a concern + +If you are being harassed or feel uncomfortable, notice that someone else is being harassed, or have any other concerns, please speak to the event organiser(s) immediately. You can also contact the event organiser through Meetup and Slack. + +If you are not able to to do this or you feel that your concern is not being taken seriously then please contact the Equity Officer. This is currently Marie Fayard, who can be reached on Discord, on Slack, or by email ([marie.fayard@gmail.com](mailto:marie.fayard@gmail.com)). + +CodeWith is here to listen to your concerns or questions and you don’t have to make a formal report unless you want to. You do not have to give us details of the harassment. + +If you wish to report it, we will take details of the harassment and work with you to respond to the issue in a way that helps you feel safe. + +If necessary, the event organisers will help participants contact police or venue security, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the event. + +### Where and when this code of conduct applies + +We expect participants to follow this code of conduct at all our events, partner events, related social events, such as post-event drinks, networking discussions, meetups and workshops. Event sponsors must also follow this anti-harassment policy, which includes not using sexualised images, activities, or other material. + +### Exceptions + +Any discussion or images that relate to sex, pornography, discriminatory language, or similar must meet the following criteria. + +- The organisers must specifically grant permission in writing. +- It must be necessary to the topic of discussion and no alternative exists. +- It must be presented in a respectful manner. +- Attendees must be warned in advance and respectfully given plenty of warning and the opportunity to leave beforehand. +- This exception specifically does not allow the use of gratuitous sexual images as a device to grab attention or for unnecessary examples. + +Thank you + +This document was based on the [Sheffield Digital Code of Conduct](https://sheffield.digital/events/meetup-code-of-conduct/), which in turn is based on the work of JSConf, Geek Feminism, confcodeofconduct.com, and inspired by resources provided by Ashe Dryden. + +Licensed under a Creative Commons Attribution 3.0 Unported License. +Version 1 + +This is version 1 of the CodeWith Code of Conduct. It was last updated by Simon Davey on 31 August 2020. If you think we have made any errors or omissions, please contact us by email ([contact@codewith.org.uk](mailto:contact@codewith.org.uk)) or through one of the communication channels listed on the [contact page](contact.html). From 31ec47c5238fafa91dae9bf4efb13f15c041be90 Mon Sep 17 00:00:00 2001 From: Keiran Wilkinson Date: Thu, 5 Aug 2021 21:57:39 +0100 Subject: [PATCH 02/11] Adds the cookie consent page, styling and adding it to the default template. Also removes tracing for noscript because we have no way of asking permission. --- _includes/cookie-consent.html | 40 +++++++++++++++++++++++++++++++++++ _layouts/default.html | 5 +---- css/style.css | 32 ++++++++++++++++++++++++---- 3 files changed, 69 insertions(+), 8 deletions(-) create mode 100644 _includes/cookie-consent.html diff --git a/_includes/cookie-consent.html b/_includes/cookie-consent.html new file mode 100644 index 0000000..a86efba --- /dev/null +++ b/_includes/cookie-consent.html @@ -0,0 +1,40 @@ + + \ No newline at end of file diff --git a/_layouts/default.html b/_layouts/default.html index a2ad70b..3e197c8 100644 --- a/_layouts/default.html +++ b/_layouts/default.html @@ -4,10 +4,6 @@ Skip to main content - - -
{% include sidebar.html %} @@ -30,6 +26,7 @@

CODEWITH

{% include scripts.html %} + {% include cookie-consent.html %} \ No newline at end of file diff --git a/css/style.css b/css/style.css index 1639ad9..43a5973 100644 --- a/css/style.css +++ b/css/style.css @@ -534,10 +534,34 @@ div.event-book-button { } @media screen and (min-width: 992px) { +/*Cookie Notice*/ - .masthead, - .mastfoot, - .cover-container { - width: 700px; +#cookie-notice { + padding: 0.5rem 1rem; + display: none; + text-align: center; + position: fixed; + bottom: 0; + width: 100%; + background: #222; + color: rgba(255, 255, 255, 0.8); + z-index: 2; +} + +#cookie-notice a { + display: inline-block; + cursor: pointer; + margin-left: 0.5rem; +} + +@media (max-width: 767px) { + #cookie-notice span { + display: block; + padding-top: 3px; + margin-bottom: 1rem; + } + #cookie-notice a { + position: relative; + bottom: 4px; } } \ No newline at end of file From 7dfd3d0de39b1dbb607196e34f11bb1d29d91ade Mon Sep 17 00:00:00 2001 From: Keiran Wilkinson Date: Thu, 5 Aug 2021 21:57:59 +0100 Subject: [PATCH 03/11] Lower the Sidebar z index so it displays behind the Cookie Consent --- css/sidebar.css | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/css/sidebar.css b/css/sidebar.css index 8df30ba..0edd5c1 100644 --- a/css/sidebar.css +++ b/css/sidebar.css @@ -28,7 +28,7 @@ -ms-transition: all 0.3s ease; -o-transition: all 0.3s ease; transition: all 0.3s ease; - z-index: 10000; + z-index: 1; } /* Show sidebar button */ From 14b1fcfacab2bc567e87e06184e1d5e1f09187e1 Mon Sep 17 00:00:00 2001 From: Keiran Wilkinson Date: Thu, 5 Aug 2021 21:58:35 +0100 Subject: [PATCH 04/11] Moving the Google Tag Manager code to a separate file --- _includes/google-tag-manager.js | 8 ++++++++ _includes/head.html | 9 +-------- 2 files changed, 9 insertions(+), 8 deletions(-) create mode 100644 _includes/google-tag-manager.js diff --git a/_includes/google-tag-manager.js b/_includes/google-tag-manager.js new file mode 100644 index 0000000..03b144c --- /dev/null +++ b/_includes/google-tag-manager.js @@ -0,0 +1,8 @@ +(function (w, d, s, l, i) { + w[l] = w[l] || []; w[l].push({ + 'gtm.start': + new Date().getTime(), event: 'gtm.js' + }); var f = d.getElementsByTagName(s)[0], + j = d.createElement(s), dl = l != 'dataLayer' ? '&l=' + l : ''; j.async = true; j.src = + 'https://www.googletagmanager.com/gtm.js?id=' + i + dl; f.parentNode.insertBefore(j, f); +})(window, document, 'script', 'dataLayer', 'GTM-WPSF3G7'); \ No newline at end of file diff --git a/_includes/head.html b/_includes/head.html index 28f9931..df6656e 100644 --- a/_includes/head.html +++ b/_includes/head.html @@ -8,14 +8,7 @@ CodeWith - {{ page.title }} - - - - + From f10354309f19a469a77699b8a0b7486290575a73 Mon Sep 17 00:00:00 2001 From: Keiran Wilkinson Date: Thu, 5 Aug 2021 22:10:49 +0100 Subject: [PATCH 05/11] Added some privacy policy headings --- privacy.md | 79 ++++++++---------------------------------------------- 1 file changed, 11 insertions(+), 68 deletions(-) diff --git a/privacy.md b/privacy.md index 0478b30..4a4781d 100644 --- a/privacy.md +++ b/privacy.md @@ -14,78 +14,21 @@ title: Code of Conduct CodeWith wants to be a friendly community where everyone feels welcome and safe at meetups and events. -This code of conduct is to protect that atmosphere of inclusivity. It helps us all to understand the community’s shared values and provides clear guidelines on how we should behave. - -All attendees, speakers, hosts, and mentors must agree with this code of conduct. We must all cooperate to ensure a safe environment for everybody. +The aim of this policy is to protect privacy whilst enhancing your experience using contact tools and providing CodeWith with analytics to improve the website. ## Summary -We want to make sure that all CodeWith events are a harassment-free experience for everyone, regardless of gender, age, sexual orientation, disability, physical appearance, body size, race, or religion (or lack thereof). - -We should all listen and communicate respectfully, regardless of appearance or background. We do not tolerate harassment of participants in any form. - -Sexual language and imagery are not appropriate for any venue, including talks, parties, Twitter, Facebook, Eventbrite, our Slack channel, and other online media. - -CodeWith events are not for people to attend with the sole purpose of selling or recruiting. - -Anyone who breaks this code of conduct may be sanctioned or expelled from events at the organisers’ discretion. +CodeWith uses the below tools to enhance the user experience +* Eventbrite +* Facebook Messenger +CodeWith uses the below tools to gather anonymous analytics +* Hotjar +* Google Analytics ## The details -### No harassment - -We do not tolerate harassment at any CodeWith event. - -Harassment includes offensive verbal comments that relate to gender, age, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. - -We also have a general policy that we do not tolerate disruptive behaviour including repeated interruption, inebriation (or similar intoxication), fighting and open aggression. - -We expect anyone who we ask to stop any disruptive or inappropriate behaviour to do so immediately. - -If someone being at an event becomes a problem, we will take appropriate action, which may include a warning or expulsion without a refund (if applicable). - -### No selling or solicitation - -CodeWith is not a platform for anyone to send spam or broadcasts, nor is it for solicitation or job recruiting. Anyone who attends a CodeWith event with the sole purpose of selling products or goods will not be tolerated. - -Speakers who use their time to sell a particular product will also find their talk won’t be well received. It’s fine to mention that your company sells products, but talks should focus on its technical aspects. Encourage people to try it out – avoid solution selling. - -### No recruiting during events - -We want job seekers to find employment and for our attendees to be successful, but there is a right way to communicate. - -It may be appropriate for a recruitment company to sponsor refreshments and do a quick pitch to a relevant audience of potential candidates, but this is down to the discretion of the event organiser(s). Recruiting during an event without prior arrangement will be treated as a breach of this code of conduct. - -### What to do if you have a concern - -If you are being harassed or feel uncomfortable, notice that someone else is being harassed, or have any other concerns, please speak to the event organiser(s) immediately. You can also contact the event organiser through Meetup and Slack. - -If you are not able to to do this or you feel that your concern is not being taken seriously then please contact the Equity Officer. This is currently Marie Fayard, who can be reached on Discord, on Slack, or by email ([marie.fayard@gmail.com](mailto:marie.fayard@gmail.com)). - -CodeWith is here to listen to your concerns or questions and you don’t have to make a formal report unless you want to. You do not have to give us details of the harassment. - -If you wish to report it, we will take details of the harassment and work with you to respond to the issue in a way that helps you feel safe. - -If necessary, the event organisers will help participants contact police or venue security, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the event. - -### Where and when this code of conduct applies - -We expect participants to follow this code of conduct at all our events, partner events, related social events, such as post-event drinks, networking discussions, meetups and workshops. Event sponsors must also follow this anti-harassment policy, which includes not using sexualised images, activities, or other material. - -### Exceptions - -Any discussion or images that relate to sex, pornography, discriminatory language, or similar must meet the following criteria. - -- The organisers must specifically grant permission in writing. -- It must be necessary to the topic of discussion and no alternative exists. -- It must be presented in a respectful manner. -- Attendees must be warned in advance and respectfully given plenty of warning and the opportunity to leave beforehand. -- This exception specifically does not allow the use of gratuitous sexual images as a device to grab attention or for unnecessary examples. - -Thank you - -This document was based on the [Sheffield Digital Code of Conduct](https://sheffield.digital/events/meetup-code-of-conduct/), which in turn is based on the work of JSConf, Geek Feminism, confcodeofconduct.com, and inspired by resources provided by Ashe Dryden. +### Eventbrite +### Facebook Messenger -Licensed under a Creative Commons Attribution 3.0 Unported License. -Version 1 +### Hotjar -This is version 1 of the CodeWith Code of Conduct. It was last updated by Simon Davey on 31 August 2020. If you think we have made any errors or omissions, please contact us by email ([contact@codewith.org.uk](mailto:contact@codewith.org.uk)) or through one of the communication channels listed on the [contact page](contact.html). +### Google Analytics \ No newline at end of file From 7cec334e00ace9a2930cdd2cd06dbf57ac519dc9 Mon Sep 17 00:00:00 2001 From: Keiran Wilkinson Date: Fri, 27 Aug 2021 19:12:42 +0100 Subject: [PATCH 06/11] Remove a rogue media query --- css/style.css | 1 - 1 file changed, 1 deletion(-) diff --git a/css/style.css b/css/style.css index 43a5973..94ba2ff 100644 --- a/css/style.css +++ b/css/style.css @@ -533,7 +533,6 @@ div.event-book-button { } } -@media screen and (min-width: 992px) { /*Cookie Notice*/ #cookie-notice { From 55240847ad37f74657b886f524d97a024816778b Mon Sep 17 00:00:00 2001 From: Keiran Wilkinson Date: Fri, 27 Aug 2021 19:14:56 +0100 Subject: [PATCH 07/11] Adding a media query that was removed by accident back in --- css/style.css | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/css/style.css b/css/style.css index 94ba2ff..6a57b56 100644 --- a/css/style.css +++ b/css/style.css @@ -533,6 +533,14 @@ div.event-book-button { } } +@media screen and (min-width: 992px) { + .masthead, + .mastfoot, + .cover-container { + width: 700px; + } +} + /*Cookie Notice*/ #cookie-notice { From 61297e52d72c4fef6d090bcfca7b7b32835ca71c Mon Sep 17 00:00:00 2001 From: Keiran Wilkinson Date: Fri, 27 Aug 2021 19:15:59 +0100 Subject: [PATCH 08/11] Reorganise stylesheet --- css/style.css | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/css/style.css b/css/style.css index 6a57b56..43d7086 100644 --- a/css/style.css +++ b/css/style.css @@ -533,14 +533,6 @@ div.event-book-button { } } -@media screen and (min-width: 992px) { - .masthead, - .mastfoot, - .cover-container { - width: 700px; - } -} - /*Cookie Notice*/ #cookie-notice { @@ -571,4 +563,12 @@ div.event-book-button { position: relative; bottom: 4px; } +} + +@media screen and (min-width: 992px) { + .masthead, + .mastfoot, + .cover-container { + width: 700px; + } } \ No newline at end of file From 40a0bf3310860e924f4eabd343782e964579cb5a Mon Sep 17 00:00:00 2001 From: Keiran Wilkinson Date: Fri, 27 Aug 2021 19:23:49 +0100 Subject: [PATCH 09/11] Adding first draft of privacy policy --- privacy.md | 85 +++++++++++++++++++++++++++++++++++++++++++++--------- 1 file changed, 71 insertions(+), 14 deletions(-) diff --git a/privacy.md b/privacy.md index 4a4781d..ece055d 100644 --- a/privacy.md +++ b/privacy.md @@ -11,24 +11,81 @@ title: Code of Conduct --- # Privacy Policy +## Services -CodeWith wants to be a friendly community where everyone feels welcome and safe at meetups and events. +Welcome to CodeWith! We are a community of programmers at all levels from beginner to experienced software architect. Through our GitHub-hosted web site, Slack workspace, Discord server, Eventbrite account, and Google account, we enable and support people all over the world to share experiences, learn how to code, and help others. The various tools we use and events we host, including but not limited to the aforementioned GitHub, Slack, Discord, Eventbrite, and Google accounts, are collectively referred to as our "Services". -The aim of this policy is to protect privacy whilst enhancing your experience using contact tools and providing CodeWith with analytics to improve the website. +Privacy Policies for each external service are available here: -## Summary +GitHub: [Privacy Policy](https://docs.github.com/en/github/site-policy/github-privacy-statement) -CodeWith uses the below tools to enhance the user experience -* Eventbrite -* Facebook Messenger +Slack: [Privacy Policy](https://slack.com/intl/en-gb/trust/privacy/privacy-policy) -CodeWith uses the below tools to gather anonymous analytics -* Hotjar -* Google Analytics -## The details -### Eventbrite -### Facebook Messenger +Discord: [Privacy Policy](https://discord.com/privacy) -### Hotjar +Eventbrite: [Privacy Policy](https://www.eventbrite.co.uk/support/articles/en_US/Troubleshooting/eventbrite-privacy-policy?lg=en_GB) -### Google Analytics \ No newline at end of file +Google: [Privacy Policy](https://policies.google.com/privacy?hl=en-US) + +Facebook: [Privacy Policy](https://www.facebook.com/policy.php) + +## Who's Who + +When this Privacy Policy uses the term "Organiser" we mean any of our mentors and volunteers running, hosting, or helping out with our various events and workshops, or anyone with administrator-level access to the Services. Any parties consuming information from or interacting with tools and documents provided using our Services are referred +to in these Terms collectively as "Users". + +CodeWith is a collection of mentors and volunteers, with its principal address being ________. + + +## Privacy Statement +This Privacy Policy sets forth our policy with respect to information that can be associated with or which relates to a person and/or could be used to identify a person ("Personal Data") that is collected from Users on or through the Services. We take the privacy of your Personal Data seriously. Because of that, we have created this Privacy Policy. Please read this Privacy Policy as it includes important information regarding your Personal Data and other information. + +"Non-Personal Data" as used in this Privacy Policy is therefore any information that does not relate to a person and/or cannot be used to identify a person. When you interact with the Services, we may collect Non-Personal Data. The limitations and requirements in this Privacy Policy on our collection, use, disclosure, transfer and storage/retention of Personal Data do not apply to Non-Personal Data. + +The Organisers try to limit collection of Users' Personal Data, but a small amount of data is necessary to provide the community chat workspace/servers and events. These include: + +* Names (partial or full): These are voluntarily provided for use on Slack and Discord. +* Email addresses: These are required by Eventbrite to allocate tickets through their services. +* Facebook profile link: This may be provided by using the Facebook Messenger button on the web site. +* Any other information that Users choose to provide and/or that enables Users to be personally identified. + +## How We Use Your Personal Data +We collect and use the Personal Data we collect in a manner that is consistent with this Privacy Policy, and applicable privacy laws. We may use the Personal Data as follows: +### For Specific Reasons +If you provide Personal Data for a certain purpose, we may use the Personal Data in connection with the purpose for which it was provided. For instance, if you contact us by email, we will use the Personal Data you provide to answer your question or resolve your problem and will respond to the email address from which the contact came. + +### Access and Use +If you provide Personal Data in order to obtain access to or use of the Services or any functionality thereof, we will use your Personal Data to provide you with access to or use of the Services or functionality. +### Internal Business Purposes +We may use your Personal Data for internal business purposes, including without limitation, to help us improve the content and functionality of the Services, to better understand our Users, to improve the Services, to protect against, identify or address wrongdoing, and to generally manage the Services and our community. +### Organiser Emails +We allow Organisers to use our email tools to contact Users for current and past events, so you may receive emails originating with Organisers. If you registered for an event on the Services, your email address is available to the Organisers. However, Organisers may also import the email addresses they have from external sources and send communications through the Services to those email addresses. +### Use of Interest-Based Data + +We encourage Users to fill in forms from time to time, and there may be occasions on which an Organiser requests that the form only be filled in once. In this case, a User's Google Account details may be collected. +### Other Purposes +If we intend to use any Personal Data in any manner that is not consistent with this Privacy Policy, you will be informed of such anticipated use prior to or at the time the Personal Data is collected or we will obtain your consent subsequent to such collection but prior to such use. +## Data Disclosure And Transfer +We will never disclose, transfer, share, sell, or otherwise give your Personal Data to third parties without further notice to and agreement by you. +### Social Media and Other Third Party Connections +In "Liking" or "Following" CodeWith on Social Media, including but not limited to Facebook, Instagram, Twitter, and LinkedIn (to the extent we provide that capability), we may collect some information from you including your name, email address, and any comments or content you post relevant to us. We likewise may collect your information if you submit information to us through social media sites. + +#### Facebook Plug-Ins and Links on Our Pages +CodeWith's own website contains a widget which connects Users to us through Facebook Messenger. When you interact with this feature, your browser will establish a direct link with the Facebook servers, and Facebook will receive information about your browser and activity, and may link it to your Facebook user account. For more information about how Facebook uses data, please see Facebook's own policies (linked above). + +### Legal Requirements +We may disclose your Personal Data if required to do so by law in order to (for example) respond to a subpoena or request from law enforcement, a court or a government agency (including in response to public authorities to meet national security or law enforcement requirements), or in the good faith belief that such action is necessary to +comply with a legal obligation, +protect or defend our rights, interests or property or that of third parties, +prevent or investigate possible wrongdoing in connection with the Services, +act in urgent circumstances to protect the personal safety of Users of the Services or the public, or +protect against legal liability. + +### How We Store Your Personal Data +We may store Personal Data itself or such information may be stored by third parties to whom we have transferred it in accordance with this Privacy Policy. We take what we believe to be reasonable steps to protect the Personal Data collected via the Services from loss, misuse, unauthorised use, access, inadvertent disclosure, alteration and destruction. However, no network, server, database or Internet or email transmission is ever fully secure or error free. Therefore, you should take special care in deciding what information you send to us electronically. Please keep this in mind when disclosing any Personal Data. + +## How You Can Access, Update, Correct, or Delete Your Personal Data +You can request a copy of any and all Personal Data stored by Organisers at any time by emailing us at contact@codewith.org.uk and we will endeavour to provide said information in a reasonable time.However, if that Personal Data is stored by another company as a result of your use of our Services its deletion may be beyond our abilities and/or control and you may have to request deletion by contacting the third party that runs said service. For example, we may not be able to remove your email address from Eventbrite ourselves and it would be the responsibility of the User to contact Eventbrite and request removal of the Personal Data in accordance with their policies. + +## Exclusions +This Privacy Policy does not apply to any Personal Data that you provide to another User or visitor through the Services or through any other means, including to Organisers on event pages or information posted by you to any public areas of the Services. \ No newline at end of file From d54481cde0b2ad015def27dbd59965342f027939 Mon Sep 17 00:00:00 2001 From: Keiran Wilkinson Date: Fri, 27 Aug 2021 19:25:13 +0100 Subject: [PATCH 10/11] Adds hotjar privacy policy --- privacy.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/privacy.md b/privacy.md index ece055d..e1139e7 100644 --- a/privacy.md +++ b/privacy.md @@ -29,6 +29,8 @@ Google: [Privacy Policy](https://policies.google.com/privacy?hl=en-US) Facebook: [Privacy Policy](https://www.facebook.com/policy.php) +Hotjar [Privacy Policy](https://www.hotjar.com/legal/policies/privacy/) + ## Who's Who When this Privacy Policy uses the term "Organiser" we mean any of our mentors and volunteers running, hosting, or helping out with our various events and workshops, or anyone with administrator-level access to the Services. Any parties consuming information from or interacting with tools and documents provided using our Services are referred From a79d82e245d14870889f9e1bc913dae07d5c5368 Mon Sep 17 00:00:00 2001 From: Keiran Wilkinson Date: Fri, 27 Aug 2021 19:25:38 +0100 Subject: [PATCH 11/11] Missing colon --- privacy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/privacy.md b/privacy.md index e1139e7..0b8fb67 100644 --- a/privacy.md +++ b/privacy.md @@ -29,7 +29,7 @@ Google: [Privacy Policy](https://policies.google.com/privacy?hl=en-US) Facebook: [Privacy Policy](https://www.facebook.com/policy.php) -Hotjar [Privacy Policy](https://www.hotjar.com/legal/policies/privacy/) +Hotjar: [Privacy Policy](https://www.hotjar.com/legal/policies/privacy/) ## Who's Who