Your business data is sensitive. We treat it that way.
TurfDispatcher holds your customer data and your business records: names, addresses, gate codes, the work you did at each property, and what every customer owes you. That data is sensitive, and some of it can put people at risk if it leaks. So we did not leave its security to chance, or to whatever a tool produces by default. It is designed in from the first line of code, not bolted on later.
Built like your data matters
A lot of software gets built fast now by pointing an AI at a database and shipping whatever comes out. That is fine for a to-do list. It is not fine for your customers' addresses and gate codes. Three principles keep this platform on the right side of that line.
A real server in between
Your app never talks straight to the database. A server we control sits in the middle, so the keys and the rules for who can see what live somewhere your phone, and anyone who ends up holding it, can never reach.
Least privilege, everywhere
No single key can do everything. Each part of the system gets the narrowest access it needs and nothing more. A weakness in one corner does not hand over the rest.
We test it by trying to break it
A wall nobody attacks is just a hope. We wrote the checks that try to read one business's records as another, and they have to fail before anything ships.
Live today: protecting the waitlist
Everything in this section is in place on this website now.
We collect as little as possible
The waitlist asks for your email, state, and business name, plus two optional questions. That is it. There is nothing sensitive to lose because we never asked for it. See our Privacy Policy for the full list.
The sign-up form cannot reach anything else
This is least privilege in practice. The part of our system that takes your sign-up is allowed to do exactly one thing, add you to the list. It cannot read the list back, and it holds no access to anything else. So even in a worst case where that public page were fully compromised, it reaches zero customer records.
Bot and spam protection
The sign-up form runs a background check from Cloudflare to keep bots and junk out, without making you solve a puzzle.
Encrypted connection and locked-down browser rules
The site is served only over an encrypted (HTTPS) connection, with a strict set of browser security rules that block common web attacks and stop the page from being embedded or tampered with.
Keys stay on the server, never in your browser
The secret keys that reach our database and services live in a locked server vault. They are never shipped to your browser or your phone, where anyone could pull them out. A lot of quickly-built apps skip that step. They wire the app straight to the database and bury the key inside it, and anyone who downloads that app can read it back out. Ours never leaves the server, so there is no key sitting in the app for anyone to find.
As we build the app: protecting your business
These are commitments and design decisions for the app that ships to operators. They describe how it is being built, not something you have today.
Your business is walled off from every other business
Each business's data is isolated from every other business, and that wall is enforced at the database itself, not just in our code. It is the kind of protection you check by trying to break it, so we test that one business can never read another's records.
Records cannot be quietly changed
Once a spray or fertilization record is completed, it cannot be edited in place. A correction creates a new, dated amended version and leaves the original standing. Your history stays trustworthy, which matters both for security and for the record itself.
Card details never touch our servers
Payments run through Stripe. Your customers' card numbers go straight to Stripe and never pass through or sit on our servers.
On your phone: addresses and gate codes stay locked to the device
Addresses and gate codes are encrypted on your phone and protected behind your device lock. Sign-in is yours to control, with two-factor available so a stolen password is not a stolen business.
Shared records use expiring links
When you send a record or an invoice as a PDF, it goes out as a link that expires, not as a permanent public URL that anyone could stumble onto later.
Text messages go out only with recorded consent
The app never texts a customer who has not opted in. Each opt-in and opt-out is written to a record that cannot be quietly changed, so there is always an honest history of who agreed to messages and when. Phone numbers are walled off to your business like the rest of your customer data, we never sell them or share them for anyone's marketing, and our text-messaging provider only ever handles a message to deliver it. Every message supports STOP to opt out.
What we will not tell you. We will not tell you we are unhackable, because no honest company can. And we will not tell you that we cannot see your data, because we run the servers that store it. What we will do is keep our access limited, tell you plainly what we hold and why, and protect it the way people who understand this data would want it protected.
Back to TurfDispatcher · Read our Privacy Policy