Safety & Abuse Policy

1. Guild Isolation as a Core Safety Principle

Guild isolation is ScriptVault's foundational safety mechanism. Each server's library is completely separate from all other servers. No user can access another server's library data through any intended or unintended ScriptVault feature. Any attempt to access another server's library is treated as a P0 safety incident.

2. Upload Safety

ScriptVault validates uploaded files before storing them. Validation includes:

• File type verification (.gpc only)
• File size limit enforcement (per plan)
• SHA-256 hash-based duplicate detection
• GPC syntax validation and feature extraction

ScriptVault does not scan script content for malicious logic beyond structural validation. Server administrators are responsible for reviewing scripts before approval.

3. Storage Abuse

Plan limits exist to prevent storage abuse. Attempting to circumvent storage limits through automated uploads, bulk import abuse, or any other method is prohibited and may result in immediate library suspension.

4. Spam and Rate Limits

ScriptVault enforces rate limits on search commands and other high-frequency operations. Repeated triggering of rate limits may result in temporary command lockout for the affected user.

5. Circumvention Attempts

Any attempt to circumvent plan limits, guild isolation, approval workflows, or rate limits is a serious violation. This includes using multiple bot accounts, automated tooling, or exploiting bot edge cases. Circumvention attempts may result in immediate and permanent library suspension.

6. Report Abuse

The report system is intended for legitimate content concerns. Submitting false reports, harassing report submissions, or coordinating report campaigns against a user or script is prohibited. See the Content Reporting Policy.

7. Harassment

Using ScriptVault features to target, harass, or intimidate other users — including through report abuse, bulk actions against a specific user's uploads, or staff role misuse — is prohibited.

8. Suspicious Files

If a script is reported or flagged as potentially malicious, it may be quarantined pending manual review. Viridex Systems staff may review the file contents in this context. Confirmed malicious files are permanently removed.

9. Enforcement Tools

Viridex Systems has access to the following enforcement actions:

• Script level: reject, quarantine, archive, permanent delete
• Server level: upload suspension, bulk operation suspension, library suspension, library removal
• Platform level: escalation to Discord for Terms of Service violations

10. P0 Isolation Breach Protocol

Any confirmed or suspected breach of guild isolation triggers immediate incident response:

1. Affected servers are notified
2. Impacted functionality is suspended pending investigation
3. Root cause is determined and patched
4. Affected data is assessed and reported to relevant parties

11. Evidence Preservation

Evidence related to safety incidents, policy enforcement, or active investigations is preserved even if the underlying content has been removed. This includes logs, script files, metadata, and report records.

12. Appeals

Server owners may appeal enforcement actions through the ScriptVault Hub. Appeals are reviewed by Viridex Systems staff. Decisions on appeals are final during the alpha period. See the Support page.

Effective date: [to be set before public listing]