Is Peek - Design & Asset Toolkit safe?
Peek - Design & Asset Toolkit sends active tab URLs and persistent analytics IDs to peek-extension-proxy.netlify.app when enabled.
When analytics is enabled, the extension reads the active tab's domain and full URL during popup and content-script flows and includes them in analytics events. It also stores or reuses analytics client and session identifiers and sends them with browser and platform details to Peek's Netlify analytics proxy.
Who publishes itKhalid Hasan Zibon - no other listings under this identity, 1 shared hostname
Khalid Hasan Zibon - no other listings under this identity, 1 shared hostname
What this publisher told the store about itself, and the other listings that told it the same thing.
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.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
Where it sends data
Destinations our analysis observed Peek - Design & Asset Toolkit contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- peek-extension-proxy.netlify.app
Peek - Design & Asset Toolkit sends data to peek-extension-proxy.netlify.app. No other extension we have analysed sends data here.