Privacy and data policy
How your contact details, irrigation plans, drawings, measurements, and conversations are handled—and how to control optional features or request changes to your information.
Who this notice covers
This notice explains how Nano Flow Irrigation handles information through this website, its planning and account tools, chat, scheduling, project submissions, and related correspondence. For questions about these practices, contact Israel Ruttenberg at ruttenberg@nanoflowirrigation.com. A signed project agreement may add project-specific confidentiality or data-handling requirements.
Information collected and its purpose
| Activity | Information | Purpose |
|---|---|---|
| Contact, scheduling, and participation inquiries | Name, email, optional phone, organization, role, preferred times, notes, and submitted project interests. Scheduling and intake can also include the source page, referrer, and campaign tags. | Arrange calls, respond to requests, assess fit, and keep correspondence associated with the request. |
| Build a System, diagnostics, and system reviews | Site or general location, acreage, crop or application, water source, delivery constraints, pressure, storage, emitter configuration, runtime, and other inputs you provide. | Calculate preliminary scenarios, save progress where supported, prepare reports, and review feasibility. |
| CAD and project uploads | Drawings, maps, coordinates, photographs, site references, reviewer details, and information contained in uploaded files, including metadata. | Inspect and process your files, clarify requirements, and prepare the requested review or deliverable. |
| Accounts and saved work | Email, authentication and session records, saved builds, and access or sharing records. | Verify access, retrieve saved work, and enforce permissions. |
| Chat and correspondence | Messages, generated replies, attachments where applicable, and contact or project context. | Answer questions, maintain the conversation, and support follow-up in the customer relationship management system (CRM). |
| Site operations and optional analytics | Security request metadata, including IP addresses; with optional analytics enabled, page context, interaction events, and browser or session identifiers. | Protect the service, diagnose errors, and understand use of the site. |
| Acceptance and privacy requests | Accepted document version, timestamp, submission reference, verification information, request status, and action records. | Document acceptance, locate relevant information, verify the requester, and record the outcome. |
Provide only information needed for the request. Remove unrelated personal details and third-party confidential information from drawings, photographs, and file metadata before upload. Public intake is not the place to send passwords, payment-card details, identity documents, or restricted research.
Where information goes
| Recipient or system | Information and purpose |
|---|---|
| Website hosting, database, and private storage | Submitted information, saved work, CRM records, conversations, files, and operational logs are processed on the website infrastructure. Hosting and infrastructure administrators may have access needed to operate and secure those systems. |
| Zoho | Public-form email delivery can include recipient and sender addresses, message content, and relevant attachments. |
| Brevo and Amazon SES | Supported CRM email transports. The transport used for a message receives its recipients, content, and applicable attachments; the presence of both options does not mean each message goes to both. |
| OpenAI | Public chat messages and reference context are sent for automated responses. Enabled CRM AI functions can process task-specific context. Chat messages and replies are also retained in the CRM. |
| LinkedIn, when you load a post or follow a link | Your browser connects to LinkedIn and sends connection information. Embedded content may use cookies under LinkedIn’s own practices. |
Information may also be disclosed when required by law or needed to investigate misuse or protect the service and affected people. We do not sell personal information or use it for cross-context behavioral advertising. Giving us a project inquiry does not authorize public release of your drawings, identity, or results.
Provider-held records and any backup copies are distinct from the active website records. A deletion from the website does not itself delete a delivered email, a recipient’s copy, or a provider’s retained records. Provider and backup removal must be addressed as part of the specific request.
Automated chat and human follow-up
The public chat is an automated intake and information tool, not a live-agent connection. Messages and replies are recorded for follow-up; human review or a reply is not guaranteed for every chat. AI output may be wrong and cannot approve a design, promise a result, set a price, or enter an agreement.
Submitting a chat message requires processing to generate the response even when optional analytics is off. Do not submit confidential research or unnecessary personal information. This notice does not promise zero provider retention or a particular provider training setting.
Cookies, browser storage, and your choices
The Privacy choices control lets you allow or decline optional site analytics and automatic LinkedIn posts. Optional analytics requires an allow choice. Global Privacy Control keeps optional analytics and automatic LinkedIn loading off. The preference lasts up to 90 days in that browser; another browser or cleared cookies may require a new choice.
Locally served post summaries remain available without loading LinkedIn. You can load an individual post without enabling analytics. Allowing analytics and LinkedIn posts enables automatic embeds; an older analytics-only choice does not enable them. Loading a post or following a LinkedIn link connects to LinkedIn under its privacy policy. Withdrawing permission removes automatic embeds and stops future optional analytics, but cannot recall information already sent.
Session and security cookies support account access and form protection. Browser storage can also retain drafts, saved progress, and display preferences. These functions are separate from optional analytics. Declining analytics clears known analytics identifiers, not your draft content or past server records. Clear site data in your browser to remove local drafts; this may also sign you out or remove saved progress. Use a privacy request for server-held information.
Email and marketing choices
Submitting a request allows us to respond about that request; website terms acceptance is separate from marketing permission. To stop marketing follow-up, use an unsubscribe option where provided or contact ruttenberg@nanoflowirrigation.com. Service messages about an existing request or account may still be needed.
CRM emails can include an image that records opens and tracked links that record clicks. Email software, image blocking, and automated scanners can affect those records, so an event does not prove that a person read a message. Website analytics preferences do not control email tracking. Blocking remote images in your mail application can prevent the open image from loading; tracked links can still record a click.
How long information is kept
The local cleanup process is scheduled daily. Its configured default targets are listed below; they apply to the specified stores, not every copy of the same information.
| Record category | Local cleanup target |
|---|---|
| Raw website analytics events | 90 days after creation. |
| Inactive analytics sessions | 365 days since last activity. |
| System-review submissions and CAD submission files | 365 days, based on the stored file or submission-record modification time. |
| Temporary CAD review exports | 30 days, based on the export record modification time. |
| Archived application logs covered by cleanup | 90 days, based on file modification time. |
| Quarantined intake records | 30 days, based on file modification time. |
| Security sinkhole records | 7 days, based on file modification time. |
These are cleanup targets, not a guarantee of deletion at an exact hour. CRM contacts, correspondence, saved builds, other submissions, chat and AI caches, acceptance records, privacy-request records, provider copies, and backups are not all covered by this schedule. Their retention requires review of the service purpose, active project, dispute, security need, and applicable recordkeeping obligations. There is no single automatic expiry covering those categories.
A privacy request includes checking relevant stores and documenting necessary retention exceptions. Removing one submission does not automatically remove related correspondence or an exported report. De-identified research is treated as anonymous only when it no longer identifies a person; restricting access alone does not make a record anonymous.
Access, correction, and deletion
Use the privacy-request form or contact Israel Ruttenberg at ruttenberg@nanoflowirrigation.com. Include the email used for the original submission, the type of request, and any project or submission reference. Do not send passwords or identity documents with the initial request.
- Your request is recorded with a reference and status.
- Identity and authority are checked before private records are disclosed or deleted. Additional information may be needed to locate or verify the records.
- Relevant submissions, correspondence, reports, analytics, conversations, acceptance records, providers, and backups are reviewed for action or a documented exception.
- The outcome should explain what was corrected, supplied, or removed and any retained records or limits. Contact the policy contact with the request reference if you need a status update or disagree with the outcome.
Available rights and response deadlines depend on applicable law; nothing in this notice limits those rights. Deleting information needed for an active service can prevent continued access or completion of that service.
Security and updates
Controls include restricted access, protected sessions, upload validation, private storage for project uploads, and encryption for certain private records. These measures reduce risk; they do not make every record encrypted or guarantee against unauthorized access. Report a suspected disclosure to the policy contact without forwarding other people’s private records.
Changes are dated and versioned. Submission acceptance records identify the terms and privacy snapshot presented at the time. A later notice does not by itself authorize a new use inconsistent with earlier commitments.