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 accounts and client information
Readyloom uses agency account details, workspace membership, client contact and notification-permission records, request instructions, submitted answers, uploaded files, project approvals, and review history to provide its collection workflow. Billing records identify the subscription and its status; payment-card entry belongs to the payment provider.
Agencies decide what ordinary project information they request from clients. The product is not intended for medical records, identity documents, payment-card information, passwords, or API keys. For access to another platform, clients should invite an agency-owned email through that platform.
Information supports authentication, request sharing, private file storage, versioned submissions, review, authorized transactional reminders, subscription enforcement, abuse prevention, and troubleshooting. Contact information alone is not treated as permission to send marketing.
Before a new workspace or team membership is opened, the application requires acknowledgement of an approved terms version. It records the verified account identifier, terms version, text hash and acceptance time, and preserves the exact agreement text. This acknowledgement does not opt you into marketing or optional measurement. The receipt remains separate from workspace records; workspace closure does not erase it, while deletion of the Auth account removes its associated receipt from the application database. Provider backups have separate retention. Final terms and the retention basis still require review before enrollment opens.
Readyloom prospect and contact records
The operator has separate tools for managing potential business customers. These can hold business names and websites, business contact names, roles and email addresses, source links and observations, notes, contact-permission evidence, outreach drafts, reply status and limited message headers, and opt-out records. Sources can include information a person provides, operator-entered records and public business websites. These records support research, review of possible business relevance and permission-based follow-up; they are separate from an agency's client workspace.
A public contact address is not, by itself, permission to send a message. Suppression records are kept separately to prevent further contact after an opt-out. Live research, AI drafting, outreach and mailbox polling remain disabled pending their separate approvals and configuration. The final retention schedule and provider data flows for these records still require review before those features are activated.
Service providers and processing locations
The application is built for Supabase authentication, database and private storage; Stripe subscriptions; Resend transactional email; and Vercel hosting. The configured Supabase project is in Canada Central. Resend stores account data, including email metadata and logs, in the United States. This does not establish that all information stays in Canada. Production processing locations, provider access and retention terms must be verified before launch; customer enrollment, live delivery and subscriptions are not open.
Optional AI features
Agency checklist drafting would send the project description supplied by the agency to OpenAI when enabled. That feature does not automatically send client answers or uploaded files. Do not put confidential client information or credentials in a drafting prompt.
Separate founder tools would send a company name, website and niche for business research, or selected business details, contact name and role, and supporting observations and source excerpts for outreach drafting. Content drafting uses the operator's selected brief. These are different data flows from agency checklist drafting. AI features are currently disabled; enabling them requires separate provider, budget and data-handling review. Generated text still requires human review.
Client links and necessary cookies
A client link grants access to one request. Anyone holding a valid link may act within that request; the link does not prove their identity. Treat links as private and ask the agency to revoke a link shared with the wrong person. Session cookies support authenticated access. Portal tokens and client content must not be used in advertising events.
The authentication library requests a cookie lifetime of up to 400 days when it writes an authentication cookie; a refresh can renew that cookie. This is not a promise of 400 days of account access or token validity. Token expiry, session revocation, sign-out and browser limits can end access or remove cookies earlier. Cookie lifetime is separate from the retention of account and project records.
Public demo and optional measurement
The interactive demo uses fictional data in your browser tab. Its sample uploads do not read or transmit your files. Resetting or reloading clears demo changes. It does not send messages or create subscriptions. No advertising pixel or third-party analytics script is currently installed, and private client portals do not collect marketing attribution.
When optional campaign measurement is enabled, Privacy choices lets you allow or decline it. The choice cookie is set for 180 days. Choosing Allow can separately save an allowlist of campaign labels in a protected cookie for 30 days. The product does not silently capture the labels again after expiry. At agency workspace creation, those labels may be linked to that workspace for up to 180 days. Reports keep absent, expired or withdrawn attribution as unknown. Browsers may remove cookies sooner.
Withdrawing through Privacy choices saves a declined choice in this browser immediately and requests removal of its campaign record. If signed in as the workspace owner, withdrawal also requests removal of linked workspace attribution. If the connection fails, an encrypted browser record may remain until it can be cleared or expires, but the declined choice prevents its use for measurement. The product reports incomplete removal and lets you retry. A minimal account withdrawal timestamp prevents older consent from restoring linked attribution; that timestamp contains no campaign labels and is removed when the Auth account is deleted. Workspace closure does not itself delete that account.
Export, closure and retention
The workspace export contains JSON records, including settings, clients, requests, submission and review history, comments, and file metadata. It does not contain the uploaded file contents. Download any originals you need separately through their authorized download controls before closing the workspace, because closure revokes ordinary workspace and client-link access.
Deleted project metadata has a default retention setting of 30 days, adjustable by the workspace owner from 7 to 365 days. This controls eligibility for scheduled purge, not a guaranteed deletion deadline. Stored files must be confirmed removed, and upload-capability holds, unresolved deliveries and billing operations can postpone completion. Active and archived requests remain stored; archived files continue to count toward storage. Production maintenance schedules and provider backup timelines still require verification.
Workspace closure does not automatically delete the Auth account or every billing, suppression or accounting record. A small closed-workspace record linked to its owning user remains to prevent repeated trials. Retained billing can remain available to the owner while outstanding operations are reconciled. Provider-side records and backups follow separate rules, and deletion cannot remove copies already downloaded by an authorized person.
After project records are purged, scheduled maintenance removes identifying workspace and user links, description fingerprints and raw provider response or error details from eligible AI checklist usage records. Cleanup may finish in a later batch. Minimized accounting records remain to reconcile costs and prevent duplicate processing; they are not treated as anonymous. Unresolved usage stays reserved against spending limits until verified settlement.
Suppression records survive workspace purge to prevent further contact. The final retention basis and periods for account identities, closed-workspace records, billing, suppression and accounting must be settled and disclosed before customer use. This draft does not promise that closing a workspace erases all information.
Questions and privacy requests
Use the Readyloom contact channel for questions, access or correction requests, deletion requests, objections to contact, or privacy complaints. State whether your request concerns an agency workspace or Readyloom's own prospect records. Clients can also contact the requesting agency about project information it controls. Do not include passwords, private links or client files in the first message; identity or authority may need to be checked before information is disclosed or changed.
Requests to delete an Auth account are separate from closing a workspace and can be raised through that contact channel. The operating entity and final procedures remain pending. This draft status does not postpone or limit any rights you have under applicable law.
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