Privacy

A plain description of what this site does with your information, written from what the site actually does. Last updated October 2026.

In short

  • You can look around, use the quote tool and try the “do we come to you?” check without an account. To make that work, your browser gets a random visitor number in a cookie and we save what you enter.
  • We ask for your email address only to send you something you asked for: a sign-in link, a copy of an estimate, a field report, a heads-up when we are flying near you, or a field-day confirmation.
  • There are no passwords. You sign in with Google or with a link we email you.
  • We use no third-party advertising or analytics tools. We do count, for ourselves, how many visitors reach each step of the quote tool, by visitor number (the trail of steps, below). A few outside companies see part of a visit, and they are named below.

What we save when you use the tools

Everything you enter in the quote tool and the field-report tool is saved on our server as you use it, whether or not you have an account (a request over our per-address or daily limits is answered but not kept): field outlines and their names, the crop and options you choose, each estimate you are shown, and the dates and results of satellite reports. We do this so you can come back to an estimate and so we can prepare a firm quote for you.

The first time you use a tool that saves something (or the “do we come to you?” check), we also make a visit record for your browser: its visitor number, when we first and last saw it, and the description of your browser and device that the browser sends with every request (the “user agent”, such as “Chrome on Android”; we keep only its first 200 characters). We do not save the address of the page you came from (the Referer): an earlier version of the site did, and what it had saved was erased. We do not save your IP address in the visit record or with your entries.

We also keep a short trail of the steps you reach, so we can see which parts of the site help and which do not: for example, saw a price, drew a field, left an email address, asked for a quote, or followed a link in one of our emails. Each step is saved with your visitor number, the time, and a few details of that step, such as the place you checked in the “do we come to you?” check (the start of the line the address search found, which can be a street address), your answers to its questions, the price shown, or, for a link in one of our emails, the page it led to. We use the trail to count, by visitor number, how many different visitors reach each step, which part of our site they came through and what timing they chose; the counts are shown to administrators on a private page, and no outside analytics company receives them.

When you create an account or sign in, the entries from that browser are attached to your account. For an email link this happens only in the browser that asked for the link, so a link opened on another device signs you in there without moving anything.

On the map, the “Use my location” button asks your browser for your position. Your browser asks your permission first, and the position is used only to move the map to where you are: it is not sent to us. The map pictures for that area still load from the map companies named below, and a field you then draw there is saved like any other.

Email addresses, phone numbers and requests

Several parts of the site let you leave an email address for one thing: a field report, keeping your fields, a copy of an estimate, a heads-up when we are flying near you, a field-day reservation or a demo pass. We keep that address in a contact record, with when and where you asked, your name and phone number if you gave them, the crop and acres you told us about, and a short history of what we did for you (for example “area sign-up”, “field day reserved”, “estimate copy sent”). If you asked for a heads-up near you, the contact record also keeps the place you picked (the start of the line the address search found, which can be a street address) and its position on the map; if you asked for a demo pass, it keeps the map position of the centre of your fields. Quote requests keep your name, phone, email, timing and notes with the field outlines and the estimate. Demo requests keep the map position of the centre of your fields, the crop and acres, and the road distance from our base. Field-day sign-ups keep how many people are coming.

For most of these there is also a separate box, unticked to start, agreeing to seasonal tips, field-day invitations and offers. Two asks have no box: asking for a heads-up near your town, or reserving a field-day spot, is itself your agreement to the emails named right there and nothing more. In every case we record the exact sentence you agreed to, with the time and place.

“Send this quote request” sends your details, field outlines and the estimate to us, and emails you a copy. A satellite field report is emailed to you: we ask for your address, send a sign-in link, build the report when you open the link, and email you a copy. Email is not encrypted. We use what you send us to reply, to prepare and carry out work you ask for, to keep records of that work, to send the seasonal tips, invitations and offers you agreed to, to protect the site from misuse (see below), and to count how many visitors reach each step (the trail of steps, above). People we have given administrator access to can see these records.

Some links in our emails pass through our server first, so that we can tell which messages people act on: when you follow one, we save that you did, with the page it led to, against your contact record and visitor number. Those tracking links work for 400 days; after that they still take you to the page, but nothing is saved. We keep no third-party tracking. Your browser may also keep the email address and name you typed in a form for as long as that tab stays open, so the next form can be filled in for you; that copy stays in your browser.

Accounts and signing in

You can sign in with Google or with a link we email to you. There are no passwords, so there is no password for us to keep or lose. Season-long emailed field reports are not offered at present (there is no season subscription; it is switched off): each report is emailed to you once, when it is ready.

