Privacy Policy

1. Who we are

Smart Site Plan, a spatial intelligence platform, is operated by Juno Maps, LLC ("we," "us," or "our"). This Privacy Policy explains what personal data we collect, why, how we use and share it, how long we keep it, and the rights and choices you have. For personal data you upload or generate in your projects, you are the controller and we act as your processor under our Data Processing Agreement.

We are the controller for the account, billing, security, and usage data described below. Privacy is built into the platform, not bolted on.

2. Data we collect

Account and profile: name, email address, and authentication data when you create an account. If you enable security features, we store passkey credentials, two-factor settings, trusted-device records, and (only if you enable SMS two-factor) a phone number. Passkeys use your device's biometrics or screen lock to authenticate locally; your biometric data stays on your device and is never sent to or stored by us.

Project content: the maps, layers, features, drawings, measurements, comments, forms and submissions, files, and photos you create or upload.

Location and GPS data: when you use GPS or live location features, we process device location (latitude, longitude, and where available altitude, accuracy, heading, and speed), a reverse-geocoded place name, and session timestamps. Photos you upload may contain embedded GPS coordinates (EXIF). See Section 4.

Property and search lookups: the addresses, coordinates, and queries you submit to look up property, parcel, open-data, or search results.

AI inputs: when you use an AI feature, the content you submit for it (such as a site boundary and development program for Site Plan AI, the text of an Ask anything request, a project image you ask it to trace, or the plan pages you send for digitizing) and any context you provide. See Section 5.

Usage, device, and security data: server log data, IP address, browser and operating-system type, login activity, and an approximate location (city or region) derived from your IP address for security and audit purposes. To recognize a device you marked as trusted and to tell you about a sign-in from a new device, we keep a one-way hash of your browser's user agent, language, and browser hint headers. We do not use it, or any other device fingerprint, for analytics or advertising.

Product usage (analytics): how the Service is used, as described in Section 7: the pages you view, the features, panels, tools, and map layers you use, searches and their categories, errors you see, and session timing, with coarse device, browser, operating-system, and country information.

Usage limits: to count free usage (the weekly allowance of a free account, and the daily allowance without an account), we keep a random device token signed by our servers in your browser and count use against that device as well as against your account. Without an account, use is also counted against a one-way hash of your IP address. These counters hold no name or email address and expire within about eight days.

Email and disclosure records: for each account email we send, the recipient, subject, a copy of the message, whether it was delivered, and, when our email provider reports them, whether it was opened and the first time a link in it was clicked. We also record the terms, renewal, and price disclosures you were shown or accepted, with the IP address and browser at the time.

Property owners and other people named in public and licensed records: the Service shows public government map data and property records, which can name property owners and show their mailing address, parcel number, sale history, and assessed or market values. This comes from county and other government sources and, for property lookups, from our property data provider (ATTOM), and it is about people who may not use the Service. The free property sample shows a real parcel record with the owner's name and every financial figure removed on our servers before it reaches your browser. Our Terms (Sections 6 and 9) forbid using this data to decide anyone's eligibility for credit, insurance, employment, or housing.

Billing data: subscription tier and status, billing email, and payment records. Payments are processed by Stripe; we do not store full card numbers.

Form and field submissions: when you build forms, we process the submissions you collect, which can include the respondent's name, answers, files, photos, and location, and which may come from people who do not have an account. For this data you are the controller and we are your processor (see Section 6 and our DPA).

Sharing and access logs: when you publish a share link, we record limited access information for it, which can include the viewer's IP address and time of access, so you can understand reach and so we can protect the Service.

Notifications: if you enable browser push notifications, we store the push subscription your browser provides. If you enrol in the academy, we store your course progress and, for any certificate you earn, your name, score, and a verification record, which is viewable by anyone you give the certificate's verification link to.

Communications: messages you send us, support requests, and feedback.

3. Where your data comes from and how we use it

We collect personal data directly from you, automatically from your device as you use the Service, from collaborators and administrators who invite you or share with you, from OAuth identity providers if you sign in with one (for example Google), from our payment processor (Stripe) and email provider (Resend) about payments and email delivery, from security and fraud-prevention tools, and from public records published by government agencies and licensed property data providers (ATTOM), which can include information about property owners who do not use the Service. We use personal data to:

