Is Transkriptor: Transcribe Audio to Text safe?
Transkriptor posts meeting links and stored account identifiers to its AWS API after users ask it to add a meeting bot.
On Google Meet, Microsoft Teams, and Zoom pages, the extension offers to add a Transkriptor meeting assistant. After the user confirms, it sends the meeting URL, selected language, stored user ID, and email address to Transkriptor's AWS API endpoint.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
What it can do
Permissions this extension asks for, as declared in version 2.0. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Read and change your data on app.transkriptor.com
https://app.transkriptor.com/*
Read and change your data on transkriptor.com
https://transkriptor.com/*
Read and change your data on dashboard.transkriptor.com
https://dashboard.transkriptor.com/*
Act on the current tab, but only after you click the extension
activeTab
Run its own code inside the pages you visit
scripting
Store data in your browser
storage
Where it sends data
Destinations our analysis observed Transkriptor: Transcribe Audio to Text 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.
- 9367iu6ljh.execute-api.eu-central-1.amazonaws.com
Transkriptor: Transcribe Audio to Text sends data to 9367iu6ljh.execute-api.eu-central-1.amazonaws.com. No other extension we have analysed sends data here.