ShuffleCrush

Moderation Policy

Last updated: October 22, 2026

ShuffleCrush is a one-to-one live video chat platform. Calls are real-time streams relayed through our video provider's media servers: ShuffleCrush does not record or store them and cannot replay them. We cannot technically prevent a participant from recording on their own device, which is why that is prohibited without consent. This revised policy is an unpublished preparation; dated production observations below are not proof of deployment of this revision.

1. No Recording, and What That Means for Moderation

ShuffleCrush does not record, store, transcode, or archive video or audio from any call. There is no recording feature in the product: the video provider's media servers forward streams in real time and no ShuffleCrush component stores a copy. Calls use transport encryption, not end-to-end encryption.

Because no recording exists, we do not claim to review call video after the fact. Instead, moderation is enforced through pre-call gating, in-call user controls, report-triggered investigation of the metadata and evidence we do hold, and account-level enforcement.

Separately from any after-the-fact review, authorised moderation personnel may observe a live session in real time where there is a safety, compliance or enforcement reason to do so. Real-time observation is limited to authorised moderation staff, requires the session to be selected explicitly, is logged in an internal moderation access log, and is not recorded by us: nothing is captured, stored or replayed.

The evidence available to a moderator for a reported call consists of: the report itself (reason, free-text description, reporter, reported user, call identifier, timestamp), the session record for that call (participants, duration, join and leave events, device and network signals, disconnect reason), any text chat exchanged during that call, and the full enforcement history of both accounts.

2. Who Is Allowed on the Platform

Access is restricted to adults (18+). No one can appear on camera as a host without passing identity and age verification first.

  • every account must confirm it is 18 or older at registration;
  • hosts must additionally complete identity verification before they can ever be matched. A new host verification requires a declared legal name, a declared date of birth that is checked against the 18+ requirement, a supported government-issued photographic identity document — a passport, a national identity card, or a residence permit — and the live gesture evidence described below;
  • the live gesture evidence consists of images captured in the moment showing specific requested hand gestures, used to establish that a real, present adult is behind the account;
  • every submission is reviewed by an authorised human reviewer, not by an automated pass. The reviewer checks the declared identity details against the document and compares the portrait on the identity document with the live gesture evidence;
  • a submission cannot be approved while the required identity-document evidence is missing or incomplete; this is enforced by the platform itself, not only by the reviewer;
  • only approved hosts may participate as verified hosts. Unverified, pending or rejected accounts cannot be shown to other users as hosts;
  • historical host approval alone does not establish current eligibility. In the original 178-host legacy cohort, the 20 October 2026 snapshot (16:11 UTC) recorded 7 completed reverifications and 171 outstanding, with all 171 outstanding enforced-blocked. The communicated 25 September deadline was distinct from actual enforcement activation on 1 October; new sessions and tokens recheck the current eligibility authority;
  • verification can be revoked at any time by a moderator. Revocation is a distinct, recorded enforcement state: the account is immediately taken offline, removed from matching, and cannot host again unless it is re-verified.

To be explicit about what this process is not: ShuffleCrush does not perform automated biometric or facial-recognition matching, does not query any government or third-party identity database, does not run automated document text extraction as a verification step, and does not use a third-party identity-verification provider. The comparison between the identity document and the live evidence is made by an authorised human reviewer.

Identity documents and live verification images are stored in restricted, non-public storage. They are never shown to other users, and are accessible only to authorised administrators and compliance personnel through short-lived, single-use links generated for a specific review.

Host identity review described here is separate from consumer age assurance. Consumer procedure v2.2 is an October 1 review draft; implementation evidence v1.2 is also held in the Library. Their receipt or adoption by Segpay has not been established. Current consumer-provider completion and configuration are not proved by this policy; unchanged age-assurance gates fail closed when required proof is missing.

The 20 October 2026 snapshot (16:08 UTC) recorded 532 approved host profiles, of which 20 hold a current host agreement acceptance — all version 1.1 matching the current package — and 512 do not. Current agreement enforcement has been active since 4 October 2026 12:17:43 UTC. Approved does not mean eligible: approval of a profile is not permission to go live; current agreement, reverification and applicable declaration requirements are rechecked. Existing sessions predating agreement enforcement have a specific continuation exception; a new reviewer counterpart has no such exception.

3. Controls During a Live Call

Every user has immediate, one-tap safety controls available at all times during a call, without leaving the call or navigating away:

  • end or skip the call instantly, which terminates the stream on both sides;
  • mute their own microphone or disable their own camera;
  • report the other participant from inside the call, without ending it;
  • leave at any time — no user is ever required to stay in a call.

Filing a report always and automatically separates the two accounts. This is unconditional: the two users are permanently excluded from ever being matched with each other again by the matchmaking system. It is not an optional checkbox, and it does not depend on the outcome of the review.

4. Reporting and Human Review

Reports can be filed during a call or afterwards, and are categorised by reason (for example nudity or sexual content involving a non-consenting party, harassment, threats, scams, underage suspicion, or illegal content). Users may add a free-text description.

