Privacy policy — Reply Refactor

Reply Refactor is a Google Chrome extension developed by SKYL4R S.R.L., Via XX Settembre 40, 00187 Roma (RM), Italy, VAT IT18639911009. Contact: [email protected] · certified email: [email protected].

Reply Refactor does not collect, transmit or sell personal data. Speech recognition and text rewriting run entirely on your device. We have no servers receiving your audio or text, no account is needed, and there are no analytics or ads.

When you start dictation, the extension uses the microphone to transcribe what you say with a speech recognition model (Whisper) running in the browser. Audio is processed in memory and discarded right after transcription: it is never stored or sent to us or anyone else. The microphone is only on while dictation is running, shown by the red bubble and the "REC" badge on the icon.

Dictated text is inserted into the field where your cursor is. When you use "Rewrite", the selected text (or the field's content) is rewritten by a language model running in the browser. Text never leaves your device and is not kept by the extension. What you type into websites is then subject to those websites' own policies.

• Settings (language, tone, punctuation, engine) in Chrome's local storage.
• The list of sites where you turned the bubble on (names only, e.g. "mail.google.com"), in local storage: it is not synced to your account.
• The bubble's position on screen.
• The downloaded AI models, in the extension's private storage (Origin Private File System).

Uninstalling the extension removes all of the above.

The only external connection is downloading the models from Hugging Face (huggingface.co and its delivery servers), on first setup or when you pick a different model: about 0.6–3 GB depending on the models, once. As with any download, Hugging Face receives the request's technical information (such as the IP address); the extension sends no audio, text or other personal data. Site icons in the popup come from Chrome's local cache, with no external request.

• Site access: none at install. Chrome asks site by site, only when you turn the extension on for that subdomain. Turning the bubble off only hides it; to give the permission back to Chrome, use “Remove” in the extension's Options, or Chrome's settings.
• Active tab: when you use the shortcut or the popup, the extension can act on the current tab, only at that moment.
• Storage, offscreen document, scripting, site icons: needed for the features described above.

The extension is not specifically aimed at children and collects no one's data.

If this policy changes, the updated version is published at this address with the new date.