With Google we receive your name, email address and profile picture address from Google and store them, with a record that ties your account to your Google account and the sign-in tokens Google gives us (the access and refresh tokens are kept encrypted). Your Google sign-in details stay with Google and we never see them. With an email link we keep your email address and any name, phone number or farm name you choose to give us. The link works once and lasts 24 hours, and we keep only a scrambled copy of it.

Each time you sign in, a session record keeps the IP address and the browser and device description it came from, and the time. A session stays valid for 30 days after you last visit. It ends sooner when you sign out, when you delete your account, or if an administrator blocks the account; we do not yet sweep out old session records on a schedule.

Your account page shows your details, saved fields, estimates and reports. You can change your details there, remove saved fields, and delete the account.

Deleting your account, and what stays

On your account page, press “Delete my account”. We email a confirmation link to your address; open it, signed in on the same device, within 24 hours and the account is deleted. If nothing arrives within a minute, wait and try again.

Deleting the account removes your account record (name, email address, phone number, farm name and picture address), your sign-in sessions, the link to your Google account, the fields saved to your account (including ones you had already removed) and any emailed-report schedules.

It does not erase the records we keep about requests and contact. These stay, with the account taken off them: quotes and estimates, quote requests you sent us, satellite reports, demo requests, your contact record (your email address, your name and phone number if you gave them, and what you agreed to), the visit records of your browsers (one with nothing attached to it is deleted 60 days after that browser was last seen), the trail of steps (each step is deleted when it is 120 days old), the do-not-mail list, the email log (the address and subject of each email we tried to send, until it is 90 days old) and the administrator log (which can mention your account or quote by number, and anything an administrator typed about it). An estimate that nobody asked us about is deleted 7 days after it was last changed (30 days if we emailed you a copy of it), as it is for anyone. Removing a saved field on your account page hides it; the outline itself is kept until the account is deleted. To ask us about anything else, contact us using the details at the end of this page.

Cookies

We set these cookies. None is used for advertising, and none belongs to an advertising or analytics company.

  • ds_visitor: your anonymous visitor number. Set on your first visit to any page, kept for 400 days, and not readable by scripts on the page. It keeps your entries together, lets them be attached to your account when you sign in, and is the number the trail of steps is counted by.
  • better-auth.session_token (shown as __Secure-better-auth.session_token on the live site): your sign-in session. Set only when you sign in, kept for 30 days after your last visit.
  • better-auth.state: set for about 5 minutes while you sign in with Google, so we can check the sign-in came back to the browser that started it.
  • ml_nonce: set when you ask for an email sign-in or report link, kept for 24 hours. It ties the link to the browser that asked for it.

The human check (below) and the demo video may set their own cookies or browser storage; those belong to Cloudflare and YouTube, and we do not control them.

Counters and logs that protect the site

Anyone can use the forms, so we count requests to stop a script from filling them or sending email to strangers.

  • Request counters. We count requests by the address they come from, by visitor number and by email address. These counters hold a scrambled one-way code of the IP address, visitor number or email address, never the thing itself. The one exception is the mail domain, the part of an address after the @ sign (such as gmail.com): for email sent to people who have not signed in, we count how many go to each domain in a day, so that one mail system is not flooded, and that domain is kept as it is. Counters are removed by the daily clean-up once the minute, hour or day they count is over, so normally within about a day and a half.
  • The sign-in system's own counter keeps your actual IP address and the name of the sign-in page you asked for, and is removed after about a day.
  • Email log. Each time we try to send an email we write down the address, the subject line, the kind of email, whether it went or why it was held back, a scrambled code of the IP address of whoever asked for it, and the country our hosting provider says the request came from. Rows are deleted after 90 days.
  • Do-not-mail list. When someone presses Stop, or an address bounces, or someone marks one of our emails as spam, the address (or only a scrambled code of it, when the request came from a Stop link) goes on a list of addresses we must not email. We keep it so that we do not email them again.
  • Address search answers. To search an address we pass the text you typed to the address-search service. We keep each answer for a day or two, filed under a scrambled code of the text, with no name, visitor number or account.
  • Administrator log. When an administrator changes something (sends a quote, changes a setting, blocks an account), a record of who did what and when is kept for the owner's use. The record can include what the administrator typed, such as the message sent with a quote and the address it was sent to. It is not cleared on a schedule.
  • Hosting logs. Our hosting provider (Vercel) keeps its own server logs for a short time, such as IP address, page and browser type.

