This cookie statement was last updated on March 26, 2020 and applies to citizens of the United Kingdom.
1. Introduction
Our website, https://richardtice.com (hereinafter: "the website") uses cookies and other related technologies (for convenience all technologies are referred to as "cookies"). Cookies are also placed by third parties we have engaged. In the document below we inform you about the use of cookies on our website.
2. What are cookies?
A cookie is a small simple file that is sent along with pages of this website and stored by your browser on the hard drive of your computer or another device. The information stored therein may be returned to our servers or to the servers of the relevant third parties during a subsequent visit.
3. What are scripts?
A script is a piece of programme code that is used to make our website function properly and interactively. This code is executed on our server or on your device.
4. What is a web beacon?
A web beacon (or a pixel tag) is a small, invisible piece of text or image on a website that is used to monitor traffic on a website. In order to do this, various data about you is stored using web beacons.
5. Cookies
5.1 Technical or functional cookies
Some cookies ensure that certain parts of the website work properly and that your user preferences remain known. By placing functional cookies, we make it easier for you to visit our website. This way, you do not need to repeatedly enter the same information when visiting our website and, for example, the items remain in your shopping cart until you have paid. We may place these cookies without your consent.
5.2 Advertising cookies
We do not use any advertising cookies on this website.
5.3 Social media buttons
On our website we have included buttons for Facebook, Twitter and Instagram to promote webpages (e.g. “like”, “pin”) or share (e.g. “tweet”) on social networks like Facebook, Twitter and Instagram. These buttons work using pieces of code coming from Facebook, Twitter and Instagram themselves. This code places cookies. These social media buttons also can store and process certain information, so a personalized advertisement can be shown to you.
Please read the privacy statement of these social networks (which can change regularly) to read what they do with your (personal) data which they process using these cookies. The data that is retrieved is anonymized as much as possible. Facebook, Twitter and Instagram are located in the United States.
6. Placed cookies
Go Daddy
We use Go Daddy for website hosting. Read more
| Name | Retention | Function |
| Purpose pending investigation | ||
| _tccl_visitor | ||
| _tccl_visit |
Sharing
Google Analytics
We use Google Analytics for website statistics. Read more
| Name | Retention | Function |
| Statistics | ||
| _ga | 2 years | Store and count pageviews |
| _gid | 1 day | Store and count pageviews |
| _gat | 1 minute | Read and filter requests from bots |
| _gat_gtag_UA_* | 1 minute | Store a unique user ID |
Sharing
For more information, please read the Google Analytics Privacy Policy.
Elementor
We use Elementor for content creation. Read more
| Name | Retention | Function |
| Statistics (anonymous) | ||
| elementor | persistent | Store performed actions on the website |
Sharing
This data is not shared with third parties.
Google Fonts
We use Google Fonts for display of webfonts. Read more
| Name | Retention | Function |
| Marketing/Tracking | ||
| Google Fonts API | expires immediately | Read user IP address |
Sharing
For more information, please read the Google Fonts Privacy Policy.
YouTube
We use YouTube for video display. Read more
| Name | Retention | Function |
| Marketing/Tracking | ||
| GPS | session | Store location data |
| Functional | ||
| VISITOR_INFO1_LIVE | 6 months | Provide bandwidth estimations |
| Statistics | ||
| YSC | session | Store a unique user ID |
| PREF | 1 year | Store and track visits across websites |
Sharing
For more information, please read the YouTube Privacy Policy.
We use Instagram for display of recent social posts and/or social share buttons. Read more
| Name | Retention | Function |
| Marketing/Tracking | ||
| actppresence | 1 year | Store ad display frequency |
Sharing
For more information, please read the Instagram Privacy Policy.
We use Facebook for display of recent social posts and/or social share buttons. Read more
| Name | Retention | Function |
| Marketing/Tracking | ||
| _fbc | 2 years | Store last visit |
| fbm* | 1 year | Store account details |
| xs | 3 months | Store a unique session ID |
| fr | 3 months | Provide ad delivery or retargeting |
| act | 90 days | Store logged in users |
| _fbp | 3 months | Store and track visits across websites |
| datr | 2 years | Provide fraud prevention |
| c_user | 90 days | Store a unique user ID |
| sb | 2 years | Store browser details |
| *_fbm_ | 1 year | Store account details |
| Functional | ||
| wd | 1 week | Read screen resolution |
| csm | 90 days | Provide fraud prevention |
| presence | session | Store and track if the browser tab is active |
Sharing
For more information, please read the Facebook Privacy Policy.
We use Twitter for display of recent social posts and/or social share buttons. Read more
| Name | Retention | Function |
| Functional | ||
| local_storage_support_test | persistent | Provide load balancing functionality |
| Marketing/Tracking | ||
| metrics_token | persistent | Store if the user has seen embedded content |
Sharing
For more information, please read the Twitter Privacy Policy.
Complianz
We use Complianz for cookie consent management. Read more
| Name | Retention | Function |
| Functional | ||
| complianz_policy_id | 365 days | Store accepted cookie policy ID |
| complianz_consent_status | 365 days | Store cookie consent preferences |
| cmplz_user_data | 365 days | Determine which cookie banner to show |
Sharing
For more information, please read the Complianz Privacy Policy.
Zopim
We use Zopim for chat support. Read more
| Name | Retention | Function |
| Functional | ||
| __zlcmid | persistent | Store a unique user ID |
Sharing
For more information, please read the Zopim Privacy Policy.
Hotjar
We use Hotjar for heat maps and screen recordings. Read more
| Name | Retention | Function |
| Statistics | ||
| _hjid | 1 year | Store a unique user ID |
Sharing
For more information, please read the Hotjar Privacy Policy.
QuantCast
We use QuantCast for advertising. Read more
| Name | Retention | Function |
| Marketing/Tracking | ||
| __qca | 5 years | Store and track audience reach |
| Functional | ||
| googlepersonalization | 1 year | Store cookie consent preferences |
Sharing
For more information, please read the QuantCast Privacy Policy.
HubSpot
We use HubSpot for marketing automation (automated email marketing). Read more
| Name | Retention | Function |
| Marketing/Tracking | ||
| hubspotutk | 13 months | Store and track a visitor's identity |
| __hstc | 13 months | Store time of visit |
| Purpose pending investigation | ||
| __hssrc | session |
Sharing
For more information, please read the HubSpot Privacy Policy.
Adroll
We use Adroll for cross-channel advertising. Read more
| Name | Retention | Function |
| Marketing/Tracking | ||
| __adroll_fpc |
Sharing
For more information, please read the Adroll Privacy Policy.
LiveChat
We use LiveChat for chat support. Read more
| Name | Retention | Function |
| Purpose pending investigation | ||
| lc_sso* |
Sharing
For more information, please read the LiveChat Privacy Policy.
Google DoubleClick
We use Google DoubleClick for cross-channel advertising. Read more
| Name | Retention | Function |
| Marketing/Tracking | ||
| __ar_v4 | persistent | Store and track conversions |
| __gads | 13 months | Provide ad delivery or retargeting |
| IDE | 2 years | Provide ad delivery or retargeting |
| _drt_ | 90 days | Provide ad delivery or retargeting |
| ___gads | 13 months | Provide ad delivery or retargeting |
| id | 90 days | Provide ad delivery or retargeting |
| ar_v4 | persistent | Store and track conversions |
| DSID | 2 weeks | Store user preferences |
| idIDE | 2 years | Provide ad delivery or retargeting |
| Purpose pending investigation | ||
| 1P_JAR |
Sharing
For more information, please read the Google DoubleClick Privacy Policy.
WP Engine
We use WP Engine for website hosting. Read more
| Name | Retention | Function |
| Purpose pending investigation | ||
| wpe_test_group | ||
| Statistics | ||
| __utmzz | 8 months | |
| Marketing/Tracking | ||
| __utmzzses | session | |
| Functional | ||
| wpe_is_consent_required | session |
Sharing
For more information, please read the WP Engine Privacy Policy.
Optimizely
We use Optimizely for website statistics. Read more
| Name | Retention | Function |
| Statistics | ||
| optimizelyEndUserId | 6 months | Store a unique user ID |
| optimizelySegments | 10 years | Store ID's of experiments and sessions for A/B testing |
| optimizelyBuckets | 10 years | Store ID's of experiments and sessions for A/B testing |
Sharing
For more information, please read the Optimizely Privacy Policy.
Atlassian Jira Servicedesk
We use Atlassian Jira Servicedesk for customer support management. Read more
| Name | Retention | Function |
| Purpose pending investigation | ||
| ajs_user_id | ||
| ajs_group_id | ||
| Statistics | ||
| ajs_anonymous_id | 1 year | Store last visit |
Sharing
This data is not shared with third parties.
AddToAny
We use AddToAny for display of recent social posts and/or social share buttons. Read more
| Name | Retention | Function |
| Functional | ||
| __cfduid | 30 days |
Sharing
For more information, please read the AddToAny Privacy Policy.
AddThis
We use AddThis for providing social share buttons. Read more
| Name | Retention | Function |
| Marketing/Tracking | ||
| uvc | 13 months | Track visits across websites |
Sharing
For more information, please read the AddThis Privacy Policy.
Miscellaneous
| Name | Retention | Function |
| Purpose pending investigation | ||
| opt_in_consent | ||
| __reff | ||
| portal_user | ||
| wpe_utmb | ||
| wpe_utmb_sess | ||
| ss_cid | ||
| ss_cookieAllowed | ||
| crumb |
Sharing
This data is not shared with third parties.
7. Your rights with respect to personal data
You have the following rights with respect to your personal data:
- You have the right to know why your personal data is needed, what will happen to it, and how long it will be retained for.
- Right of access: You have the right to access your personal data that is known to us.
- Right to rectification: you have the right to supplement, correct, have deleted or blocked your personal data whenever you wish.
- If you give us your consent to process your data, you have the right to revoke that consent and to have your personal data deleted.
- Right to transfer your data: you have the right to request all your personal data from the controller and transfer it in its entirety to another controller.
- Right to object: you may object to the processing of your data. We comply with this, unless there are justified grounds for processing.
To exercise these rights, please contact us. Please refer to the contact details at the bottom of this cookie statement. If you have a complaint about how we handle your data, we would like to hear from you, but you also have the right to submit a complaint to the supervisory authority (the Information Commissioner's Office (ICO)).
8. Enabling/disabling and deleting cookies
You can use your internet browser to automatically or manually delete cookies. You can also specify that certain cookies may not be placed. Another option is to change the settings of your internet browser so that you receive a message each time a cookie is placed. For more information about these options, please refer to the instructions in the Help section of your browser.
Please note that our website may not work properly if all cookies are disabled. If you do delete the cookies in your browser, they will be placed again after your consent when you visit our websites again.
9. Contact details
For questions and/or comments about our cookie policy and this statement, please contact us by using the following contact details:
Richard Tice
London, UK
United Kingdom
Website: https://richardtice.com
Email: contact@richardtice.com
This cookie policy was synchronized with cookiedatabase.org on July 30, 2021
