Keyboard Layout Detector Privacy and Data Use

Last updated: 2026-03-15

Short answer

Why correction and feedback are necessary

Data flows in this project

1) Keyboard fixing (content script)

  • Runs on-page to detect/convert words in focused inputs.
  • Uses local dictionary files bundled inside the extension.
  • No network request is made for normal fixes.

2) Popup feedback

  • Sends only after you click Send to improve dictionary accuracy and fix bugs.
  • Default payload is privacy-safe and minimal.
  • You stay in control: no send happens unless you submit to improve dictionary accuracy and fix bugs.

3) In-page wrong-word report

  • When you report a wrong conversion, the pair wrong -> correct is submitted to improve dictionary accuracy and fix conversion bugs.
  • This report is also sent to Google Forms to improve dictionary quality and fix bugs faster.

4) Local storage

  • Pause setting: chrome.storage.sync.pauseExtension
  • Last shortcut used: chrome.storage.local.kldLastShortcut
  • Feedback draft text/type: localStorage.kld-feedback-draft-v1

Exactly what popup feedback can include

Always included (minimal mode):

Nothing extra is collected in feedback mode. Minimal mode is always on.

What is not collected automatically

Important: if you type sensitive information into the feedback message yourself, that text will be submitted (only after you click Send) to help troubleshoot and fix your reported issue.

Permissions and why they exist

Where data is sent

Only send information you are comfortable sharing.

You stay in control: if you do not submit, nothing leaves your browser. If you do submit, it is only to improve dictionary accuracy and fix bugs.

Your controls