Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Tallentor is an embedded SaaS web widget loaded into a host website. It can set first party and provider cookies to keep the widget working and to remember visitor interactions.
Tallentor is a software as a service web widget that site owners embed into their pages with a small script. Once loaded, it renders an interactive component served from the provider and can exchange data with the Tallentor backend to deliver its features.
Because it is a third party embed that runs in the visitor browser and can store cookies, Tallentor falls within the scope of European cookie and data protection rules and should be treated like any external tracking or functional component.
Tallentor may set first party cookies to keep the widget working across page loads and provider cookies to recognise the visitor or session on the Tallentor service. In operation it can process technical data such as IP address, browser details and interaction events, and depending on its purpose it may also handle information the visitor enters into the widget.
Where these cookies and calls go beyond what is strictly necessary to provide a function the visitor requested, they require consent and clear disclosure.
Under the ePrivacy Directive, only strictly necessary cookies are exempt from consent. Cookies used for analytics, recognition or marketing within the widget need prior consent. Under the GDPR, the host site is usually the controller and the Tallentor provider acts as a processor, which means a data processing agreement is required.
You should map exactly what the widget does before deciding which cookies qualify as necessary and which need consent.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Where Tallentor sets non essential cookies or sends behavioural data to the provider, consent must be obtained before the widget loads. That consent must be freely given, specific, informed and unambiguous, and visitors must be able to use the rest of the site and to withdraw consent without detriment.
The Tallentor backend may be hosted outside the European Economic Area, including in the United States. If visitor data leaves the EEA, you need a valid transfer mechanism such as Standard Contractual Clauses or reliance on an adequacy decision, together with any supplementary measures the situation requires.
Load Tallentor only after consent for any non essential use, sign a data processing agreement with the provider, document the cookies and data flows, and confirm the hosting location and transfer safeguards. List the widget in your privacy and cookie notices and review the configuration whenever the provider updates the embed.
Websites using Tallentor must obtain user consent under GDPR regulations.
DPIA considerations
Because Tallentor is a third party widget that can load remote scripts and set cookies, review which data the widget collects, whether it observes visitor behaviour and whether identifiers are shared with the provider. A DPIA is recommended where the widget processes contact details, enables profiling or systematically monitors visitors at scale.
Sample consent text
This page uses the Tallentor widget, which may set cookies and connect to the Tallentor service. We load it only after you accept. You can withdraw your consent at any time through our cookie settings.
Third-party domains contacted
tallentor.comcdn.tallentor.comapi.tallentor.comwidget.tallentor.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| tallentor_session | Functional | Session | Keeps the embedded widget state consistent during a single browsing session. |
| tallentor_uid | Functional | 1 year | Stores an identifier so the provider can recognise the visitor or device across visits. |
| tallentor_consent | Functional | 6 months | Records whether the visitor accepted loading the widget and its related cookies. |
| tallentor_analytics | Analytics | 13 months | Measures how visitors interact with the widget to improve the provided feature. |
Tallentor collects user analytics data — you legally need a consent banner. Try FlowConsent free.
Tallentor can set first party cookies that keep the embedded widget working across page loads and provider cookies that recognise the visitor or session on the Tallentor service. The exact names depend on your configuration. Any cookie that is not strictly necessary for a function the visitor requested requires consent.
It depends on what the widget does. If Tallentor only provides a function the visitor actively requested and uses strictly necessary cookies, consent may not be needed. If it sets analytics, recognition or marketing cookies, or shares behavioural data with the provider, prior consent is required before it loads.
For non essential cookies the basis is visitor consent under Art. 6(1)(a) GDPR. For a purely functional widget that the visitor requested, legitimate interest under Art. 6(1)(f) GDPR may apply to the related processing, but the cookie itself must still meet the strictly necessary test under ePrivacy.
It can, depending on where the provider hosts the Tallentor backend. If visitor data is processed outside the European Economic Area, including in the United States, you need a valid transfer mechanism such as Standard Contractual Clauses and any supplementary measures the transfer requires.
A DPIA is recommended where Tallentor processes contact details, enables profiling or systematically monitors visitors at scale. For a simple functional widget a documented screening assessment is usually enough, but you should record your reasoning either way.
Map what the widget collects, load it only after consent for any non essential use, sign a data processing agreement with the provider and confirm the hosting location and transfer safeguards. Disclose the widget and its cookies in your privacy and cookie notices and retest after each provider update.
Alternatives include self hosted widgets that keep data on your own infrastructure, EU hosted SaaS widgets, or building the feature natively so no third party embed is loaded. The right choice depends on the function you need and your appetite for third party data sharing.
List the Tallentor cookies with their names, purposes and durations, state whether the widget loads before or after consent and name the provider as a recipient. Review the entry whenever the provider changes the embed, its cookies or its hosting locations.