Legal / Hosting

Sklash Content & Hosting Policy

Responsibilities and safety rules for user-created Sites, hosted files, media, domains, storage, bandwidth, and publication through Sklash.

Version: Sklash Legal v1.0 Beta Effective: August 13, 2026 Status: Official beta policy
Overview

What this means in practice

Explore the systems, responsibilities, and workflows behind this part of Sklash.

Hosted by Sklash

Sklash supplies storage, publishing, subdomain/custom-domain, and related hosting infrastructure according to the user’s service entitlement.

Controlled by the user

Users decide what lawful content to upload and publish and remain responsible for rights, claims, products, and public operation.

Safety controls

Uploads and activity may be scanned, logged, quarantined, blocked, preserved, or escalated by automated and manual protection systems.

Resource limits

Storage, bandwidth, file type/size, Site, Page, domain, and service limits may vary by entitlement and may be enforced automatically.

Hosted-content responsibility

Publishing through Sklash does not make Sklash the source of user-created material.

Account holders must ensure they have the rights and authority required for uploaded and published content. Sites using a Sklash subdomain and Sites using a custom domain are subject to the same baseline safety obligations.

Scanning and quarantine

Sklash may inspect technical signals and content for legitimate safety purposes.

Files and related metadata may be screened for malware, prohibited content, abuse indicators, known hashes or signatures, suspicious behavior, policy evasion, or other configured Trust & Safety signals. A scanner result is a signal, not necessarily a final factual determination.

Sklash may quarantine or prevent publication while a high-risk result is reviewed. Severe or credible risks may trigger immediate account restrictions and evidence preservation.

Repeat abuse

Network information may help identify patterns but is not treated as identity proof by itself.

Sklash may correlate accounts, events, IP/network information, provider identifiers, devices or derived technical signals where reasonably necessary to detect repeated abuse or evasion. Administrative alerts may be raised when multiple accounts appear connected to repeated prohibited activity.

Automated correlation must remain reviewable and subject to the configured retention, appeal, and evidence-handling rules.

Free vs. Hosting service

Different tiers can carry different capacity and hosting privileges.

Free Creator publishing may have lower storage, Site, Page, upload, file-type, bandwidth, domain, or other limits. A Hosting entitlement may provide additional capacity and hosting functionality. Commerce may separately unlock hosting capabilities needed to operate an eligible storefront without granting unrelated Creator capabilities.

A user may not evade service limits by fragmenting files or Sites across accounts, abusing remote loading/hotlinking, or using Sklash primarily as an external file-delivery network.

Continue

See prohibited material on a Sklash-hosted location?

Use the structured abuse-report channel so Sklash can preserve, investigate, route, and respond to the report.

Report abuse