Policy Cookies
This page was last updated on 25th August 2020. Whenever this policy is changed in a material way, you will be asked to renew your cookie consent.
We, Synthesia Technology (“Synthesia Affiliate/s”), through our website https://blog.synthesia.com/ and www.synthesia.com use cookies. These cookies help to ensure that our websites are secure and work properly, and if you consent so, it will help us to improve your experience across our websites by, for example, remembering your preference settings or sending you personalised information about our products and services.
What are cookies?
Cookies are text files containing small amounts of information, which are downloaded to your computer or mobile device by websites that you visit. They can improve your experience of using a website by, for example, remembering your preference settings and tracking your use of a website so that it can be improved to meet your needs. Most of our cookies only collect anonymous information. However, we or the other companies we use for cookies (listed below), may collect information such as log-in details and IP addresses that in some countries is considered personal data. We take your privacy seriously and would like you to understand how we process this personal data as per our Website Privacy Notice.
You may be able to access other websites from Synthesia Technology website, these websites are not under our control. Please review their cookie and privacy policies when you visit them.
Also, when you use an external account (such as Facebook or Disqus) to log in to our website, note that any preferences saved (such as remembering log-in details) are saved and further managed by your account provider and this is outside of our control .
What cookies do we use?
We know that understanding cookies, their uses and how these uses affect your online experience can be challenging. We want to make this as simple as possible for you. Below, you will find a summary of the purposes for which we use cookies followed by a complete cookie list.
Type 1: Functionality Cookies
Strictly necessary cookies are used for security, or to enable the website to function – without these cookies you will not be able to use our websites.
Functionality cookies that provide website services to enhance your experience and cookies that save your preferences e.g. website language, enquiries or comments you make on our website – these cookies are not necessary for your use of our websites but enabling these cookies can improve your website experience. A full list of functionality cookies is available below.
Type 2: Analytical Cookies (Anonymised)
Cookies that can tell us how (anonymised) users interact with our website, to help us improve. For these cookies, you will allow the companies we use (e.g. Google) to see some personal information e.g. IP address, but Synthesia Technology will not see this information.
If you accept these cookies, we will be able to analyse anonymous interactions such as:
- the sources from which you access our website,
- general online behaviour and interactions with our websites e.g. user clicks and number of website visits, and;
Type 3: Analytical Cookies (Personal)
If you accept these cookies, we will be able to analyse interactions such as:
- Utilising third party cookies (this means that they are provided by other companies, for example, Google or Facebook) to
advertise to you based on your interests and interactions with Synthesia Technology.
What consent options do I have?
Our use of strictly necessary cookies does not require your consent. If you do not agree with the saving of strictly necessary cookies on your device, you should stop browsing our webpages.
If you do not consent to our functionality cookies, some parts of our website may not work as you wish.
Consent for Synthesia Technology cookies will last for 12 months, after which time we will ask you to renew your cookie consent.
Can I withdraw my consent or manage my cookies?
To manage your cookie preferences, please click below.
You can also manage your cookies from your browser settings. You can find more information on how to do this here:
- Google Chrome: https://support.google.com/chrome/answer/95647?hl=en-GB
- Internet explorer: ttps://support.microsoft.com/en-gb/help/17442/windows-internet-explorer-delete-manage-cookies
- Mozilla Firefox: http://support.mozilla.org/en-US/kb/enable-and-disable-cookies-website-preferences
- Safari: https://support.apple.com/en-gb/guide/safari/sfri11471/mac
- Microsoft Edge: https://support.microsoft.com/en-gb/help/4468242/microsoft-edge-browsing-data-and-privacy-microsoft-privacy
What is the difference between a 'persistent' and a 'session' cookie?
| Persistent Cookie | Session Cookie |
| These cookies remain on your device between browsing sessions. They are activated each time you visit the website. | These cookies allow website operators to link your actions during a browsing session. A browsing session starts when you open your browser window and finishes when you close the browser window. These cookies are created temporarily. Once you close your browser, all cookies are deleted. |
Third-party cookies
In addition to our own cookies, we may also use various third-parties cookies to report usage statistics of the Service, deliver advertisements on and through the Service, and so on.
- Google Analytics is used to analyse traffic on our website;
- YouTube is used to play video content on our website;
- Google Maps is used to provide map functionality on our website;
- Google Adwords is used to analyse and optimise advertising from other sources;
- LinkedIn Insight Tag is used to measure conversion tracking from LinkedIn;
- HubSpot's tracking code sets a number of tracking cookies when a visitor lands on your site.
|
COOKIE NAME |
EXPIRES |
PURPOSE |
|
PHPSESSID |
When the user's browser is closed. |
To store a simple message when a form is submitted that can be displayed on a different page. For example, if an enquiry form is completed incorrectly, a message will be stored and presented to the user to indicate the errors in the submission. When an enquiry form is submitted successfully, a message is stored and presented to the user thanking them for their enquiry. No personal information is stored in this cookie. |
|
wordpress_test_cookie |
When the user's browser is closed. |
WordPress sets this cookie when you navigate to the login page. The cookie is used to check whether your web browser is set to allow, or reject cookies. |
_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. |
__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. |
__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. |
| HUBSPOT COOKIES | ||
| __hs_opt_out |
Expires: 13 months | 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. |
| __hs_do_not_track |
Expires: 13 months | 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, as it still allows anonymized information to be sent to HubSpot. |
| hs_ab_test |
end of session | This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before. |
| <id>_key |
When visiting a password-protected page, this cookie is set so future visits to the page from the same browser do not require login again. The cookie name is unique for each password-protected page. |
|
| hs-messages-is-open |
30 minutes |
This cookie is used to determine and save whether the chat widget is open for future visits. It resets to re-close the widget after 30 minutes of inactivity. |
| hs-messages-hide-welcome-message |
1 day |
This cookie is used to prevent the welcome message from appearing again for one day after it is dismissed. |
| __hsmem |
1 year |
This cookie is set when visitors log in to a HubSpot-hosted site. |
| __hstc |
13 months |
The main cookie for tracking visitors. It contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
| hubspotutk |
13 months |
This cookie is used to keep track of a visitor's identity. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
| __hssc |
30 minutes |
This cookie keeps track of sessions. This is used to determine if HubSpot 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. |
| __hssrc |
end of session |
Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. If this cookie does not exist when HubSpot manages cookies, it is considered a new session. |
| messagesUtk |
13 months |
This 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 chat with a visitor who later returns to your site in the same cookied browser, the messages tool will load their conversation history. |
