Privacy and browser permissions

Last updated: October 18, 2026.

Rifty is a browser and frontend debugging tool. It has no developer-operated telemetry or hosted backend, and it does not bundle browsing data. Its extension and MCP server run locally. It communicates with the local MCP Bridge, local Whistle, and destinations chosen by the user through debugging actions. Agent clients decide what they do with tool results, including whether to send them to a remote AI provider; those results may contain page content or network data. Local execution does not mean data can never leave the device.

Permissions

tabs: select and navigate browser tabs and show their titles/URLs.
debugger: inspect DOM/page state, capture screenshots and input, observe network/Console events, and override requests.
scripting: run packaged request helpers in a user-selected tab for page-context HTTP requests. Arbitrary user/agent-requested JavaScript uses the debugger API in the selected page's MAIN or isolated world.
webRequest: observe HTTP(S) request lifecycle metadata for debugging traces, including URL, method, status, timing and redirects.
storage: save request rules, presets and desired proxy configuration in extension-local storage.
declarativeNetRequestWithHostAccess: persistent browser-wide header modifications and resource redirects under the existing HTTP(S) host permissions.
declarativeNetRequestFeedback: unpacked-build-only match diagnostics; omitted from the store upload. Sanitized URL paths and bounded counters are stored in session storage when this capability is available. Store builds do not promise this debug-only event stream.
proxy: explicitly configure/release a proxy for the regular browser profile.
sidePanel: open a compact workspace alongside a page.
alarms: reconnect the extension to the local agent Bridge when its service worker wakes.
HTTP/HTTPS host access: operate on developer-selected web pages. Protected browser pages are not supported.

No content script is installed on every page. A packaged layout helper runs on loopback pages (localhost, 127.0.0.1, and [::1]) to support the embedded local Whistle interface. Page evaluation happens through an explicitly selected debugger target. Tab overrides intercept attached tabs. Header profiles and resource mappings apply browser-wide without Attach; proxies affect the regular profile.

Stored and returned data

Rules, header values, resource mappings, mock bodies, presets and proxy addresses persist locally. Recordings and Console messages are bounded in-memory buffers. Screenshots are returned on demand. Explicit HAR/preset exports are local downloads. Header profiles and resource mappings persist as Chrome dynamic rules. Whistle requests go only to the configured loopback management origin, omit credentials and reject redirects; selected files affect other clients of that Whistle instance.

Network/Console results redact common password, token, cookie and authorization fields by default. Redaction is best effort and does not recognize every possible secret or personal field. includeSensitive requests raw fields for a specific investigation. Page snapshots, screenshots and arbitrary script results can also contain private information; review them before sharing.

Rifty may therefore handle website content, browsing activity, identifiers and authentication data that appear in the pages or requests being debugged. HTTP replay may send cookies or credentials according to the selected request context and options. Header rules, redirects and proxy configuration may change where subsequent browser requests are sent. Use these capabilities only with destinations and agents you trust.

Presets deliberately include user-supplied configuration values. Review headers, URL parameters and mock bodies before exporting or applying an imported preset. Import is separate from activation.

MCP tools can control pages and browser-wide proxy settings. Use trusted local agent clients. The Bridge is bound to loopback, and local IPC separates response routing between sessions. Browser state itself remains shared.

The WebSocket endpoint accepts the packaged extension's origin and checks its identity/protocol greeting. IPC peers authenticate with a per-user local secret; on Unix the runtime directory and token use owner-only permissions. These checks do not defend against an already-compromised local user account. Multiple Chrome profiles using the same extension share one endpoint; the most recently connected profile takes over the extension connection. Use one profile per Bridge.

Sharing and retention

Rifty does not sell data or use it for advertising, analytics, creditworthiness or data brokerage. Data is used to perform the debugging actions requested by the user and their selected agent. Tool results delivered to an agent are subject to that client's and its AI provider's data practices. User-selected sites, proxies and local Whistle instances may also receive data as part of those actions.

Uninstalling the extension removes its extension-local configuration. Stop recording and detach debugging targets to end collection; closing or restarting the extension service worker clears its in-memory buffers. Exported files and copies retained by agent clients, AI providers, destination services or Whistle are separate and must be deleted through those systems. Removing the browser extension does not delete those copies or uninstall the separately installed Agent package.

Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Publisher and contact

Website: sgnilo.cn

Support and privacy inquiries: xujiangpingnilo@gmail.com

These public contact details are shared with the publisher’s TabMind extension. Rifty has its own data practices as described above.