Cookie Policy
Last updated: October 6, 2026. Version 1 of this document.
Here is every cookie and every item Talent360Show stores in your browser, what it is for and how long it lasts, and how to decide what you allow.
2. Who sets them
- Us: all necessary cookies and local storage are first-party, set on our own domain.
- Google, Meta and LinkedIn: their scripts only load if you give permission. They set cookies on our domain and, in some cases, on their own (for example, linkedin.com). Each company also applies its own privacy policy to that data.
- Content embedded in presentations: if a user includes a YouTube video (which we load from youtube-nocookie.com) or a Vimeo video (with the do-not-track option, dnt=1), or other third-party content, in their presentation, those services may use their own cookies or storage under their own policies. We do not control them; the decision to embed them is made by the user who created the presentation.
- Payment pages: when you pay, you go to the Stripe or dLocal Go page, which use their own cookies on their own domain, mainly for payment security and fraud prevention, under their own policies. We do not set them and they are not loaded on our site.
3. Necessary cookies
These are used without asking you because without them we could not give you what you ask for: signing in, submitting forms securely, viewing a protected presentation or remembering your cookie decision.
| Name | Type | Purpose | Duration |
|---|---|---|---|
| authjs.session-token (or __Secure-authjs.session-token) | First-party cookie, httpOnly | Keeping you signed in | 30 days |
| authjs.csrf-token (or __Host-authjs.csrf-token) | First-party cookie, httpOnly | Protecting against requests forged from other sites | Until you close the browser |
| authjs.callback-url (or __Secure-authjs.callback-url) | First-party cookie | Returning you to the right page after signing in | Until you close the browser |
| t360_share_<project> | First-party cookie, httpOnly | Remembering that you have unlocked a password-protected presentation | 7 days |
| t360_consent | First-party cookie (SameSite=Lax; Secure over https) | Storing your cookie decision: categories, policy version and date. Not sent to third parties | 24 months |
4. Local storage: preferences and operation
| Name | Where it is stored | Purpose | Duration |
|---|---|---|---|
| t360_locale | Local storage (localStorage) | Remembering the language you choose for the application | Until you clear the site's data |
| chunkReloadAt | Session storage (sessionStorage) | If a file of the application fails to download, reloading once without falling into a reload loop | Until you close the tab |
Neither is sent to any server. They do not need your permission: the first stores a preference you ask for and the second is essential for the application to load.
5. Analytics cookies (only with your permission)
Google Analytics 4 tells us which pages of the public website are visited and how people reach them.
| Name | Provider | Purpose | Duration |
|---|---|---|---|
| _ga | Distinguishing visitors | Up to 2 years | |
| _ga_<id> | Keeping the session state | Up to 2 years | |
| _gid | Distinguishing visitors | 24 hours | |
| _gat | Limiting the request rate | 1 minute |
6. Advertising cookies (only with your permission)
These measure the results of our campaigns on Google, Meta and LinkedIn, for example how many people create an account after seeing an advertisement.
| Name | Provider | Purpose | Duration |
|---|---|---|---|
| _gcl_au and other _gcl_* and _gac_* | Google Ads | Measuring advertisement conversions | Around 3 months |
| _fbp | Meta | Measuring advertisement results | Around 3 months |
| _fbc | Meta | Remembering that you arrived from a Meta advertisement | Around 3 months |
| li_fat_id, li_gc and other li_*, lidc, bcookie, AnalyticsSyncHistory, UserMatchHistory | LinkedIn (some on linkedin.com) | Measuring advertisement results | Between 1 day and 2 years, depending on the cookie |
7. Where they are used
Analytics and advertising tools can only load on the public website (home page, template gallery and legal documents) and on the sign-in and registration pages. They never load in the application, in shared or embedded presentations or in presentation mode, even if you have accepted them. If you enter the application from a page where they were loaded, the whole page is reloaded to drop them. The tables list every tool we may use; only those we have switched on at the time actually load.
8. Your decision, and how to change it
- The first time you visit the public website we ask you, and until you say yes nothing related to analytics or advertising loads: the scripts are not even present on the page.
- Refuse and accept are on the first layer of the banner, with the same weight. The checkboxes in the detail panel are never pre-ticked. The banner does not block the page and links to this policy.
- You can change your mind whenever you like from 'Cookie settings', in the footer of every public page (including the legal documents), on the sign-in and registration pages, and in the application's user menu.
- Your decision expires after 24 months, at which point we ask again. We also ask again if we change the categories or the tools within them, because permission given for one set does not cover another.
9. What happens when you withdraw permission
When you withdraw it, we delete that category's cookies from our own domain, by name or by prefix (list below), and reload the page, because a script that has already loaded cannot be unloaded any other way. The deletion is repeated on every visit while there is no permission, and also when your decision expires. It works by category: if you withdraw permission for advertising and keep analytics, the advertising cookies go and the analytics ones stay.
- Analytics: _ga, _ga_*, _gid, _gat and _gat_*.
- Advertising: _gcl_*, _gac_*, _fbp, _fbc, li_*, lidc, bcookie, AnalyticsSyncHistory and UserMatchHistory.
There is one honest limit worth knowing: no website can delete cookies that Google, Meta or LinkedIn hold on their own domains, such as google.com, facebook.com or linkedin.com. Those depend on your browser settings and on your account with those services.
10. The record of your consent
The law requires us to be able to demonstrate that consent was given, not merely to collect it. So each time you answer the banner, we store a record on our server of what you accepted or refused in each category, the policy version, the language in which the banner was shown to you, the date, your IP address and your browser identification (user agent, up to 500 characters). We keep it for 24 months, after which it is deleted automatically. The record is created whether you accept or refuse, because proof of a refusal matters just as much. If the record failed to save, your decision would still be applied.
11. International transfers
If you accept analytics or advertising cookies, Google, Meta and LinkedIn also process the corresponding data in the United States. All three are certified under the EU-U.S. Data Privacy Framework, which the European Commission regards as providing an adequate level of protection; Google and Meta are also certified under its UK Extension, and LinkedIn additionally applies the Standard Contractual Clauses. If you do not accept them, no transfer takes place, because their tools never load. More detail in the Privacy Policy.
12. Managing cookies in your browser
Independently of our own panel, your browser lets you accept, refuse or delete cookies, block third-party ones and clear local storage. Bear in mind that if you delete the session cookies you will have to sign in again, that if you block all cookies you will not be able to use your account, and that if you delete t360_consent we will ask you about cookies again.
13. Changes to this policy
We may amend this policy if the tools we use or the applicable law change. When we do, we will update the date and version shown at the top and publish the new text on this same page. If the change affects anything that requires your permission, we will change the policy version and ask you again.
14. Versions in other languages
This document is published in English, Spanish, French, German, Portuguese, Italian and Catalan so that you can read it in your own language. Translations are offered as a courtesy and, in the event of any discrepancy between versions, the English version prevails.