Is Ziplyne JH Staging Player safe?
Ziplyne JH Staging Player reports per-step walkthrough analytics, including an internal user ID, to its configured Ziplyne backend.
This is a digital-adoption-platform extension that injects a guided walkthrough player into every page so a configured tenant (here, a Johns Hopkins Medicine staging deployment) can build on-screen tutorials over third-party or internal web apps. When a walkthrough is played, completed, or abandoned, it sends the internal user_id, company_id, usergroup_id, the current page's URL/host/path, and per-step timing data to the tenant's Ziplyne API host. This only fires while a walkthrough configured by the tenant is actively running, not on every page visit.
Who publishes itZiplyne - 27 other listings from the same operator, none carrying a finding
Ziplyne - 27 other listings from the same operator, none carrying a finding
What this publisher told the store about itself, and the other listings that told it the same thing.
Same store account
19 other listings published from this account, 64k+ users between them, none of them carrying a finding.
Same operator - 8 listings
Published under a different store account, but sharing the registered address, contact or declared legal entity this one gave the store.
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 Ziplyne JH Staging Player 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.
- Ziplyne tenant API (*.ziplyne.com or *.hosts.jhmi.edu, depending on environment)
Ziplyne JH Staging Player sends data to Ziplyne tenant API (*.ziplyne.com or *.hosts.jhmi.edu, depending on environment). Named as a recipient in this extension's own analysis.