Clipper Hub CLIPPERHUB Back to the ranking →
Legal notice & termsPrivacyCookiesAffiliates & advertising

Privacy policy

What data is processed and what is not: no sign-up, no forms, no analytics in your browser, no cookies, and how to exercise your rights.

Version 1.9 In force since 7 October 2026 Clipper Hub
This is a translation. Clipper Hub is operated from Spain and its legal texts are written in Spanish. If this English version and the Spanish original ever disagree, the Spanish one prevails.
In short: this site does not ask you for data, does not register you, has no analytics in your browser and sets no cookies, neither its own nor anyone else's. If you never write an email, the site owner never learns who you are. The only thing that happens is what happens when you request any page on the internet: the server that serves it (Cloudflare, Inc., United States) receives your IP address, which page you asked for and which browser you used, and uses that to deliver it and for aggregate counts. Section 3 sets it out and the cookie policy confirms it.

On this page

  1. Data controller
  2. What this site does not do
  3. What data is processed, why, and on what legal basis
  4. Who it is disclosed to
  5. When you click a link and leave
  6. Campaign data (and why there are no people in it)
  7. How long it is kept
  8. Your rights
  9. Minors
  10. Security
  11. Changes to this policy

1Data controller

Controller
Fernando Morales
Tax ID (NIF)
53.044.286-F
Address
El Boalo, Madrid (Spain)
Contact
contact@clipperhub.co

Given the volume and the nature of the processing —no special categories of data, no systematic monitoring of individuals, no large-scale processing— there is no obligation to appoint a data protection officer. Privacy matters are handled at the contact address above.

2What this site does not do

3What data is processed, why, and on what legal basis

DataWhenWhyLegal basis (GDPR)
Server logs: IP address, date and time, page requested, response code, browser and operating system On every visit, automatically Serving the page, keeping the service secure, detecting abuse and faults, and producing aggregate technical counts (never individual ones) Legitimate interest in the operation and security of the site (art. 6(1)(f))
Counts of page views and of exits to campaigns: which page, or which campaign you went to with the buttons that lead to it, from which country, which site you came from (the domain only), whether the request came from a browser or a bot, the kind of device (phone, tablet or computer), the browser family and the operating system family, with no version, and the protocol and the Cloudflare data centre that served the page. Since version 1.9, also: the page of this site you came from, if any; the utm_ parameters of the link you arrived by; your internet provider's network (the number and name of its autonomous system, such as "Telefonica de Espana"); the approximate region and city Cloudflare infers from the connection; the time zone and local time; the first language your browser asks for; and the connection latency. No IP address, no cookie and no identifier of any kind, so there is no way to tell which pages the same person has viewed or which campaigns they went to On every page served and every exit to a campaign, automatically Knowing which parts of the site get read, where visitors come from and how many visits end up in a campaign, and producing aggregate statistics about the sector Legitimate interest in understanding aggregate use of the site (art. 6(1)(f))
Advertising: which ad was shown in each slot of the page, which one you clicked, if any, and the context it was chosen with (the page and its campaign, whether you came from another page of this site or from elsewhere, country and region, language, device type, browser and operating system, and local time). To link a click with what was shown, each page served carries a random number written into the page itself and its links: it is not stored in your browser, it changes on every page and it does not connect one visit with another. No IP address and no cookie On every page with ads and every click on one, automatically Choosing which ad to show based on the page and its context, never on who you are, and knowing which ads interest people and where, in aggregate Legitimate interest in funding the site with useful advertising and measuring its aggregate use (art. 6(1)(f))
The filters, sort order and search text you use in the campaign table, together with the same connection information as the previous row. No IP address, no cookie and no identifier of any kind, and nothing stored in your browser When you change the table's filters or search: the final state, a few seconds after the last change Knowing what people using the site look for, to improve the table and produce aggregate statistics about the sector Legitimate interest in understanding aggregate use of the site (art. 6(1)(f))
Whether you come back: how many days since your last visit, on how many different days you have come and how many since the first. And your answer to the cookie notice (shown, accepted, rejected or configured). For this your browser keeps the date of your first and your last visit (see the cookie policy); the server only gets those counts, with no identifier Only if you accept the "Measurement" category of the cookie notice, and at most once a day Knowing, in aggregate, how many people come back and how often Consent (art. 6(1)(a) GDPR and art. 22.2 of the Spanish LSSI), which you can withdraw at any time from the cookie policy
The campaign link you send with the «Add your campaign» form, together with the country it is sent from and the language of the page. No IP address, no email and no identifier of any kind: there is no way to know who sent it Only if you use that form Reading that campaign on its platform and adding it to the ranking Legitimate interest in completing the site's catalogue (art. 6(1)(f))
Your email address and the content of your message Only if you write to the contact address Reading and answering your query, complaint, takedown request or exercise of rights Legitimate interest in replying to whoever gets in touch and, where applicable, compliance with a legal obligation (arts. 6(1)(f) and 6(1)(c))

