Transit Fabric Privacy Policy
Version 1 · Effective 2026-11-17 · We may update this policy; the current version is always at this URL. It goes with the Terms of Service, version 1.
This policy explains what personal data the Transit Fabric testnet services collect, why, and what you can do about it. The services are the site at transitfabric.xyz, the claim page, the findings sandbox at submit.transitfabric.xyz, the stats API at api.transitfabric.xyz, the release files at github.com/transitfabric/releases, and testnet subnet 611 (the "Services").
1. Who we are
The controller is TransitFabric.xyz ("we", "us"). Contact for anything in this policy: privacy@transitfabric.xyz.
2. The short version
- We collect as little as we can. We never ask for your name, date of birth, postal address or government ID.
- No tracking and no analytics. Our pages set no cookies, run no analytics or advertising scripts, record no sessions (no session replay) and capture no keystrokes, and load nothing from third parties: no web fonts, no CDNs. Fonts are your device's own.
- No email from us. We send no marketing email and keep no mailing list.
- We never publish an IP address. Locations we publish are coarse: a country or first-level region, or a circle centred on a whole degree, never a city.
- Some data is public by nature and outside our control: blockchain data, and anything you post in a public GitHub Issue.
3. What we collect, by service
3.1 The claim page (bounty registration)
The page runs in your browser and sends nothing anywhere. You then file the result yourself, either as a public GitHub Issue or as a private GitHub security advisory. A registration holds:
- your GitHub login;
- your SS58 address (a hotkey or coldkey public address);
- the signed message: your login, address, the date,
age=18+, the terms version and the attestation sentence; - the signature.
A public Issue is visible to anyone. A private advisory is visible to you and the repository's maintainers.
3.2 The findings sandbox (submit.transitfabric.xyz)
- Signed finding form: your GitHub login and registered SS58 address, the finding's fields (title, version, severity, tier, component, steps, expected, actual, details), the proof-of-concept zip, the signed message and signature, a receipt, and the time received.
- Plain upload: your markdown file, an optional zip, and an optional contact (a Discord name or an email address, only if you choose to give one).
- Age attestation: with both, we store only
{ age_attested: true, terms_version, ts }, the fact that you ticked the box, which terms version, and when. No date of birth. - IP address: used, but not stored with your submission. The Worker uses your address (an IPv4 address, or an IPv6 /64) in memory as a rate-limit key, and keeps a daily counter whose key is a hash of that address, the day and a secret salt. The counter expires after 2 days.
Submissions are private: read by the maintainers, never served back to the public. Don't put keys, seed phrases, IP addresses or hostnames in what you send.
3.3 Eligibility and the pass history
To decide a registrant's bounty tier, our tools link your registered address to public chain data (the UIDs whose hotkey or coldkey it is) and to the validators' published test results for the nodes bound to those UIDs. We keep a history of which node keys passed under which UID, per window.
3.4 Running a node, solver or validator
When you take part in the network, other participants and validators necessarily see some data:
- Your node's public key and derived overlay address, and your hotkey binding (signed by you and committed on chain).
- Your node's IP address and port, seen by the validators and peers it connects to. A public node's endpoint is listed in the validators' peer directory, which participants exchange. Validators run by other operators are independent; they decide for themselves what they keep.
- Measurements: round-trip times, capacity tests, uptime and the route tables you serve or carry.
- Fault reports: if your node runs System One (
fabric-sense), it may send validators a signed fault report: a symptom code, the software version and commit, the node kind and platform, and for a crash an assertion hash. No IP address and no personal data. Validators publish counts only.
3.5 The stats API and coarse location
The stats API publishes testnet data that a majority of validators agree on. It never publishes a node's internet IP address and never a coldkey. It does publish each node's full public key and its fabric address: an overlay address in fc00::/8 derived from that public key, which is not routable on the internet and reveals nothing beyond the key itself. UIDs and hotkeys are public on chain.
Location is derived from IP addresses, coarsely:
- Country and first-level region (a state or province), looked up on our publisher in a local copy of the DB-IP Lite database. Only for addresses already public: a public node's endpoint in the peer directory, the seed nodes a release lists, and the axon address a UID publishes on chain.
- A claimed location: each validator looks up the address your node's probe session comes from, in its own local copy of the same database, on the validator. Only the country, the first-level region and coordinates rounded to whole degrees leave the validator, never the address or a city. It is checked against the validated region below.
- A validated region: a circle centred on a whole degree of latitude and longitude, with a radius of tens to thousands of km, worked out from round-trip times alone, never from an address.
- Never at city level, never a street address.
When you call the API, the Worker uses your address only in memory as a rate-limit key and keeps no request log.
3.6 The site (transitfabric.xyz) and the releases repository
The site is static. It sets no cookies, runs no analytics, records no sessions and captures no keystrokes. The claim page's wallet libraries are served from the site itself, and the page makes no network request. The host serving the pages (see section 6) receives your IP address and browser details as part of serving any web request.
3.6a The network dashboard (dashboard.transitfabric.xyz)
The dashboard is read-only. It sets no cookies, runs no analytics, records no sessions and loads nothing from third parties; it reads only from our stats API. It remembers whether you last chose the map or the globe in your own browser's local storage, which never leaves your device. The host serving it receives your IP address and browser details as part of serving any web request.
3.7 Public records we publish
- The leaderboard and the weekly ledger show your GitHub login or the handle you registered with, and your points. They contain no IP addresses.
- With your permission, we credit you by name or handle for a fixed finding.
3.8 Discord
If you join the Transit Fabric Discord, Discord processes your account data under its own privacy policy. We see your Discord username, your messages in our server, and the roles we give you (such as Founding Tester). Our bots post announcements, including a digest of public GitHub Issue titles and links; they don't collect data from members.
3.9 Blockchain data
Hotkeys, coldkeys, registrations, weights, commitments and stake on the Bittensor testnet are public and permanent by design. We read them; we don't control them and can't delete them.
4. Why we use it, and our legal bases (GDPR Article 6)
| Purpose | Data | Legal basis |
|---|---|---|
| Registering you, checking your signature and age attestation, recording credit and points | GitHub login, SS58 address, signed message, attestation record | Performance of a contract with you (Art. 6(1)(b)) |
| Receiving, triaging and fixing findings; crediting them | Finding fields, zip, receipt | Contract (Art. 6(1)(b)); our legitimate interest in securing the software (Art. 6(1)(f)) |
| Replying to a plain upload | Optional contact | Your consent, by giving it (Art. 6(1)(a)); you may withdraw it |
| Rate limits, abuse prevention and security of the Services | IP address (in memory), hashed daily counter | Legitimate interest in keeping the Services available and safe (Art. 6(1)(f)) |
| Running and measuring the network; publishing aggregate testnet statistics | Node keys, endpoints, measurements, coarse location | Legitimate interest in operating a measurable network (Art. 6(1)(f)); contract, for participants (Art. 6(1)(b)) |
| Keeping minors out; sanctions and tax compliance | Attestation record; what the law requires | Legal obligation (Art. 6(1)(c)); legitimate interest (Art. 6(1)(f)) |
| Public credit for a finding | Your name or handle | Your consent (Art. 6(1)(a)) |
Where we rely on legitimate interests, you can object (section 8).
5. How long we keep it
| Data | Kept |
|---|---|
| Rate-limit counters (hashed) | 2 days |
| IP addresses at our Workers | Not stored. We keep no request logs of our own; Cloudflare processes request data as our host under its own policies (section 6) |
| Registrations | For the life of the bug bounty plus 2 years, to settle credit and appeals. A public Issue stays on GitHub until it is deleted |
| Signed findings, their zips and attestation records | For the life of the bug bounty plus 2 years, then deleted, except what a fix, a regression test or a threat-model entry needs (with no personal data) |
| Plain sandbox uploads, their zips and attestation records | Deleted 1 year after triage |
| Pass history and published ledgers | For the life of the program; published ledgers stay public |
| Optional contact on an upload | Until the finding is closed, then deleted |
6. Who processes it for us
We use these providers. Each processes data on our behalf, or under its own terms where it acts as an independent controller:
- Cloudflare hosts the findings sandbox and the stats API (Workers and their key-value store) and may serve or proxy the site. To deliver and protect them it processes request data, including your IP address, under its own policies. We have not turned on Workers request logging, and we keep no request logs of our own.
- GitHub hosts the releases repository, Issues, private advisories and the site (GitHub Pages).
- Vultr hosts our testnet servers: validators, the reference solver, seed nodes and the stats publisher.
- Discord hosts the community server.
We don't sell personal data and we don't share it for advertising.
7. International transfers
Our providers are based in, or process data in, the United States and other countries. Where personal data from the EEA, the UK or Switzerland is transferred to a country without an adequacy decision, we rely on the provider's Standard Contractual Clauses or its participation in the EU-U.S. Data Privacy Framework (and its UK and Swiss extensions), as applicable.
8. Your rights
Depending on where you live (in the EEA and UK under the GDPR, and under similar laws elsewhere), you have the right to:
- access the personal data we hold about you;
- correct it;
- delete it ("right to be forgotten");
- restrict or object to our use of it, including use based on legitimate interests;
- data portability;
- withdraw consent at any time, without affecting earlier processing;
- complain to your data protection supervisory authority.
Write to privacy@transitfabric.xyz. We may ask you to prove you control the GitHub account or sign a message with the registered address. We answer within one month.
Limits: we can't delete blockchain data, data held by independent validators, or what others copied from a public Issue. Deleting your registration ends your eligibility for credit.
9. Children
The Services are not for anyone under 18, or under the age of majority where they live if that is higher. Every registration, finding and upload requires an attestation that you meet this age. We don't knowingly collect data from anyone younger. If we learn that we have, we delete it and close the registration. Tell us at privacy@transitfabric.xyz if you believe this has happened.
10. Security
Submissions are stored privately and read only by maintainers with an access token. Signatures are checked on receipt. Client addresses are not stored. No system is perfectly secure; report a vulnerability through a private GitHub security advisory.
11. Changes
Each version of this policy has a number and a date. We post a changed version on the site and announce material changes in the Transit Fabric Discord and on the releases repository before they apply.