Menu

Privacy and security

Wireflip is designed to keep request-debugging data on your device.

Data handling

  • Rules and settings are stored in local browser extension storage.
  • Traffic inspector logs are held in memory and disappear when the service worker stops.
  • Request URLs, headers, bodies, rules, and logs are not uploaded to Wireflip servers.
  • Sensitive header values—including Authorization, Cookie, Proxy-Authorization, and Set-Cookie—are redacted in the inspector by default.
  • The website does not need an account to use the extension or SDK.

Local processing includes matching tabs’ URLs and origins, request URLs, methods, resource types, status codes, timing, request/response headers and rule matches. The inspector uses these details to show the traffic in a session you explicitly start. Authentication headers may be handled while applying your rules; their values are masked before being added to inspector logs. Custom headers, URLs and mock bodies you enter are stored as part of your local rules. URLs and custom values can themselves contain sensitive information, so review them before exporting a backup or sharing a screenshot.

This local processing supports only the request debugging features described in the extension. Wireflip does not sell or transfer this data to third parties, use it for advertising or unrelated purposes, or use it to determine creditworthiness. The developer does not receive or read your traffic or rules. Wireflip’s use of data follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

Permissions

<all_urls> allows rules to target developer-selected endpoints and lets the local SDK bridge identify the real calling page. declarativeNetRequest applies browser-managed rules. Chrome’s debugger permission supports enabled saved Mock, delay and CORS rules, optional request recording and temporary tab controls. tabs, storage, and sidePanel provide tab scope, persistence, and the inspector.

Keep rules narrowly scoped. Disable a saved rule or its group to stop its changes; stopping request recording does not stop enabled saved rules. Rules, exact-origin website trust choices and recent completed website operations remain in local extension storage.

Saved rules and recording

In Wireflip 2.1, enabling a saved rule or approving a website-owned rule lets it run automatically on matching supported pages, including new matching tabs. Previously enabled 2.0 Mock, delay and CORS rules may therefore start running after the update without starting a tab recording session. Chrome may show its native debugging indicator while a rule, recording or temporary control requires debugger access. Page preparation is asynchronous; requests sent before readiness may pass through.

Recording is separate and starts explicitly. Stopping recording clears temporary changes but keeps enabled saved rules running. Disable the rule or its group to stop its changes. Chrome’s native Stop pauses execution until an explicit Retry; retrying rules does not start recording. Closing a tab releases its attachment, and navigation reconciles rules for the new page origin. An actual debugger takeover ends that attachment; opening DevTools can coexist on browser versions that support it.

SDK boundary

The new wireflip SDK communicates through a packaged content-script bridge. The retained cors-unlocker SDK uses its original iframe on cors.forth.ink; that bridge exchanges messages locally between the calling page and extension and does not upload request logs. The extension derives scope from the actual calling page instead of trusting an arbitrary origin supplied by page JavaScript.

Website changes require approval in a Wireflip-owned window unless the user has manually trusted that exact origin in the popup. Credential access still requires confirmation. Trust applies only to the site’s own rules; websites cannot manage manual, older unowned or other-origin rules. Revoking trust restores prompts without changing saved rules. Drafts are disabled for review; a website may request an enabled rule after approval. SDK calls are size- and rate-limited. The legacy hosted bridge retains its existing page confirmation in addition to the extension’s authorization boundary.

v1 migration

The first v2 startup creates a local snapshot of v1 settings before writing the validated v2 state. The snapshot is retained for recovery; it is not used as live configuration after migration.

Reporting an issue

Please report privacy or security concerns through the GitHub repository. Do not include real authorization headers, cookies, or private request bodies in a public issue.