• Provide, maintain, secure, and improve the Service and its features.
• Authenticate you, protect your account, and detect and prevent fraud, abuse, and security threats.
• Generate the maps, analyses, lookups, and AI outputs you request.
• Process payments and manage subscriptions.
• Send transactional and account messages (verification, security, billing, alerts, and notifications you have configured).
• Send occasional product updates, tips, and offers, unless you opt out. Every such message includes an unsubscribe link, and opting out never affects the transactional and account messages above.
• Measure how the Service is used, find what is hard to use, and decide what to improve (Section 7).
• Enforce plan limits and free allowances, and protect our data catalog from scraping.
• Maintain audit logs and comply with legal obligations.

We never sell your personal data or business content, never use your project content to train our own AI models, never share your content with other customers, and never show advertising based on your content.

4. Location and GPS data

Precise location (GPS) is sensitive personal information under California law and sensitive data under most other state privacy laws, and we treat it with heightened care. We use it only to provide the location features you turn on, and we do not sell or share precise geolocation, and never use it for advertising.

Location features are optional and off until you enable them. Live location requires a device to opt in, typically by entering a pairing code or accepting an invitation, so a person is not tracked without a deliberate action on their device. Tracking runs only within sessions you start, not continuously in the background. Collected positions are associated with the project and the tracker you create.

You can switch location off in two ways: revoke the location permission in your device or browser settings, and end the session or delete the tracker in the app. Live location history is kept on a rolling 30-day window per tracker and is automatically pruned after that; deleting a tracker removes its positions and the place names derived from them. If you collect location data about other people, including field workers or form respondents, you are the controller and you are responsible for providing notice and obtaining any consent the law requires, as described in our Terms.

Photos you upload may include GPS coordinates in their metadata (EXIF), which can reveal the location of the person or place photographed. When you use photo-to-map analysis, those coordinates may be used to place the result on the map. Be mindful that a shared or exported photo may carry this location, and only upload content you are authorized to share.

5. AI processing

The AI features below send content to our AI sub-processor Google through the Gemini API, processed in the United States. No account identifiers are sent with these requests.

• Site Plan AI turns a site boundary and development program into a dimensioned concept site plan. It sends a numeric summary of the site geometry, the development program, any submittal requirements you paste in, and any site or plan images, aerial captures, or map captures you provide or ask it to read. The parcel street address and identifier (APN) are left out of these prompts.
• Ask anything reads what you ask for, finds and reviews the public government datasets that answer it, and carries out the request. It sends the text of your request, the earlier requests in the same conversation, the places you name, the names of your project's layers and groups when a request names one, and the names, fields, and sample records of the public datasets it considers.
• Ask anything image tracing and fitting traces what a project image shows into map features and lines an image up with the aerial map. It sends the project image you ask about (for example a drone photo, a site photo, or a plan picture), Esri aerial imagery of the same ground, and the outlines already traced on it.
• Plan digitizing reads utility plans into map layers of pipes and structures. It sends the pages of the plans you send (PDF pages or pictures, sent as images), including whatever the sheets print, such as project names, addresses, engineers, and dates.
• Open data catalog labeling labels and checks public government map layers in our open data catalog ahead of any request. It sends the listings, field names, and sample records of public government map layers. No customer content or account data is sent.
• Internal product analytics summarizes how the product is used for our own team. It sends aggregated usage statistics: counts and revenue totals by feature, page, journey, plan, country, and category, including the categories of searches that found nothing. Groups of fewer than five people are removed, and account, visitor, and project identifiers, email addresses, names, network addresses, and anything a person typed (searches and feedback) are stripped before anything is sent.

This content is sent to Google through the Gemini API and processed under Google's Gemini API terms, which allow Google to retain it for a limited period to detect abuse and policy violations. Those terms, not ours, govern what Google may do with that content, so do not submit content you are not authorized to share with a third-party processor. Images are never used to identify people. We do not use your content to train our own models.

AI assistant connector: if you connect an AI assistant to Smart Site Plan, the assistant sends us the map data request you make in it, and we run it as an Ask anything search, so the processing above applies. Signed in, the search is saved as a conversation in your account. Without an account, the assistant's connection receives a signed session identifier that lasts 31 days and is used only to count that connection's free searches; the search runs under an internal account that is not linked to you, and its results are published on a results page that anyone with the link can open for 90 days. Do not put personal information in a request you make without an account.

