Cookie policy

1. What cookies are

Cookies and similar mechanisms (such as localStorage) are small pieces of data a site stores in your browser. They let the browser remember, among other things, that you are signed in and which language you want the interface in.

2. What we use them for

Sign-in: Firebase Authentication keeps a session token so you do not have to sign in on every visit. Settings: the language you pick is stored in localStorage under the key "telc.locale". Faster loading: the PWA mechanism stores the App's interface files in the browser so they are not fetched every time. The tasks, the recordings and the results all come over the network — without an internet connection the App will not run. Analytics: with your consent, Google Tag Manager loads Google Analytics, which stores an identifier so that your repeat visits count as one visitor rather than several. The same consent turns on Microsoft Clarity, which stores identifiers of its own and records how you use the site — cursor movement, clicks and scrolling; what you type into a field is masked in the recording. Marketing: with your consent, Google Tag Manager also loads Meta Pixel, which stores an identifier linking your visits to the App with your Meta ad account.

Sign-in, settings and the cache are needed for the App to work. Analytics and marketing are not — block them and everything else keeps working. Each of them only turns on after its own separate consent.

3. What is stored, exactly

Firebase session token — keeps you signed in; valid until you sign out or it expires. "telc.locale" — the interface language; persistent, until site data is cleared. Service worker cache — the App's interface files; refreshed on update. Google Analytics — "_ga" and "_ga_*"; tells one visitor from another; up to two years. Microsoft Clarity — "_clck" (a user identifier; up to a year), "_clsk" (ties page views into one session; up to a day) and "CLID" (up to a year), only with the analytics consent. "telc.source" — where the first visit came from (UTM tags, referring domain, landing page), only with analytics consent; until an account is created or consent is withdrawn. Meta Pixel — "_fbp" (and sometimes "fr", set directly by Meta); links your visits to the App with your Meta ad account; up to 90 days.

4. How to manage them

You can clear all of this in your browser settings (Chrome, Firefox, Safari, Edge — the privacy and site-data section). Signing out removes the session token. Clearing site data will sign you out and reset the language to the default. Analytics and marketing are switched on and off separately here too, without clearing anything else.

5. Changes

If the set of files we use changes, we will update this page and the date at the top.

6. Contact

Questions about cookies: