Privacy and Cookie policy

Privacy Policy

realityhouse is committed to protecting and respecting your privacy.

This policy (together with our terms of use and any other documents referred to in it) sets out the basis on which any personal data we collect from you, or that you provide to us, will be processed by us.

Please read the following carefully to understand our views and practices regarding your personal data and how we will treat it. By visiting www.realityhouse.co.uk (our “site”) you are accepting and consenting to the practices described in this policy.

For the purpose of the Data Protection Act 1998 (the “Data Protection Act“), the data controller is realityhouse Limited whose registered office is at 6 Monmouth Place, Bath BA1 2AU. Our Data Protection registration no. is Z8304135.

Information we may collect from you

We may collect and process the following data about you:

Information you give us. You may give us information about you by filling in forms on our site or by corresponding with us by phone, e-mail or otherwise. This includes information you provide when you enter details on our site (for example, via our enquiry function), requesting our services or newsletters or if you report a problem with our site. The information you give us may include your name, address, company and e-mail address.
Information we collect about you. With regard to each of your visits to our site we may automatically collect the following information:

  • technical information, including the Internet protocol (IP) address used to connect your computer to the Internet, your login information (if applicable), browser type and version, time zone setting, browser plug-in types and versions, operating system and platform; and information about your visit, including the full Uniform Resource Locators (URL) clickstream to, through and from our site (including date and time), services you viewed or searched for, page response times, download errors, length of visits to certain pages, page interaction information (such as scrolling, clicks, and mouse-overs), and methods used to browse away from the page.

Cookies

What are cookies?

Our website uses cookies. A cookie is a small text file which is stored on your computer, tablet or phone when you visit a website. These cookies allow us to distinguish you from other users of our website. This helps us to provide you with a good experience when you browse our website and also allows us to improve our website.

There are two main types of cookie:

  • session cookies—these are deleted when you finish browsing a website and are not stored on your computer longer than this
  • persistent cookies—these are stored on your computer after you have finished using a website so that the website provider can remember your preferences the next time you use it

Cookies can be set by the website you have browsed, i.e. the website displayed in the uniform resource locator (URL) window. These are called first party cookies. Third party cookies are set by a website other than the one you are browsing.

To find out more about cookies, including how to see what cookies have been set and how to manage and delete them, visit www.allaboutcookies.org.

How do we use cookies?

The table below shows what cookies we use and why.

