Privacy & Data Handling
Share the workflow. Keep sensitive records out.
How enquiries are reviewed and delivered, the providers involved, and your privacy and retention choices.
Who to contact
Last updated:
LaunchSoloAI is operated by Kirill Derhachenko in Calgary, Alberta, Canada, working remotely across Canada and the U.S. Privacy questions, access/correction requests, deletion requests and complaints can be sent to kirill@launchsoloai.com.
Website enquiries can be submitted directly to LaunchSoloAI after you review and explicitly submit them.
What you choose to share, and why
The initial analysis asks for a name, contact email, an optional company name, an operating topic and a description of one bottleneck. Current tools and the result you want are optional. You may also tell us how you found us; this optional answer is included in your reviewed enquiry and helps us understand which channels bring enquiries. It is not sent to visit analytics. A calculator scenario or diagnostic snapshot may also be included when you choose that path.
The purpose is to understand the workflow, review the enquiry and respond with a practical next step. No system credentials, database access or customer records are needed. If you send the draft by email, your sender address and the content you choose to send become part of the correspondence.
Describe the workflow, not individual customers, patients, employees or legal matters. Do not provide passwords, API keys, financial credentials, payment card data, government IDs, health/patient records, confidential legal case files or customer/employee personal records.
The current draft stays under your control
Typing into Analyze and preparing a draft do not send an enquiry. The form processes the draft in the page. You can inspect it, copy it or download a complete text file. Opening the email link opens your mail application; you decide whether to send. When direct delivery is enabled, choosing Submit enquiry sends your reviewed contact details and enquiry to LaunchSoloAI. Submission is not marketing consent and does not subscribe you to a mailing list. The enquiry form sends workflow content for AI-assisted review only if you select the separate optional Solo review checkbox. The optional AI consultant is described below.
Form fields are not sent to analytics. If you choose to carry an AI consultation into the enquiry form, its editable summary is stored temporarily in this tab’s session storage, expires after 30 minutes, and is removed when you choose to include or discard it. The expiry is checked on access; closing the tab or clearing site data removes the stored item. Your browser may manage autofill, history or session recovery according to its settings. Downloads and clipboard copies are under your device’s controls. Do not place confidential information in a URL or shared calculator link.
Use, service providers and processing locations
Enquiry correspondence is used to review and respond to the request and clarify any next engagement. Sending an email involves your mail service and the recipient’s mail service. The website hosting service also receives ordinary requests needed to serve pages, which can include IP address, browser/request information and requested URLs. Form fields are not intentionally added to these requests.
The production website submission uses a Vercel server-side function and Resend as the transactional email provider to deliver your contact email and approved enquiry content to kirill@launchsoloai.com. Resend stores customer data, including message content and delivery logs, in the United States. The recipient’s email service also processes and stores delivered correspondence. Processing is not Canadian-only. Resend’s sending region does not change its United States customer-data storage. Provider-specific retention and deletion periods are not asserted here. Contact Kirill before sharing information with a geographic processing requirement.
Enquiries are not automatically added to marketing lists. If marketing is introduced later, it requires a separate, unchecked opt-in, a record of consent and a working unsubscribe path.
Retention, deletion and your choices
If you explicitly choose optional Solo review, we save your submitted enquiry in our Neon database. The workflow description is imported into our private local work queue for AI-assisted review through Codex/OpenAI. Name, email and company are kept separately for Kirill and are not included as dedicated fields in that AI queue; avoid identifying information in free text. We do not automatically publish your enquiry to iLands or its social feed. Without this optional choice, website delivery remains email-only. A downloaded or copied draft remains wherever you save it; remove those copies using your own device tools. Reloading or leaving the page ends the site’s current in-memory draft, subject to browser session/autofill behavior.
For email correspondence, request access, correction or deletion at the privacy contact. Explain the request without sending additional sensitive records. Kirill will review it, seek only the identification needed to handle it and explain any applicable retention constraints.
LaunchSoloAI’s policy for unconverted enquiries is deletion 90 days after the last meaningful interaction. Active or contracted work is handled separately as business/client records under the applicable engagement and retention requirements. This is LaunchSoloAI’s correspondence policy, not a promise that Resend, hosting or mailbox-provider logs and backups are deleted on the same schedule. Provider retention and deletion arrangements must be reviewed separately. You can ask to stop further use or withdraw consent where applicable; any effect on responding to the request and any required retention will be explained.
Website visit analytics
The production website uses Vercel Web Analytics to count visits and page views and understand broad traffic sources, browser/device categories and approximate location. Vercel processes network request information to derive these statistics and uses a short-lived visitor hash; this integration does not enable analytics cookies or persistent visitor identification.
We send only recognized public page paths. URL query parameters and fragments are removed from page URLs, and referral URLs are reduced to their origin. For optional Google Analytics, only fixed source, medium, campaign and nonpersonal material labels can be passed separately after your consent. Unrecognized labels and recipient identifiers are discarded. This integration reads labels from the current page URL and adds no campaign storage or URL propagation between pages. Names, email addresses, form fields, Site Guide questions, diagnostic answers and feedback text are not sent to analytics. Vercel custom interaction events are disabled on the current plan. If you choose Allow analytics, Google Analytics also measures recognized page visits and fixed steps such as opening the assistant, continuing to an enquiry, reviewing a form and submission success or failure. With this choice, we also measure active reading in short intervals while the page is visible, focused and recently used; scroll milestones; clicks on recognized service or enquiry links; broad local-search categories and whether a result was found; assistant response stages; and the category of a form validation error. Reading time is an estimate, not proof that a person read or understood the page. An optional inline feedback control lets you choose a reason such as needing a price or a relevant example. We send only that fixed category. We do not infer a reason for leaving from silence. These events contain no form values, search terms or conversation text. A successful submission event means the server accepted the request, not that a sale occurred. You can change your choice from this page using analytics preferences or turn analytics off. Google Analytics loads only after this optional choice and uses analytics cookies with a configured 30-day expiration. Google processes technical request information; analytics cookies contain technical browser and session identifiers and can recognize a browser across visits; this is not fully anonymous measurement. Advertising personalization and Google Signals are disabled. Session recordings are not enabled. Preview sites do not send these page views.
Vercel is the analytics provider; processing is not represented as Canadian-only. You can exclude this browser from visit analytics or enable counting again. This choice stores an exclusion flag in this browser’s local storage, not form data, and stops future analytics events. The optional Google Analytics choice is also stored locally; excluding analytics revokes that choice and removes accessible Google Analytics cookies. Previously collected statistics are not erased by opting out. It applies to this browser profile; clearing site data removes it, and other browsers/devices need their own setting. Google Analytics is provided by Google and processing is not represented as Canadian-only. See Google’s privacy policy. Browser tracking protection or blocking the analytics script can also prevent counting without preventing use of the site. See Vercel’s analytics privacy documentation for its visitor identification and processing details. Contact Kirill for privacy questions.
Security and AI handling
Initial contact is intentionally limited to a workflow description. The submission endpoint validates a limited set of enquiry fields, keeps its Resend API key server-side, and does not deliberately log enquiry bodies. Account access, MFA, provider retention/deletion and recovery settings must be reviewed before activation. Optional Solo review uses a server-side enquiry queue; its access credential is never included in the browser. AI review does not authorize automatic client messages or commitments.
Where the optional AI consultant is enabled, sending a message after checking the consent box sends your current conversation, the current public page category and relevant public website material through our server to DeepSeek to prepare a response. Do not include confidential or personal records. Replies may be incomplete or incorrect; Kirill confirms project scope, price and commitments. You can instead use the site search without AI or contact Kirill directly. LaunchSoloAI does not deliberately store conversation transcripts on its server or send them to visit analytics. With separate optional consent, we retain only fixed broad question categories, an unrelated random conversation identifier, and response stages in our active database for up to seven days to review recurring questions. We do not store message text, contact details or IP addresses in these observations. Daily cleanup removes observations early, normally after six to seven days; expired observations are excluded from reports. Weekly summaries contain aggregate counts, not conversation identifiers. This does not train the model or automatically change the website. Database-provider recovery copies follow their separate retention settings; this active-data period is not a promise to erase provider backups immediately. With your consent to continue the conversation, the dialogue and draft message are kept in this tab’s session storage for up to 30 minutes so you can browse other pages without starting again. Clear conversation removes this local copy. Expiry is checked when accessed and while the page is active; browsers may restore tab sessions. When storage is blocked, the conversation remains only on the current page. The optional “Use my browsing context” choice keeps up to six known public page paths, an allowlisted link-source/campaign category and selected task/goal categories in this tab for 30 minutes. These hints are sent to DeepSeek with your message only while this option is enabled. Unchecking it or clearing the conversation removes the saved browsing context. Without it, only the current public page category accompanies your message. Raw URLs, query strings, referrer URLs, form text, names and contact details are not collected by this context feature. It does not identify a visitor or prove which company they represent. This does not enable email follow-up or identify anonymous visitors. A session-storage flag remembers dismissal of the assistant invitation. Abuse and usage controls use the existing Neon database to hold request counters, a random consultation identifier and a keyed daily hash derived from the network address. Raw IP addresses and conversation text are not stored in this counter table. These records are used to limit automated use and API spending, not for marketing. DeepSeek’s published privacy policy describes processing in China and possible use to improve its models, while noting that downstream applications need their own notices. See DeepSeek’s policy. Provider processing, retention and use are governed by the applicable API terms; we do not promise Canadian-only processing, zero provider retention or exclusion from training. Ask Kirill before using this feature if your information has specific processing requirements.
If something goes wrong
The response process is to contain the issue, identify affected information, assess the risk, coordinate with service providers, document decisions and take corrective action. Required notifications and escalation will be assessed with appropriate advice. Report a concern to kirill@launchsoloai.com; do not include passwords or a copy of exposed confidential records.