Privacy Policy

Last updated: 6 September 2026

Information we collect

When you request an online assessment, use a purchased workspace, submit support or request an automation assessment, we collect the contact and business information you provide. This may include your name, business email, company, team size, authorised opportunity records, enquiry source, current tools, follow-up challenge, approval activity and support requests. Stripe processes payment details; ClientMorrow does not store full card details.

How we use it

We use this information to assess fit, respond to requests, deliver and support purchased services, isolate customer workspaces, maintain an audit trail, assess repeatable workflow patterns and improve ClientMorrow operations. An automation assessment request does not authorise implementation or automatic sending.

Service providers

We use Vercel for hosting, Supabase for authentication and data storage, Stripe for payments, Resend for transactional email and Cloudflare for DNS and security. Google authentication and Gmail access are used only when the customer chooses those functions and grants the requested permission. These providers process data under their own terms and privacy commitments.

Website analytics

We use Vercel Web Analytics to measure page views, referral sources and device information without analytics cookies. URL query parameters are removed before page-view events are sent. We do not send contact details or customer opportunity content as analytics event properties.

Retention and access

We retain information only for legitimate sales, delivery, support, accounting, security and legal needs. Audit records may be archived rather than immediately deleted where they are required to protect transaction or service integrity. You may request access, correction or deletion where applicable by contacting hello@clientmorrow.com.

No automatic outreach

AI may assist with classification and drafts, but Launch does not automatically send outreach. Creating a Gmail draft requires customer approval and does not send the message. Any future automatic action requires a separately accepted scope and approval boundary.