Icons
Icons
Icons
Consultant working on a short-term mapping project

Does Maptive Offer a Short Term Pass or Only Plans

November 4, 2026
Small business owner reviewing software expenses

How Much Mapping Software Costs a Small Business

November 7, 2026

How Maptive Keeps Your Data Secure & Private

November 6, 2026

Map your data in minutes with Maptive

10-day free trial No credit card required

Start Free Trial

Anyone reviewing the security of a browser-based tool asks about the same handful of things, in about the same order. How is the data encrypted? Where is it hosted? What audit reports are there? Who else handles the data, how is it deleted, and who can see it? Maptive encrypts your data in transit and at rest, stores it in the United States on Amazon Web Services, and keeps a map private until you share it.

Maptive publishes full answers to some of these. For others you have to request a document. A few details aren’t published at all, and you’ll need to ask Maptive about those.

Is Data Encrypted in Transit and at Rest

Yes, both. “In transit” means while your data travels between your computer and Maptive. “At rest” means while it’s in storage.

In transit, data is encrypted using TLS 1.2 or higher. The insecure protocols, which are HTTP and TLS 1.0 and 1.1, are disabled. That covers traffic between your browser and Maptive, and it covers traffic between Maptive’s own services.

At rest, data is encrypted using AES-256, and that includes databases, block storage and backups. The encryption keys are kept in a dedicated key management service with strict access controls and automatic key rotation. Account passwords are stored using one-way hashing.

Where Is Maptive Data Hosted

Maptive is cloud-hosted, so your data is stored on Maptive’s servers. Those servers are hosted entirely on Amazon Web Services in the US East region, in Northern Virginia, and Maptive processes and stores its data in the United States. Production runs in a dedicated virtual private cloud with separate public, private and data subnet tiers, and the application and database services have no direct inbound internet access. That US region is the only one Maptive lists.

What Audit Reports Does Maptive Have

Maptive’s trust center lists a SOC 2 report. It covers the Maptive platform against the applicable trust services criteria for Security, Availability and Confidentiality, and it is valid from August 20, 2026, through August 20, 2027. The listing doesn’t say if it is a Type I or Type II report, so check the report itself for that.

The trust center also lists a penetration test report. Maptive brought in security experts to run a vulnerability assessment and penetration test of the Maptive web application. Separately, Maptive runs vulnerability assessments on production every week.

A reviewer who gets a SOC 2 report usually checks which product is in scope, what period it covers, which criteria it includes and if it notes any exceptions.

Neither document is a public download. You request each one through “Get Access” on the trust center.

Who Owns the Data You Upload and Who Else Handles It

Data Ownership and How Maptive Uses Your Data

You keep ownership of your content. Maptive’s terms say so directly, and they add that intellectual property rights in your content are not transferred to Maptive. The terms do give Maptive a license to use that content in connection with providing the service.

Maptive is not in the business of selling your information, and it doesn’t use client data for any purpose other than to provide the contracted services. It will release personal and account information in response to lawful requests by public authorities.

On the privacy side, you act as the data controller and Maptive processes personal data on your behalf as a data processor. That means the privacy obligations you have to the people on your list are still yours. If the GDPR applies to your use of Maptive, the terms include a data protection addendum that applies to you.

Outside Processors and Address Geocoding

Amazon Web Services hosts the data. Google Maps is the other outside company a reviewer will ask about. Maptive uses the Google Maps API to get the latitude and longitude for the addresses you upload, which is how an address becomes a point on the map. Maptive doesn’t publish which fields from your file are sent in that step, so ask Maptive if you need that for your review.

The current list of outside processors is on Maptive’s trust center.

If you use Google Sheets, you pick the sheets you want with read-only access, and Maptive creates a copy of the sheets you select on its servers.

Maptive does not store credit card information on its own systems.

How Long Is Data Kept and How Is It Deleted

Deleting Maps and Account Data

You can delete maps and data yourself at any time. Deleting the maps on your account permanently deletes the data in them.

You can also have Maptive do it. If you cancel and ask in writing, Maptive will remove all of your content within 5 business days of the cancellation.

If you close an account and don’t ask for that, Maptive keeps the data in the account for up to a year so that you can start using the service again. It will delete that data any time you ask.

Maptive follows NIST SP 800-88 when it deletes data. That’s the US government’s guideline for media sanitization. When your data is deleted, it is permanently purged from Maptive’s AWS storage and databases.

Backups and Recovery Targets

Maptive runs automated daily backups of its production databases and critical volumes. The backups are encrypted at rest and stored in geo-redundant storage, and there is a geographically separate disaster recovery environment in AWS.

Maptive’s targets are a recovery point of 24 hours and a recovery time of 4 hours. In plain terms, up to a day of changes could be lost in a disaster, and the target for being up and running again is four hours. Maptive tests and validates its recovery once a year.

After you delete something, copies may remain on Maptive’s backup storage systems for about 45 days.

Who Can See Your Data Before You Share a Map

By default, all the data on your map is private. Only you control sharing, and you can share or unshare a map at any time.

Customer data is logically segregated, so each customer can access only their own uploaded data, maps and outputs.

Inside Maptive, access to production is restricted by job responsibility and least privilege. It is given to individual users, and elevated permissions require documented approval. Production customer data is not used in development or test environments.

Then there’s your own login. Each user can set up two-factor authentication from Account Settings. Maptive also lists single sign-on, which connects Maptive to your identity provider so the team logs in with work credentials. It doesn’t publish which identity providers, protocols or plans that covers, so if you need those details for your review, ask Maptive.

The Sharing Settings You Control

Sharing is the part Maptive leaves to you. Whoever shares a map decides what a viewer can see and what they can take away with them.

Password Protected and Public Links

Maptive has two privacy options for sharing a map outside your account, Password Protected and Public. Open the map, click Share on the left, choose Share Externally, pick the privacy level, pick the starting map view, and then email or copy the link.

A Public map doesn’t show up in a web search. Public means anyone with the link can view the map, so anyone the link gets forwarded to can open it.

A Password Protected map has only one password. Everyone you share it with gets the same one. You can’t remove one person’s access, and changing the password locks everyone out at once.

Viewers don’t need a login and can’t make permanent edits to the map. An embedded map has the same two privacy levels, and on a public web page anyone who visits that page can see it.

Hiding Tools, Columns and Exports From Viewers

The viewer settings are in Map Settings, under Shared Maps/Presentational Maps. That section lets you choose which tools people without a license can see and use, and which they can’t.

You can also turn off individual columns so they’re hidden on the shared map. A sales column or a contact column can be hidden while the address stays.

Viewers can’t export your data until export is authorized. You request that in the same settings, and once it’s authorized you choose which tools shared users can export with. Even then, you can leave columns out of the export.

Two more settings limit the area a viewer sees. Restrict zoom level sets how far out or in they can go, and Restrict Map Panning stops them from moving the map. Maptive’s own advice for a shared map is that less is more.

Team Access and Exported Files

For teammates on the same account, sharing works differently. On Team and Enterprise, which include map collaboration, you give each teammate editing or view-only access to a map.

Keep track of exports too. As the map owner, you can export the entire dataset, the filtered data or the data visible on the map. Once that file is downloaded, it’s an ordinary spreadsheet, and Maptive’s controls no longer apply to it.

Before you upload, cut the file down to the fields the map needs. A branch coverage map may need an address, a customer ID and a service category without needing names or contact details.

gray-logo

Related Articles

✕