{"id":28596,"date":"2025-02-18T17:13:07","date_gmt":"2025-02-18T11:43:07","guid":{"rendered":"https:\/\/www.kaspersky.co.in\/blog\/?p=28596"},"modified":"2025-02-18T17:13:07","modified_gmt":"2025-02-18T11:43:07","slug":"geolocation-data-broker-leak","status":"publish","type":"post","link":"https:\/\/www.kaspersky.co.in\/blog\/geolocation-data-broker-leak\/28596\/","title":{"rendered":"Geolocation data brokers: What they do and what happens when they leak"},"content":{"rendered":"<p>Our smartphones and other devices collect and then transmit massive amounts of data about us to dozens, maybe hundreds, of third-party companies every single day. This includes our location information, and the market for such information is huge. Naturally enough, the buying and selling goes on without our knowledge, creating obscure risks to our privacy.<\/p>\n<p>The recent <a href=\"https:\/\/www.reuters.com\/technology\/cybersecurity\/location-tracking-company-unacast-tells-norway-its-data-was-hacked-broadcaster-2025-01-11\/\" target=\"_blank\" rel=\"nofollow noopener\">hack<\/a> of location data broker Gravy Analytics clearly illustrates the potential pitfalls of such practices. This post analyzes how data brokers operate, and what can happen if the information they collect leaks. We also give tips on what you can do to protect your location data.<\/p>\n<h2>What location data brokers are<\/h2>\n<p>Data brokers are companies that collect, process, and sell information about users. They get this information from mobile apps, online ad networks, online analytics systems, telecom operators, and a host of other sources from smart-home devices to <a href=\"https:\/\/www.kaspersky.com\/blog\/spies-on-wheels-how-carmakers-sell-your-intimate-data\/49341\/\" target=\"_blank\" rel=\"noopener nofollow\">cars<\/a>.<\/p>\n<p>In theory, this data is only collected for analytics and targeted advertising. In practice, however, there are often no restrictions on usage, and seemingly anyone can buy it. So, out there in the real world, your data can be used for pretty much any purpose. For example, an investigation last year revealed that commercial data brokers \u2014 directly or through intermediaries \u2014 may even serve <a href=\"https:\/\/www.kaspersky.com\/blog\/disable-rtb-ad-tracking-law-enforcement-spy-agencies\/51019\/\" target=\"_blank\" rel=\"noopener nofollow\">government intelligence agencies<\/a>.<\/p>\n<p>Data brokers collect all kinds of user information, of which one of the most important and sensitive categories is location data. It\u2019s so in demand, in fact, that besides more generalized data brokers, firms exist that focus on it specifically.<\/p>\n<p>Those are the location-data brokers \u2014 organizations that specialize in collecting and selling information about user location. One of the major players in this segment is U.S. location tracking firm Gravy Analytics, which <a href=\"https:\/\/www.prnewswire.com\/news-releases\/gravy-analytics-and-unacast-merge-to-become-leader-in-location-data-and-insights-302000184.html\" target=\"_blank\" rel=\"nofollow noopener\">merged<\/a> with Norway\u2019s Unacast in 2023.<\/p>\n<h2>The Gravy Analytics data leak<\/h2>\n<p>In January 2025, news broke of a data leak at Gravy Analytics. At first it was confined to <a href=\"https:\/\/techcrunch.com\/2025\/01\/13\/gravy-analytics-data-broker-breach-trove-of-location-data-threatens-privacy-millions\/\" target=\"_blank\" rel=\"nofollow noopener\">unofficial reports<\/a> based on a post that appeared on a private Russian-language hacker forum. The poster claimed to have hacked Gravy Analytics and stolen the location data of millions of users, providing screenshots of the data trove as proof.<\/p>\n<p>It wasn\u2019t long before <a href=\"https:\/\/www.nrk.no\/norge\/oppdaget-datainnbrudd-da-hackeren-tok-kontakt-1.17201694\" target=\"_blank\" rel=\"nofollow noopener\">official confirmation<\/a> came through. Under Norwegian law, Gravy Analytics\u2019 parent, Unacast, was legally required to notify the national regulator.<\/p>\n<p>The company\u2019s <a href=\"https:\/\/fido.nrk.no\/8a09133d2b14a7e72c31006ef2611b22fd78d7c6bfd7cc62f7d35f13b3c2d338\/Datatilsynet_Unacast_Security%20Incident%20Notification_Redacted.pdf\" target=\"_blank\" rel=\"nofollow noopener\">statement<\/a> reported that on January 4, an unauthorized individual gained access to Gravy Analytics\u2019 AWS cloud storage environment \u201cthrough a misappropriated access key\u201d. The intruder \u201cobtained certain files, which could contain personal data\u201d.<\/p>\n<h2>Analysis of the data Gravy Analytics leaked<\/h2>\n<p>Unacast and Gravy Analytics were in no hurry to specify what data could have been compromised. However, within a few days, an independent security researcher published their own in-depth <a href=\"https:\/\/x.com\/fs0c131y\/status\/1876975966334964076\" target=\"_blank\" rel=\"nofollow noopener\">analysis<\/a> of the leaked information based on a sample of the stolen data they\u2019d been able to obtain.<\/p>\n<div id=\"attachment_53058\" style=\"width: 3505px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2025\/02\/18165908\/geolocation-data-broker-leak-1-EN.jpg\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-53058\" class=\"size-full wp-image-53058\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2025\/02\/18165908\/geolocation-data-broker-leak-1-EN.jpg\" alt=\"User location-data leaked worldwide \" width=\"3495\" height=\"1946\"><\/a><p id=\"caption-attachment-53058\" class=\"wp-caption-text\">The Gravy Analytics leak included the location data of users worldwide. <a href=\"https:\/\/x.com\/fs0c131y\/status\/1876980558183407925\" target=\"_blank\" rel=\"nofollow noopener\">Source<\/a><\/p><\/div>\n<p>It turned out that the Gravy Analytics hack did indeed leak a gigantic set of location data of users worldwide \u2014 from Russia to the United States. The fragment analyzed by the researcher was 1.4GB in size, and consisted of around 30 million records \u2014 mostly collected in the first days of January 2025. Meanwhile, the hacker claimed the stolen database is 10TB, meaning it could potentially contain over 200 billion records!<\/p>\n<p>This data was collected by mobile apps and acquired by Gravy Analytics to be aggregated and subsequently sold to clients. As the analysis of the leak showed, the list of apps used to collect location data runs into the thousands. For example, the sample studied contained data collected from <a href=\"https:\/\/gist.github.com\/fs0c131y\/f498b21cba9ee23956fc7d7629262e9d\" target=\"_blank\" rel=\"nofollow noopener\">3455 Android apps<\/a> \u2014 including dating apps.<\/p>\n<div id=\"attachment_53057\" style=\"width: 3594px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2025\/02\/18165955\/geolocation-data-broker-leak-2.jpg\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-53057\" class=\"size-full wp-image-53057\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2025\/02\/18165955\/geolocation-data-broker-leak-2.jpg\" alt=\"UK-based Tinder users' location \" width=\"3584\" height=\"1990\"><\/a><p id=\"caption-attachment-53057\" class=\"wp-caption-text\">UK-based Tinder users\u2019 location data is an example of what can be found in the data leaked from Gravy Analytics. <a href=\"https:\/\/x.com\/fs0c131y\/status\/1876983147503513800\" target=\"_blank\" rel=\"nofollow noopener\">Source<\/a><\/p><\/div>\n<h2>Tracking and deanonymizing users with the Gravy Analytics\u2019 leak data<\/h2>\n<p>What\u2019s most unpleasant about the Gravy Analytics hack is that the leaked database is linked to advertising IDs: <a href=\"https:\/\/support.google.com\/authorizedbuyers\/answer\/3221407?hl=en\" target=\"_blank\" rel=\"nofollow noopener\">IDFA for iOS and AAID for Android<\/a> devices. In many cases, this makes it possible to track users\u2019 movements over time. Here, for instance, is a map of such movements in the vicinity of the White House in Washington, D.C. (remember that this visualization uses only a small sample of the stolen data; the full database contains a lot more):<\/p>\n<div id=\"attachment_53056\" style=\"width: 3594px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2025\/02\/18170039\/geolocation-data-broker-leak-3.jpg\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-53056\" class=\"size-full wp-image-53056\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2025\/02\/18170039\/geolocation-data-broker-leak-3.jpg\" alt=\"Tracking users through the Gravy Analytics leak \" width=\"3584\" height=\"1994\"><\/a><p id=\"caption-attachment-53056\" class=\"wp-caption-text\">Data in the Gravy Analytics leak linked to advertising IDs can be used to track users\u2019 movements over time. <a href=\"https:\/\/x.com\/fs0c131y\/status\/1877099954029703588\" target=\"_blank\" rel=\"nofollow noopener\">Source<\/a><\/p><\/div>\n<p>Worse yet, some data can be deanonymized. For example, the researcher was able to track the movements of a user who visited the Blue Origin launch pad:<\/p>\n<div id=\"attachment_53055\" style=\"width: 1484px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2025\/02\/18170111\/geolocation-data-broker-leak-4.jpg\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-53055\" class=\"size-full wp-image-53055\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2025\/02\/18170111\/geolocation-data-broker-leak-4.jpg\" alt=\"First example of user deanonymization through the Gravy Analytics leak \" width=\"1474\" height=\"1414\"><\/a><p id=\"caption-attachment-53055\" class=\"wp-caption-text\">An example of user deanonymization using location data leaked from Gravy Analytics. <a href=\"https:\/\/x.com\/fs0c131y\/status\/1877311309080940942\" target=\"_blank\" rel=\"nofollow noopener\">Source<\/a><\/p><\/div>\n<p>Another example: the researcher was able to track a user\u2019s movements from the Columbus Circle landmark in Manhattan, New York City, to his home in Tennessee, and then to his parents\u2019 house the next day. Based solely on OSINT data, the researcher learned a great deal about this individual, including their mother\u2019s name and the fact that their late father was a U.S. Air Force veteran.<\/p>\n<div id=\"attachment_53053\" style=\"width: 1482px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2025\/02\/18170129\/geolocation-data-broker-leak-5.jpg\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-53053\" class=\"size-full wp-image-53053\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2025\/02\/18170129\/geolocation-data-broker-leak-5.jpg\" alt=\"Second example of user deanonymization through the Gravy Analytics leak \" width=\"1472\" height=\"1522\"><\/a><p id=\"caption-attachment-53053\" class=\"wp-caption-text\">Another example of user deanonymization using location data leaked from Gravy Analytics. <a href=\"https:\/\/x.com\/fs0c131y\/status\/1877128999240962290\" target=\"_blank\" rel=\"nofollow noopener\">Source<\/a><\/p><\/div>\n<p>The Gravy Analytics data breach demonstrates the serious risks associated with the data broker industry, and location data brokers in particular. As a result of the hack, a huge volume of user location records collected by mobile apps spilled out into the public domain.<\/p>\n<p>This data makes it possible to track the movements of a great many people with fairly high accuracy. And even though the leaked database doesn\u2019t contain direct personal identifiers such as first and last names, ID numbers, addresses, or phone numbers, the linkage to advertising IDs can in many cases lead to deanonymization. So, based on various quasi-identifiers, it\u2019s possible to establish a user\u2019s identity, find out where they live and work, as well as trace their social connections.<\/p>\n<h2>How to protect your location data?<\/h2>\n<p>Unfortunately, collecting user location data is now such a widespread practice that there\u2019s no easy answer to this question. Alas, there\u2019s no switch you can simply flick to stop all the internet companies worldwide harvesting your data.<\/p>\n<p>That said, you can at least minimize the amount of information about your location that falls into the hands of data brokers. Here\u2019s how:<\/p>\n<ul>\n<li>Be strict with apps asking for access to location data. Often, they\u2019ll work just fine without it \u2014 so unless there\u2019s a compelling reason for the app to know your location, just say no.<\/li>\n<li>Carefully configure privacy in apps that <em>genuinely<\/em> need your geolocation to function. For example, see our <a href=\"https:\/\/www.kaspersky.com\/blog\/running-apps-privacy-settings-part1-common\/52403\/\" target=\"_blank\" rel=\"noopener nofollow\">guides to configuring all the most popular running apps<\/a>.<\/li>\n<li>Don\u2019t allow apps to track your location in the background. When granting permissions, always select the \u201cOnly while using the app\u201d option.<\/li>\n<li>Uninstall apps you no longer use. In general, try to keep the number of apps on your smartphone to a minimum \u2014 this will reduce the number of potential data collectors on your device.<\/li>\n<li>If you use Apple iOS, iPadOS, or tvOS devices, <a href=\"https:\/\/www.kaspersky.com\/blog\/apptracking-transparency-in-ios-ipados-tvos-14-5\/39690\/\" target=\"_blank\" rel=\"noopener nofollow\">opt out of app tracking<\/a>. This will prevent data collected on you from being deanonymized.<\/li>\n<li>If you use Android, <a href=\"https:\/\/support.google.com\/googleplay\/android-developer\/answer\/6048248?hl=en\" target=\"_blank\" rel=\"nofollow noopener\">delete your device\u2019s advertising ID<\/a>. If this option is unavailable in your OS version, reset the advertising ID regularly.<\/li>\n<li>Install a <a href=\"https:\/\/www.kaspersky.co.in\/premium?icid=in_bb2023-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kprem___\" target=\"_blank\" rel=\"noopener\">robust security solution<\/a>\u00a0capable of blocking ad-tracking on all your devices.<\/li>\n<\/ul>\n<p>For more tips on how to put the brakes on generalized data brokers collecting information on you, see our post <a href=\"https:\/\/www.kaspersky.com\/blog\/disable-rtb-ad-tracking-law-enforcement-spy-agencies\/51019\/\" target=\"_blank\" rel=\"noopener nofollow\"><strong>Advertisers sharing data about you with\u2026 intelligence agencies<\/strong><\/a>.<\/p>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"premium-geek\">\n","protected":false},"excerpt":{"rendered":"<p>The recent leak at major location-data broker, Gravy Analytics, shines a light on the implications of mass location-data collection.<\/p>\n","protected":false},"author":2726,"featured_media":28598,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1855,2196],"tags":[105,14,191,3442,260,2878,22,1219,1173,181,43,742,527,787],"class_list":{"0":"post-28596","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-privacy","8":"category-threats","9":"tag-android","10":"tag-apple","11":"tag-data","12":"tag-data-collection","13":"tag-data-protection","14":"tag-geolocation","15":"tag-google","16":"tag-ios","17":"tag-leaks","18":"tag-mobile-apps","19":"tag-privacy","20":"tag-surveillance","21":"tag-threats","22":"tag-tracking"},"hreflang":[{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/geolocation-data-broker-leak\/28596\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/geolocation-data-broker-leak\/23836\/"},{"hreflang":"ar","url":"https:\/\/me.kaspersky.com\/blog\/geolocation-data-broker-leak\/12373\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/geolocation-data-broker-leak\/28711\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/geolocation-data-broker-leak\/28053\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/geolocation-data-broker-leak\/30890\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/geolocation-data-broker-leak\/29591\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/geolocation-data-broker-leak\/39072\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/geolocation-data-broker-leak\/13278\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/geolocation-data-broker-leak\/53050\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/geolocation-data-broker-leak\/22720\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/geolocation-data-broker-leak\/23650\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/geolocation-data-broker-leak\/32083\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/geolocation-data-broker-leak\/28839\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/geolocation-data-broker-leak\/34663\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/geolocation-data-broker-leak\/34292\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.co.in\/blog\/tag\/privacy\/","name":"privacy"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/28596","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/users\/2726"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/comments?post=28596"}],"version-history":[{"count":2,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/28596\/revisions"}],"predecessor-version":[{"id":28599,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/28596\/revisions\/28599"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/media\/28598"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/media?parent=28596"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/categories?post=28596"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/tags?post=28596"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}