Who we are. What personal data we collect and why we collect it
This is the web site of the foundation Stichting LOVEFREQUENCIES – KvK nummer 72509015. Our website address is: https://www.lovefrequencies.org.
Comments
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.
An anonymised string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.
Media
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.
Contact forms
We use two kinds of contact forms:
1 the contact form named “Subscribe our newsletter” (please find here an example), by which we collect data only to send newsletters, and which does not require an additional consent checkbox;
2 the contact form for general enquiries (please see here an example), which clearly requests the user’s explicit consent (mandatory field) in accordance with GDPR compliance.
Cookies
If you leave a comment on our website, 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 have an account and you log in to this website, 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.
Please read here how Google uses cookies
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.
These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.
Analytics
This site use Google Analytics.
You can read here how Google is committed to complying with applicable laws concerning data protection.
Please read below how Google Analytics uses cookies to measure user-interactions on websites.
Overview
Google Analytics is a simple, easy-to-use tool that helps website owners measure how users interact with website content. As a user navigates between web pages, Google Analytics provides website owners JavaScript tags (libraries) to record information about the page a user has seen, for example the URL of the page. The Google Analytics JavaScript libraries use HTTP Cookies to “remember” what a user has done on previous pages / interactions with the website.
Google Analytics supports three JavaScript libraries (tags) for measuring website usage: gtag.js, analytics.js, and ga.js. The following sections describe how each use cookies.
gtag.js and analytics.js – cookie usage
The analytics.js JavaScript library is part of Universal Analytics and uses first-party cookies to:
- Distinguish unique users
- Throttle the request rate
When using the recommended JavaScript snippet, gtag.js and analytics.js set cookies on the highest level domain they can. For example, if your website address is blog.example.co.uk, analytics.js will set the cookie domain to .example.co.uk. Setting cookies on the highest level domain possible allows users to be tracked across subdomains without any extra configuration.
gtag.js and analytics.js set the following cookies:
| Cookie Name | Expiration Time | Description |
|---|---|---|
_ga |
2 years | Used to distinguish users. |
_gid |
24 hours | Used to distinguish users. |
_gat |
1 minute | Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>. |
AMP_TOKEN |
30 seconds to 1 year | Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service. |
_gac_<property-id> |
90 days | Contains campaign related information for the user. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more. |
Customization
Read the analytics.js Domains & Cookies developer guide to learn all the ways these default settings can be customized.
Read the Security and privacy in Universal Analytics document for more information about Universal Analytics and cookies.
ga.js – cookie usage
The ga.js JavaScript library uses first-party cookies to:
- Determine which domain to measure
- Distinguish unique users
- Throttle the request rate
- Remember the number and time of previous visits
- Remember traffic source information
- Determine the start and end of a session
- Remember the value of visitor-level custom variables
By default, this library sets cookies on the domain specified in the document.host browser property and sets the cookie path to the root level (/).
This library sets the following cookies:
| Cookie Name | Default Expiration Time | Description |
|---|---|---|
__utma |
2 years from set/update | Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics. |
__utmt |
10 minutes | Used to throttle request rate. |
__utmb |
30 mins from set/update | Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics. |
__utmc |
End of browser session | Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit. |
__utmz |
6 months from set/update | Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics. |
__utmv |
2 years from set/update | Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics. |
Customization
The following methods can be used to customize how cookies are set:
_setDomainName– Sets the domain to which all cookies will be set._setCookiePath– Sets the path to which all cookies will be set._setVisitorCookieTimeout– Sets the Google Analytics visitor cookie expiration in milliseconds._setSessionCookieTimeout– Sets the new session cookie timeout in milliseconds._setCampaignCookieTimeout– Sets the campaign tracking cookie expiration time in milliseconds._storeGac– Pass infalseto disable the GAC cookie. Defaults totrue
Read the Tracking Multiple Domains guide to learn how to configure ga.js to measure user interaction across domains.
urchin.js – cookie usage
Historically, Google Analytics provided a JavaScript measurement library named urchin.js. When the newer ga.js library launched, developers were encouraged to migrate to the new library. For sites that have not completed the migration, urchin.js sets cookies identically to what is set in ga.js. Read the ga.js cookie usage section above for more details.
Google Analytics for Display Advertisers – cookie usage
For customers that are using Google Analytics’ Display Advertiser features, such as remarketing, a third-partyDoubleClick cookie is used in addition to the other cookies described in this document for just these features. For more information about this cookie, visit the Google Advertising Privacy FAQ.
Content Experiments – cookie usage
For websites using Google Analytics content experiments, the following cookies are used for these features in addition to the other cookies described in this document:
| Cookie Name | Expiration Time | Description |
|---|---|---|
__utmx |
18 months | Used to determine a user’s inclusion in an experiment. |
__utmxx |
18 months | Used to determine the expiry of experiments a user has been included in. |
Optimize 360 – cookie usage
For websites using Optimize 360, the following cookie is used in addition to the other cookies described in this document:
| Cookie Name | Expiration Time | Description |
|---|---|---|
_gaexp |
Depends on the length of the experiment but typically 90 days. | Used to determine a user’s inclusion in an experiment and the expiry of experiments a user has been included in. |
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.
Send a request of removal your personal data to [email protected] with “Erase Personal Data” in object.
Where we send your data
Visitor comments may be checked through an automated spam detection service.
