Privacy notice

Information collected

• Service address and property context
• Symptoms, scope answers, optional photos, and access notes
• Name, phone, email, contact preference, and availability
• Security, audit, acknowledgment text/version/timestamp, and request-status records
• Landing page, traffic source, and supplied UTM campaign parameters
• First-party advertising impression and click events
• Server access logs, including IP address, requested URL, browser user agent, referrer, and timestamp

How information is used

We use submitted information to check coverage, classify and route the request, communicate about it, protect the service, and improve operations.

Provider disclosure

Before acceptance, an offered provider receives approximate area and service context—not full address, direct contact details, or private access notes. There is currently no provider login or automatic contact-detail unlock. Provider notifications contain only service, planning estimate, and city/state/ZIP. Any later disclosure must be limited to an identified provider authorized for an accepted request.

Storage and retention

Status links expire. Uploads are kept in protected server storage excluded from public HTTP access. The current system has no automated deletion schedule for requests, uploads, acknowledgment records, mail logs, or advertising events. They remain stored until manually removed. Server access/error logs are configured for daily rotation with 14 rotated files; actual duration depends on rotation and traffic. Status links currently expire after seven days, but expiry does not delete their database records. A category-specific retention schedule and documented exceptions must be approved before release.

Advertising and services

First-party scripts measure an advertisement impression after at least half is visible for one second, and record clicks before redirecting to the advertiser. Stored event fields are event type, campaign and creative identifiers, placement, signed-token digest, service category, three-digit ZIP prefix when available, and timestamp. These event records do not contain customer phone, email, full address, IP address, or user agent. Operators can view reporting. An advertiser receives a visit when you follow its link and may collect information under its own notice.

The active page uses locally hosted scripts, images, and ZIP/metro data. An AdSense account meta tag is present; it does not load Google advertising scripts. A session cookie supports drafts, submission security, and operator login. Request details and confirmation messages are stored in the platform database, private upload storage, and local mail logs. Hosting/service recipients and their retention terms still require confirmation.

Choices and contact

Use your secure status page to cancel further matching or submit a correction/deletion request. You can also contact sim@smartirrigationmanagement.com about a privacy request. An operator must verify identity through the recorded contact before changing or deleting information. Any records kept for an obligation require a documented reason and expiry.