Is Dictation for Gmail safe?

Clean risk

Dictation for Gmail sends Gmail draft IDs with persistent analytics client IDs when dictation controls are used.

When you use the dictation controls in Gmail, the extension posts analytics events for dictation start, dictation end, and language selection. Those events include a persistent client ID, a session ID, and the current Gmail draft ID when one is present; the reviewed code does not show email body text, recipients, cookies, or dictated text being sent to this endpoint.

Greg Sadetskyv1.0.14Chrome Web Store
0Risk
Who publishes it

Greg Sadetsky - no other listings under this identity

What this publisher told the store about itself, and the other listings that told it the same thing.

Publisher
Greg Sadetsky
Registered address
244 5th Ave Suite G212, New York, NY 10001-7604, US
Registered contact
Gregory Sadetsky

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 1.0.14. 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 mail.google.com

    *://mail.google.com/*

  • Run its own code inside the pages you visit

    scripting

  • Store data in your browser

    storage

Where it sends data

Destinations our analysis observed Dictation 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.

  • analytics.dictation.tools

    Dictation sends data to analytics.dictation.tools. No other extension we have analysed sends data here.

Updated 30 September 2026eggdmhdpffgikgakkfojgiledkekfdce