Policy draft: operator details and legal review are required before public launch.
Security statement
Policy version: 2026-10-09
Security practices
The service uses hashed passwords, server-side workspace checks, private file storage, rate limits, and signed billing webhooks. Production requires HTTPS, protected secrets, maintained dependencies, tested backups, and a running queue worker.
Reporting vulnerabilities
Use the contact channel below for security concerns. Do not include passwords, tokens, or private customer files in ordinary feedback. Do not test other accounts or disrupt the service. No certification or absolute security guarantee is claimed.
Operator and contact
- Operator
- To be confirmed before launch
- Contact email
- To be confirmed before launch
- Address
- To be confirmed before launch
- Jurisdiction
- To be confirmed before launch
- Hosting region
- To be confirmed before launch
- Service providers
- To be confirmed before launch
- Retention details
- To be confirmed before launch