Principle : Kicklinks limits data to what is needed for accounts, certification, verification, security, billing and legal obligations.
1. Controller
The data controller is KickLinks, a platform for certifying and verifying digital assets.
Contact: use the form matching your request.
2. Data processed
Kicklinks may process account information, email addresses, links, domains, social accounts, monetization links, technical metadata, statuses, histories, revocations, certificates, payment data and identity-verification data when required.
3. Purposes
Processing is used to create and manage accounts, verify identity, prevent fraud, produce technical proof, generate certificates, manage payments, secure the service, maintain useful logs and comply with legal obligations.
4. Legal bases
Depending on the processing, the legal basis may be contract performance, Kicklinks’ legitimate interest in securing the service, compliance with a legal obligation or consent when required.
5. Providers
Kicklinks may rely on Scaleway SAS, Neon Postgres, Resend, Bunny.net and Stripe. These providers process data needed for their missions under an appropriate contractual framework. Identity verification will rely on a specialist provider. This feature is currently being activated; the provider used and information about the processing of personal data will be communicated before any verification takes place.
6. Public data
Some data may become public when the user publishes a proof, badge, verification page or public identity page. Displayed information is limited to understanding the status and proof.
An active public proof can be accessed through its link and, when included in public service surfaces such as the proofs sitemap, may be listed or indexed at scale. Users should not publish private or sensitive documents without understanding this exposure.
7. Retention
Data is retained for the time needed for the service, proof traceability, security, billing and legal obligations. Certificates, revocations and histories may be retained to preserve evidentiary consistency.
8. Security
Kicklinks applies technical and organizational measures intended to limit unauthorized access, loss, alteration or misuse.
9. Individual rights
You may request access, rectification, erasure where applicable, restriction, objection or portability. Some evidentiary or legal data may require controlled retention instead of immediate deletion.
10. Cookies
Cookies are described in the dedicated policy.
YouTube API Services
When the YouTube feature is enabled, KickLinks uses YouTube API Services solely to resolve a public channel and, at its owner's request, observe a temporary code placed in its public description.
KickLinks reads the channel ID, title, handle or custom URL when available, the description in memory for the duration of the check, and the fetch time. The full description, statistics, videos, subscribers, and comments are not retained.
KickLinks retains the canonical identifier and dated verification result for the proof lifecycle. The title and handle read during resolution are not retained as current provider metadata. There is no continuous monitoring: a new read occurs only for an explicitly requested check. Deletion in KickLinks does not delete or change anything on YouTube. Deletion requests can be submitted through the contact form.
