Safety Escalation

How urgent creator discovery reports involving safety, consent, age, exploitation, doxxing, or impersonation should be triaged and escalated.

Policy Desk

Regulation & Compliance

May 2, 2026·4 min read

JuicyScout, JuicyIndex, and JuicyPulse should prioritize reports that involve credible safety, consent, age, exploitation, doxxing, impersonation, or legal risk.

This page describes our escalation framework for support and trust review. It does not replace emergency services, legal advice, platform reporting, or law enforcement reporting where those channels are appropriate.

Issues That Need Priority Review

Escalate promptly when a report involves:

A minor or suspected minor.
Non-consensual intimate content or stolen material.
Trafficking, exploitation, coercion, blackmail, or threats.
Doxxing, private addresses, private contact details, government IDs, or payment information.
Exact or real-time location details.
Impersonation that could mislead users about official creator channels.
Links to leaked, hacked, subscriber-only, or otherwise private material.
A credible creator safety concern tied to offline harm, stalking, harassment, or event attendance.
A legal notice, regulator inquiry, or law enforcement request.

When a report is unclear but potentially severe, our reviewers will restrict or suppress the affected material while the case is assessed.

Initial Triage

We will capture:

The affected URL on JuicyScout, JuicyIndex, or JuicyPulse.
The reported creator username, display name, source URL, or official link.
The reporter contact information, if provided.
The specific safety concern.
Any public evidence or screenshots needed to understand the report.
Whether the issue appears urgent, ongoing, or connected to private information.
The immediate containment action taken, if any.

Do not ask reporters to send intimate content, government IDs, private addresses, passwords, or payment information through ordinary support channels.

Containment Actions

Depending on the report, reviewers may:

Remove or suppress a profile from discovery.
Hide a sensitive field.
Replace an exact location with a broader label.
Remove a link that appears unofficial, unsafe, or misleading.
Mark a profile, source, or claim as under review.
Block a source from future ingestion.
Pause refresh, ranking, or comparison use for the affected profile.
Route a copyright-specific issue to the DMCA workflow when appropriate.

Containment can happen before a final decision when continued display creates avoidable risk.

Escalation Review

Escalated cases should be reviewed for:

Severity and likelihood of harm.
Whether the affected material is public, private, creator-submitted, or unauthorized.
Whether the source appears official, disputed, impersonating, or stale.
Whether the report involves age, consent, exploitation, or legal obligations.
Whether the requester appears to be the creator or an authorized representative.
Whether re-ingestion should be blocked after removal or correction.

Cases involving minors, credible exploitation, law enforcement, legal notices, or imminent harm should not be handled as routine content edits.

Documentation

Internal records should capture:

Date and time received.
Reporter type, when known.
Affected URLs and source URLs.
Risk category.
Action taken.
Reviewer or escalation owner.
Follow-up needed.
Re-ingestion or source-block decision.

Avoid adding unnecessary private personal data to review notes. Store only what is needed to understand and audit the decision.

FAQ

Is every incorrect profile a safety escalation?

No. Routine typos, stale bios, and category corrections can use correction or claim workflows unless they create privacy, impersonation, consent, or safety risk.

Should support wait for full verification before suppressing dangerous material?

No. When a report credibly suggests severe risk, temporary suppression or field hiding can happen while verification continues.

Can copyright complaints use this process?

Use safety escalation for urgent safety concerns. Copyright-specific allegations should also be routed to the DMCA process when they involve alleged infringement.