Cookies
A cookie lets a website recognise your device and store some information about your preferences or interactions.
Why we use cookies
We use propertyfactorregister.gov.scot cookie tracking data to make informed decisions on whether the site is meeting your needs, which leads to us making improvements. For example, we monitor how much traffic each part of the site gets and work to improve areas which are not being found when they should be.
Turn cookies on or off
Cookies needed for the website to work
These cookies do things like keep the website secure. They always need to be on.
Google Analytics
We use Google Analytics to collect information about how you use propertyfactorregister.gov.scot.
We store information about:
- the pages you visit and how long you spend on each page
- how you got to propertyfactorregister.gov.scot
- what you click on while you’re visiting propertyfactorregister.gov.scot
We do not:
- collect information that can be used to identify you; for example, we never receive your name or address
- make any attempt to find out the identities of people visiting propertyfactorregister.gov.scot
- allow the tools that we use to find out the identities of people visiting propertyfactorregister.gov.scot
- sell, trade or give your details to third parties, unless we are required to do it by law
All information we get through cookies and analytics will be treated in confidence.
Find out more about security and privacy in Google Analytics.
You can opt out of Google analytics cookies.
| Cookie name | Description | Expiry time |
|---|---|---|
| _ga | This is used to understand and differentiate between different users. | 2 years |
| _ga_* | Used to collect data on the number of times you have visited a site, as well as dates of your first and most recent visit. | 2 years |
| _gid | _gid has a different ID for each page set on, and a timestamp. This assists with plotting user journeys. | 24 hours |
| _gat_UA-* | Used to reduce the number of requests to Google. | 1 minute |
Hotjar
Hotjar is used to better understand user behaviour as they interact with our sites such as user journey recording and feedback widgets.
Features set by Hotjar:
- screen recording
- heatmap
| Cookie name | Description | Expiry time |
|---|---|---|
| _hjAbsoluteSessionInProgress | This cookie is used to count how many times different users visit the site. It assigns the users an ID, so the user does not get registered twice. This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie. | 30 minutes |
| _hjSessionUser_* | This cookie is set when a user first lands on a page with the Hotjar script. It's used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behaviour in subsequent visits to the same site will be attributed to the same user ID. | 1 year |
| _hjIncludedInSessionSample_* | This cookie lets Hotjar know whether your current visit is included in data sampling. | TBC |
| _hjSession_* | This cookie holds the current session data. This makes sure that subsequent requests within the session window will be attributed to the same Hotjar session. It expires after 30 minutes. | 30 minutes |
| _hjFirstSeen | Tells Hotjar if this is the first time you have visited the site. | Session |