Privacy Policy
We collect as little as possible, and what little we keep is hashed. This policy describes what the Robyn AnyGas service actually does — not an aspirational version of it.
1.What we collect
Operating a relay requires minimal usage and operational logs for reliability, security, and abuse prevention. Concretely, per request we may record:
- Request method, path, HTTP status, and latency.
- A salted hash of the client IP address — we store the hash for rate-limiting and abuse detection, not the raw IP.
- A hashed API-key identifier (so we can attribute usage to a key without storing the key itself).
- Timestamps.
What we do collect
- Method / path / status / latency
- Salted hash of client IP
- Hashed API-key id
- Timestamps
- An API-key label, only if you provide one
What we don't collect
- No raw IP addresses
- No wallet addresses or amounts in public feeds
- No names or email addresses
- No private keys — ever
- No selling of any of it
We do not collect names, emails, or other personal information unless you choose to provide it — for example, a human-readable label you attach to an API key. Our public activity feeds (such as the route explorer) are anonymized: they do not expose wallet addresses or amounts.
2.Data stored in your browser
The site uses browser local storage only for your own convenience, and it is never sent to us as tracking:
- Your theme preference (the
anygas-themesetting). - For service owners, a session-held owner key used to authenticate to the owner console — it stays client-side and is sent only to authenticate your own requests.
We do not use advertising cookies or third-party trackers.
3.How we use it
- Operating the service — routing, quoting, fronting gas, and returning results.
- Security & abuse prevention — rate-limiting and detecting misuse using the hashed identifiers above.
- Anonymized analytics — understanding aggregate reliability and usage patterns.
We do not sell your data, and we don't share it except as needed to operate the service (below) or as required by law.
4.Third parties
To move value across chains, the Service submits transactions through independent third-party bridges and aggregators — for example LI.FI, Bungee, deBridge, Allbridge, and Chainflip — and the underlying blockchains. These providers operate their own infrastructure and privacy practices, which we do not control; review their policies where relevant.
Our endpoints sit behind Cloudflare, which provides network protection and may process request metadata (such as IP addresses) under its own privacy policy as part of delivering and securing traffic.
5.Data retention
Operational logs are kept only as long as needed for reliability, security, and abuse prevention, then rotated out. Because the identifiers we retain are hashed, they cannot be reversed back into raw IPs or keys.
6.Changes & contact
We may update this policy; the "Last updated" date reflects the latest version. For questions about privacy, reach us via the contact channels on anygas.xyz or the project repository. See also our Terms of Service.