Who Owns MapQuest? System1, Not Google, Explained

Mention MapQuest in conversation and Google Maps tends to come up as some kind of corporate cousin. It isn't. The short answer to who owns MapQuest is System1, a digital-advertising company, not Google (SlashGear, Monday). System1 bought MapQuest from Verizon in 2019, in a deal small enough that Verizon didn't break it out separately in its financial filings (SlashGear, Monday; Wikipedia).

MapQuest also predates Google Maps by years. It launched in 1996 as the first commercial web mapping service, back when printing out a set of directions from a website felt genuinely new (Wikipedia; Tedium, last year).

This article answers two separate questions. First, who owns MapQuest right now. Second, what MapQuest's own apps say they collect from a phone. Ownership doesn't answer the second question, and treating them as the same thing is where a lot of confusion about this app starts.

Who owns MapQuest now?

System1 describes itself as an "omnichannel digital marketing platform" powered by machine learning and AI, built to put ads in front of the right people at the right time. It's an advertising business, not a mapping company, headquartered in Marina del Rey, California (SlashGear, Monday).

MapQuest's leadership has kept some day-to-day independence under that ownership, at least on one visible decision. When the U.S. government renamed the Gulf of Mexico, MapQuest declined to follow suit on its own maps, with leadership calling the call "easy" since it lined up with a similar decision the company had made a year earlier (SlashGear, Monday).

MapQuest ownership history: from Nasdaq debut to System1

The ownership chain runs through a handful of clean handoffs:

• 1996: MapQuest launches as the first commercial web mapping service (Wikipedia).
• February 1999: MapQuest goes public on Nasdaq (Wikipedia).
• December 1999: AOL announces a $1.1 billion acquisition of MapQuest; the deal closes in 2000 (Wikipedia; SlashGear, Monday).
• 2015: Verizon acquires AOL for $4.4 billion, absorbing MapQuest in the process (Wikipedia; SlashGear, Monday).
• 2019: Verizon Media sells MapQuest to System1 for an undisclosed amount (Wikipedia; SlashGear, Monday).

Nobody has published the actual sale price for that last transaction. The cited reporting only indicates the amount was too small for Verizon to disclose separately, not what the figure was (SlashGear, Monday; Tedium, last year).

One technical detail has stayed constant through all of that corporate churn. Since 2014, MapQuest has leaned on TomTom's mapping data rather than building its own map tiles from scratch (Wikipedia). That deal predates the System1 sale and outlasted it, and it's a good reminder that who owns the MapQuest brand, who supplies its map data, and what a given MapQuest app collects on a phone are three different questions.

Is MapQuest owned by Google? Why the mix-up happens

Google did not own MapQuest, and never has. The confusion is about market position, not corporate lineage, and it traces back to a specific product gap rather than any shared ownership.

When Google launched Google Maps in 2005, its biggest advantage over MapQuest was something that sounds basic now: dragging the map to a new spot without reloading the page. MapQuest's site wasn't built for that kind of panning, and it showed (Tedium, last year). Less than two years later, the iPhone arrived with Google's mapping app built in, not MapQuest's (Tedium, last year). That's roughly when a lot of people's mental map of "who makes maps" shifted toward Google for good.

Knowing System1 runs MapQuest's ad business tells you who currently owns and operates the brand. It doesn't tell you what a specific MapQuest app puts on a phone's permissions screen, and that's worth checking directly rather than assuming.

What MapQuest's apps declare about your data

MapQuest currently operates at least two distinct products: the standard "MapQuest GPS Navigation & Maps" app, and a separate Android app called Private Maps by MapQuest. They carry different disclosures, and treating them as interchangeable is a mistake if privacy is the reason someone's choosing between them.

iPhone app: what the App Store label declares

PrivacyScan's April 2026 report examined version 10.14.0 of the iOS app, using Apple's own privacy label along with a static look at the publicly accessible parts of the app bundle, things like the frameworks folder and entitlements file. No code was decompiled or reverse engineered, and the label itself is self-reported by the developer to Apple, not independently audited (PrivacyScan, earlier this year).

Under that label, the app declares data linked to a user's identity, including location, device identifiers, and usage data, plus cross-app tracking through identifiers (PrivacyScan, earlier this year). It separately declares collecting purchases, contacts, search history, and diagnostics data, though Apple's categories list those as not linked to identity (PrivacyScan, earlier this year).

On permissions, the app requests six declared capabilities: App Tracking Transparency, location access in three separate modes, contacts, and Face ID (PrivacyScan, earlier this year). Requesting a permission isn't the same as every user granting it. The app also bundles six third-party SDKs, split evenly across analytics, infrastructure, and other functions, with none classified as advertising or attribution SDKs (PrivacyScan, earlier this year). An SDK being present in the bundle doesn't confirm it's actively pulling data at runtime; it just means the capability exists in the code.

The scan also found the app registers four background modes, meaning it's allowed to perform certain tasks while it isn't actively open (PrivacyScan, earlier this year). That's a technical permission, not proof the app is continuously logging location while closed, and this kind of static analysis doesn't include the network traffic monitoring that would settle that question either way.

All of this reflects one version of the iOS app, checked once, several months ago. It doesn't cover the Android version of the standard MapQuest app, and it's built on a self-reported label plus static inspection, not observed runtime behavior (PrivacyScan, earlier this year).

Private Maps by MapQuest: a claim, not yet an audit

MapQuest introduced Private Maps last year as an Android-only app built specifically around privacy (Los Angeles Times, last year). The launch announcement promises no tracking, no data sharing, no ads, search history that stays on the device, and analytics the company describes as anonymous (Los Angeles Times, last year).

Take that at face value only as far as it goes. The announcement confirms Android availability; it doesn't confirm the app is exclusively on Android, since it doesn't address iOS one way or the other. And it's a company claim from a launch announcement, not a Play Store Data Safety review or an independent audit of the privacy policy. The supplied research doesn't include either kind of verification for this System1 MapQuest product.

Comparison at a glance:

What to actually check before you trust either app

Before picking between these two apps, confirm a few things directly instead of guessing:

• Check the exact app name and platform first. "MapQuest GPS Navigation & Maps" and "Private Maps by MapQuest" are not the same product, and a privacy claim about one doesn't carry over to the other.
• On iPhone, open the current App Store listing for whichever app is installed and check the privacy label's version date, then review granted permissions under Settings > Privacy. Labels change between updates, and the snapshot cited here is already a few months old.
• On Android, check the Play Store's Data Safety section directly instead of relying on either app's marketing copy, since that section wasn't independently reviewed for this article.

Don't assume a no-tracking claim on one MapQuest product applies to the other. Pull up the current store listing for the specific app before deciding whether it fits what a privacy-conscious user actually wants.