Closed beta terms
DesirForge Beta Testing Terms
These draft terms support closed beta validation. They are not legal advice and do not replace attorney-reviewed production terms.
Testing boundary
Beta testers validate discovery, intake, delivery workspace, order lifecycle, support, disclosure, and admin visibility with safe test data.
Public beta scope
This beta is a non-paid preview. Paid transactions are disabled, payment states are mock/local validation only, and buyer file uploads are unavailable while production storage and scanning proof remains open.
AI-powered delivery disclosure
DesirForge uses an AI-powered delivery team and automated agent workforce. The experience may feel consultative, but testers are not hiring hidden human freelancers.
Data safety
Do not submit secrets, credentials, regulated data, protected customer records, private keys, tokens, or production-only information during beta testing.
Feedback and support
Each tester should submit feedback through `/beta/feedback`. Blockers, bugs, security concerns, and support issues should be submitted through `/beta/support` for operator triage.
Launch limitation
Controlled public beta readiness does not authorize public production launch. Attorney review, real external beta sessions, production storage/file scanning, production deployment proof, rollback approval, and production gates remain required.