Open Data search also ranks how well public government datasets match your search with an image-classification model that runs on our own servers; it evaluates rendered previews of those public map layers, sends nothing to a third party, and does not process your project content.

Other AI features, such as analyzing an uploaded photo into map features, the site-plan PDF analysis tool, the regulatory assistant, and the chat assistant, are not currently enabled. When we enable one, the content you submit for it is sent to our AI sub-processor Anthropic (Claude), processed in the United States, and we will reflect that here and in our Sub-Processor Register.

Our AI features analyze and summarize the content you provide or public data; they do not generate synthetic images of real people or places, and they assist you rather than decide for you. AI outputs are informational only, and positions read from a plan are approximate; see our Terms for the limits on relying on them. We do not use AI to make decisions that produce legal or similarly significant effects about you without human involvement, so the GDPR's rules on solely-automated decision-making do not apply. You review AI outputs and decide how to use them.

The AI sub-processors we use are listed in our Sub-Processor Register.

6. How and with whom we share data

We do not sell your personal data. We share it only:

• With sub-processors who process data on our behalf to run the Service, under contract and subject to confidentiality and security obligations. The current list is in our Sub-Processor Register.
• With collaborators and recipients you choose, including project members you invite and anyone you give a share link to.
• For legal reasons, when required by valid legal process or to protect the rights, safety, and security of our users, the public, or us.
• In a business transfer, such as a merger, acquisition, or sale of assets, in which case we will continue to protect your data and notify you of any change in control or applicable policy.

7. Cookies, analytics, and similar technologies

Essential cookies keep you signed in and secure your session. They are required for the Service to work and are never shared with advertisers. We also set one first-party attribution cookie that remembers how you first arrived; it is not strictly necessary to use the Service, is never shared with advertisers, and is not used for cross-site tracking or advertising. You can clear it at any time in your browser settings. Every cookie and browser storage item we use is listed in our Cookie Policy.

Our own analytics. We measure how the Service is used ourselves, on our own servers, so we can find and fix what is hard to use and decide what to build. No analytics or advertising vendor receives this data, and only our own staff see it, in an internal dashboard; aggregated statistics with no identifiers may be summarized with an AI model as described in Section 5. We do not record what you type into your projects, the contents of your projects, or your screen, and we do not use analytics for advertising, to sell or share data, or to make decisions about you.

Optional analytics in your browser. When optional analytics is on, your browser sends us:

• the pages you view, identified by the kind of page (its route), not the full web address;
• the panels and tools you open and close and how long they were open, the features you use, the search results you open, and the map features and layers you interact with, add, or remove (the kind of layer and, for public data, its catalog source, never the contents of your own features);
• the plan and upgrade screens you see, whether a sample of the tool's result was shown, and what you choose on them, and when you reach a usage limit;
• downloads and exports (their format and kind), errors shown to you, several rapid clicks on the same control (a sign something is not working), how heavy the map may draw on your device, and engaged time (whether the tab is visible and in use, reported every 30 seconds);
• how you arrived: the referring website's domain and any campaign (UTM) tags in the link; and the app version.

Our servers add a coarse device class (desktop, tablet, or phone), browser family, operating-system family, the country our hosting provider resolved from your IP address, and the plan of the account or workspace the action happened in. We do not store your IP address with analytics. If you are signed in, events are linked to your account and to the project they happened in. To group events, your browser keeps a random identifier (replaced after 13 months and when you sign out), a visit identifier (renewed after 30 minutes without activity), and a short queue of events waiting to be sent. When you sign in or create an account, we link that browser's earlier events to your account, so we can see how people find and start using the Service. With optional analytics on, we also keep the text of the Open Data and data catalog searches you run, after removing email addresses, phone numbers, and street numbers and shortening it to 200 characters, for 90 days. If your organization's administrator chooses essential analytics only, we record none of these optional events for its members.

