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.
The service and its users
Readyloom is designed to help agencies request ordinary project information, files and approvals from clients. The agency would be the account customer; clients use scoped request links. Account users must be authorized to act for their workspace and provide truthful details. Clients should use only links intended for them.
Your content and permissions
You retain your rights in the content you provide. You are responsible for having permission to upload, share, request and process it. Agencies are responsible for appropriate instructions and notification permission. Do not collect passwords, API keys, payment-card information, government identity documents or medical records through the service.
Do not upload malware, attempt unauthorized access, bypass usage limits, infringe intellectual property rights, harass recipients or use the service to send unsolicited messages. A public business email address alone is not notification permission.
Project approvals
Approvals record a declared name, decision, timestamp and specified reference/version. They are project workflow records, not certified electronic signatures or independently verified proof of identity. Agencies must review submissions; file arrival does not mean a requirement has been accepted.
Proposed plans and commercial terms
The pricing page shows proposed recurring monthly plans in Canadian dollars and their intended usage limits. It is a pre-launch comparison, not an available purchase offer. Active requests, seats, storage and draft caps are defined in the product. A paid entitlement would depend on verified billing state, not a checkout redirect.
Before purchases are enabled, the owner must finalize and review the seller's identity, renewal terms, cancellation method and effective date, any proration, refund policy, and applicable taxes, then verify that the Stripe checkout and billing portal implement those terms. The full price and applicable charges must be disclosed before a customer agrees to pay. This draft does not promise a particular cancellation date or refund outcome, and it does not exclude or waive rights required by applicable law.
The current application does not automatically delete content on a downgrade; additional usage may be restricted until the workspace fits the plan. Trial and past-due access behavior is described on the pricing page. Those implementation details do not replace the final commercial disclosures.
Availability and integrations
Third-party hosting, storage, authentication, email, payment and optional AI services can affect availability. Live delivery, billing and AI execution remain disabled. Delivery states distinguish provider acceptance from actual delivery. Software controls cannot guarantee prevention of every provider failure or delayed event.
Workspace closure and retained information
Before closing a workspace, export the JSON records and separately download any uploaded originals you need. The JSON export includes file metadata, not file contents. Closure revokes ordinary team and client-link access. It does not itself cancel payment-provider billing or delete the Auth account. Outstanding Checkout operations and subscription cancellation must be resolved and verified through billing first.
Deleted project metadata defaults to a 30-day eligibility period, adjustable from 7 to 365 days. Eligibility is not a guaranteed purge date: stored-file removal, outstanding operations and capability holds can delay completion. Active and archived content, necessary billing and accounting records, suppression records, and the closed-workspace record used to prevent repeated trials have separate treatment. Provider records, backups and previously downloaded copies are not erased by workspace closure. See the privacy information for current behavior and the retention details still awaiting review.
Preview status and remaining legal terms
Readyloom is a working name. Company registration and trademark clearance have not been established. The operating entity, business address, governing law, dispute process and finalized commercial terms require owner-supplied information and legal review before customer use. This page claims no certification or regulatory approval and does not limit mandatory statutory rights.
You can raise questions or privacy concerns through the contact channel below while those details are pending. The draft status does not make applicable rights conditional on launch or owner review.
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