Privacy Policy

1. Information we collect

We may collect information you choose to provide, including your name, business name, email address, phone number, service interests, project details, and the content of messages you send through the AI assistant or other contact channels.

Technical systems may also process IP address, browser and device information, request timestamps, referring pages, security events, error logs, and similar diagnostic data.

2. AI assistant and message processing

The public AI assistant is an automated system, not a human, and is intended only for business automation questions. When you send a message, the message, recent conversation context, language setting, and a temporary session identifier are sent through our Netlify function to our configured automation workflow, including Make.com, and may be processed by an AI model provider used by that workflow.

Do not submit passwords, payment-card data, Social Security numbers, medical records, diagnoses, insurance information, or other sensitive personal information through the public demo. The public demo is not for patients, treatment, diagnosis, medical or insurance inquiries, or emergencies. It is not intended to receive protected health information or consumer health data and is not presented as a HIPAA-compliant patient communication channel. We use technical guardrails intended to reduce forwarding of obvious sensitive content to downstream automation or AI providers, but no filter is perfect; do not submit sensitive data.

3. How we use information

• Respond to inquiries and discuss services you request.
• Operate, secure, troubleshoot, and improve the website and AI demo.
• Prepare proposals, demonstrations, scopes, or recommendations requested by you.
• Maintain reasonable business and security records.
• Comply with law and protect our rights, users, systems, and services.

4. Service providers and disclosures

The website uses Netlify to host pages, functions, and submitted inquiries; Make to route leads and AI messages; Google Sheets (Google Workspace) to store CRM copies of inquiries; and the AI model provider used by the active Make scenario for business-use chat. If you enable optional advertising measurement, Google Ads may receive device and conversion data. Incoming inquiries may also be copied to email, messaging services, or other tools expressly chosen in a requested project. Service providers may process information under their own documented terms and approved processing arrangements.

We may also disclose information where reasonably necessary to comply with law, respond to valid legal process, investigate abuse or security incidents, or protect rights and safety.

5. Sale, sharing, and targeted advertising

We do not sell personal information for money. Optional Google Ads conversion measurement is disabled until you actively allow it in our privacy choices. If you refuse, we do not load the Google Ads tag. If you allow it, Google may process technical and advertising attribution data for conversion measurement; form fields (name, email, phone, business description) are not intentionally sent to the tag. We do not enable remarketing or personalized advertising in this implementation.

6. Cookies, local storage, and session storage

The site stores essential language, service-selection and AI session preferences in the browser. A consent preference, policy version, pseudonymous random receipt identifier and timestamp are stored locally. When you consent to Google Ads measurement, a minimal affirmative consent receipt is first submitted to Netlify Forms. We do not activate the optional Google tag if that record cannot be submitted. Our Cookie Policy explains your choices and how to withdraw them.

7. Retention

We keep inquiries in Netlify Forms and may copy them through Make to Google Sheets. We review unanswered or completed inquiries and plan to remove inactive lead records after 90 days unless a longer period is necessary for an active request, legal obligation, or dispute. This is a proposed operational retention rule, not a claim that automatic deletion already runs: deletion across Netlify, Make and Google Sheets is presently reviewed manually and must be kept consistent. Make scenario settings can limit retention of detailed execution history; other service-provider logs may follow their own documented schedules. Request access or erasure through the privacy contact below.

8. Security

We use reasonable administrative and technical safeguards designed to protect information. No internet transmission, AI service, automation platform, or storage system can be guaranteed completely secure.

9. Your privacy choices and U.S. state rights

You may request access to, correction of, or deletion of your personal data; where applicable, you may also request portability, restrict or object to processing, withdraw consent, or exercise relevant US state rights. Requests can be sent to leadflow.on@gmail.com. We will assess them under applicable law, verify identity where necessary, and coordinate removal from Netlify and Google Sheets when appropriate. We do not treat a service inquiry as permission for unrelated marketing. You may also complain to your relevant data-protection authority where the law provides this right.

To submit a privacy request, email leadflow.on@gmail.com.

10. California online privacy disclosure (CalOPPA)

California has specific online privacy disclosure requirements, including under the California Online Privacy Protection Act (CalOPPA). For those purposes, this policy describes the categories of personally identifiable information we collect, the categories of third parties or service providers with whom information may be shared, and a method to request review or correction. The deployed site uses Google Ads conversion measurement as described above, but does not add Google Analytics, Meta Pixel, Google Ads remarketing, personalized advertising, or behavioral audience-building code. Because there is no uniform legacy “Do Not Track” standard, a DNT browser setting does not independently change the functional operation of this site. Where an applicable law requires recognition of a legally recognized opt-out preference signal for covered processing, we will honor it as required.

11. Marketing communications

Submitting a website chat message or contacting us for information authorizes us to respond to that request. It does not by itself constitute consent to receive automated marketing calls or text messages. Any campaign that requires separate consent must obtain that consent separately.

12. Children

The site is designed for business users and adults and is not directed to children under 13. We do not knowingly collect personal information from children under 13 through this website. If you believe a child has submitted personal information, contact us so we can review and, where appropriate, delete it.

13. International processing

LeadFlow ON and its service providers may process information in countries different from the country where you are located. Data protection rules may differ across jurisdictions. Where a transfer mechanism or other safeguard is legally required for a particular processing activity, the responsible parties should use the required mechanism.

14. Changes and contact

The persons responsible for LeadFlow ON website data processing are Ihor Skyba (Ігор Скиба) and Volodymyr Koval (Володимир Коваль), Ukraine, acting together for this unregistered project. Questions and privacy requests: leadflow.on@gmail.com. We update this policy when data practices or obligations change.

Privacy questions and requests can be sent to leadflow.on@gmail.com.

15. Purposes and legal bases (where GDPR/UK GDPR applies)

We process submitted enquiries and requested AI demo messages to take steps at your request before entering a potential contract or, where appropriate, for legitimate interests in responding to business enquiries; technical security logs for legitimate security interests; optional Google Ads conversion measurement only after explicit opt-in consent. You can withdraw optional tracking consent via Cookie settings without affecting the lawfulness of earlier processing. Applicable legal bases and rights depend on the circumstances and location.