Acceptable use

Sklash Open Beta Acceptable Use Policy

Rules that protect Sklash, its users, infrastructure, providers, and the public during open beta.

Overview

What this means in practice

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

Build responsibly

Use Sklash for lawful websites, content, testing, and creator workflows that you have the right to operate.

Protect the platform

Do not attack, overload, scrape, probe, bypass, or interfere with Sklash systems, limits, accounts, or connected providers.

Respect other people

Do not publish deceptive, abusive, exploitative, privacy-invasive, infringing, or harmful content.

Beta enforcement

Sklash may restrict features, remove content, pause publishing, or suspend accounts while investigating risk during beta.

Prohibited activity

Do not use Sklash to harm people, systems, or legitimate rights.

  • Malware, phishing, credential theft, impersonation, fraud, scams, or deceptive collection of information.
  • Harassment, threats, exploitation, non-consensual intimate content, or content that facilitates serious harm.
  • Copyright, trademark, privacy, publicity, or other rights violations.
  • Attempts to bypass beta limits, authorization boundaries, account controls, payment protections, or AI-provider safeguards.
  • Automated activity that creates unreasonable load, cost, spam, or disruption.
Creator responsibility

You remain responsible for what you create, connect, and publish.

Review AI-generated content before using it. Confirm that you have permission to use uploaded media, customer information, brand assets, domains, and published claims.

Report suspected security problems privately through the beta feedback channel rather than exploiting or publicly disclosing them before Sklash can investigate.

Continue

Acceptable use works together with the Open Beta Terms.

The Terms explain beta availability, data resets, user responsibilities, and feature changes.

Read the Open Beta Terms