Last updated: August 5, 2026

Privacy Policy

This site is an independent editorial resource about paid traffic platforms and their pricing, built around a single Cheap Website Traffic reference page. It is not an advertising network, it sells no advertising, it operates no user accounts, and it processes no payments. The practical consequence for a visitor is that the amount of personal data involved here is unusually small. This policy describes precisely what remains. The operator of the site is the publisher of its editorial content, Smith Jones, reachable at [email protected], and this version takes effect on August 5, 2026. Processing is carried out in line with the UK GDPR and the Data Protection Act 2018, and with Regulation (EU) 2016/679 for visitors in the European Economic Area.

What is collected

Data you provide directly. There are no forms, no comment fields, no newsletter signup and no account registration anywhere on this site. The only way to send information is to write to one of the published email addresses, in which case the processed data is whatever you chose to put in that message: your address, your name if you sign it, and the content of the correspondence. Payment details, advertising account credentials and identity documents are never requested and should never be sent. What happens to a correction report after it arrives is described in how figures are checked.

Data collected automatically. Like any web server, the host records a request log. Each entry contains the IP address making the request, the user agent string identifying browser and operating system, the URL requested, the referring URL where the browser supplies one, and a timestamp. These entries exist for two purposes: keeping the site available, by identifying traffic spikes and abusive request patterns, and diagnosing errors when a page fails to load. They are never aggregated into visitor profiles, and they feed no advertising system.

Analytics. One measurement tool runs on this site: Google Analytics 4, property G-XCK2XCC5KT, loaded through the gtag.js library from googletagmanager.com. It records which pages are opened, how long a session lasts, which country and device type the request comes from, and which site or search engine referred the visit. IP addresses are truncated by Google before storage and are not available in reports. The data answers one editorial question: which pages readers actually use, so time goes into updating those.

What is not collected. No advertising pixels, remarketing tags or social platform trackers are present. No session recording, no heatmaps, no form capture, no fingerprinting script. Google Analytics here runs in its default configuration with no Google Signals, no advertising features and no user ID, so no cross-site advertising profile is built from your visit. Open the network tab in your browser's developer tools and check: requests go to this domain and to Google's analytics endpoints, and nowhere else.

Cookies

The site itself sets no cookies. Google Analytics sets two: _ga, which stores a randomly generated client identifier used to count returning devices and expires after two years, and _ga_XCK2XCC5KT, which holds the state of the current session for the property above and also expires after two years. Neither contains a name, an email address or anything you typed.

No advertising, remarketing or personalisation cookies are set by anyone here. Campaign parameters on outbound sign-up links are query strings in the URL, not storage on your device, and they are read by the destination platform after you arrive there. You can refuse analytics cookies without losing anything on this site: block cookies for this domain in your browser, use its tracking protection, or install Google's official Analytics opt-out browser add-on. Every page remains fully readable either way.

Legal basis for processing

Server logs are processed under legitimate interest, Article 6(1)(f), the interest being the security and availability of a public website, which cannot be operated safely without them. Email correspondence is processed under legitimate interest as well, or under Article 6(1)(b) where the exchange concerns a request you have made, since answering a message you sent is the purpose of receiving it. Analytics is the one place where consent under Article 6(1)(a) applies, since the cookies described above are not strictly necessary; refusing them through your browser or the opt-out add-on withdraws that consent at any time, with no effect on the lawfulness of processing that happened before. No marketing communications are sent from this site at all. Where a legal obligation applies to retaining records, Article 6(1)(c) covers it.

Who else is involved

The hosting provider. Whoever serves these files necessarily processes request logs on the operator's behalf, under a processor relationship, and applies its own security measures at infrastructure level.

Google LLC. Google Analytics processes the measurement data described above on this site's behalf, under Google's own data processing terms. What Google receives is page addresses, timestamps, coarse location derived from a truncated IP address, device and browser type, and the referring URL. Google's handling of that data is governed by its privacy policy, which this site does not control.

Destination platforms you choose to visit. Sign-up buttons lead to AdsCompass and carry campaign parameters so the destination can attribute the visit. Following such a link places you on that platform's site under its own privacy policy and cookie practices, which this site neither controls nor receives data from beyond aggregate referral counts. Source links to help centres, standards bodies and platform documentation behave the same way.

Nobody else. Personal data is not sold, rented, traded or shared with data brokers, advertising networks or list buyers, and there is no arrangement under which any third party receives visitor data from this site. If a lawful authority made a valid, binding request, it would be complied with and, where legally permitted, disclosed on this page.

International transfers

Hosting, email infrastructure and Google Analytics may process data outside the United Kingdom and the European Economic Area, which is unavoidable for a site read primarily by a United States audience. Where that happens, transfers rely on the standard safeguards available under UK and EU data protection law: adequacy decisions where they exist, and standard contractual clauses where they do not. A visitor can request details of the safeguards applying to their data by writing to [email protected]. The answer will name the current arrangement, not describe one in the abstract.

Retention periods

• Server logs: 90 days. This is long enough to investigate a security incident or a recurring error and short enough that historical request data does not accumulate indefinitely. After that period entries are deleted.
• Email correspondence: 12 months from the last message in the thread. Correction reports are kept for this period so that a figure changed on the basis of a reader's report can be traced back to its source if the change is later disputed.
• Google Analytics event data: 14 months. This is the maximum retention period the property allows for user-level and event-level data; aggregated reports remain available afterwards, but the underlying records are deleted on that schedule.
• Nothing else is retained. There is no visitor database, no CRM and no mailing list, because none of that data is collected in the first place.

Your rights

Under the UK GDPR and Regulation (EU) 2016/679 you may request access to the personal data held about you (Article 15), correction of inaccurate data (Article 16), erasure (Article 17), restriction of processing (Article 18), portability in a machine-readable format (Article 20), and you may object to processing based on legitimate interest (Article 21). In practice, exercising any of these against this site concerns three things: server log entries associated with your IP address, Google Analytics records associated with your device identifier, and email correspondence you have sent. Requests go to [email protected], are acknowledged within 72 hours and answered within thirty days, and require enough information to locate the data, which for a log request means an approximate date and the IP address in question.

If you consider a request mishandled, you may complain to a supervisory authority: in the United Kingdom the Information Commissioner's Office, or in the European Economic Area the authority for your country of residence. Complaining to a regulator does not require having asked here first, though asking here is usually faster.

Security

Pages are served over TLS, so traffic between browser and server is encrypted end to end; a certificate warning on this domain would indicate something is wrong and should be reported. The site is a set of static files with no database, no login system and no user-generated content, which removes the attack surface most often responsible for data breaches on content sites. The only third-party script loaded on any page is the Google Analytics library. Administrative access is protected with two-factor authentication, and the software serving the files is kept current. No system is perfectly secure, and this policy claims only that the measures in place are proportionate to a site that holds almost no personal data.

Minors

The subject matter here is commercial advertising procurement, written for people running marketing budgets, and the site is neither directed at nor intended for anyone under 18. No age verification is performed because no accounts exist and no personal data is knowingly solicited from anyone. If you believe information about a child has reached this site through correspondence, write to [email protected]. It will be deleted on receipt, with no assessment step.

Changes to this policy

This policy is reviewed whenever the technical setup of the site changes, for example if analytics were ever introduced or a form added, and at least once a year regardless. The last updated date at the top of this page always reflects the current version, and material changes will be summarised at the top of the page for at least thirty days after they take effect. Questions about anything above go to [email protected], or through the contact page; the rules governing the editorial side of the site are in the editorial policy.