Policy Cookies
Last updated: 5th August 2019
Synthesia Technology uses cookies on blog.synthesia.com . By using this website (the "Service"), you consent to the use of cookies.
Our Cookies Policy explains what cookies are, how we use cookies, how third-parties we may partner with may use cookies on the Service, your choices regarding cookies and further information about cookies.
What are cookies
Cookies are small pieces of text sent by your web browser by a website you visit. A cookie file is stored in your web browser and allows the Service or a third-party to recognize you and make your next visit easier and the Service more useful to you.
Cookies can be "persistent" or "session" cookies.
How Synthesia Technology uses cookies
When you use and access the Service, we may place a number of cookies files in your web browser.
We use cookies for the following purposes: to enable certain functions of the Service, to provide analytics, to store your preferences, to enable advertisements delivery, including behavioral advertising.
We use both session and persistent cookies on blog.synthesia.com and we use different types of cookies to run blog.synthesia.com:
Essential cookies. We may use essential cookies to authenticate users and prevent fraudulent use of user accounts.
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. |
|
|
What are your choices regarding cookies
If you'd like to delete cookies or instruct your web browser to delete or refuse cookies, please visit the help pages of your web browser.
Please note, however, that if you delete cookies or refuse to accept them, you might not be able to use all of the features we offer, you may not be able to store your preferences, and some of our pages might not display properly.
