Evidence
Reports, scans, provider signals, account history, technical evidence, and administrator review can contribute to an incident record.
Legal / Enforcement
Sklash Enforcement & Appeals Policy
How Sklash applies warnings, strikes, restrictions, quarantine, suspensions, evidence retention, incident review, and appeals.
Overview
What this means in practice
Explore the systems, responsibilities, and workflows behind this part of Sklash.
Proportional response
Responses can range from education or quarantine to capability restrictions, Site suspension, or account termination.
Repeat-abuse detection
Strikes and correlated risk signals can identify patterns requiring stronger review or administration alerts.
Appeal
Where available and appropriate, users may challenge an enforcement action and provide context for administrative review.
Enforcement factors
Sklash considers more than a raw strike count.
- Severity and immediacy of the risk.
- Confidence and quality of the available evidence.
- Whether the activity appears accidental, negligent, deliberate, repeated, coordinated, or evasive.
- Prior warnings, strikes, restrictions, appeals, account recovery events, and relevant provider or security signals.
- Potential harm to users, third parties, infrastructure, providers, or legal obligations.
Three-strike policy
Three strikes are an escalation rule, not a promise of three chances.
Sklash may use three qualifying strikes as a repeat-abuse threshold for stronger administrative review or enforcement. Accounts or related accounts may be escalated when multiple qualifying events indicate a pattern.
Severe unlawful exploitation, credible malware/phishing, serious fraud, active compromise, dangerous attacks, or similarly high-risk conduct may result in immediate protective action regardless of prior strikes.
Appeals and recovery
Review should be possible where it can be offered safely and lawfully.
An appeal may consider mistaken identity, false positives, authorization evidence, remediation, compromise of an account, or other relevant context. Filing an appeal does not automatically restore content or capability while a serious risk remains unresolved.
Account recovery following suspected compromise is distinct from excusing deliberate policy abuse and may require identity/account verification and security remediation.
Evidence retention
Retention follows policy and active holds.
Incident evidence is retained according to configured Trust & Safety retention policies. Active legal, copyright, security, fraud, safety, or investigation holds can suspend ordinary deletion for relevant evidence. Access should be limited to authorized operational or administrative purposes.
Continue
Read Acceptable Use
Enforcement is grounded in the conduct rules.
Review the Acceptable Use Policy for the categories of content and behavior that may trigger these responses.