Privacy Policy

What Infuse does

Infuse lets you edit web pages in your browser using CSS, JavaScript, text replacements, XPath rules, and a DOM preview. You pair the extension with the editor using a code. Saved rules can continue running on matching pages after the editor is disconnected.

Information handled by Infuse

• Pages and tabs: open-page URLs, titles, favicons, tab identifiers, and navigation or availability changes used to display and select pages in the paired editor.
• Your edits: CSS, JavaScript, replacement text, XPath paths, element selections, colors, clone settings, and website-matching rules that you create or save.
• Page content: text, HTML, links, image and stylesheet references, element attributes, and current form-field values read for inspection and DOM previews. A preview can contain the whole page, not just the highlighted element.
• Feature interactions: element-picker pointer movements and clicks are processed to highlight and select elements. Selected-element information is sent to the editor.
• Connection information: pairing codes, client identifiers when provided, connection status, and messages needed to route commands and responses.
• Support messages: if you email the publisher, the information you choose to send is used to respond to your request.

How information is used

Information is used to provide Infuse's page-editing features, save and restore your rules, maintain connections, and support the service. The publisher does not sell user data, use it for advertising or profiling, or use it to determine creditworthiness or for lending.

Infuse's handling of data obtained through browser permissions is limited to its disclosed functionality and support. Data is not used or transferred for unrelated purposes. The extension and editor do not include advertising or third-party analytics SDKs. Support access to page content should be limited to information you specifically choose to share for your support request.

Transmission and service providers

The public editor and extension communicate over HTTPS and WSS through a Cloudflare-hosted relay. Editing messages, page information, and preview content pass through that relay to the paired client. Transport is encrypted, but this is not end-to-end encryption: the relay processes message contents. Protect your pairing code and connect only to an editor you trust.

Cloudflare provides hosting, connection routing, and Durable Object storage for queued messages. It also processes technical request information, such as IP addresses and connection metadata, to deliver and protect its services. Its handling of service-provider information is described in Cloudflare's Privacy Policy.

DOM previews may load images, stylesheets, fonts, or other resources from the original website or its providers. Those providers receive the resulting resource requests. JavaScript that you choose to run can make additional network requests; review your scripts before using them.

Storage and retention

• Extension: rules, edits, preferences, and pairing state are saved in the browser's local extension storage.
• Editor: drafts and workspace state use local storage; saved DOM previews use IndexedDB in the browser where you open the editor.
• Relay: active connections are maintained for pairing. If a peer is offline, messages can be persisted in Cloudflare Durable Object storage until delivered. The relay clears its queues when both registered peers are removed from the room. There is no fixed time-based expiry in the current queue implementation.
• Support and infrastructure: support correspondence is retained as needed to handle the request. Infrastructure metadata retention depends on the hosting provider and service configuration; it is separate from Infuse's message queues.

Your controls and deletion

Disconnect stops the live editor connection; it does not delete saved rules, scripts, drafts, or previews. Disable or delete rules while connected to stop their saved effects. Disabling a rule does not delete its configuration.

To remove local editor drafts and previews, clear site data for the editor in that browser. To remove extension storage, use the browser's extension-removal controls. These are separate stores; clearing one does not clear the other. User-created scripts can have effects outside Infuse's stored rules that require separate cleanup.

For privacy questions, access or deletion requests relating to information held by the publisher, contact asf.eagle0304@gmail.com. Do not include passwords, pairing codes, or unnecessary sensitive page content in your message. Requests are handled as applicable to the information retained and the relevant legal requirements.

Changes to this policy

This page will be updated when Infuse's data practices change. The date above identifies the latest revision.