Privacy Policy
Effective October 25, 2026
Lekua turns an address into site analysis, CAD base plans, and permit paperwork for landscape designers, and runs Turf Check, a free lawn-rebate lookup for California homeowners. Doing that requires storing some of your data. This page says exactly what, where, and for how long — and the one promise that governs all of it: we never sell or share your data. No ad networks, no data brokers, no cross-site tracking. Your data exists to appear on your own screens and your own documents, and to let our own small team see how Lekua is used so we can make it better — the only exceptions are the narrow legal ones listed below, in plain sight.
What we store, and why
Your account
Your email address and sign-in method (email link or Google), managed by our authentication provider. Sign-in sessions last up to 90 days of inactivity before you’re asked to sign in again.
Saved projects
When you’re signed in, each address you analyze is saved as a project: the address, assessor parcel number, county, coordinates, parcel size and outline, and a log of project activity (analysis run, base plan exported, plan check run, plant list saved). This exists so you can leave, design, and pick up where you left off. Signed-out searches are not saved as projects.
Address searches
Every address you search in site analysis is recorded in our own database: the address, its coordinates, city and county, whether we found a parcel for it, your account if you’re signed in, and otherwise an anonymous session id. We use it to improve Lekua — to find parcels we drew wrong, analyses that failed, and places we don’t cover yet. It stays in our database, readable only by us, and is never sent to an analytics provider or anyone else. Deleting a project doesn’t remove these records; deleting your account removes your account from them. Turf Check searches aren’t recorded here; see Turf Check below.
Exported files
When you download a base plan (DXF) or site report (PDF) while signed in, a copy is stored so you can re-download it from your projects list later.
Uploaded planting plans
Files you upload for a plan check are read to extract the plant schedule, then deleted from storage after processing. The plan-check results (flag counts, water-budget outcome) are saved to your project when one matches; the uploaded design itself is not kept. Its plant schedule and any existing trees it shows are also recorded, with the address the plan is for, on the plan-check event described under product analytics. Each check is also saved so its share link can reopen it: the address, your file’s name, the plant schedule we read, where each plant and existing tree sits on the property, and the outline of your plan as placed — not the file or an image of it. It is stored privately and opens only through that link. A check that isn’t part of one of your projects is deleted after 30 days; one that is goes when you delete the project.
Surveys
When you’re signed in and add a survey to a project, we keep the file privately with that project, along with what we read from it: the surveyor’s firm, the survey’s date, record reference and citation as printed, the boundary, trees and features it draws, and how it fit the county parcel. Remove the survey, or delete the project, and they go with it.
Your plant list
When you’re signed in and a plan check matches one of your projects, the plant schedule it read is saved to that project: each plant name as printed, the name we matched it to, the quantity and where we read it from, the container size, and the remarks column. We keep it so the list can be checked against what California nurseries publish, and so the packet you hand a contractor comes from your own schedule. Delete the project and the list goes with it.
Nursery availability lists
We read the availability lists that California native-plant nurseries publish on their own websites, once a week, and keep dated copies. Those lists describe a nursery’s stock, not you; we mention them here because what they say is shown beside your plant list with the nursery’s name and the list date. A nursery can ask us to stop reading its list at any time and we do so the same day. Nursery prices are shown only to the nursery itself unless it asks otherwise.
Product analytics
We measure how the product is used with PostHog, a product-analytics service: page views, error reports when something breaks, and product events such as “ran a site analysis,” “generated a plant palette” (with the species it recommended), “opened a planting zone or the full plant list,” “exported a base plan,” or “copied a share link.” Our events give location at county and city level, with two exceptions that also record a street address. Adding a survey to a project records the street address the survey is for, along with how the survey fit the county parcel and how many trees it shows, by species. A plan-check event records the street address the plan is for, along with the species and quantities read from the plan’s schedule and the existing trees it shows, by species. Neither records the file itself, its drawing, its notes, or the details of the surveyor or designer who prepared it. Like any web service, PostHog also receives your IP address with each request and can estimate a rough location from it. Web addresses are cleaned before they’re sent: an address in a link, a sign-in token, and the code in a shared plan-check or Turf Check link are all removed, including inside page-speed and click-map data. Until October 20, 2026, the code in a plan-check or Turf Check link you opened was sent to PostHog with the page address, and page-speed and click-map data could also carry the full link, including an address searched in site analysis; those older records are still held there. Signed-in activity is tied to your account id, with your email as a profile attribute; signed-out activity is anonymous. These requests go through our own domain, we record no session recordings or keystrokes, and a copy of the events is exported nightly into our own database for reporting.
How we use it ourselves
Our team reviews usage in an internal, access-controlled admin: how many people reach each step of each tool, which features get used, how accurate our data is by area, and which accounts use Lekua most, so we know who to ask for feedback. Only named members of our team can open it, and the pages that show an address or an account are limited further. None of it leaves Lekua.
Plant-demand statistics
To understand which plants designers actually use by region, we log the plants site analysis recommends and the plant lines read from every plan uploaded for a plan check (each plant’s name, quantity and container size), with the site’s county, fire-hazard zone, water-use region and plant community, each plant’s type and rank, and a random id. These records don’t contain an address, your name or your account. A site analysis’s rows carry the same per-tab id as our address-search log, so our team can match them to the search they came from; a plan check’s rows can’t be matched that way. From them we build county-level totals such as how many of a species designers in one county specified in a quarter. We may share those totals with California nurseries so they can grow what designers are specifying. A total never includes a project, an address, your name or your firm. Before we share any totals, we’ll leave out every county with so few projects that a total could point to one of them. We also log the existing trees shown on plans uploaded for a plan check and on surveys added to a project — each tree’s species when its label names one — with the site’s county and ZIP code and a fingerprint of the uploaded file, so the same file is counted once — never an address, the file itself, or your identity.
On your device
We use local storage for your theme preference, your last-searched address and up to five recent searches, each with its coordinates and county (so the app can restore and offer them), the email address you last asked us to send a sign-in link to (to fill in the sign-in form), and your sign-in session. Signing out doesn’t clear the recent searches or that email; clearing this site’s data in your browser does. Session storage, which your browser empties when you close the tab, holds a copy of the last address searched in that tab, the random per-tab id our search and plant-demand logs use, and our analytics’ own per-tab id. Our analytics keeps its data in local storage, not in a cookie: a random id while you’re signed out, and once you sign in, your account id and email (both removed when you sign out). It also stores the first page you opened here, the first page of your latest visit, and the site that linked you here; these stay in your browser, and what’s sent to PostHog is cleaned like every other web address. We use no advertising cookies. Our analytics never follows you to other sites, so browser signals like Do Not Track and Global Privacy Control change nothing — every visitor already gets that treatment.
Turf Check
What it asks for
Turf Check is our free lawn-rebate lookup for California homeowners. It needs no account. You type a street address; on the result you can also enter or correct your lawn area, change the property type we guessed, and, where two water systems overlap, pick the one that sends your bill.
Where your address goes
As you type, your browser sends what you’ve typed to Mapbox for suggestions. When you press the button, the address goes to our server inside the request, not in a web address, and our server sends it to Mapbox to find the point on the map. That is the only place it goes. We don’t write the address you typed to our logs or our database, and we don’t send it to your county, your water supplier or anyone else.
What we look up with the point
With the point, not the address, we ask public services: your county’s parcel map (or the State of California’s statewide parcel layer, where we have no county map or the county’s returns nothing), for the lot, its parcel number and the county’s own address for it; when needed, the U.S. Census Bureau, to name the county; the State Water Board’s service-area map and regional water-district maps, to find your supplier; in some counties a regional land-use map, or the county’s assessor roll by parcel number, for the property type; and the soil, climate, fire-zone and other public map services behind the plant suggestions, including iNaturalist for plants recorded nearby. Our host, Vercel, logs every request with your IP address and the web address asked for. For a result page, that web address is your result link, which our server can decode back to the point we found, and our server’s own logs there can also include the lot’s map coordinates.
Measuring your lawn
When a result opens without a lawn figure, your browser takes a picture of the aerial imagery of your lot, marked with a grid and with the land around it dimmed, and sends it to our server, which asks our AI provider, Anthropic, to mark the lawn. Only that picture and our instructions are sent: no address and no parcel number. The imagery itself comes from Mapbox, so your browser’s map requests, and your IP address, reach Mapbox like any map website.
Your result link
The result’s web address never contains your street address. It holds a sealed code: the point we found, to about a metre, with the county and city, encrypted with a key only our server holds. Anyone you share the link with can open it and see the result, including the lot’s outline on the map and the county’s address and parcel number for it, and a lawn measurement made when they open it is recorded like one of yours. The lawn area (measured from the imagery or entered by you), whether it was measured, and any property type or supplier you choose are added to the link as plain text. Search engines are told not to index result pages, and the links to a water agency’s site carry no referrer.
What we keep
Besides the analytics below, we keep one kind of record: when the page measures your lawn, or you change the lawn area, the property type or the supplier, we save what the page said and what it became, the sealed code from your link, the county and city, the county’s public record of the lot (its parcel number and street address), and a code made from your connection’s IP address with a secret key, which groups one visitor’s changes. Without that key it can’t be matched back to the IP address, and we don’t store the IP address itself. Only our team can read these records, and we use them to find where our data is wrong. They aren’t tied to an account: email us the address or the result link and we’ll delete the records for that lot. Turf Check saves no account, project or plant list. Apart from these change records and our host’s request logs, its record of searches is in our analytics: one entry when you search, with the county and city, and another each time a result page loads, with the figures it showed. None of them include the address.
Analytics on Turf Check
PostHog counts each check, including searches that fail and why, and each lawn measurement, change, print, copy and click through to an agency’s site, with the county and city, the property type, the lawn area, the lot size, the supplier and the rebate figure shown — never the address or the parcel number. Page views are sent with the code removed from the link. The search, and each load of its result page, also carry a short code made from your result link. PostHog can’t turn it back into a place, though the lot size (to a hundredth of an acre), the exact lawn area, the supplier and the city it receives could together narrow a check down to a few lots. Our team can match the code to the lot using the link: one you send us, or one in our change records or our host’s logs. The measurement and change counts don’t carry this code; from October 25, 2026, the print, copy and click-through counts do. A copy of these events is kept in our own database, as described above. If you’re signed in to Lekua, what your browser sends is tied to your account.
On your device
A lawn measurement is kept in this browser’s local storage under the lot’s county and parcel number (or the point, when there’s no parcel number), with the lot’s map frame, so a return visit shows the same map. We stop using it after 30 days and delete it the next time you open a Turf Check result with a lawn map in this browser. To remove it sooner, clear this site’s data. Turf Check sets no cookies.
Water agencies
Lekua doesn’t apply for you and sends nothing to your water supplier. The apply and program links open the agency’s own website and carry nothing from your result, and the application is something you print or copy yourself. No water agency endorses Turf Check or receives data from us.
Where your data lives
We don’t sell or share your data, and we use service providers only to run the product itself: Supabase (database and authentication), Vercel (hosting and file storage), Fly.io (hosting for our file-reading service: plans and surveys you upload are sent there to be read; it keeps a file only while reading it — though the pieces of a large upload that stops partway can stay until the service next clears them or restarts — and holds its last few results in memory to answer repeat requests), Resend (transactional email), PostHog (product analytics, as described above — usage events with county- and city-level location, plus the street address on survey and plan-check uploads), and Mapbox (mapping — the address you type is sent to Mapbox to locate the parcel, and your browser requests map tiles directly, which exposes your IP address to Mapbox and sends its standard map-usage telemetry, like any map website). In site analysis, in counties that publish a public address-point layer, the house number and street name (not the city, and not your account) are also sent to that county’s addressing service, to confirm we drew the right lot; and the coordinates of each search are sent to the U.S. Census Bureau’s public county lookup to name its county. When site analysis can’t confirm which lot an address belongs to, the address can appear in our server logs at our host, Vercel. Nurseries receive data only when you send it: when the availability request feature launches, pressing send will email the plants, quantities and sizes you chose, the project county, and your name and firm as the buyer to the nurseries you pick, through Resend. Nothing about a project reaches a nursery before you press send, and a street address or your plan file never does. Generating your site analysis also queries public data sources (county GIS servers, USDA, USGS, iNaturalist for plants and wildlife recorded nearby, and similar) with the coordinates of the parcel being analyzed. Plant photos are loaded by your browser from Wikipedia and from iNaturalist’s photo hosting. Part of the analysis runs on an AI provider (Anthropic): an aerial image of the parcel is sent to detect trees, lawn, and hardscape, and any plan you upload for a plan check, or survey you add to a project, may be sent to read its plant schedule and title block. Each provider processes data solely to provide their service to us.
The narrow exceptions
Two situations could require disclosing data despite everything above. If we receive a subpoena, court order, or other valid legal process — or need to protect someone’s safety — we may be required to disclose information, and where it’s lawful and practicable we’ll notify you first. And if Lekua is ever acquired or merges, your data may transfer to the successor, who must honor this policy; we’ll tell you before any such change takes effect. That’s the complete list.
Today we email you only to sign you in. When project emails launch, they’ll be limited to things you asked for: a receipt with your exported file, at most one reminder per project to run a plan check, and follow-ups on flagged plants — each with an unsubscribe link, honored immediately. No newsletters unless you explicitly opt in to product updates.
Deleting your data
Every project has a delete option (the ⋯ menu on your projects list) that removes the address, its activity log, its stored files, and any scheduled reminders from our production systems immediately (the search record described above is kept); residual copies in encrypted backups expire within 30 days. Analytics events already recorded, including the address on a survey or plan-check upload, are not removed by deleting a project; email us and we’ll delete your analytics profile and its events. To delete your entire account and everything attached to it, email hello@lekua.design from your account email (that’s how we verify it’s really you) and we’ll complete it within 45 days — usually much sooner. Turf Check records aren’t tied to an account; email us the address or the result link and we’ll delete the records for that lot.
Security
Data is encrypted in transit and at rest, and database access rules ensure your projects are readable only by your account. No system is perfectly secure, but we keep the attack surface small: no ad-tech, no third-party scripts beyond the services named above.
Who this service is for
Lekua is operated by LoveCRM. It is a United States service built around California properties and California regulations. Site analysis and plan check are made for professionals; Turf Check is for anyone with a California property. It is not directed to children, and we don’t knowingly collect information from anyone under 16.
Your rights
You can ask us what data we hold about you, ask for a copy, correct it, or delete it — regardless of where you live. California residents: we do not “sell” or “share” personal information as defined by the CCPA/CPRA, and we don’t use it for cross-context behavioral advertising, so there is nothing to opt out of. We will never treat you differently for exercising any of these rights. Requests: hello@lekua.design.
Changes
If this policy changes in a way that matters — new data collected, a new category of provider — we’ll update the effective date above and, for significant changes, tell signed-in users in the product before the change applies.