Who we are
Our website address is: https://cerg.scot.
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 anonymized 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.
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.
Who we share your data with
If you request a password reset, your IP address will be included in the reset email.
How long we retain your data
If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize 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 your data is sent
Visitor comments may be checked through an automated spam detection service.
Cookie Policy
Essential
Essential cookies enable basic functions and are necessary for the proper function of the website.
| Cookie ID | Purpose | Duration |
|---|
| wpconsent_preferences | This cookie is used to store the user's cookie consent preferences. | 30 days |
CloudFlare
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Learn more| Cookie ID | Purpose | Duration |
|---|
| cf_use_ob | The cf_use_ob cookie informs Cloudflare to fetch the requested resource from the Always Online cache on the designated port. Applicable values are: 0, 80, and 443. The cf_ob_info and cf_use_ob cookies are persistent cookies that expire after 30 seconds. | session |
| __cfwaitingroom | The __cfwaitingroom cookie is only used to track visitors that access a waiting room enabled host and path combination for a zone. Visitors using a browser that does not accept cookies cannot visit the host and path combination while the waiting room is active. | session |
| cf_chl_rc_i | These cookies are for internal use which allows Cloudflare to identify production issues on clients. | session |
| cf_chl_rc_ni | These cookies are for internal use which allows Cloudflare to identify production issues on clients. | session |
| cf_chl_rc_m | These cookies are for internal use which allows Cloudflare to identify production issues on clients. | session |
| __cfruid | Used by the content network, Cloudflare, to identify trusted web traffic. | session |
| __cf_bm | Cloudflare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions. | session |
| __cflb | When enabling session affinity with Cloudflare Load Balancer, Cloudflare sets a __cflb cookie with a unique value on the first response to the requesting client. Cloudflare routes future requests to the same origin, optimizing network resource usage. In the event of a failover, Cloudflare sets a new __cflb cookie to direct future requests to the failover pool. | session |
| _cfuvid | The _cfuvid cookie is only set when a site uses this option in a Rate Limiting Rule, and is only used to allow the Cloudflare WAF to distinguish individual users who share the same IP address. | session |
| cf_clearance | Whether a CAPTCHA or Javascript challenge has been solved. | session |
| __cfseq | Sequence rules uses cookies to track the order of requests a user has made and the time between requests and makes them available via Cloudflare Rules. This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies. | session |
| cf_ob_info | The cf_ob_info cookie provides information on: The HTTP Status Code returned by the origin web server. The Ray ID of the original failed request. The data center serving the traffic | session |
Statistics
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Learn more| Cookie ID | Purpose | Duration |
|---|
| _gac_ | Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together. | 90 days |
| __utma | ID used to identify users and sessions | 2 years after last activity |
| __utmt | Used to monitor number of Google Analytics server requests | 10 minutes |
| __utmb | Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server. | 30 minutes after last activity |
| __utmc | Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session. | End of session (browser) |
| __utmz | Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server | 6 months after last activity |
| __utmv | Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server. | 2 years after last activity |
| __utmx | Used to determine whether a user is included in an A / B or Multivariate test. | 18 months |
| _ga | ID used to identify users | 2 years |
| _gali | Used by Google Analytics to determine which links on a page are being clicked | 30 seconds |
| _ga_ | ID used to identify users | 2 years |
| _gid | ID used to identify users for 24 hours after last activity | 24 hours |
| _gat | Used to monitor number of Google Analytics server requests when using Google Tag Manager | 1 minute |
