Plain-language policy

Privacy

The public calculators run in your browser. The values you type into them are not sent to Lawn Ledger.

What this website collects today

You can sign in with the same Google account the Android app uses. Signed in, the desk shows your own lawn records — the zones, applications, mowing and watering your phone has synced. They are read from the same account database the app writes to. For lawn care records, this website writes only the entries you log on it — a watering, a mow or an application, saved under your own account so your phone picks them up on its next sync — and nothing else: it never edits or deletes a record in your lawn history, and it never changes a zone, a threshold or a setting. There are no third-party analytics or advertising scripts. Signed out, the desk uses invented sample lawn data. The light-or-dark switch in the header can save your appearance choice in your own browser storage; you can clear them through your browser at any time.

Images and network requests

The site’s lawn artwork is served with the site. No third-party image or font service is contacted by the page. Signing in sends you to Google and back by an ordinary link, so no code from Google or anyone else runs on these pages; while you are signed in the page talks to Supabase, which stores your account and your lawn records, and to nothing else. Separately, this website’s server asks the Lawn Ledger weather service for the forecast at each of your zones, sending that zone’s saved coordinates and your sign-in token. That request comes from the server, not from your browser, and it is the same weather service the app uses — which is why the readings agree. Nothing you type into the public calculators is part of it.

Optional referral codes

If you confirm a referral code on the signed-in desk or in Android Settings, Lawn Ledger saves the first code with your account, its campaign category (creator, organic or paid advertising), and the capture time. Codes can be added only within 30 days of account creation and before the first subscription verification. This helps us measure where customers came from. A verified Play-access observation may be linked later, including when no code was supplied. A trial, renewal or complimentary grant is not treated as proof of a paid sale; financial records are reconciled separately. Referral reports use a separate random account key and omit email, lawn records, location and purchase tokens. We do not use a tracking SDK, fingerprinting or advertising cookies for this feature, and we do not give creators your identity or lawn data. Account deletion removes linked attribution; restricted backups expire separately.

The Android app

This section is about the phone app, not this website. When you measure a lawn by tracing it on a map, the satellite images come from Google, so Google is told the spot you are looking at. The outline you trace stays on the phone — only the size it works out is saved with your lawn. Separately, the app sends a zone’s coordinates to the Lawn Ledger weather service for weather and soil data; sends what you type in the address box to that same service, which asks Google for the coordinates, and saves the address you pick with your lawn; and sends photos used for identification to Google’s AI service. The Cultivar Advisor sends your answers, notes, state or province, and your latitude rounded to about 11 km to Google’s Gemini AI service, which writes its recommendation. The Germination advisor sends your project notebook, recent chat and AI memory to OpenAI or Google’s Gemini, which writes its replies. Both go through Lawn Ledger’s server. Weed ID and Disease ID send your photo and your answers through Lawn Ledger’s server to Google’s Gemini AI service; the photos are not kept. Grass ID also sends your grass photos to Google’s Gemini AI service, and before it sends a photo it asks you to accept that Lawn Ledger keeps private copies. The photos, your answers, any species or blend you declare and the AI result are stored with your account and used to review and improve Grass ID, until you delete them in the app’s Settings or delete your account. The app removes location data from every photo before sending it. Deleted photos may remain in restricted backups until those backups expire, and a minimal record of the deletion stays until your account is deleted, so a delayed retry cannot restore the photo. Lawn Ledger does not publish these photos or use them to train AI models. See the Grass ID photo terms. The phone app explains the data used by each available feature.

Customer support

When online support is enabled, messages you explicitly submit and the replies are stored in Supabase. Signed-in requests belong to your account. Signed-out requests use a separate, case-specific browser cookie that is Secure, HttpOnly and SameSite; losing that cookie can prevent you from returning to the case. A case reference or supplied email address does not grant account access. Support staff can read cases and keep private notes. No support email or attachments are accepted by this first version.

AI processing is optional. Only if you allow it and draft generation is enabled, the support conversation and relevant help articles are sent through Lawn Ledger’s server to OpenAI to prepare a private reply draft. A person reviews and approves every published reply. Declining AI keeps human handling available. We request that responses are not stored as conversation state by the AI service; this does not mean the provider retains no data, including for abuse monitoring. Support cannot read unsynced phone records or change your lawn through this feature. Closed conversations expire after 90 days; signed-out cases expire 90 days after creation. Account deletion removes linked active support records and cancels their draft work; restricted backup and provider expiry remain separate. Do not include passwords, purchase tokens or access credentials.

Future changes

This policy will be updated before the website accepts uploads or payments, or adds another use of your information. The page does not describe a feature as active before it exists.

Last updated 19 October 2026.