Privacy and terms

camsite.org is a static site: a folder of HTML files built locally and uploaded to Cloudflare Pages. There is no database, no login, no comment box, no newsletter and no upload form. That is not a privacy promise, it is just what the site is, and most of what follows comes from it.

The version of this page before 19 September 2026 was boilerplate pasted in from a WordPress plugin in 2019. It described DoubleClick ad cookies this site has never served, a forum that no longer exists, and a licence over content you upload to a site with nothing to upload to. It was wrong in a way nobody would ever check, which is the same fault this whole site exists to point at on other people’s pages. So it was rewritten.

And then the rewrite was wrong too, for four weeks, in the section below. What it said and how long it said it is at the foot of this page, with the date.

What this site itself takes from you

Nothing, and there is nowhere for it to go. No account, no form, no comment box, no newsletter, no upload. I could not build a list of readers if I wanted one, because there is no field anywhere on this site that accepts your name or your address.

That sentence used to be the whole of this page’s answer. It is not, because it only covers the code I wrote.

The page counter, in full

I run StatCounter on this site, and have since 22 August 2026. It is a page counter. It tells me how many people opened a page, which pages those were, and roughly where in the world they were. It is the only measurement this site has and the only third party on it: no ad network, no fonts from somebody else’s CDN, no embeds, no tag manager, no session recorder.

It is not something I can describe as harmless by choosing my words carefully, so here is the inventory instead. It is built from the same file the site’s security policy is built from, so this page cannot fall out of step with what the site actually loads again.

What StatCounter records on every page you open. Its own documentation is the source for this list, read on 2026-09-20:

  • the date and time of the visit
  • your IP address
  • the country, region, city and network that IP address resolves to
  • your browser and its version
  • your operating system and its version
  • your screen resolution
  • the page you asked for, and its title
  • the page you came from, where your browser sent one
  • how long you stayed on the page before the next one

The two cookies it sets. They are set by StatCounter's own server on .statcounter.com, which makes them third-party cookies, and nothing on this site can decline them on your behalf.

  • is_unique, tells a first visit from a returning one, five years.
  • is_visitor_unique, stops one person being counted twice, two years. StatCounter's own cookie page lists this as a first-party cookie named sc_is_visitor_unique; what its server actually set here was is_visitor_unique on .statcounter.com, which is a third-party cookie.

How to refuse it. StatCounter publishes its own refusal page, and it works across every site that uses StatCounter rather than just this one. Refuse Statcounter Analytics Cookies sets a refusal_cookie in your browser and destroys the cookies above. It is per browser and per machine, because it is itself a cookie. Blocking c.statcounter.com in an ad blocker does the same thing without one.

Sources, all StatCounter's own pages: what it collects, its cookie list and what it reports to me. Read 2026-09-20. Running since 2026-08-22.

There is no consent banner, and that is a decision rather than an oversight.

This is first-party measurement of which pages get read, not advertising. Nothing here builds a profile, follows you to another site, or is sold to anybody, and no decision about you is made from it. A consent box that interrupts every reader to ask about a page counter would be theatre, and it would be the only interruption on the site.

You may disagree with that, and the refusal link above works whether you do or not. It is not a preference I store, because I store nothing: it is StatCounter’s own cookie, set in your browser, and I never see that it happened.

What I actually look at. A weekly count of page views per URL, where the traffic came from, and roughly which country. I do not look up individual visitors, and the plan this site is on has no API attached to it, so nothing here is piped anywhere else. StatCounter’s own terms say that a visitor’s name, telephone number, postal address and email address are technically impossible for it to collect and that no attempt is made to do so. Your IP address is not in that list, and it is collected.

What my host sees

Cloudflare serves the files, so Cloudflare’s servers see the ordinary things a web server sees: your IP address, your browser’s user-agent string, which page you asked for, when, and what page you came from if your browser sent that. I do not have access to those logs page-by-page. I see aggregate request counts in a dashboard, nothing tied to a person.

That data is handled under Cloudflare’s privacy policy, not mine. If you would rather they did not see it, a VPN is the answer, not a setting on this site.

This is the part that pays for the site, so here it is in full.

I make money when you sign up to a cam site through my links. The buttons and the ranked table point at /go/<platform>/ on this domain, which is a small page that forwards you to the platform’s own tracking URL. Two things happen when you use one:

The platform sees you arrive, and from that moment their policy is the one that applies. You are on their site, under their terms, and they will set their own cookies and run their own tracking, which may be a great deal more than a page counter. I have no control over any of it and no visibility into it. Their policy is the one to read, and every review here links to the site it covers.

I get a report with a number in it. The tracking URL carries a subID that names the page you clicked from, such as flingster-review or home, so the affiliate network can tell me that seven people clicked from that page and one signed up. It identifies the article, not you. I never receive your name, your email, your card, or anything you do on the platform after you land there.

I do not sell ad space, run banner networks, or let anybody else drop a script on this site. The only commercial relationship is the affiliate one, it is marked sponsored on every link, and it never changes what you pay.

There are pages here where I earn nothing at all. Flingster and FapChat are two of them, and they say so at the top.

Age

The site is about adult cam platforms. You need to be 18, or older where your jurisdiction says older, and you need to be somewhere that permits you to look at this. Nothing here asks a reader their age, and nothing here would let me tell one reader from another, so I hold nothing about a child to delete. If you believe otherwise, email me and I will look.

Your rights over your data

I hold no file with your name on it, because no part of this site asks for one. What exists is the page-counter record described above, and an IP address counts as personal data in the EU and the UK even when nobody has attached a name to it. So the honest answer is narrower than the one this page used to give:

  • Access, correction, export. I cannot find you in the counter to produce a record, because I have no identifier of yours to search with. If you can give me a date, a time and an IP address, I will look and tell you what is there.
  • Deletion. The refusal link above stops the collection going forward, which is the part I control. For what is already recorded, StatCounter is the data processor and its own policy is the route.
  • Objection. The refusal link, or an ad blocker. Neither costs you anything on this site: nothing here is gated, metered or personalised, so a reader who blocks the counter gets exactly the same site.

Email me either way and I will answer in writing.

Terms

Short version, because there is very little to agree to.

The reviews, ratings and prices on this site are my opinion and my research. Prices move. Every figure carries the date I last checked it, and the data page says which platforms I have confirmed at the checkout and which I have not. Check the price at the checkout before you buy. I say so on the redirect page too.

I do not guarantee that any platform here still works, still trades, or still offers what it offered when I looked. If something here costs you money because it was out of date, I am sorry, and I am not liable for it.

Links out go to sites I do not control. What happens there is between you and them.

I can change these terms or this policy. When I do, the date at the top of this page moves and the change is described rather than silently swapped in.

Contact

hello@camsite.org, which is also the address for everything else. The contact page says what to send.

What changed, and when

20 September 2026. The analytics section was false and is corrected. From 22 August 2026, when StatCounter went live on the published site, until today, this page carried a section headed “Analytics” that read:

“I do not run any today. If that changes I will use something cookieless that does not build a profile, and I will name it here on the day it goes live, with the date. If this section still says ‘none’ then none is what there is.”

The counter had been live for four weeks when that was read. The page description, the search listing and the social card carried the same claim in shorter form.

Two of those three sentences were promises about how this would be handled and both were broken: it was not named here on the day it went live, and “none” was what this section said while a counter ran. Nothing caught it, because the beacon was a fact about the build and the denial was a fact about a paragraph, and no file in this project held both. One does now, and a build that ships a counter this page does not describe fails before it can be published.

19 September 2026. The contact address moved from a Gmail account to one on this domain.