Liveblog Data protection

Which data do we process?

Mandatory Data Processing

The following data is always processed to ensure the liveblog functions securely and efficiently:

  • Accesses Logs (IP Addresses, Date, Time, URL)
  • Anonymous Analytics Data (Clicks, Page Loads, Data Fetches, Timing data)
  • Optional when using the comments feature: IP adresses and user IDs and user names

Optional Data Processing

These data points are only collected when certain features are used:

  • Comments Feature: IP addresses, user IDs and user names
  • Poll Feature: IP addresses and Random ID
  • Anonymous Analytics Data (Retention, Unique Users): random unique token

Why do we save the data?

Access Logs

Access logs are created for IT security purposes and protect our infrastructure (e.g. against DDoS attacks). The following data is stored:

  • IP Address
  • Accessed Page (URL)
  • Timestamp (Date and Time)

IP Addresses are deleted after 30 days.

Liveblog Analytics Data

We collect anonymous usage data to generate statistics for our liveblog customers. Unique user and retention metrics are tracked using a random token generated on the client side, which is aggregated on the server. Assignment to individual users is not possible afterwards.

The random token can be disabled (see useCookies option). If disabled, unique user tracking and retention statistics will no longer be available in the analytics data.

Optional: Comments Feature

If the comments feature is enabled, we store the following data per comment:

  • IP Address (for Rate Limiting, Spam Scoring, and User Blocking)
  • Name / Pseudonym

IP addresses are deleted after 30 Days.

Optional: Comments Feature with Custom Authentication

For every post the user id and name provided by the customer website are stored, to be displayed and to be used by comment moderators.

Optional: Poll Features

If the poll feature is enabled, we store the following data per participated poll:

  • IP Address (for Rate Limiting and User Blocking)
  • Random ID (prevent double voting)

IP addresses are deleted after 30 Days.

Who is affected?

Users read the live blog, create comments, or answer polls.

Local Storage Entries (“Cookies”)

By default, the embed script stores information on the end user’s computer for the following categories:

  • Essential (Required for features to work correctly)
  • Functional (Improves user experience, e.g., saving usernames in comments, consent to display content from external providers)
  • Analytics (Gathers anonymous usage statistics)

The useCookies option allows fine-grained control over which types of cookies are set:

Option Essential Functional Analytics
all ✅ Enabled ✅ Enabled ✅ Enabled
functional ✅ Enabled ✅ Enabled ❌ Disabled
none ✅ Enabled ❌ Disabled ❌ Disabled

To disable all but essential cookies, use:

<tickaroo-liveblog 
  liveblogId="5f47bdba2a03d3abfab3c607" 
  useCookies="none"
  clientId="5c99e3358dce8c729e697547">
</tickaroo-liveblog>

From a technical standpoint, the embed does not use traditional browser cookies but instead relies on local storage entries.

List of Local Storage Entries (“Cookies”)

tickaroo-tika (Category: analytics)

Randomly generated token for creation of anonymous statistics (retention, unique users). Will be created when the tickaroo embed script tracks analytics data to tickaroo.

tickaroo-embedconsent (Category: functional)

Created when a user gives consent to display content from a certain external provider (such as X, Instagram, etc.).

tickaroo-comments-author (Category: functional)

Comments feature stores the username entered, so the user does not have to reenter it next time. This is a convenience feature for Users.

tik_vote_id_<POLL_ID> (Category: essential)

The poll feature stores the selected answer and a random ID for each poll. This cannot be disabled with the “useCookies” option. If you do not want to store any information, please avoid using this feature.

Social Media Embeds (X, Instagram, etc.)

Our embed system provides flexible options for handling social media content while respecting user privacy.

We offer a consent mechanism that allows users to opt-in before social media content from third-party providers (e.g., X, Instagram) is loaded. This ensures that no external requests are made unless the user has explicitly agreed. Learn more about our consent system here: Consent Handling

When embedding posts from third-party platforms (e.g., X, Instagram), these providers may set their own cookies and track user behavior. We have no control over this tracking.

Privacy-Friendly Alternative: Simplified Preview Mode

For an even more privacy-conscious approach, our simplified preview mode displays a static preview of the embedded content without making requests to the social media providers. This prevents external tracking and ensures compliance with stricter data protection policies (see Option simple in Consent Handling Documentation).