The owner collects nothing else. There is no visitor identifier, neither the owner's nor a third party's. If you agree to us counting whether you come back, what tells your second visit apart from your first is two dates that stay in your browser; the server only gets how many days have passed, never who you are.

4Who it is disclosed to

There are no transfers of data to third parties, other than any legal obligations that might arise towards courts, law enforcement or public authorities.

Processors are involved, that is, providers who process data on the controller's behalf and under contract:

Where any of those providers is established outside the European Economic Area, the international transfer relies on an adequacy decision of the European Commission —such as the EU-US Data Privacy Framework for certified US providers— or, failing that, on the standard contractual clauses approved by the Commission, with any additional safeguards required.

5When you click a link and leave

Links to campaigns, platforms, regulations and advertised products lead to third-party sites. From the moment you click, it is that site processing your data, under its own privacy policy and its own cookies. Clipper Hub neither controls that processing nor receives personal information about you through it.

In the specific case of affiliate links, the destination platform may record that the visit came from this site in order to attribute a possible commission. What the owner gets to see of that is aggregate statistics —number of clicks, sign-ups and commissions— never the identity of whoever clicked or what they did next.

6Campaign data (and why there are no people in it)

The site's database holds information about campaigns: brand or agency, rate, budget, number of participants, deadlines and conditions. That is company data and aggregate figures, not personal data.

Clippers' names are not stored. Some campaign pages publish a leaderboard of top earners and most-viewed videos. From those lists only the figures for each position are kept —what the first earned, the second…, or the views of the best video—, with no name, no username, no identifier and no link, to measure how a campaign's money is shared out. Everything else is discarded at the reading stage and never reaches the database.

If a campaign's name coincides with a person's —artists, creators or personal brands— that is treated as public professional information, on the basis of the legitimate interest in reporting on a commercial offer open to the public. Anyone can object by writing to contact@clipperhub.co, and their campaign will be removed from the site.

7How long it is kept

8Your rights

You may exercise at any time your rights of access, rectification, erasure, objection, restriction of processing and portability, and withdraw a consent where you have given one. Just write to contact@clipperhub.co stating which right you are exercising; some reasonable identity check may be requested, but only if there is well-founded doubt about who is writing.

Requests are resolved within a maximum of one month, extendable to two if complex, and exercising these rights is free of charge.

If you believe your data has not been handled properly, you may lodge a complaint with the Spanish Data Protection Agency (www.aepd.es, C/ Jorge Juan 6, 28001 Madrid), or with the supervisory authority of your country of residence. A prior attempt to sort it out by writing to the contact address is appreciated, though not required.

9Minors

The site is aimed at people over 18 and does not knowingly collect data from minors. If any were detected, it would be deleted immediately.

10Security

Technical and organisational measures reasonable and proportionate to the risk are applied: the site is static, exposes no databases to the internet and stores no credentials or user data, because it asks for none. In its public deployment it is served over an encrypted connection (HTTPS). No system is infallible; if a breach occurred with a risk to anyone's rights, it would be notified in accordance with articles 33 and 34 of the GDPR.

11Changes to this policy

This policy may be updated if the service or the law changes. The version in force is the one published here, with its version number and date. If the owner introduced a new purpose of their own accord, it would be announced on the site and consent would be requested before applying it.

Last updated: 7 October 2026.