Extension privacy.

What this policy covers

This policy covers the TypeLilt Background Typing Bridge browser extension. The extension connects the separately installed TypeLilt desktop app to a browser editor you select.

The desktop app’s licensing, trial, activation, payment, updates, draft storage, and other app features are outside this extension-only policy. Applicable desktop-app and purchase policies are separate. Websites where you type, including Google Docs, also have their own privacy practices.

How the extension works

The extension keeps an editing session attached to a selected tab, frame, editor, and insertion position. It receives individual characters and correction commands from the desktop app, applies them to that destination, and returns success or error acknowledgements. The app must be installed and have an active trial or license.

Content scripts run on browser-accessible pages and frames so the extension can remember the recently focused supported editor. They observe local focus and selection-related events and keep editor and caret references in memory. Actual capture and insertion are requested by the desktop app.

Information handled on your computer

The extension handles the information needed to connect the app and the selected editor:

• Editor references, editable-field values when needed for local replacement, caret or selection positions, and editor type.
• Tab and frame identifiers, destination titles and URLs used to find and validate the selected page, and capture, focus, and selection timestamps.
• Characters and correction commands supplied by the desktop app, insertion sequence numbers, and temporary acknowledgement and error information.
• Browser name, browser user agent, extension version, local connection status, and keepalive timestamps.

Google Docs

Google Docs support uses the browser’s debugger API on the captured tab. It checks the document’s own caret and compares a limited number of nearby rendered canvas tiles to confirm an edit occurred. This temporary rendered content stays inside the captured document for comparison. Those canvas images are not sent to the desktop app or a remote service. The browser may show an attachment notice while the session is active.

The extension does not monitor a system-wide keyboard stream or send operating-system mouse or keyboard events. It does not read password-input values. Text you choose to type can contain personal or sensitive information, and other webpage content may be sensitive. Use a destination you trust.

Where information goes

The extension’s only server connection is the local WebSocket at ws://127.0.0.1:38471/flowtype, on the same computer. It sends connection details, capture metadata such as destination title and editor type, and acknowledgements, status, and errors to the installed TypeLilt app. The app sends the characters to insert and the commands to capture or release a session.

The extension has no remote TypeLilt server endpoint, analytics service, advertising SDK, or third-party data broker integration. It does not upload browsing history or document text to a TypeLilt cloud service. The separate desktop app may contact its own licensing or update services under its own policy.

All executable extension logic ships in the extension package. The extension does not fetch executable code from a remote server.

The website you choose

When text is inserted into a website editor, that website can receive, save, or sync it in the normal operation of the page. For example, a Google Docs document may sync to Google. This is governed by that service’s terms and privacy policy.

TypeLilt does not use this extension to sell user data, target advertisements, or determine creditworthiness or lending eligibility. Information handled by the extension is used to provide its browser-typing function.

Storage and retention

Captured editor references, selection and range state, insertion history, and acknowledgement caches are held in browser memory. Small capture metadata records are kept in chrome.storage.session so the background worker can find its active destination. This is temporary browser-session storage. The extension does not use Chrome sync storage or a persistent local data store.

Releasing a capture removes its associated session metadata and editing state. Google Docs attachment state is also released on navigation, capture failure, or local connection loss. Tab or document closure removes the corresponding in-page state.

Some in-memory caches or session metadata may remain until cleared by the extension or until the browser session ends. Candidate snapshots are short-lived and are pruned when the extension next examines candidates. Every local record is not necessarily erased immediately when a desktop connection closes.

The extension does not retain the desktop app’s license key, payment details, or hardware identity. It does not manage the separate desktop app’s saved drafts, activation receipt, or settings.

Your choices

You choose the destination editor before starting a session. The desktop app provides pause, resume, and reset controls. The browser’s extension controls let you disable or remove the extension and control its permitted site access. Restricting site access can prevent capture on those pages. Access to file URLs requires the browser’s separate file-access setting.

You can cancel a Google Docs debugger attachment using the browser’s attachment notice, which ends that capture. Close the browser session or remove the extension to clear its browser-managed session storage.

Copies of text already entered into a website must be managed using that website’s controls. Data saved by the separate desktop app must be managed in that app.

Changes and contact

TypeLilt will update this policy if the extension’s information handling changes. The effective date appears at the top of this page.

For questions about this extension or its privacy practices, email support@typelilt.com.