The operating entity, business contact details, production provider configuration, retention schedule, and legal review must be completed before commercial launch. No certification or compliance approval is claimed.
Agency access and workspace boundaries
The application uses managed authentication. Agency membership determines access to a workspace. Owner and member roles have different controls; billing, membership, and deletion actions require the appropriate authority. Founder growth tools are a separate permission boundary.
Request-scoped client links
Client grants are designed for one request, with expiration and revocation. The application exchanges the link secret for a bounded session. Possession of a valid link allows action within that request, so links should be shared carefully. Client identity is not independently verified by possession of a link.
Private files
Client files belong in private storage. Upload and download permissions must be checked against the request and workspace. File names are treated as untrusted metadata. The initial supported formats are JPG, PNG, WebP, PDF, TXT, and validated DOCX, with a default limit of 25 MB per file and 10 files per item.
Documents must be downloaded as attachments, not executed as trusted page content. A file is not described as malware-scanned unless a scanner actually processed it. Treat unscanned documents with care. Revoking access does not erase downloaded copies or instantly invalidate every previously issued, short-lived storage capability.
Deliberate review and message controls
Submissions are versioned. Acceptance is attached to the version reviewed. Saving a draft does not submit it; replacing a version requires a new review. Client reminders include only required missing items or requested changes, subject to notification permission and service availability.
Development and preview deployments keep external messages, billing actions, AI spending, outreach, and advertising disabled by default. Demonstration actions use isolated synthetic data.
AI usage and retention
AI checklist drafting reserves spending capacity before a provider request. Unresolved usage remains reserved until verified settlement, even after workspace deletion. Once workspace project records have been purged, scheduled maintenance removes identifying links and related description and provider details from the usage records. Minimized accounting records remain; cleanup may finish in a later batch and does not erase provider data or backups.
Deployment verification
Application code alone is not evidence of a secure live deployment. The commercial launch gate requires successful authorization tests, database policies, private-storage validation, configured provider credentials, operational monitoring, business details, and owner review. This preview does not claim a certification, penetration-test attestation, data-residency guarantee, or regulatory approval.
Report an issue
Report the affected page, approximate time, expected behavior, and a safe description of the issue. Do not include secret links, raw tokens, passwords, or other clients' content. The support and abuse-reporting channel below must be configured before customer use.
Contact and questions
For privacy, account, security, or abuse reports, use the configured contact below. Do not include passwords, access links, payment-card information, or client files in an initial report.
readyloom@gmail.com