Overview

FRB is built for traders and infrastructure operators who need transparency around how their data is handled. This Privacy Policy explains what information we collect across ai-frb.com, the installer, and connected services, how we use it to deliver reliable MEV execution, and what controls you have. We favor data minimization—FRB never asks for private keys, seed phrases, or custody of customer funds.

We periodically review these guidelines to reflect new features or regulatory requirements. The current effective date is 2025-09-19, and material updates will be highlighted in-product and via release notes.

What this privacy policy covers

This policy applies to the FRB website, documentation, desktop installer, relay integrations, and any telemetry or diagnostics pipelines we control. It does not cover third-party wallets, block explorers, or infrastructure providers you may pair with FRB. Those services have their own privacy terms, and we encourage you to review them carefully.

If FRB links to partner services, the link is provided for convenience only. We do not grant partners access to FRB user data unless you explicitly authorize a data share in writing or through a documented API integration.

Data we collect

We only gather the minimum information required to keep FRB secure, performant, and compliant. The categories below summarize what may be collected depending on your interaction with the platform.

Usage analytics

We log anonymized page views, feature toggles, and high-level workflow events. This telemetry helps us understand which relay integrations are most popular, whether documentation is discoverable, and where traders abandon a flow. Identifiers are rotated regularly and do not include wallet addresses or personal names. See the telemetry and data policy for instrument detail.

Diagnostics & reliability data

The desktop agent can send crash traces, error codes, CPU/OS metadata, and network timestamps when a failure occurs. These payloads allow our reliability team to reproduce issues such as failed bundle submissions or RPC drift. You can disable optional diagnostics in the agent settings, though doing so may limit our ability to resolve complex incidents.

Account & operational contact details

When you register for early access or open a ticket, we request a work email, organization name, and role. This ensures we route responses to authorized operators and keep sensitive relay configuration out of unintended hands. We do not collect payment card data on this site.

Data we do not collect

• Private keys, seed phrases, or custody credentials.
• Unencrypted bundle contents or MEV strategies stored at rest.
• End-user personal data unrelated to FRB operations.

How we use your data

Data collected through FRB is used to operate, secure, and improve the platform. We analyze aggregate telemetry to size infrastructure, tune block template distribution, and prioritize roadmap items. Diagnostics and support transcripts inform patches, regression tests, and documentation updates so traders can ship bundles with fewer surprises.

We may use contact details to send operational bulletins—such as relay maintenance windows or urgent security advisories. Marketing content is opt-in, and every message includes an unsubscribe link or instructions. We do not sell, rent, or trade your information with third parties for advertising purposes.

Data retention and deletion

Aggregated analytics are typically retained for up to 12 months to analyze long-term execution trends. High-fidelity diagnostics are stored for the shorter of 90 days or the duration of an open investigation, after which they are automatically pruned. Contractual obligations or legal holds may extend retention for specific audit records, but those cases are rare and documented.

You may request deletion of support tickets or diagnostic bundles tied to your account by emailing the FRB support desk. We honor verified deletion requests unless retention is required by applicable law.

Third-party services & analytics

FRB leverages vetted infrastructure vendors for cloud hosting, monitoring, secure email, and incident tooling. These providers only receive the data necessary to deliver the contracted service, and each agreement includes confidentiality, security, and data-processing clauses.

Where possible, we proxy telemetry through FRB-controlled collectors before forwarding pseudonymous metrics to analytics vendors. We do not embed third-party advertising pixels, and we review every integration for alignment with our documented security standards.

Security controls

Access to telemetry and support systems is gated behind hardware-backed authentication, role-based permissions, and continuous monitoring. Logs are encrypted in transit and at rest, and administrative actions are recorded for auditability. We conduct regular tabletop exercises to validate incident response plans and coordinate closely with the team that maintains the vulnerability disclosure program.

Your choices & how to manage preferences

• Disable non-essential analytics in the installer or browser banner where local regulation requires consent.
• Request a copy, correction, or deletion of your data by emailing support. We validate identity before acting on sensitive requests.
• Leverage private networking options or self-hosted relays if you prefer to keep operational telemetry on-premise.

You can also reach out for clarifications on how a specific feature processes data. We aim to respond with actionable detail rather than generic boilerplate.

How to contact us

Questions about privacy, telemetry, or compliance can be sent to support@ai-frb.com or contact the support team. Please include the context (e.g., FRB version, organization, relevant relay) so we can route the request to the correct team. For security-sensitive issues, use the channels documented on our vulnerability disclosure page.

Privacy FAQ

Last reviewed: 2025-09-19