Overpex home
Log inStart mapping

Legal

Privacy Policy

Effective November 9, 2026

This policy explains what personal information Hiler Company ("Overpex", "we", "us") collects when you use the website at overpex.com, the documentation at docs.overpex.com, the map app at maps.overpex.com, the Overpex iOS and Android apps, and the Overpex API and MCP server (together, the "Service"), and what we do with it. It works alongside our Terms of Service, which use the same terms, including "Your Content".

We don't sell your personal information for money, and we don't show ads in Overpex. We do use Google and Meta tools in the map app in your browser to measure and advertise Overpex, which some US state laws count as "sharing" personal information or "targeted advertising". Section 5 explains how to opt out. The iOS and Android apps don't use these tools, or any of the usage analytics described below.

1. What we collect

Your account. Your email address and a password, which we store only in hashed form. If you sign in with Google, we receive your name, email address and Google account ID from Google. You can add a first and last name, company, phone number, photo, time zone and measurement units to your profile.

Your Content. The maps, projects, roads, markers, areas, styles and notes you create, and the files you upload, such as GeoTIFF imagery and 3D models. Maps of private land can reveal where you live or work, so we treat Your Content as personal information when it relates to you.

Survey requests. When you request an aerial survey, we collect your name, email, phone number and preferred contact method, the property's address, location and boundary, its size and type, how to access it, and anything you add in the notes.

Reports about maps. When you report a shared map, we collect the reason you choose, anything you write, and the map it's about. If you're signed in, we link the report to your account. If you're not, we store a code derived from your IP address instead, so we can spot repeated reports. We don't tell the map's owner who reported it.

Enterprise requests. When you ask to move to an enterprise account, we collect what you tell us: your organization, how many maps you need, how you'll use them and, if you add one, a phone number. We record it with your account's name, email address and how many maps you have.

People you add. When you invite a collaborator, you give us their email address, and we email them the invitation. When our team sets up a map for a prospective customer, we create an account for them with their name, email address, company and property name, email them a link, and record when they first and last opened it and how often.

Location. The iOS and Android apps, and the map app in your browser, can use your device's location to show where you are on a map, but only if you allow it. Your location stays on your device unless the map's owner turns on location sharing and you choose to join it. While you're connected, your position is sent live to the map's owner and collaborators. We don't store it: it disappears when you disconnect.

Purchases. Payments are taken by RevenueCat and its processor Stripe on the web, or by Apple or Google in their app stores. We don't receive your card details. We keep a record of what you bought, when it renews or ends, and the store's transaction ID.

How you use the Service. We keep a history of actions in your account, such as creating a map, inviting someone or changing a setting, including which app was used. We count the imagery data delivered from each account's files, for billing. When you use an API token, we record when it was last used.

Usage analytics on the web. On our website, our documentation and the map app in your browser, our own analytics record the pages you open and what you do there: for example, which buttons you press, whether you sign up, which drawing tools you use, whether directions work, and whether a purchase goes through. Each record is the kind of action and a few fixed details about it, such as "drew a road" or "copied a share link". We set this up not to record what you type or search for, the names or contents of your maps, your email address, or your account or map IDs, and they remove sign-in and invitation codes and map IDs from page addresses before recording them. They also note whether you're signed in. Google and Meta tools in the map app receive similar information (section 3). The iOS and Android apps don't collect usage analytics.

Device and diagnostics. Like most online services, our servers receive your IP address, browser or app version, and the pages and requests you make. We use IP addresses briefly to rate-limit traffic and stop abuse. When something goes wrong in the map app, our error-reporting provider records the error and your browser details. For a sample of sessions, and for sessions where an error occurs, it also records a replay of the page layout and clicks around the problem, with all text and images masked.

Emails to us. If you email us, we keep the message and your contact details to reply.

2. How we use it

3. Who we share it with

People you choose. Collaborators, people with a link, and anyone who can see a public map see that map's content. Collaborators also see the names or email addresses of the other people on the map.

Service providers that run parts of the Service for us. They may use the information only to provide their service:

Tools you connect. If you give an API token to another app or an AI assistant, it can read and change what the token allows, and that tool's provider handles the data under its own terms.

Legal and business reasons. We may disclose information if the law requires it, to protect people's safety or our rights, or as part of a merger, sale or reorganisation of our business, in which case this policy continues to apply to it.

4. Automated processing and AI

Smart Trace suggests roads from imagery. It runs on our own servers.

Illustrated basemaps are made by sending sections of map imagery to an AI image service, accessed through OpenRouter, which turns them into a drawn-style map. Only imagery is sent, not your account details.

Neither feature makes decisions about you that have legal or similarly significant effects.

5. Cookies, analytics and advertising

The map app keeps you signed in using your browser's local storage. It also sets one cookie, which tells this website that you're signed in so it can show the right buttons. It holds no account details. The map app also notes a few first-time steps in local storage, such as making your first map, so each is counted once. Google Analytics and the Meta pixel set their own cookies.

Our own usage analytics don't use cookies. They use your IP address and browser details to estimate your country and to recognise a visit as you move between the website, the documentation and the map app, without keeping your IP address in the analytics records. The iOS and Android apps don't use cookies, Google Analytics, the Meta pixel or our usage analytics.

Opting out of sharing and targeted advertising. You can do this in any of these ways:

Our own usage analytics also don't run when your browser sends a Do Not Track signal. Clearing or blocking cookies doesn't stop the map app working, but signing in needs local storage.

6. Our team's access

A small number of Overpex staff can open accounts and maps to support customers, set up maps for them, deliver survey imagery, review reports about maps and answer enterprise requests. When we act on a report, we may make the map private. Staff changes made on a customer's behalf are recorded in an audit log.

7. How long we keep it

We keep your account and Your Content while your account is open. When you delete something, it's removed from the Service, and copies in backups are overwritten on a rolling basis. When you delete your account, we delete your profile, your maps, uploads, styles and imagery, and your account history, and remove your files from storage shortly afterwards. Changes you made on other people's maps stay on those maps, without your name. We keep reports about maps and enterprise requests while we handle them and afterwards as a record of what we decided. We keep records of purchases and survey requests as long as tax, accounting and other laws require, and error reports and server logs only for as long as they're useful for diagnosing problems. Usage analytics records hold no account details, and we keep them for as long as they help us understand how Overpex is used.

8. Your choices and rights

Depending on where you live, you may also have the right to ask for a copy of your personal information, to correct or delete it, to opt out of its sale, sharing or use for targeted advertising, to object to or restrict how we use it, and to appeal if we turn down your request. You can use an authorised agent to make a request for you. Email [email protected]. We may need to confirm your identity first, and we won't treat you differently for exercising these rights.

9. Security

We use encryption in transit, hashed passwords and API tokens, access controls on every map, and limited staff access. No service is perfectly secure, so keep your password and tokens private and tell us if you think your account has been misused.

10. Children

Overpex is for people aged 18 and over. We don't knowingly collect information from children. If you think a child has given us information, contact us and we'll delete it.

11. Where it's processed

We're based in the United States, and your information is processed in the United States and in other countries where our service providers operate. Where the law requires it, we use appropriate safeguards for those transfers.

12. Changes to this policy

We'll update this policy as Overpex changes. For a material change, we'll tell you by email or in the app before it takes effect.

13. Contact

Questions or requests about your privacy: [email protected], or write to Hiler Company, 9505 Wildcat Ridge, Godley, TX 76044, United States.