LEGAL
Cookie Policy
1. What we use cookies for
On lawnise.com, we use cookies and equivalent storage technologies for consent-gated web analytics and to remember your cookie-banner preferences. The platform application at app.lawnise.com is a separate domain with its own cookie surface and policy materials.
2. Cookies we set on lawnise.com at Stage 1
Stage 1 is the initial Lawnise web-analytics deployment. The list below reflects what is actually set on lawnise.com today, not a speculative future list. Future additions to the Google Tag Manager container will be reflected here with the next regular policy review cadence.
lawnise.com does not require login and does not set session, authentication, or workspace-preference cookies of its own. The only cookies set on lawnise.com at Stage 1 are the Google Analytics 4 cookies listed below, and only when the user grants analytics consent via the cookie banner. The platform application at app.lawnise.com is a separate domain with its own cookies; those are documented in the platform-specific privacy materials.
Analytics cookies (consent-gated)
Set only when you grant analytics consent via the cookie banner. Until consent is granted, no analytics cookies are written to your browser (cookieless denied-state pings may still occur per ADVANCED Consent Mode v2 — these set no cookies and contain no identifiers).
- _ga — Google Analytics 4 client identifier. Attributes a session to a pseudonymous client. 2-year expiry. Set only when analytics consent is granted.
- _ga_<container> — Google Analytics 4 session identifier (the <container> segment matches the GA4 stream container ID). 2-year expiry. Set only when analytics consent is granted.
3. Cookies we do NOT set at Stage 1
For transparency, two cookies commonly associated with Google analytics are explicitly NOT set at Stage 1:
- _gid — Universal Analytics legacy cookie. Universal Analytics was deprecated by Google in 2023. Google Analytics 4 does NOT set _gid.
- _gcl_au — Google Ads / Conversion Linker cookie. Requires an Ads tag inside Google Tag Manager. Stage 1 does NOT load any Ads tag (per the Subprocessors page Web analytics section). This cookie will only ever be set after a future Ads-tag deployment, alongside a corresponding subprocessors and cookie-policy update.
4. Managing your preferences
On the public marketing surface (lawnise.com), a cookie consent banner appears on your first visit so you can accept analytics, reject all non-essential cookies, or configure per-category preferences. Your choice is stored in your browser for 365 days; after that the banner reappears.
To revoke a prior consent choice and trigger the banner again, clear the lawnise.com cookies and site data in your browser. Clearing site data removes your stored banner preference, so the banner will appear again on your next visit. You can also manage cookie preferences through your browser settings, which let you block or delete cookies.
5. Future tag additions
Future additions to the Google Tag Manager container — Ads conversion linkers, Meta Pixel, LinkedIn Insight, or any other third-party tag — will be reflected on this page with the next regular policy review cadence, alongside corresponding subprocessor and consent-banner updates. New non-essential categories trigger a banner re-appearance so existing users can re-consent under the new category surface.
6. Contact
For questions about how we use cookies, contact legal@lawnise.com.
DOCUMENT HISTORY
Changelog
1 version · last updated 2026-05-05Start with what fits.
Talk to our team about Public AI governance for your sector — sign up free to see what AI says about your brand, or book a briefing for a working session.
100 visibility checks per month. No credit card.
For procurement and Enterprise scope.