Privacy Policy — McFiddles Browser Relay

Extension: McFiddles Browser Relay (Chrome extension, id oklbkdfgjgjajfpdpbkdgnnoebndcfgf)
Last updated: 2026-10-16


What this extension is

McFiddles Browser Relay connects your Chrome browser to your McFiddles platform so that one of your own McFiddles agents can operate the browser on your behalf — but only when you explicitly grant control, only for the duration you choose, only on the sites you allow, and only until you stop it. The extension runs on your machine and acts as the authoritative local enforcer of what an agent is allowed to do: the remote platform is advisory, and this extension has the final say on every action.

This extension is intended for McFiddles operators and their teams. Using it requires a McFiddles platform account with the browser-relay capability enabled for your tenant.

What data the extension accesses

When — and only when — you grant an agent control of a tab, the extension may access the following, scoped to that tab and that grant:

Microphone — only while you turn voice on

The side panel can let you talk to the agent (voice). Chrome microphone permission is required; if Chrome cannot show its prompt in the panel, Allow microphone in a tab opens a permission page. You can refuse, and typing keeps working.

The extension does not access, and the agent can never reach through it:

Secrets are scrubbed before they leave your browser

Before any extracted visible text is sent anywhere, the extension redacts true secrets in-page — authentication tokens, API keys, JWTs, auth headers, and credit-card / SSN-shaped values are replaced with [REDACTED] so they never leave your browser.

Authentication data

What is stored locally vs. sent to the platform

Stored locally in your browser (chrome.storage, IndexedDB), never sold or shared with third parties:

Sent to your McFiddles platform (the platform you signed in to, under your account) to provide the single advertised function:

The extension does not send your data to any party other than the McFiddles platform you connect it to.

Audit logging — metadata only

Your McFiddles platform keeps an immutable, per-tenant audit trail of relay activity. By design it records metadata only — never payloads:

Recorded Never recorded
event type, action/method, outcome, block reason typed text / keystrokes
origin (host only) full URLs (only a one-way url_sha256 hash)
a hash of the URL, not the URL itself cookies, auth tokens, session state
agent/device/session identifiers, sequence number request/response bodies
method profile, action size in bytes (not its content) page content / DOM

This boundary is enforced structurally: the audit writer rejects any field that looks like a raw payload. The log records that an action happened and where (which host) — it is not a place where your content or secrets accumulate.

Retention

How we use the data

Solely to provide the extension's single function — letting your agent operate your browser under your control, and giving you an auditable record of what it did. We do not:

Your control

Children

This extension is a professional tool for McFiddles operators and is not directed to children.

Changes to this policy

If this policy changes, we will update the version date above and the hosted copy. Material changes will be reflected in the extension's listing.

Contact

Questions about this policy or your data: gcp-developers@mcfiddles.ai (mcfiddles inc.). The McFiddles platform's own privacy policy is at mcfiddles.ai/privacy.