Every platform receives a score from 0 to 10 on each of seven criteria. The criteria are weighted because they are not equally important: a platform with excellent customer support but unwatchable streams is a worse cam site than one with mediocre support and 4K video, and the weights reflect that.

Criterion weights
Criterion	Weight
Stream Quality	20%
Verification and Deepfake Protection	20%
Pricing and Token Economics	15%
Anonymity and Privacy	15%
Interactivity (Cam2Cam, Toys, VR)	10%
Mobile Experience	10%
Customer Support	10%

The full score is the weighted average, expressed on a 10-point scale and rounded to one decimal.

1. Stream Quality — 20%

What we measure. Actual delivered resolution, not advertised. Bitrate stability over a continuous 10-minute private session. End-to-end latency measured from a model's action (tap, smile, hand-wave) to its appearance on the viewer screen. Frame-drop count per 10 minutes. Audio-video sync drift over the same window. Availability of 4K streams expressed as a percentage of the live model list at peak hours.

How we measure it. OBS Studio captures the encoded stream locally. Chrome DevTools network panel logs bitrate fluctuations and segment-load times. Latency is measured by having the model perform a synchronised action against a wall clock and timestamping the appearance on our screen against the same clock — repeated five times per session, median taken.

Scoring rubric:

10 / 10: Consistent 1080p or higher delivered, latency under 80 ms median, zero frame drops in a 10-minute window, 4K available on at least 5% of streams at peak.
7 / 10: 1080p available on most streams, latency 80–150 ms, occasional drops, no 4K.
4 / 10: Capped at 720p, latency 150–300 ms, frequent buffering.
0 / 10: Capped at 480p, latency over 300 ms, unwatchable on a 100 Mbps connection.

Why this is weighted highest. Stream quality is the single thing a cam site cannot fake. Marketing copy can claim "ultra HD," but a real ten-minute recording either holds 1080p at low latency or it does not.

2. Verification and Deepfake Protection — 20%

What we measure. Model identity verification depth. Document submission requirements. Liveness checks. Public reporting tools and their response times. Presence of deepfake detection on uploaded content (clips, photos, profile media). Public removal-request policy for non-consensual content. Time-to-takedown on test reports we file ourselves on demonstration content.

How we measure it. We attempt to register as a model on each platform using a documented test identity. We log every verification step required. We file a takedown request on a publicly available test clip (where legally and ethically possible to simulate) and time the platform's response. We review the platform's published trust-and-safety policy line-by-line against the eight items on our verification checklist.

Scoring rubric:

10 / 10: Government ID plus selfie plus liveness check required, photographic verification of every uploaded clip, public deepfake detection tooling disclosed, takedown response under 24 hours, published incident report.
7 / 10: ID and selfie required, no deepfake disclosure, takedown response 24–72 hours.
4 / 10: Light verification, takedown response 3–7 days, no deepfake policy.
0 / 10: No verifiable identity checks, no published takedown SLA, or evidence of unresolved non-consensual content reports older than 30 days.

Why this is weighted equal-highest. A cam site that cannot guarantee the people on screen are who they say they are, with consent, is not a cam site we are willing to recommend, regardless of price or features.

3. Pricing and Token Economics — 15%

What we measure. Real cost per minute of a typical private show, computed end-to-end: (USD price of token package ÷ tokens in package) × tokens-per-minute charged by the median model in that platform's most popular category. Token-package pricing tiers and the discount structure across them. Existence and meaningfulness of welcome bonuses. Presence and depth of public price disclosure (do they show prices before sign-up, or only after?). Crypto payment options and their effective fees. Currency support outside USD.

How we measure it. We buy at least one starter token pack and one mid-tier pack per platform. We log the actual delivered tokens, including any platform bonus. We then time a 10-minute private session with a median-priced model and compute the real per-minute cost. We repeat this for cam2cam and group shows where they exist. All purchases use the same test credit card across platforms for parity.

Scoring rubric:

10 / 10: Effective private-show cost under $3 per minute on a mid-tier pack, transparent pricing shown before sign-up, USDT or BTC accepted with under 2% effective fee, meaningful welcome bonus.
7 / 10: $3–$5 per minute, transparent pricing, crypto accepted.
4 / 10: $5–$8 per minute, opaque pricing, no crypto.
0 / 10: Over $8 per minute or pricing only revealed after card-on-file.

Why 15% and not higher. Price matters, but cheap streams that buffer at 480p are not a bargain. We deliberately rank price below quality and trust.

4. Anonymity and Privacy — 15%