ServiceCookie NameDescriptionExpiration Time
Google Analytics gtag.js and analytics.js_gaUsed to distinguish users.2 years
_gidUsed to distinguish users.24 hours
_gatUsed to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>.1 minute
AMP_TOKENContains 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.30 seconds to 1 year
_gac_<property-id>Contains campaign related information for the user. If you have linked your Google Analytics and AdWords accounts, AdWords website conversion tags will read this cookie unless you opt-out.90 days
Google Analytics ga.js__utmaUsed 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.2 years from set/update
__utmtUsed to throttle request rate.10 minutes
__utmbUsed to determine new sessions/visits. The cookie is created when the javascriptlibrary executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics.30 mins from set/update
__utmcNot used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmbcookie to determine whether the user was in a new session/visit.End of browser session
__utmzStores 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.6 months from set/update
__utmvUsed 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.2 years from set/update
Google MapsNID, OGPC, APISIDThese cookies are used by Google to store user preferences and information when viewing pages with Google maps on them.From 1 month to 6 months
Google1P_JAR, CONSENT, APISD, HSID, S, SIDCC, NID, SIDGoogle uses these cookies, based on recent searches and interactions, to customise ads on Google websites.From 1 month to 20 years
DV, UULEThese cookies are used by Google to collect information about how visitors use our site.1 day
OTZA cookie used by Google Analytics that provides an aggregate analysis of Website visitors1 week
PHP SystemPHPSESSIDThis cookie contains information that identifies the user and is destroyed when the session expires.Session
HotjarhjClosedSurveyInvitesThis cookie is set once a visitor interacts with a Survey invitation modal pop-up. It is used to ensure that the same invite does not re-appear if it has already been shown.1 Year
_hjDonePollsThis cookie is set once a visitor completes a Poll using the Feedback Poll widget. It is used to ensure that the same Poll does not re-appear if it has already been filled in.1 Year
_hjMinimizedPollsThis cookie is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site.1 Year
_hjDoneTestersWidgetsThis cookie is set once a visitor submits their information in the Recruit User Testers widget. It is used to ensure that the same form does not re-appear if it has already been filled in.1 Year
_hjMinimizedTestersWidgetsThis cookie is set once a visitor minimizes a Recruit User Testers widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site.1 Year
_hjDoneSurveysThis cookie is set once a visitor completes a survey. It is used to only load the survey content if the visitor hasn’t completed the survey yet.1 Year
_hjIncludedInSampleThis session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate Heatmaps, Funnels, Recordings, etc.1 Year
_hjShownFeedbackMessageThis cookie is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if they navigate to another page where it is set to show.1 Year
Twitter_ga, _gid, lang, kdt,
syndication_guest_id, dnt, guest_id,
personalization_id, twid, netpu, guest_id,
tfw_exp, remember_checked_on,
twitter_ads_id, co, auth_token
These are Twitter cookies that are used on websites with Twitter feeds and / or Twitter sharing functionalities. For more information, please see https://help.twitter.com/en/rules-and-policies/twitter-cookiesFrom session duration to 2 years
LinkedInli_oatml, lidc, bcookie, __utma, VID, ELOQUA, _ga, liap, _guid, _liptUsed by the social networking service, LinkedIn, for tracking the use of embedded services.From Session to 2 years
LinkedIn AdslangRemembers the user’s selected language version of a websiteSession
BizoIDThe BizoID cookie stores a unique LinkedIn user ID.
Note: The LinkedIn user ID does not contain personally identifiable information.
90 days
BizoUserMatchHistoryThis cookie stores the last time cookie IDs were synced with a given authorized network partner and is part of LinkedIn’s server-to-server data integration solution.90 days
BizoDataThe BizoData cookie stores anonymous business demographic profile data for the user. Business demographic data may include anonymous codes for business demographics such as company size, industry, job function, or seniority level, but will not include any personally identifiable information.90 days
BizographicsOptOutThe BizographicsOptOut cookie tracks if the user has opted out of LinkedIn tracking.90 days
BizoNetworkPartnerIndexBizographic information generated from authorized LinkedIn Data Provider accounts is shared with authorized third party network partners. This cookie tracks which network partners have received data for a given user.90 days
UserMatchHistoryunclassified179 days
Facebookpl, c_user, act, fr, wd, xs, presence, sb, lu, spin, dprThese cookies are used for re-targeting, optimisation, reporting and attribution of online advertsFrom session to 10 years
datrA Facebook cookie that monitors your Facebook account for suspicious behaviour such as failed login attempts or attempts to create spam accounts
YouTubeVISITOR_INFO1_LIVE, YSC,
LOGIN_INFO, APISID, CONSENT, HSID
SAPISID, SID, SSID, PREF, NID
These cookies are set as a result of embedded YouTube videos. They help register anonymous data on usage.

For more information, read the general Google Privacy policy.

