Publish only what you can stand behind

01

Required rights declarations

• You have the right and authority to submit every included file and grant the limited service permissions described in the Terms.
• License, attribution, asset source, third-party notice, and modification statements are complete and accurate.
• You have reviewed the artifact, including AI-assisted output, and disclose the tools and scope required by the submission form.
• You accept the current submission-rights-v1 attestation. False or incomplete declarations can block validation, publication, or continued listing.

02

Content we do not accept

• Malware, exploit code intended to cause harm, credential theft, tracking that is not declared and approved, or attempts to escape the preview or validation boundary.
• Passwords, access tokens, private keys, private Prompt, confidential source, unnecessary personal data, or data obtained without authority.
• Content that infringes copyright, trademark, privacy, publicity, contractual, or other rights; unlawful harassment, fraud, impersonation, or deceptive endorsement.
• Dependencies, remote resources, active behavior, or public claims that conflict with the submitted metadata, declared license, platform allowlist, or review evidence.

03

Validation and moderation

Uploads remain quarantined while strict structure, dependency, secret, rights, and preview checks run. A passing scan is evidence for review, not a guarantee of safety, quality, legality, or publication.

Authorized reviewers can request changes, reject, approve, feature, disable, or withdraw a listing. High-risk state changes require a recent administrator session, scoped permission, rate-limit capacity, and an audit event.

04

Rights complaints and counter-notices

Use the rights category in Support & requests. Identify the work or mark, the affected SlideBlocks URL or coordinate, your relationship to the right, the requested action, and a way to verify the claim. Do not send credentials or unrelated personal data.

SlideBlocks records the request, preserves relevant evidence, checks identity and scope, and can temporarily disable access while risk is assessed. The submitter may be asked for a focused response or counter-notice. Restoration, modification, or continued removal is an attributable moderation decision—not an automatic result.

05

Emergency security reports

Use the security category for active compromise, leaked secrets, malicious artifacts, or isolation failures. Include only the minimum reproduction details and non-sensitive request or release identifiers. Do not publish a working exploit or another person’s private data.

Maintainers may revoke sessions, disable content, pause processing, rotate secrets, preserve logs, or isolate affected resources. Risk determines priority; this pre-production policy does not promise a public response or resolution time.

06

Appeals, withdrawal, and policy changes

Use Support & requests to appeal a decision or withdraw content. Include the affected coordinate and decision Request ID when available. Repeated, deceptive, or abusive requests may be rate-limited or closed.

Material changes update the policy version and effective date. Earlier immutable submission attestations remain linked to the version accepted at submission.