Is THYNK - Optimizing Your Claims Revenue. safe?
THYNK reads healthcare claim fields from the active tab on click and sends them to its Santechture backend.
When the user clicks within the side panel, the extension reads claim fields (payer, diagnosis and procedure codes, form inputs) from the active page using XPath rules fetched from its own server. The collected values are posted with a bearer token to the vendor's validation API. It has no content scripts or host permissions and relies on activeTab, so it only acts on user action.
Who publishes itSANTECHTURE DMCC - no other listings under this identity, 1 shared hostname
SANTECHTURE DMCC - 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 THYNK - Optimizing Your Claims Revenue. 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.
- thynk-api.santechture.com
THYNK - Optimizing Your Claims Revenue. sends data to thynk-api.santechture.com. No other extension we have analysed sends data here.