Is Datanyze Chrome Extension safe?
Datanyze is low risk. Clicking reveal on a matched profile prepares a POST to Datanyze's my-data service with the person's ID, company ID, a fixed source label, and profile URL from page data. The capture did not reach this flow, so no request body was recorded.…
Who publishes itZoomInfo Technologies Inc. - 3 other listings from the same operator, none carrying a finding
ZoomInfo Technologies Inc. - 3 other listings from the same operator, none carrying a finding
Same operator - 3 listings
Published under a different store account, but sharing the registered address, contact or declared legal entity this one gave the store.
Shared hosts - 1 hostname
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
Datanyze findings
Reveal button posts matched profile identifiers to Datanyze
Clicking reveal on a matched profile prepares a POST to Datanyze's my-data service with the person's ID, company ID, a fixed source label, and profile URL from page data.
The capture did not reach this flow, so no request body was recorded.
What actually happens
You click the reveal button for a matched person.
The button handler runs only when the reveal control is enabled and has not already been clicked.
The extension dispatches the matched person record together with profile data from the page.
A later service method maps those records into the POST body for Datanyze's reveal endpoint.
Fields the reveal service maps into the request
- Matched person IDpersonId: 41879231 (illustrative)
This identifies the person record you asked the extension to reveal.
- Matched company IDcompanyId: 872645 (illustrative)
This links the revealed person record to a company record.
- Request sourceEXTENSION
This marks the request as coming from the browser extension rather than another Datanyze surface.
- Social profile URLhttps://www.linkedin.com/in/jordan-rivera-312a87 (illustrative)
This ties the reveal request to the profile page associated with the matched person.
Captured request
No request body or response was recorded because the traffic capture did not reach the successful reveal flow.
The code that does this
The click handler and reveal service in shipped and deobfuscated code
Deobfuscated click handler and action dispatch
deobfuscated/987.jsfunction Zt(n, s) { if (1 & n) { const e = t.RV6(); t.j41(0, "div", 11)(1, "dn-primary-btn", 12), t.bIt("click", function() { t.eBV(e); const o = t.XpG(); return t.Njj(o.onRevealDetails()) }), t.k0s()() } if (2 & n) { const e = t.XpG(); t.R7$(), t.Y8G("text", e.primaryButtonText)("size", "medium")("disabled", e.isDisabled)("loading", e.loading) }}onRevealDetails() { this.isDisabled || this.isRevealButtonClicked || (this.isRevealButtonClicked = !0, this.loading = !0, this.sendEventToGa(N.Q), this.store.select(w.BH).pipe((0, x.s)(1)).subscribe(e => { this.store.dispatch((0, b.lx)({ payload: { matchedData: [this._personDetails], scrapedData: (0, l.A)(e, "organizedScrapedData") } })) }))}Deobfuscated mapping and POST
deobfuscated/main.jsconst e = { env: "production", production: !0, COOKIE_TOKEN: "dn-tk", COOKIE_VERIFICATION_ID: "dn-verification-id", DN_NOTI_COOKIE_TOKEN: "dn-noti", DEVICE_ID: "deviceId", MATCH_MS_URL: "https://api.datanyze.com/match", MY_DATA_MS_URL: "https://api.datanyze.com/my-data", PAYMENT_MS_URL: "https://api.datanyze.com/payment", WEBSITE_URL: "https://www.datanyze.com", IDENTITY_MS_URL: "https://api.datanyze.com/identity", USER_SETTINGS_MS_URL: "https://api.datanyze.com/user-settings", CONFIG_MS_URL: "https://api.datanyze.com/config", DIRECTORIES_SITE_URL: "https://www.datanyze.com/people", PLATFORM_SITE_URL: "https://app.datanyze.com", DIRECTORY_MS_URL: "https://api.datanyze.com/directory/person"}revealData(g) { const b = function Ut(o, S) { return o.map(g => ({ personId: (0, E.A)(g, "personId"), companyId: (0, E.A)(g, "companyId"), requestSource: ut.EXTENSION, ...S.find(lA => (0, E.A)(lA, "socialUrl") === (0, E.A)(g, "socialUrlId")) })) }((0, E.A)(g, "matchedData"), (0, E.A)(g, "scrapedData")); return this.httpClient.post(`${this.MY_DATA_ENDPOINT}/reveal-data`, b)}this.RevealMatchedPersonData$ = (0, D.EH)(() => this.actions$.pipe((0, D.gp)(IA.lx), (0, x.M)(() => this.nyzeService.update(wA.BT)), (0, eA.Z)(rA => this.myDataService.revealData(rA.payload).pipe((0, s.T)(sA => { const [UA] = sA || [], et = ot(UA); return this.sendEventToGa(Et, UA.personId || et.personId), (0, IA.kw)({ payload: [et] })}), (0, U.W)(sA => (0, MA.of)((0, IA.Nj)(sA)))))))Destination reached by the reveal flow
- api.datanyze.com
Datanyze API host that receives the reveal-data POST constructed by the extension.
Datanyze extension sends client ID, user ID and page paths to Google Analytics
Code analysis shows analytics events carrying a client ID, a user ID and page paths are sent to google-analytics.com when consent allows.
Dynamic analysis did not observe the request.
What actually happens
You use the extension and move between its views.
It sends an analytics event with your IDs and page path to Google Analytics.
Fields in the analytics payload
- Client ID1623987412.1731402290
A persistent ID that links your events together over time.
- User IDu_58213907
An account-level ID that ties events to your user record.
- Page addresshttps://prod.extension.datanyze.com/home
The extension page path you are viewing, on the vendor host.
- Extension version6.8.14
Which version of the extension you run.
The code that does this
Consent gate and payload build in the analytics service
if (analyticsAllowed(isGDPR, hasCookieConsent)) { const pagePath = router.snapshot.url; const dl = GOOGLE_ANALYTICS.host_url + pagePath; const hit = new GaHit(v, ga_key, 'MP', clientId, clientId, userId, userId, ...); sendHttpToGa(hit);}// allowed when non-GDPR and consent is not 'false', or GDPR and consent is 'true'Where the events go
- www.google-analytics.com
Google Analytics collection endpoint; receives the event payload.
- prod.extension.datanyze.com
Vendor host used as the page host in the reported address; not contacted for this.
Observation
Static analysis finding. This behaviour was identified by reading the shipped extension code and has not yet been reproduced in a live run. The trigger conditions and the exact data sent are read from the code, not from an observed capture.
Datanyze version history
6.8.12
Mar 4, 2026
6.8.13
Apr 11, 2026
6.8.14
Jun 1, 2026
Chrome Web Store listing
- Versions
- 6.8.14 latest of 3 seen since March 4, 2026
- Store rating
- 3.7 from 238 ratings
- Last updated
- May 17, 2026
- Size
- 1.31 MiB
- Privacy policy
- www.datanyze.com
