Privacy Policy

Overview

What this means in practice

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

Purpose-limited collection

Sklash collects information needed to provide accounts, Sites, hosting, security, support, Commerce, and other requested services.

Security and abuse records

Safety events, upload attribution, policy acceptance, reports, IP/network information, and related evidence may be retained for security and enforcement.

User controls

Account settings, export/deletion features, and support channels provide available ways to review, correct, or request handling of account information.

Retention and beta resets

Retention is purpose-based. Planned beta resets may permanently delete ordinary beta data, while legal or safety holds may preserve specific records longer.

1. Information Sklash handles

Information is collected when necessary to operate or protect Sklash.

Account and identity information, including supported authentication-provider identifiers and account profile data.
Workspace, Site, Page, component, media, domain, publishing, collaboration, and configuration information.
Commerce, order, provider-connection, payment-status, and fulfillment information when Commerce features are used. Sklash does not treat a payment-provider confirmation as permission to collect unnecessary payment credentials.
AI conversations, prompts, generated results, proposals, mission context, and provider-operation metadata when AI features are used.
Security, diagnostic, Trust & Safety, policy-acceptance, abuse-report, copyright-notice, enforcement, appeal, and account-recovery information.
Technical information such as timestamps, browser/user-agent information, IP/network identifiers, session/security state, and system logs when reasonably needed for operation, fraud prevention, abuse response, or security.

2. Purposes

Sklash uses information for identified service and protection purposes.

Provide, authenticate, personalize, maintain, troubleshoot, and improve requested Sklash services.
Publish and host user-directed Sites and assets, operate domains, and deliver requested Commerce or AI workflows.
Detect malware, fraud, prohibited content, account compromise, policy evasion, attacks, and other threats.
Investigate reports, preserve evidence, administer strikes or restrictions, process appeals, and comply with lawful obligations.
Communicate material service, security, policy, account, or operational information.

3. Providers and disclosure

Information may be shared only where a service, legal, or protection purpose requires it.

Sklash may use third-party providers for authentication, hosting/infrastructure, email, AI processing, payments, fulfillment, monitoring, analytics, domain services, or other configured platform functions. Those providers may process information under their own terms and privacy obligations.

Sklash may preserve or disclose information when required by applicable law, valid legal process, or when reasonably necessary to protect Sklash, users, third parties, or the integrity of the service, subject to applicable legal limits.

4. Retention and safeguards

Ordinary data is not kept merely because it can be kept.

Sklash uses purpose-based retention and access controls. Security and Trust & Safety evidence may have different retention periods from ordinary creator data. Active legal, copyright, safety, fraud, or investigation holds may suspend normal deletion for the affected evidence.

Sklash uses reasonable administrative, technical, and organizational safeguards appropriate to the nature of the information and the current service. No online service can guarantee absolute security.

5. Beta data

Open-beta data may be intentionally reset.

During the open beta, Sklash may intentionally wipe or recreate the beta database. Accounts, Workspaces, Sites, pages, uploads, settings, AI history, Commerce test records, and other ordinary beta data may be permanently deleted. Keep independent copies of anything important.

A beta reset does not require Sklash to destroy records that must reasonably be preserved under a legal, safety, copyright, fraud, security, or investigation hold.

Questions

Clear answers before the next step

These answers describe the current pre-release service and may evolve as Sklash approaches production.

Does Sklash use IP addresses for Trust & Safety?

Sklash may record IP or network information as a security and abuse-prevention signal. It is not intended to be used as proof of identity by itself, and retention remains subject to defined purposes and applicable rules.

Can I rely on Sklash as my only backup during beta?

No. Planned beta resets may permanently delete ordinary beta data, so users should keep independent copies of important material.

Can safety evidence outlive a deleted account?

It may where a legitimate retention purpose or active legal, security, copyright, fraud, abuse, or investigation hold requires preservation, subject to applicable law.

Continue

Privacy works together with the Sklash Terms and safety policies.

The Terms describe account responsibility, hosting, content, enforcement, beta conditions, warranties, and service boundaries.

Read the Terms of Service