Checkup by Zanevan
Privacy Policy
Effective November 16, 2026 · version 2026-11-17
In short: we collect what you give us to ask for a checkup, we never read the records inside your layers, and your reports are kept private to your organization.
1. Scope and who is responsible
This policy describes what Checkup by Zanevan collects about the people who use it, why, and what we do with it. The Service is operated by Zanevan Engineering, LLC, 1221 Oak Street, Carthage, Missouri 64836, which is responsible for the information described here. Contact: chase@zanevan.com.
This policy is about people who use the Service. The public mapping data the Service reads about an organization is covered in Section 4.
2. What we collect
Request and account information: when you ask for a summary we collect your organization's name and state, your name, your job title if you give it, your work email address, and a link to one of your public maps if you give one. When you confirm your email address, that address becomes your account. On your account page you can change your name and job title.
Sign-in: you sign in with a link we email you; there is no password, so we never see or store one. A sign-in link works once and expires.
Billing information: if you buy a report or a plan, Stripe processes your payment. We store your Stripe customer identifier, what you bought and when, the amount, and for a plan its schedule, status, and the date the current period ends. Stripe collects your billing details to take payment and meet its own legal obligations. We never receive or store your card number.
Emails: we email you to confirm your address, to send your summary, to sign you in when you ask, and, on a monitoring plan, to tell you what changed. They are sent by Resend from checkup@zanevan.com, and replies come to us. A copy of the emails about your request reaches the person at Zanevan who runs the Service. We do not add you to a mailing list.
Usage: ordinary server logs, which include IP addresses, kept for a short, rolling period for security and to prevent abuse, and short-lived counters of requests per IP address used only to limit abuse.
Visit counts: to see how many people use the Service and how they found it, we count page views with Vercel Web Analytics. Each count records the page viewed, the site that linked to it, an approximate location worked out from your network connection, and your browser, operating system, and type of device. It uses no cookies and stores nothing in your browser, and the counts are not linked to your name, your email address, or your account.
3. Why we use it
We use this information to provide the Service: to confirm that a request really comes from the organization concerned, to run the check, to deliver summaries and reports, to take payment, to run a monitoring plan, to answer your questions, and to keep the Service secure. We do not sell your information and do not use it for advertising.
4. What a check reads, and how reports are kept
A check reads only what an organization already shares publicly through ArcGIS: public item pages and the descriptions services publish about themselves, including layer and field names. It does not download feature data, so it does not read the records inside your layers, and it does not use any login.
A report lists what was found, by name. Because a report shows which of an organization's public layers can be changed by anyone, we treat reports as confidential: they are kept in a private database that only the Service's own server can read, are shown only to the signed-in account they belong to, and are never published.
Separately, MapPull by Zanevan keeps a directory of public maps. That directory is public information about organizations, not personal information about you, and is described on mappull.zanevan.com.
5. Service providers
We rely on Google (Cloud Firestore, in the United States) to hold account records and reports, Vercel to host the Service and count visits to it, Resend to send the emails described in Section 2, and Stripe to process payments. Each processes data on our behalf under its own terms, and none of them may use your information for its own purposes.
The mapping services a check reads will see requests from the Service, identified as Checkup by Zanevan with a contact address, so an organization's GIS staff can see in their logs who is reading and how to reach us.
We disclose personal information beyond these providers only where the law requires it (for example, a valid legal demand or a tax authority), to protect the Service or the rights of others, or as part of a merger, acquisition, or sale of assets, in which case this policy continues to apply to it.
6. Retention and deletion
We keep account records and reports while your account is open, so your past reports stay available to you. Payment records are kept for as long as tax and accounting law requires, generally seven years. Server logs are kept for a short, rolling period.
To delete your account and its reports, email chase@zanevan.com from the address on the account and we will do it, subject to those obligations. Stripe keeps its own payment records under its own privacy policy.
7. Security
The Service is served over HTTPS. Account records and reports are held in a database that accepts no access from browsers at all; only the Service's own server can reach it, and it does so without stored keys. Sign-in links are single-use and expire. No method of transmission or storage is perfectly secure, and we cannot guarantee absolute security.
8. Your rights
You may ask us for a copy of the personal information we hold about you, to correct it, or to delete it, by emailing chase@zanevan.com. We will respond within the time the law that applies to you requires. If you are in a place whose law gives you further rights over your personal information, we will honor them.
9. Children
The Service is for people acting for organizations and is not directed at children. We do not knowingly collect personal information from children.
10. Cookies and browser storage
The Service sets no advertising cookies, no analytics cookies, and no third-party trackers. It sets two cookies, only when you sign in: one that keeps you signed in for up to 30 days, which page scripts cannot read, and a marker that lets the page header show "My Checkup" instead of "Sign in". Stripe sets its own fraud-prevention cookie on its checkout pages, under Stripe's privacy policy. The visit counts described in Section 2 use no cookies.
11. Changes to this policy
We will update this policy when what we collect or do changes, and change the effective date above. If a change is material we will tell you by email or on the Service before it takes effect.
12. Contact
Zanevan Engineering, LLC, 1221 Oak Street, Carthage, Missouri 64836. chase@zanevan.com.
See also the Terms of Service. Back to Checkup by Zanevan.