Privacy policy
This policy explains how Kingmakr handles information when you use our website, account and connected business tools, including Prospector.
Updated 8 November 2026
Prospector access waitlist
If you join the waitlist, we store your email, preferred AI, optional offer description, language, signup source and permission/withdrawal records separately from product accounts. We use them to understand demand and email you about Prospector access through Resend. Joining does not create an account or subscribe you to unrelated marketing. Use the unsubscribe link in access emails to stop them, or contact support for access or removal. Repeat signup does not undo an unsubscribe unless you explicitly ask to receive emails again.
Information we receive
We receive account and sign-in information, such as your name and email from Google, and your connection permissions. Your AI may submit business descriptions, profiles, research sources, prospect and contact details, campaign records, assessments and outreach drafts that you authorise it to save. Support requests contain the information you choose to provide.
How we use information
We use this information to provide and resume your business workflows, maintain shared business context, enforce access and capacity, administer subscriptions, respond to support and investigate failures. Business records are stored in the workspace associated with your Kingmakr account. Review what your AI submits and only provide material you are entitled to use.
Your AI and connected services
Kingmakr provides structured tools and storage, rather than the AI model. We receive calls and information submitted to our tools, not automatic access to your entire AI conversation or mailbox. Your chosen AI and any email, browsing or other connected services handle information under their own policies and permissions. Connecting email is optional; preparing a draft does not send it.
Service providers and disclosures
We use Railway for application hosting and database infrastructure, Google for sign-in, Stripe for payments and subscription management, and private storage for files and generated artifacts where used. Stripe handles payment details; Kingmakr stores billing references and subscription status. Support email is handled through Gmail. Information is processed by providers as needed to deliver these functions and may be processed outside your country. We may also disclose information where required by law. Contact us for information about the providers and locations relevant to your request.
Cookies and operational records
We use cookies for sign-in sessions and language preferences. We retain minimised MCP call traces for 30 days to diagnose calls reaching Kingmakr. Successful calls retain technical metadata and limited summaries. For failed calls, internal traces also retain bounded submitted arguments to diagnose errors; these can include business or contact information. Credential fields and recognised secret formats are redacted, and truncation is recorded. Submitted values are not included in ordinary server logs. Internal identifiers can remain linked to workspace records; traces are not anonymous. Other business history and security records are distinct from these traces.
Retention and deletion
Business records remain available for ongoing workflows and history; they do not have a universal 30-day expiry. Some source bodies and files have separate retention or removal controls. Contact support to request deletion or understand what a removal operation covers. Revoking a connection stops its access but does not delete business records or cancel a subscription. Copies in backups, legally required billing records and data held by independent services may remain after an operational deletion.
Access, correction and concerns
You can ask us to access or correct your information, request deletion, or raise a privacy complaint through the contact link below. We may verify your identity and workspace authority, investigate the request and explain relevant limits. If your concern remains unresolved, you may contact the privacy regulator applicable to you. We update this page when our practices change.