What we measure. What information is required at sign-up. Whether email verification is mandatory. Whether the platform allows anonymous viewing of public streams. Payment-method anonymity (crypto support, prepaid-card support, gift-card support). Cookie and tracker count on the landing page measured against a clean Chrome profile. Third-party analytics presence. Whether the username appears in tipping events visible to other users. Data-retention policy for chat logs and viewing history.

How we measure it. Fresh Chrome profile, no extensions, no prior cookies. We sign up with the minimum data the platform accepts. We log every required field. We capture all third-party trackers using DevTools and a known tracker-detection list. We make a small purchase using a privacy-focused payment method where supported. We read the privacy policy against our 14-point checklist.

Scoring rubric:

10 / 10: Public streams viewable without sign-up, optional email, no email verification required for basic features, crypto and prepaid cards accepted, fewer than five third-party trackers, public username does not link to payment identity.
7 / 10: Sign-up required but minimal data, some anonymity-preserving payment, moderate tracker count.
4 / 10: Full sign-up required, no anonymous payment methods, heavy tracking.
0 / 10: Real-name verification required for any use, no privacy-preserving payment, evidence of data sale to third parties.

5. Interactivity — Cam2Cam, Toys, VR — 10%

What we measure. Cam2Cam availability, latency in cam2cam mode, and whether models can hide their counterpart from chat viewers. Interactive toy support: which protocols are integrated natively (Lovense, Kiiroo, OhMiBod), latency from tip-to-vibration, and whether tipping ranges are configurable per model. VR support: which headsets are supported, the percentage of live models offering VR streams at peak hours, and the resolution and latency of VR streams specifically.

How we measure it. We run at least one cam2cam session per platform that offers it. We tip a Lovense-equipped model in increments and time the vibration response with a stopwatch from tip-confirmation to first toy reaction. We test VR streams on the headsets the platform claims to support (we maintain Meta Quest 3 and Apple Vision Pro test units for this cycle).

Scoring rubric:

10 / 10: Cam2cam with under 150 ms round-trip latency, native Lovense plus Kiiroo plus OhMiBod with under 800 ms tip-to-toy latency, VR available on at least 3% of live models with sub-100 ms latency, multi-headset support.
7 / 10: Cam2cam available, one toy protocol native, VR available but limited.
4 / 10: Cam2cam only, no native toys, no VR.
0 / 10: No interactive features beyond text chat.

6. Mobile Experience — 10%

What we measure. Native iOS and Android app availability (and whether they are in official stores or sideloaded). Mobile web parity with desktop in terms of features available. Stream quality on mobile expressed against the desktop baseline (does a 1080p desktop stream still deliver 1080p on mobile?). Touch-target sizing and one-handed usability of the tipping interface. Push-notification policy. Battery-drain during a 10-minute stream measured against a reference baseline.

How we measure it. We test on a real iPhone (current generation) and a real mid-tier Android device. We run identical 10-minute private sessions and compare resolution, latency and battery drain against the desktop baseline. We attempt every flow a paying user runs: sign-up, deposit, private-show start, tipping, leaving a tip note, closing the session.

Scoring rubric:

10 / 10: Native iOS plus Android apps available through official channels, full feature parity with desktop, no resolution downgrade, battery drain under 8% per 10 minutes on a current-generation device.
7 / 10: Strong mobile web, no native app or apps available only via sideload, minor feature gaps.
4 / 10: Mobile web works but feels unfinished, noticeable feature gaps.
0 / 10: Mobile experience is broken or significantly less safe (e.g. unencrypted payment flow on mobile only).

7. Customer Support — 10%

What we measure. Available support channels (live chat, email, ticket system, phone, social). Response time on a real test ticket we file ourselves on a documented payment issue. Resolution time on the same ticket. Quality of the response (canned vs. specific). Availability hours and languages. Public refund policy and how it is applied in practice when we test it.

How we measure it. We file an identical test ticket on every platform during the testing window: a payment-related question with a clear correct answer. We time the first response. We time the resolution. We score the quality of the response on a 5-point internal scale and convert to the 0–10 main scale. Where a refund is appropriate by the platform's own published policy, we request it and log whether it was granted.

Scoring rubric:

10 / 10: First response under 30 minutes via live chat, full resolution under 4 hours, specific (non-canned) reply, multilingual support, public refund policy honoured without escalation.
7 / 10: First response under 6 hours, resolution under 48 hours, generally helpful.
4 / 10: Email-only support with 24–72 hour responses, generic replies.
0 / 10: No support response within 5 business days or evidence of refund policy not being honoured.