Privacy policy

Account data: your email address, display name, and the platform user identifier that authenticates you.

Key metadata: a one-way hash of each API key, a display prefix, the last four characters, a label you choose, and timestamps for creation, last use and revocation.

Usage metadata: for each forward — timestamp, account and key reference, target host, HTTP method, upstream status code, bytes in, bytes out, trips charged, and duration.

Billing records: pack purchased, amount, and the payment reference returned by the payment provider.

The request and response bodies of a completed trip are never written to a database. They are streamed, metered and returned in the same request cycle, then discarded.

Plaintext API keys are never stored. A completed trip keeps no target path, no headers and no payload — only the host, method, status, byte counts, duration and trips charged that make up your usage history.

Sensitive request headers are redacted before any metadata is written, including on a refused attempt.

To authenticate your requests, debit trips accurately, show you your own usage, respond to abuse, and meet legal and accounting obligations.

We do not sell data, profile users, or share usage metadata with third parties except the payment provider that processes a pack purchase or where legally required.

Each account can read only its own keys, balance and activity log. The relay ledger is reachable only from server-side code, never from a browser, and every query against it is scoped to your account; the records you read in the console additionally carry per-user row-level security in the database. A mistake in a query cannot cross accounts.

Every interaction — sign-in, sign-out, key management, relays, log reads and exports — travels over HTTPS, and a request made over plain HTTP is redirected before it is served. Keys are hashed with a cryptographic digest; revocations take effect on the next request.

A completed trip keeps its counters only: target host, method, status, byte counts, duration, trips and balance. Its target URL, headers, request body and response are discarded as the trip settles, so no stored copy of the transfer can surface later.

A refused attempt keeps its full detail — target URL, redacted headers and the reason — because nothing was relayed and that is the record abuse response needs.

Both kinds of entry stay readable and exportable in your console while your account is active, and are deleted or anonymised within 30 days of account closure. Activity entries are also never written for traffic that was never sent.

Billing records are kept as long as tax law requires.

You can read and export your activity log — every retained detail — as JSON, CSV or Markdown from the dashboard at any time, and you can revoke any key immediately.

To request deletion of your account and associated metadata, or to ask what is held about you, email backfireapi@outlook.com. Requests are handled by Gurutva Murdia directly.

The data controller for Backfire is Gurutva Murdia, the solo creator and operator of the service — there is no separate company, reseller or data processor acting on their behalf other than the platform and payment provider named above.

Privacy questions, correction requests and deletion requests all go to backfireapi@outlook.com, and are answered by the operator personally.