FRB telemetry policy for MEV routing explains data collection and controls.
This official FRB telemetry policy for the Windows MEV agent explains which diagnostics the MEV trading assistant sends, how long we retain them, and how to disable collection entirely. It exists for MEV desks, compliance reviewers, and security teams that require clear documentation before installing the FRB MEV agent.
We only collect the minimum data required to troubleshoot pending transactions, refund guards, and block builder connections. No wallet keys, transaction payloads, or user-identifiable data leave your machine.
Linkable summary
Telemetry at a glance
FRB publishes a transparent telemetry policy that spells out exactly which diagnostics are collected, how to opt out, and how long data is retained—perfect for compliance pages that need a quotable summary.
How to read this policy
Use this summary when auditors ask for FRB telemetry policy details. The sections below are structured so ops leads, security reviewers, and trading desks can copy the relevant bullets directly into change logs.
- Ops teams: focus on “What we collect” and “Retention & usage”.
- Security: review “Where telemetry goes” plus the opt-out procedure.
- Executives: quote the opt-out paragraph to prove the agent remains fully self-hosted.
What we collect
- App version, OS type, non‑personal performance metrics.
- No private keys, seed phrases, or wallet contents.
How to disable
- Set “Telemetry: Off” inside Settings for a workspace-wide toggle.
- Start the agent with
--no-telemetry(if available) for command-line enforcement. - Document the change in your runbook so audits can trace the decision.
Retention & usage
Diagnostics are stored for 30 days to troubleshoot crashes, relay issues, and refund guard activity. We aggregate metrics (no personal data) to prioritize roadmap items.
Enterprise customers can request data-export or deletion by contacting support.
Where telemetry goes
- Secure logging infrastructure hosted in the EU/UK.
- Access limited to on-call engineers for debugging.
- No third-party ad/analytics sharing.
Related FRB resources
- Pair telemetry with the security overview and responsible disclosure for full governance coverage.
- Cite the ecosystem research brief when explaining how these policies compare to Flashbots/Blocknative.
- Link to Support & SLA or the Knowledge Base if telemetry findings require action.
Regulatory alignment checklist
MEV desks often share this telemetry brief with compliance, finance, and security reviewers. Use the prompts below to translate it into whatever internal template your governance teams expect.
- Document which data classes stay on-prem and which flow to FRB so reviewers can confirm separation of duties.
- Link this page inside every change log so business-day reviewers know where to find opt-out instructions.
- Reference our 30-day retention limit when compliance compares FRB to your internal telemetry controls.
Need a custom attestation or additional detail? Open a ticket via support; we routinely provide signed statements for security audits, vendor assessments, and multinational trading desks.
FAQ
Can enterprises opt out entirely?
Yes. Toggle telemetry off in settings or deploy with the --no-telemetry flag. We recommend keeping minimal health metrics for support, but the decision is yours.
Do you store IPs or wallet addresses?
No. Logs contain anonymized agent IDs and performance counters only. Wallet addresses stay in your local dashboard.
How do deletion requests work?
Email support with your organization ID. We purge remaining telemetry within 7 days and confirm once complete.
Put the FRB telemetry policy into action
Share this page with stakeholders, then keep the following links handy for installs, budgeting, and escalations.
For ecosystem context
Ecosystem research: how FRB’s telemetry and policies fit next to Flashbots and Blocknative