Service records. Separately, our servers record service events whether or not optional analytics is on, because we need them to run, bill, secure, and measure the Service: for example sign-ups, projects and layers created, searches (with an automatically assigned category of what was searched for, such as zoning or flood, but not the words), property lookups, Ask anything requests, subscription changes, share links created and opened, and that a signed-in account was active that day. They are linked to your account, not to a browser identifier. We also keep a live count of who is using the Service, which forgets each person after two minutes.

Your choice. Where the law requires consent before we may store anything non-essential on your device, which includes the European Economic Area, the United Kingdom, Switzerland, Brazil, and Quebec, optional analytics stays off until you opt in through the cookie banner. Everywhere else, including the United States, it is on by default and you can turn it off here at any time; your choice is remembered on this device. Turning it off, or sending a Global Privacy Control signal from your browser, stops optional analytics and the keeping of search text on this device; the essential cookies, the attribution cookie, and the service records above continue. We do not use advertising cookies, and we do not sell or share your data with advertising networks.

Do Not Track. Our websites do not respond to browser Do Not Track signals, because there is no common standard for what they mean. We do honor Global Privacy Control, as described above.

8. Data retention

We keep personal data for as long as your account is active and as needed to provide the Service, then delete or anonymize it on the schedule below, except where longer retention is required by law or to resolve disputes and enforce our agreements:

• Account and project content: kept while your account is active.
• GPS and live location history: rolling 30-day window per tracker, then auto-pruned.
• Account and security audit logs: kept for at least 12 months on every plan to protect your account, investigate security incidents and resolve disputes, and deleted after at most 24 months. How far back you can see your own activity log in the app depends on your plan.
• Form submissions: we do not auto-delete them; you control their retention and can delete them at any time.
• Share access logs: kept for a limited, capped window per share link.
• Login activity: kept while your account is active so we can detect unfamiliar sign-ins, and deleted with your account.
• Notifications: retained for a limited window for reference.
• Ask anything conversations: each request you make and the answer it got are saved as a conversation in your account so you can return to it. Conversations are kept while your account is active. A conversation you delete leaves your history but is kept so you can restore it, until your account is deleted. Deleting your account deletes all of them.
• Search and lookup history: your recent searches and property lookups are kept in short lists so you can run them again (Open Data searches for at most 90 days), and are deleted with your account. When optional analytics is on, the text of Open Data and data catalog searches is also kept for analytics, with email addresses, phone numbers, and street numbers removed, for 90 days (Section 7). Property lookup results are not stored by us unless you save them to a project.
• Product analytics: raw usage events, visits, and the links between a browser and an account are kept for 13 months; per-person daily totals and measured journeys for 25 months; aggregate statistics that identify no one are kept. Your analytics data is deleted with your account.
• Usage-limit counters: expire within about eight days.
• Catalog trace records: public data responses carry a daily trace code so a leaked copy of our catalog can be traced to the request that took it. The link between a code and the device token or account, IP address, and day is kept for 30 days.
• Email and disclosure records: kept as evidence of what we told you and when, including after your account is deleted, where needed to resolve billing and legal disputes.
• Billing records: retained as required for tax and accounting.

When you delete your account, we delete your data within 30 days and purge encrypted backups within 90 days, except records we must keep by law and the email, disclosure, and security records described above.

9. Security

We protect your data with encryption in transit (TLS) and at rest, passwordless sign-in (one-time email codes and passkeys), optional two-factor authentication, tamper-evident audit logging, rate limiting and account lockout, role-based access controls, and continuous monitoring. Because sign-in is passwordless, there is no reusable password on your account for an attacker to guess or steal. Full detail is on our Security Practices page. No system is perfectly secure, but we work to protect your data and to respond quickly if something goes wrong.

For personal data we control, if a breach is likely to result in a risk to your rights, we will notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it, and we will notify affected individuals where the breach is likely to result in a high risk to them. When we act as your processor, we notify you so that you can meet your own obligations, as set out in our Data Processing Agreement.

10. Your rights and choices

Depending on where you live, you have some or all of the following rights over your personal data:

• Access a copy of the data we hold about you.
• Export your data in a portable format (Settings then Export Data).
• Rectify inaccurate data.
• Delete your account and associated data (Settings then Delete Account).
• Restrict or object to certain processing.
• Withdraw consent where we rely on it, without affecting prior processing.