Other companies that see part of a visit

  • Cloudflare (Turnstile). On pages with a form that sends email, your browser loads a human check from Cloudflare, and our server asks Cloudflare whether you passed, sending the result of the check and your IP address. It usually stays hidden.
  • Resend. Sends our email, so it sees the address, the subject and the message, and keeps its own log of what it sent.
  • Google. Only if you choose Google sign-in; it knows you signed in to this site. In a zone map of a field report, a “Sample here” link opens Google Maps in a new tab; Google receives that spot's position only if you press it.
  • OpenStreetMap. Street-map pictures load straight from OpenStreetMap's servers to your browser, so they see your IP address, your browser type, the area of the map you are looking at and that you came from our site (the site's address, not the page). Text you type in the address search goes through our server to OpenStreetMap's Nominatim search service, without your IP address or name.
  • Esri. Satellite map pictures load straight from Esri's servers in the same way.
  • Microsoft's Planetary Computer. A satellite field report sends your field outlines and the dates to this service from our server, with no name or email address.
  • YouTube. If a demo video is shown on the How it works page, it plays from YouTube's privacy-enhanced address (youtube-nocookie.com). YouTube learns of the visit when the page loads, even if you never press play.

Fonts are served from this site, not from Google. These services receive the information needed to answer each request, under their own privacy policies.

Stopping and managing our emails

Emails we send to someone who has not signed in (a copy of an estimate, an area heads-up, a field-day note, a demo note, a fresh link) end with a “Stop emails to this address” link, and most also carry a “Manage your emails” link. Stop opens a page with one button; pressing it puts the address on the do-not-mail list. From then on we send that address nothing, including emailed copies of estimates and quotes, except a sign-in link you ask for yourself and the confirmation for deleting your own account. The Stop link works for 400 days. Marketing-style emails also offer the one-click unsubscribe that your mail app shows.

The manage link lets you pause or resume emailed reports, give or withdraw agreement to seasonal emails, stop everything, and see the fields saved under that address. It works for 30 days; an expired one says so and has a button that emails you a fresh one. Estimate links last 30 days too. Sign-in links, the delete-account confirmation and the copy of a report we email to your signed-in account carry no Stop link; ignore them and nothing happens. The quote we send after reviewing your fields is a reply to your request and carries no Stop link either, and an address on the do-not-mail list is not sent it.

Where information is processed

Our site is hosted by Vercel and our database is with Neon, both United States companies, so your information may be stored and handled in the United States or elsewhere outside Canada. Resend, Cloudflare, Google, OpenStreetMap, Esri, Microsoft, YouTube and your own email provider may also process information outside Canada, under their own policies, and it may be accessible to authorities in those places.

How long we keep it

  • Estimates nobody asked us about, with no account on them: 7 days after they were last changed, or 30 days after they were last changed if we emailed a copy of the estimate to the address that asked for it (the link in that email has to keep opening). Their older versions keep only the time, price and area, and are cut back to the latest three after 30 days.
  • Field outlines you save with no account: kept until you remove one; a removed one is deleted 30 days later. With an account, a removed field stays until the account is deleted. The one exception is a field report you asked for before signing in and never opened: see the next line. We do not delete saved outlines on any other schedule.
  • A field report you asked for before signing in, which nobody has signed in to start: deleted 30 days after you asked, together with the field outlines that were saved with that request (unless you changed them, used them in an estimate or an emailed report, or an account holds them). The sign-in link we emailed lasts 24 hours, so a request that old can no longer be opened.
  • The email log: 90 days. Request counters: the daily clean-up deletes each one once the minute, hour or day it counts is over, so within about a day and a half. Address search answers: a day or two.
  • The trail of steps: each step is deleted when it is 120 days old.
  • Visit records: one with nothing attached to it (no account, contact record, estimate, quote request, demo request, saved field outline or satellite report) is deleted 60 days after that browser was last seen. A visit record with any of those things attached stays until we delete it. The description of your browser and device is cut to its first 200 characters when it is saved.
  • Sign-in links: 24 hours. Manage links and estimate links: 30 days. Stop links: 400 days. Tracking links in our emails: 400 days.
  • Cookies: the visitor number 400 days, the sign-in session 30 days.
  • Contact records, quote requests, demo requests, field-day sign-ups, satellite reports that were started (the unopened requests in the line above are the one exception), the do-not-mail list and the administrator log: until we delete them. We do not delete these automatically. Quote records are kept as long as we need them to run the business.

Questions

If you'd like to see, correct or delete something you sent us, use your account page or contact us and we'll answer you. If we can't resolve a concern, you can contact the Office of the Privacy Commissioner of Canada at priv.gc.ca. Contact us at quotes@dronespraying.example.