Slew · beta policy

Seller responsibilities

The authority and accuracy commitments required when a release is published.

Authority

The publishing actor must be authorized by the seller organization and must have the right to distribute every included file and grant the stated terms.

Accurate listing

Titles, screenshots, videos, compatibility claims, limitations, deliverable categories, support statements, and release notes must accurately describe the exact published release.

Security disclosure

Static screening is limited. Sellers must not knowingly conceal malicious behavior, material credential exposure, or security limitations that would change a buyer’s decision.

Creator audience obligations

A seller may use exported active creator-audience contacts and consent provenance only for the selected purpose, must honor withdrawal and suppression, protect the data, and meet applicable obligations after export. Sellers may not treat acquisition, downloads, terms, follows, public acquisition visibility, or in-app notifications as permission, and may not grant or restore consent for a member.

Ongoing responsibility

Hosted products, external services, seller promises, and creator-audience handling after export remain the seller’s responsibility. Platform screening, delivery, and platform-controlled email infrastructure do not transfer that responsibility to Slew.

Beta policy version: 2026-08-20. Creator-audience email and raw active-contact export remain disabled until jurisdiction-appropriate legal review, creator obligations, authenticated sending, provider feedback and suppression, and a staging canary are complete.