What Linkads collects and why.

This page explains the personal and workspace data used to run Linkads, measure performance, protect the service, and support connected workflows such as QR8 when enabled.

Last updated25 March 2026

FocusOperational analytics

Not built forBehavioural ad profiling

Collected data

Account details such as email address, display name, and workspace settings.
Uploaded asset records and the metadata needed to serve those files safely.
Interstitial configuration, short-link destinations, and publishing state.
Event data such as impressions, skips, continues, CTA clicks, and comment submissions.
Security and request metadata used to protect the service and investigate misuse.

Why it is used

The data exists to run the product, not to overreach.

The product needs enough information to deliver traffic, understand outcomes, and keep the service stable. The current app is not positioned as a behavioural ad tracking platform.

Run the product

We use data to create links, deliver interstitials, save assets, and keep workspaces working as expected.

Measure what happened

Runtime events power dashboards, analytics pages, and product insights for the workspace that owns the traffic.

Protect the service

Request and security metadata help detect abuse, investigate issues, and keep the platform reliable.

Practical stance

Keep measurement readable and proportionate.

Linkads is designed to help publishers understand what happened around a link click, without turning the whole product into a heavy behavioural tracking stack.