Cookies
Consent
By using this site and mobile application called Talaera (together, the “website”) you consent to the use of cookies in accordance with this Cookies Policy. You will have seen a pop up to this effect on your first visit to this website; although it will not usually appear on subsequent visits you may withdraw your consent at any time by following the instructions below.
What are cookies?
We may use information obtained about you from cookies or similar technology. Cookies are text files containing small amounts of information which we download onto your computer or device when you visit our website. We can recognise these cookies on subsequent visits and they allow us to remember you.
Cookies come in many forms, we have set out the main types below:
First and third‐party cookies
Whether a cookie is first‐party or third‐party refers to the domain placing the cookie. First‐party cookies are those set by a website that is being visited by the user. In this case the website is displayed in the URL window, e.g. https://talaera.com. Third‐Party cookies are cookies that are set by a domain other than that of the website being visited by the user. If a user visits a website and another entity sets a cookie through that website this would be a third‐party cookie.
For example on our website you may notice some cookies that aren’t related to us. If you go onto a web page that contains embedded content, for example from YouTube or Vimeo, you will be sent cookies from these websites. We don’t control the setting of these cookies, so please check the third‐party websites for more information about their cookies and how to manage them.
While using the “Live Chat” feature on our website at times when it is available, third parties may place cookies on your computer in order to provide this service.
Persistent cookies
These cookies remain on a user’s device for the period of time specified in the cookie. They are activated each time that the user visits the website that created that particular cookie.
Session cookie
These cookies allow website operators to link the actions of a user during a browser session. A browser session starts when a user opens the browser window and finishes when they close the browser window. Session cookies are created temporarily. Once you close the browser, all session cookies are automatically deleted.
Controlling cookies
If you want to delete any cookies that are already on your computer or device, please refer to the instructions for your file management software to locate the file or directory that stores cookies.
If you do not agree to the use of these cookies, please disable them by referring to your browser manufacturer’s instructions by clicking “Help” in your browser menu or by using the information on cookies available at www.allaboutcookies.org (please be aware this website uses cookies). Please note that by deleting our cookies or disabling future cookies you may not be able to access certain areas or features of our website.
After your initial visit to the website we may change the cookies we use. This cookies policy will always allow you to know who is placing cookies, for what purpose and give you the means to disable them so you should check it from time to time.
What do we use cookies for?
Cookies fall into one or more of the categories set out below. This website uses cookies that fall into all the categories set out below: category 1 (strictly necessary), 2 (performance) and 3 (functionality). We do not use targeting or behavioral advertising cookies on our website.
1. Strictly necessary cookies — These cookies enable services you have specifically asked for.
These cookies are essential in order to enable you to move around the website and use its features, such as accessing secure areas of the website. Without these cookies certain services you have asked for cannot be provided. We use this type of cookie to provide the shopping basket function on our web store.
Cookie Name
Source
Purpose
Source
talaera_admin_userTimezone
Talaera Web Client
This is used to store timezone information so that calendars can be displayed correctly
Persistent
talaera_admin_userUTCOffset
Talaera Web Client
This is also used to store timezone information, but in a different format, using the UTC offset of the users location. It is here for legacy purposes only and is replaced by talaera_admin_userTimezone
Persistent
talaera_admin_userLocation
Talaera Web Client
This is used to store the users location to support the calendar functionality
Persistent
browser_tab_id
Talaera Web Client
This is used to identify the tab the user is working with. Talaera opens multiple tabs depending on what the use is doing in the app.
Session
authToken
Talaera Web Client
This is used for authentication to the server
Session
user
Talaera Web Client
This is stores the users data during a session so we don’t have to get it from the server each time the page is refreshed
Session
allRoles
Talaera Web Client
This stores information about the access roles associated with a user. A role determines what a user can see and do in Talaera. This cookie allows us to keep track of that on the client.
Session
talaera_server_offset
Talaera Web Client
This is used to store the server time so that lessons start at the correct time, regardless of the time that is set on the users local computer
Session
tokbox_session_data
Talaera Web Client
This is the ID of a user’s upcoming session. We store this locally so that we don’t need to fetch it from the server repeatedly
Session
Cookie Name
Source
Talaera Web Client
Purpose
This is used to store timezone information so that calendars can be displayed correctly
Further Information
Persistent
Source
Talaera Web Client
Purpose
This is also used to store timezone information, but in a different format, using the UTC offset of the users location. It is here for legacy purposes only and is replaced by talaera_admin_userTimezone
Further Information
Persistent
Source
Talaera Web Client
Purpose
This is used to store the users location to support the calendar functionality
Further Information
Persistent
Source
Talaera Web Client
Purpose
This is used to identify the tab the user is working with. Talaera opens multiple tabs depending on what the use is doing in the app.
Further Information
Session
Source
Talaera Web Client
Purpose
This is used for authentication to the server
Further Information
Session
Source
Talaera Web Client
Purpose
This is stores the users data during a session so we don’t have to get it from the server each time the page is refreshed
Further Information
Session
Source
Talaera Web Client
Purpose
This stores information about the access roles associated with a user. A role determines what a user can see and do in Talaera. This cookie allows us to keep track of that on the client.
Further Information
Session
Source
Talaera Web Client
Purpose
This is used to store the server time so that lessons start at the correct time, regardless of the time that is set on the users local computer
Further Information
Session
Source
Talaera Web Client
Purpose
This is the ID of a user’s upcoming session. We store this locally so that we don’t need to fetch it from the server repeatedly
Further Information
Session
2. Performance cookies — These cookies collect information on the pages visited.
These cookies collect information about how users use a website, for instance which pages users go to most often, and if they get error messages from web pages. These cookies don’t collect information that identifies a visitor. All information these cookies collect is not associated with your personal information. It is only used to improve how the website works. We use Google Analytics and similar analytical tools which use performance cookies to provide us with information on how the website is performing and how you use the website.
The website currently uses the following analytic cookies from Google Analytics.
Cookie Name
Expiration Time
Description
_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_.
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_
90 days
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. 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.
Cookie Name
Expiration Time
2 years
Description
Used to distinguish users.
Expiration Time
24 hours
Description
Used to distinguish users.
Expiration Time
1 minute
Description
Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_.
Expiration Time
30 seconds to 1 year
Description
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.
Expiration Time
90 days
Description
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. Learn more.
Expiration Time
2 years from set/update
Description
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.
Expiration Time
10 minutes
Description
Used to throttle request rate.
Expiration Time
30 mins from set/update
Description
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.
Expiration Time
End of browser session
Description
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.
Expiration Time
6 months from set/update
Description
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.
Expiration Time
2 years
Description
Used to distinguish users.
Google’s Data Security & Privacy Policy: http://www.google.com/analytics/learn/privacy.html
Google’s Opt Out: https://tools.google.com/dlpage/gaoptout
3. Functionality cookies — These cookies remember choices you make to improve your experience
These cookies allow the website to remember choices you make and provide enhanced, more personal features. For example, a cookie is used to remember you if you have logged in during a previous session. These cookies can also be used to remember changes you have made to text size, fonts and other parts of the web pages that you can customise. These cookies are not used to track your browsing on other sites.
This website uses the following functional cookies
Cookie Name
Source
Purpose
Source
language
Talaera Web Client
Used to store the language the user selected so we can show the marketing website in that language when the user revisits the site.
Persistent
beta_accepted
Talaera Web Client
We use this to remember that a user has acknowledged the Beta state of certain features so we don’t have to ask them again
Persistent
browser_accepted
Talaera Web Client
When a user opens Talaera in an unsupported browser we will show them a warning indicating the browser is unsupported. This cookie helps us track their acceptance of that warning.
Session
temp_native_lang
Talaera Web Client
If the student doesn’t have a native language specified in their profile, but is accessing the translation features of Talaera, this cookie helps us keep track of the language the request for translation be made into
Session
talaera_admin_userListFilter
Talaera Web Client
This is used to preserve the filters that a user has specified to view a list in. For example if a user sorts their list from A‐Z then this cookie allows us to remember this preference
Session
user
Talaera Web Client
This is stores the users data during a session so we don’t have to get it from the server each time the page is refreshed
Session
talaera_server_offset
Talaera Web Client
This is used to store the server time so that lessons start at the correct time, regardless of the time that is set on the users local computer
Session
tokbox_session_data
Talaera Web Client
This is the ID of a user’s upcoming session. We store this locally so that we don’t need to fetch it from the server repeatedly
Session
HTML email web beacons
Our emails may contain a single, campaign‐unique “web beacon pixel” to tell us whether our emails are opened and verify any clicks through to links within the email. We may use this information for purposes including determining which of our emails are more interesting to you, to query whether users who do not open our emails wish to continue receiving them. The pixel will be deleted when you delete the email. If you do not wish the pixel to be downloaded to your device, you should select to receive emails from us in plain text rather than HTML
Use of IP addresses and web logs
We may also use your IP address and browser type to help diagnose problems with our server, to administer our website and to improve the service we offer to you. An IP address is a numeric code that identifies your computer on the internet. Your IP address might also be used to gather broad demographic information.
We may perform IP lookups to determine which domain you are coming from (e.g. google.com) to more accurately gauge our users’ demographics.
Information from these types of cookies and technologies or about website usage is not combined with information about you from any other source.
None of the cookies or technologies that we use will personally identify you.
Cookies policy does not cover third party websites
Please note that this cookies policy does not apply to, and we are not responsible for, the privacy practices of third party websites which may be linked to this website.
Changes to the Cookies Policy
We may update this cookies policy and we would encourage you to review the policy from time to time to stay informed of how we are using cookies. This cookies policy was last updated on 18 May, 2018.
Cookie Name
Source
Talaera Web Client
Purpose
Used to store the language the user selected so we can show the marketing website in that language when the user revisits the site.
Further Information
Persistent
Source
Talaera Web Client
Purpose
We use this to remember that a user has acknowledged the Beta state of certain features so we don’t have to ask them again
Further Information
Persistent
Source
Talaera Web Client
Purpose
When a user opens Talaera in an unsupported browser we will show them a warning indicating the browser is unsupported. This cookie helps us track their acceptance of that warning.
Further Information
Session
Source
Talaera Web Client
Purpose
If the student doesn’t have a native language specified in their profile, but is accessing the translation features of Talaera, this cookie helps us keep track of the language the request for translation be made into
Further Information
Session
Source
Talaera Web Client
Purpose
This is used to preserve the filters that a user has specified to view a list in. For example if a user sorts their list from A‐Z then this cookie allows us to remember this preference
Further Information
Session
Source
Talaera Web Client
Purpose
This is stores the users data during a session so we don’t have to get it from the server each time the page is refreshed
Further Information
Session
Source
Talaera Web Client
Purpose
This stores information about the access roles associated with a user. A role determines what a user can see and do in Talaera. This cookie allows us to keep track of that on the client.
Further Information
Session
Source
Talaera Web Client
Purpose
This is used to store the server time so that lessons start at the correct time, regardless of the time that is set on the users local computer
Further Information
Session
Source
Talaera Web Client
Purpose
This is the ID of a user’s upcoming session. We store this locally so that we don’t need to fetch it from the server repeatedly
Further Information
Session