Reports enter a moderation queue for human review. The owner alone currently handles moderation, is variably available, and has no fixed hours and no backup. No 24/7 monitoring or guaranteed urgent-response interval is claimed. Automated analysis may assist prioritisation; it is not automated live-video or CSAM detection and does not establish that a person has reviewed every report.

  • reports flagging child safety or other illegal content are triaged ahead of all other work;
  • moderators see the full report, the session record, chat content from that call, and both accounts' complete enforcement history;
  • every moderator action is written to an immutable audit log identifying the moderator, the action, the reason, and the timestamp;
  • repeat reports against the same account escalate automatically to higher-severity review;
  • accessing a moderation case is itself logged, so review activity is auditable.

5. Enforcement Actions

Depending on severity and history, a moderator may:

  • record a warning on the account;
  • restrict specific capabilities, including removing an account from matching;
  • revoke host verification, taking the account off camera immediately;
  • suspend the account temporarily;
  • permanently ban the account and block re-registration signals associated with it;
  • withhold or reverse payouts associated with the conduct;
  • escalate to law enforcement or the relevant national hotline.

Enforcement is applied to the account, not merely to a single call, because we cannot re-watch a call. Patterns of reports are therefore weighted heavily.

6. Illegal Content and Child Safety

Child sexual abuse material, any sexual content involving a minor, non-consensual content, coercion or trafficking indicators, and violent or terrorist content are absolutely prohibited and result in immediate permanent removal.

Any report or moderator observation of this kind is entered into a dedicated illegal-content escalation register, separate from ordinary moderation. For each escalation we record the category, the accounts involved, the originating report, the reviewing moderator, the action taken, whether an authority or hotline was notified, the name of that authority, and any reference number they returned.

Opening an escalation automatically places a preservation hold on all associated evidence. Records under preservation hold are exempt from every automated retention purge and cannot be deleted by routine data lifecycle jobs; they are retained until the hold is explicitly released by a moderator after the matter is concluded.

We cooperate with law enforcement and with national reporting hotlines, and will preserve and disclose the evidence described in section 1 in response to a valid legal request.

7. Evidence Retention

Moderation records are retained under a published retention schedule that is enforced automatically by a scheduled daily job, not manually. The schedule distinguishes between record types: enforcement decisions and audit logs are retained longer than transient technical session data, and in-call chat content is purged on a short cycle.

Host verification evidence is handled separately from moderation records. Raw evidence — the identity-document images and the live gesture images — is kept only while it is legitimately required for the active verification and compliance relationship, and is separated from the minimal verification metadata we keep for longer. That metadata is limited to the submission reference, the verification result, the document type, the review timestamp, the reviewer or audit reference, and the retention or hold state of the record. We do not keep document image contents, full document numbers, extracted document text, or reusable access links beyond that point.

Raw verification evidence follows one central, server-side retention policy host-evidence-v1, adopted by ShuffleCrush on 22 October 2026 as its own business decision (not an approval by a regulator, legal adviser or payment processor) and due for review by 22 January 2027: the essential identity proof, the verification decision and the signed performer agreement are kept for the whole host relationship and then for 7 calendar years from the later of the definitive end of the relationship or the last substantive change to that record; extra live gesture images are kept for 90 days after a definitive verification, but only where sufficient lasting core evidence has been explicitly established; evidence from a rejected application that was never approved and never performed is kept for 30 days after any applicable appeal is closed; and uploads proven never to have been used are kept for 7 days after upload. Where a required date or fact has not been recorded, the evidence is kept rather than deleted early — an end of the relationship is never assumed from inactivity. Automated deletion of production evidence is not active yet. When it is switched on, it is first limited to uploads proven never to have been used, and existing host identity records stay retained.

Two exceptions override every schedule: records under a preservation hold from an illegal-content escalation, and records under a documented legal or compliance hold — a regulatory or legal request, a fraud investigation, a chargeback or dispute, or a complaint or investigation. A hold is opened only for a specific documented reason, never by default for every account. While a hold is open, the evidence it covers is exempt from automated deletion and is also preserved if the account itself is deleted; the rest of that account's data is still deleted or anonymised as normal. Under the retention policy, every open hold is reviewed at least every 90 days.

Because no call video or audio exists, none is retained.

8. Appeals

Any user subject to a suspension, ban, or verification revocation can see the decision and its reason in their account, and can submit an appeal from within the product.

Appeals are reviewed by a human moderator, and the outcome, the reviewing moderator, and the reasoning are recorded. Where an appeal succeeds, the enforcement action is reversed and the reversal is logged.

Moderation decisions are final once the appeal process is exhausted, where permitted by law. Nothing in this policy limits your statutory rights, including your rights under the GDPR.

9. Contact

Safety, abuse, and illegal-content reports: [email protected]. Reports concerning child safety or an immediate risk of harm are prioritised over all other correspondence.