From session duration to 20 years
DoubleClickDSID, IDE, _drt_, id, __sonar, _dpm_id.5467These cookies are used for re-targeting, optimisation, reporting and attribution of online advertsFrom 2 days to 2 months
cookie_notice_acceptedThis cookie enables you to accept our cookie statement once every year.1 year
WordPresswp-settings-, wp-settings-time
Used to customize the view of admin interface/main site interface for logged in users.
2 weeks
wordpress_test_cookieChecks if cookies are enabled to provide appropriate user experience.Session
wordpress_logged_in_Checks whether or not the current visitor is a logged in WordPress.com user.Session
wordpress_sec_Essential WordPress session management cookies for logged in users.Session
itsec-hb-login-*Set by WP Security Plugin to change the backend login URL for additional security.Session
Vimeo__utma, _utmz, _utmc, has_logged_in, has_uploaded, is_logged_in, _ga, __qca, _ceg.s, _ceg.u, __ssidVarious cookies set by Vimeo and it’s third parties for tracking and video player performance. For more information visit https://vimeo.com/cookie_policyFrom 3 months to 12 years
site_settingsSite browsing preferences58 years
continuous_play_v3Used to keep track of whether continuous play is on or not for a user3 months
_abexpsCookie set by Vimeo for A/B testing purposes- for testing multiple versions of a feature.1 year
playerStores the preferences of the Vimeo video player.1 year
vuidVimeo analytics unique identifier2 years
optimizelyEndUserId, optimizelyBuckets, optimizelyEndUserId, optimizelySegmentsThe cookies are placed by a third party, Optimizely. They hold short alphanumeric string values to store page variant and experiment data. The cookies do not store any personally identifiable information. Read more information here.10 years
AppNexusanj, usersyncThese cookies contain data denoting whether a cookie ID is synced with AppNexus partners. Read more information.90 days
icuThe icu cookie is used to select ads and limit the number of times a user sees a particular ad.90 days
uuid2This cookie is used to help deliver ads to people who have previously visited our websites, purchased our products or used our apps and to recommend products and services based on that activity.90 days
sessIt is used by the Platform to test whether a browser is configured to accept cookies from AppNexus.Session
scorecardresearch.comUID, UIDR, CP1The UID cookie is associated with comScore; these are used to get 3rd party measurement of audience size.2 years
AlbacrossnQ_cookieId, nQ_visitId, _ga, intercom-id-ez7jrn1fTracking for business IP address lock-up provided by 3rd-party called Albacross for lead classification2 years to 70 years
Addthis.comuvc, cw_id, na_id, loc, ouid, ssc, bku, na_tc, sshs, __atuvc, uid, ssh, km_lv, kvcd, km_vs, mus, na_id, _gid, upsThese cookies are used to track usage of the Addthis.com service. Addthis allows the user to share a webpage with many social sites. You can opt out of AddThis cookies from all websites here.From 90 days to 256 days
Advertising.comASCID, ACID, JEB2, APID, IDSYNC, UMAP, GUID, FC, F1 CS1, DOMSYNCAOL Advertising Inc. is a wholly-owned subsidiary of AOL Inc., integrating AOL’s leading media properties, targeted marketing technology, and Advertising.com’s mass reach into a unified solution for advertisers and publishers. The cookie is used to target advertising.​​​​​​​From 1 – 2 years
Adrolladroll_mb, ajs_group_id, _cio, __utma, _hp2_props.*, _hp2_id.*, _hp2_ses_props.*, _ga, ajs_user_id, _vwo_uuid_v2, __zlcmid, ajs_anonymous_idThese cookies are used by Adroll and it’s third parties to serve personalised re-targeting ads. Opt out of receiving personalised ads served by Adroll here.From session to 10 years
optimizelyEndUserId, optimizelyBuckets, optimizelyEndUserId, optimizelySegmentsThe cookies are placed by a third party, Optimizely. They hold short alphanumeric string values to store page variant and experiment data. The cookies do not store any personally identifiable information. Read more information here.10 years
csrftokenHelps prevent Cross-Site Request Forgery (CSRF) attacks.1 year
mkto_trkThis cookie is associated with an email marketing service provided by Marketo. This tracking cookie allows a website to link visitor behaviour to the recipient of an email marketing campaign, to measure campaign effectiveness.2 years
CANDDi_CAN_Bld, CAN_FCld, CAN_SldUser and session identifier cookiesFrom 30minutes to 10 years
HubSpot__hs_opt_out
This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again. This cookie is set when you give visitors the choice to opt out of cookies.
2 years
__hs_do_not_track
This cookie can be set to prevent the tracking code from sending any information to HubSpot. Setting this cookie is different from opting out of cookies, which still allows anonymized information to be sent to HubSpot.
2 years
__hs_testcookieThis cookie is used to test whether the visitor has support for cookies enabled.Session
hs_ab_testThis cookie is used to consistently serve visitors the same version of an A/B test page that they’ve seen before.Session
hs_lang_switcher_choiceThis cookie is used to consistently redirect visitors to the language version of a page in the language they’ve selected on this top-level private domain in the past (if such a language version exists).
<id>_keyWhen visiting a password-protected page, this cookie is set so future visits to the page from the same browser do not require login. The cookie name is unique for each password-protected page.
hs-messages-is-open (TTL 30 minutes)This cookie is used on the visitor UI side so HubSpot can determine/save whether the chat widget is open for future visits. It resets after 30 minutes to re-close the widget after 30 minutes of inactivity30 minutes
hs-messages-hide-welcome-message (TTL 1 day)When you dismiss the welcome message in your messages tool, a cookie is set to prevent it from appearing again for one day.
__hstcThe main cookie for tracking visitors. It contains the domain, utk (see below), initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).2 years
hubspotutkThis cookie is used for to keep track of a visitor’s identity. This cookie is passed to HubSpot on form submission and used when de-duplicating contacts.10 years
__hsscThis cookie keeps track of sessions. This is used to determine if we should increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each pageView in a session), and session start timestamp.30 minutes
__hssrcWhenever HubSpot changes the session cookie, this cookie is also set. We set it to 1 and use it to determine if the visitor has restarted their browser. If this cookie does not exist when we manage cookies, we assume it is a new session.Session
messagesUtkThis cookie is used to recognize visitors who chat with you via the messages tool. If the visitor leaves your site before they’re added as a contact, they will have this cookie associated with their browser. If you have a history of chatting with a visitor and they return to your site later in the same cookied browser, the messages tool will load your conversation history with that visitor.
Bidswitch.netcRegulates synchronisation of user identification and exchange of user data between various ad services.1 year
tuuidRegisters whether or not the user has consented to the use of cookies1 year
tuuid_luUnclassified1 year
tuuid_last_updateUnclassified2 years
3lift.comtluid, tlcookieableUnclassified3 months
Casalemedia.comCMDD, CMST, CMPS, CMID, CMSUM, CMSC, CMRUM3, CMPROCollects anonymous data related to the user’s visits to the website, such as the number of visits, average time spent on the website and what pages have been loaded, with the purpose of displaying targeted ads.From session to 1 year
Openx.neti, pd, p_syncedRegisters anonymised user data, such as IP address, geographical location, visited websites, and what ads the user has clicked, with the purpose of optimising ad display based on the user’s movement on websites that use the same ad network.From 1 month to 1 year
Outbrain.comobuidHolds the anonymous user’s ID. Used for tracking user actions, such as clicks on the recommendations3 months
_ofcap_DOC1Used for Frequency capping7 days
ttd, criteo, mdfrc, cdws, _utastes_1, adrl, rcktfl, apnxsUnclassifiedFrom 1 month to 1 year
Rubiconproject.comrpx, rpx_*,Contains expiration dates for information in the rpb cookie.
put_*Bidder identifiers placed at the request of a bidder, to sync a bidder’s independent information about an end user with Rubicon Project, to allow the bidder (not Rubicon Project) to bid on ads through the Rubicon Project advertising exchange based on behavioral targeting information known only to the bidder (i.e., the user identifier will be transmitted in a bid request to the bidder that caused this cookie to be placed).Various
cdIndicates whether cookies are disabled for the device.
khaosInternal user identifier used for analytics.
ses*Indicates number of times Rubicon Project has served a user an advert for this particular unit of inventory.
vis*Indicates number of times a user action has precipitated an ad request for this particular unit of inventory.
auditUsed to record cookie consent data.
rlcdn.comrtn1-z, rlas3, ck1, pxrcCollects anonymous data related to the user’s visits to the website, such as the number of visits, average time spent on the website and what pages have been loaded, with the purpose of displaying targeted ads.From 2 months to 60 days
taboola.comtaboola_usg, taboola_vmp, tbp-consent, _mkto_trk, _gid, _ga, stpt, d_id, t_gid, taboola_mk, __cfduid, uetsid, ga_cidThese cookies are used for analytics and advertising services.
SoundCloudsc_anonymous_idunclassified10 years
Pubmatic.comKTPCACOOKIE, KRTBCOOKIE_*, pp, pubretarge, syncRTB2, _gid, PugT, PMDTSHR, _ga, SpugT, __gads, Pubmdcid, KADUSERCOOKIE,Traces the user to offer customised advertising of interest to the user on FacebookFrom 1 day to 3 years

Consent

If you continue to use our website we will assume that you are happy to receive all cookies from our website. However, if you would prefer to change your cookie settings, you can do so at any time—see below ‘Controlling our use of cookies’.

Controlling our use of cookies

Most browsers automatically accept cookies unless you change your internet browser settings. If you wish to restrict, block or delete the cookies which are set by any websites, you can generally do this through your browser settings. These settings are usually found in the ‘options’ or ‘preferences’ menu of your internet browser.

If you set your internet browser preferences to block all cookies, you may not be able to access all or parts of our site.

If you delete cookies relating to this website we will not remember things about you, including your cookie preferences, and you will be treated as a first-time visitor the next time you visit the site.

To find out more about cookies, including how to see what cookies have been set and how to manage and delete them, visit www.allaboutcookies.org.

Queries

If you have any questions or comments regarding this Cookies policy, please use our Contact Us form.