Privacy notice
Nano Flow Irrigation | Version 2026-10-28.1 | Updated October 28, 2026
What we collect and why
Contact and scheduling details, project inputs, submitted files, measurements, and correspondence help us evaluate requests and provide requested services. Security logs can include IP addresses and request metadata. Optional analytics records site interactions, page context, and session identifiers when enabled. Browser storage can preserve drafts, preferences, and active sessions.
Where information goes
| System | Information and purpose |
|---|---|
| Website server, local database, private file storage | Inquiries, project files, measurements, CRM records, conversations, and operational logs. |
| Zoho | Public-form mail, addresses, message contents, and applicable attachments. |
| Brevo and Amazon SES | Configured CRM email options. The selected transport receives recipients, contents, and applicable attachments. |
| OpenAI | Public chat messages and approved public reference instructions; limited task context for enabled CRM AI features. Do not include confidential research or unnecessary personal details. |
The hosting company, backup arrangements, and provider-specific retention settings are being verified. We do not promise that local deletion removes every provider or backup copy. We do not sell personal information or use it for cross-context behavioral advertising.
AI and human follow-up
The public chat is automated and records messages and responses in the CRM. It is not a live-agent connection. Inquiries can be reviewed for follow-up, but no human review or response is guaranteed for every chat. AI features are distinct from optional website analytics. Disabling analytics does not prevent processing needed to answer a submitted inquiry. Provider account settings and deletion requests require separate verification; this notice makes no blanket training-exclusion or zero-retention promise.
Your choices
Use Privacy choices to allow or decline optional analytics and to withdraw permission. We honor Global Privacy Control by keeping optional analytics off. Declining analytics does not prevent reading content or submitting a request. The choice lasts up to 90 days. Withdrawal stops future optional analytics and clears the known analytics identifiers; it does not automatically erase prior server records. Marketing permission is separate from terms acceptance and responding to a request.
LinkedIn cards and images are served locally. LinkedIn receives a visit when you follow its links. Other external resources and links are subject to their providers’ practices. Browser-stored drafts may remain until cleared or replaced.
Retention and deletion
Current cleanup targets are 90 days for raw analytics and covered archived logs; 365 days for inactive analytics sessions, system-review submissions, and CAD submissions; 30 days for temporary CAD review exports and quarantine records; and 7 days for security sinkhole records. These are operational targets, not a guarantee that every copy is removed at that time.
CRM records, correspondence, other submissions, AI caches, backups, provider-held copies, and records needed for an active engagement or legal obligation require a record-specific review. We document exceptions rather than describing secured identifiable records as anonymous. Only data that no longer identifies a person is treated as anonymous research data.
Requests and security
Submit an access, correction, or deletion request, or email info@nanoflowirrigation.com. We verify identity proportionately before disclosing or deleting records. Requests are tracked with status, exceptions, and completion evidence. Do not send identity documents unless specifically requested through a suitable channel.
Private uploads use restricted storage and validation. Access controls and encryption reduce risk but do not guarantee security. We retain acceptance evidence identifying the accepted document version and associated submission. Necessary retention exceptions and limits on removal from backups or external providers will be explained when responding to your request.