You can exercise these rights in-app or through our privacy request page, or by emailing privacy@smartsiteplan.com. You may also use an authorized agent. We will verify your identity and respond within the time required by law. If we decline your request, you may appeal by replying to our response or contacting privacy@smartsiteplan.com; if we deny the appeal, your state may let you complain to its attorney general. We honor browser Global Privacy Control signals as a request to keep optional analytics and the keeping of search text off; the service records described in Section 7 continue. We do not respond to Do Not Track signals. If you are in the European Economic Area or the United Kingdom, you also have the right to lodge a complaint with your local data protection authority (in the UK, the Information Commissioner's Office).

11. Legal bases (GDPR)

Where the GDPR applies, we process personal data on these bases:

• Performance of a contract to provide, maintain, and support the Service you signed up for, process payments, and manage your account.
• Legitimate interests, where we have identified a specific interest balanced against your rights: network and information security, fraud and abuse prevention, protecting and enforcing our rights, and understanding and improving how the Service is used through the service records described in Section 7 (for optional browser analytics and search text we rely on consent instead).
• Legal obligation, to comply with applicable law, including tax, accounting, and lawful requests.
• Consent, for optional analytics, for the collection of precise location through the features you turn on, and for any other processing where we ask for it. You can withdraw consent at any time without affecting prior processing.

Providing your account and billing data is necessary to create and operate your account; without it we cannot provide the Service. Optional data (such as a two-factor phone number, analytics, or push notifications) is not required, and declining it only turns off the related feature.

12. California privacy rights (CCPA/CPRA)

California residents have the right to know, delete, and correct their personal information, to data portability, to opt out of the sale or sharing of personal information, to limit the use of sensitive personal information where that right applies, and to be free from discrimination for exercising these rights. We do not sell or share your personal information for monetary consideration or for cross-context behavioral advertising, and we have not done so in the preceding 12 months. We do not knowingly sell or share the personal information of consumers under 16.

What we collected in the preceding 12 months. The categories below are the ones the California Consumer Privacy Act names. For each we list where it comes from, why we use it, the categories of recipients we disclosed it to for a business purpose, and how long we keep it. Every recipient below is a service provider or contractor bound by contract to use the data only to provide its service to us; you can see them by name in our Sub-Processor Register. We also disclose personal information to the collaborators and recipients you choose (Section 6).

Inferences. We do not build profiles that predict your characteristics, preferences, or behavior. For paid accounts we compute whether activity has dropped (fewer active days in the last two weeks than in the two before) so our staff can reach out to help; it is calculated when a staff member looks, is not stored, and is not used to make decisions about you.

You can exercise your rights, including the right to opt out, through our privacy request page or by emailing privacy@smartsiteplan.com. We will not discriminate against you for doing so, and we honor Global Privacy Control signals as described in Section 7.

Sensitive personal information. The main category of sensitive personal information we process is precise geolocation, and only when you turn on a location feature. We use it solely to provide that feature and the security and support around it, which are purposes for which the law does not require a "Limit the Use of My Sensitive Personal Information" option; we do not use or disclose it to infer characteristics about you. Most other US state privacy laws treat precise geolocation as sensitive data and require your consent before it is processed, which we obtain through the device opt-in described in Section 4.

13. International data transfers

Your data is processed in the United States, where our infrastructure is located. For transfers of personal data from the European Economic Area, the United Kingdom, or Switzerland, we rely on the European Commission's Standard Contractual Clauses, together with the United Kingdom International Data Transfer Addendum and the Swiss adaptations where they apply, and we add supplementary measures where appropriate. Where a recipient is certified under the EU-US Data Privacy Framework (and its UK and Swiss extensions), we may rely on that framework for transfers to it. You can request a copy of the relevant safeguard by emailing privacy@smartsiteplan.com. Our sub-processors and their locations are listed in our Sub-Processor Register.

14. Children's privacy

The Service is not directed to children under 18, and we do not knowingly collect personal data from them. If you believe a child has provided us personal data, contact us and we will delete it.

15. Changes and contact

We may update this Privacy Policy from time to time. For material changes we will update the version and date at the top of this page and, where appropriate, notify you. For privacy questions or to exercise your rights, contact privacy@smartsiteplan.com.