Your lawn plan
The planner runs in your browser. It does not request GPS access, look up your address, or send the location you type to a geocoding service. State and regional conditions guide the suggested plan; a city or lawn name is only a label.
If you choose “Save on this device,” your inputs, plan, and dated checklist history are stored in this browser’s local storage. The selected lawn timezone and any optional timing answers are part of that local plan. A validated migration keeps the original v1 record in a separate local backup until you clear saved data. Use “Clear saved plan” to remove both the active plan and that backup. On a shared device, other people using the same browser profile may see them.
The planner shows broad, research-linked review windows rather than verified application dates. It does not fetch live weather, geocode a lawn, or send planner inputs, grass type, timezone, labels, or answers to the usage counter. Local storage is bounded for reliability; oversized or newer records are left untouched and can be recovered or exported from the browser.
Hosting and external resources
The hosting service may process ordinary request and access information to operate this public site. Site fonts are requested from Google Fonts, which receives ordinary network request information. Research links open external publisher websites with their own privacy policies.
Optional usage counts
Turf Tally counts page views, engaged page views, planner starts, generated plans, download and print actions, and clicks to the planner or research sources. An engaged view means at least ten seconds with the page visible and an interaction such as scrolling, clicking, or using the keyboard. These are estimates of use, not verified people or unique visitors.
Our hosting database stores daily totals by page, a small list of referral sources, campaign, and action. It stores no visitor ID, IP address, full referring URL, search terms, or planner inputs. These anonymous totals are retained for comparing traffic over time. The counter briefly uses the request IP in server memory to limit repeated submissions. Ordinary hosting logs are separate and may contain network request information.
There are no analytics cookies or cross-site identifiers. Your preference below is saved only in this browser. We also respect Do Not Track and Global Privacy Control. This privacy page is not included in usage counts.
Advertising, cookies, and consent
Turf Tally is connected to Google AdSense, which may use cookies or similar identifiers and ordinary request information to check site eligibility, measure ad delivery, prevent abuse, and serve ads after Google approves the site. Google handles that data under its own policies. Turf Tally does not receive a personal profile from those identifiers.
For visitors in the European Economic Area, the United Kingdom, and Switzerland, we will use Google’s certified consent management platform when AdSense is active. Its three choices are “Consent,” “Manage options,” and “Do not consent.” The choices control Google’s use of data for personalized advertising and can be changed through the consent message. Ads will not be placed until the site passes Google’s review and the required consent settings are published.
Turf Tally has no newsletter signup or donation checkout. Our first-party usage counter remains optional and does not use advertising cookies.