Is Arabic and English on screen Keyboard safe?

Clean risk

Arabic and English Keyboard sends Teshkeel text from its popup to Farasa's diacritization API.

When you click the Teshkeel button, the extension reads the text currently in its popup text box and posts it to Farasa's diacritization API. The request includes the typed text and a hardcoded API key, and the API response replaces the text in the popup.

myextensionshelp@gmail.comv2.1Chrome Web Store
0Risk
Who publishes it

myextensionshelp@gmail.com - 1 other listing 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.

Publisher
myextensionshelp@gmail.com

Same store account

1 other listing published from this account, 6k+ users between them, none of them carrying a finding.

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.1. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.

  • Act on the current tab, but only after you click the extension

    activeTab

  • Store data in your browser

    storage

Where it sends data

Destinations our analysis observed On screen Keyboard 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.

  • farasa.qcri.org

    On screen Keyboard sends data to farasa.qcri.org. No other extension we have analysed sends data here.

Updated 30 September 2026poliiaaleefmikecbodonbdnlbbolcna