EMPECT
Privacy policy

Privacy policy

What Empect records about you, why, and who can see it. In short: your coldkey, what you set, what you sign, what the chain shows, and the addresses your requests came from.

Last updated November 6, 2026

1. What this covers

This policy explains what information Empect (empect.co) collects, why, how long it is kept and who can see it. It applies to visitors and to the three kinds of account: subnet owners, investors and escrows.

2. What we collect

InformationWhenWhy
Your coldkey addressAt sign-up, and for escrows when the collateral coldkey is linkedIt is your account. It appears on term sheets, deals and profiles to the people allowed to see them.
Signatures over the challenges and term sheets you signEach sign-in and each signed dealProof that the address agreed; kept with the deal record.
Your subnet's netuid and nameOwner sign-upTo check ownership on the chain and to price your sheet.
Discord account id and usernameWhen you sign in with Discord or link itThe escrow's account identity; a contact badge for owners and investors. We receive only the id and username; no e-mail, no messages, no token is kept.
X and Telegram handlesIf you enter themShown on your profile to people allowed to see it.
Term sheets, wishlist, visibility rules, fee settingsAs you set themTo run the Service as you configured it.
Deal records: terms, offers, messages, signatures, chain observations, payoutsDuring a dealThe record both parties and the escrow rely on.
Chain data about your coldkey: balance, stake positions, transfers that match a dealAt sign-up (investor balance), for visibility rules, and while a deal is openRead from the public Bittensor chain to apply the rules and confirm transfers.
Network address, country, browser type, time of each actionEach request that signs you in or changes somethingSecurity and abuse prevention; an audit trail of account activity.

We do not collect names, e-mail addresses, documents, payment details or wallet seeds, and we never ask for a private key.

3. Cookies

The Service sets one session cookie per role you sign in with, which keeps you signed in for up to seven days. It is required for the Service to work and holds only a signed reference to your account. A browser-side preference or two (such as a chosen tab) may be stored in your browser and never reach us. There are no advertising or tracking cookies, and no third-party analytics scripts run on the site.

4. Who sees your information

  • Other users, according to the visibility rules described in the documentation: owners see the investors who contact them or whose rules they meet; investors see owners whose sheets they may see; escrows see the deals that name them; parties to a deal see each other.
  • Service providers: Cloudflare carries all traffic to the site and sees network addresses as any such provider does; Discord confirms your Discord account when you choose to use it. Each acts under its own policy.
  • The public Bittensor chain, which already contains every transfer the Service observes. We add nothing to the chain.
  • Authorities, where we are legally required to disclose.

We do not sell information about you and do not share it for advertising.

5. How long we keep it

Account and deal records are kept for as long as the account exists and for as long afterwards as the parties to a deal may reasonably need the record. Security and audit logs are kept for ninety days. Chain snapshots used for charts are kept as aggregate market data without reference to accounts.

6. Your choices and rights

You can change your handles, wishlist, visibility rules and fee settings at any time from your profile, and unlink Discord unless it is your escrow account itself. You can ask us to delete your account; deal records in which other users have an interest may be retained in a form that still identifies the coldkeys involved, because the parties rely on them. Depending on where you live you may have rights to access, correct, export or erase information about you, and to complain to a supervisory authority.

7. Security

Traffic is encrypted in transit. Sessions are signed and expire. Signatures are verified on the server; wallets are never connected to the site. Access to the server and its logs is limited to the operator. No system is perfectly secure, and you remain responsible for your own keys.

8. Changes

We may update this policy; the date above changes when we do, and material changes are announced on the Service.