Privacy Policy

1. What we collect

• Wallet public keys you connect, and signatures that prove you control them.
• Session cookies (cp_session, httpOnly) and a CSRF cookie needed for dashboard mutations.
• CLI device-authorization codes, until they are approved, denied, or expire.
• Shred destinations you register (name, public IP, UDP TVU port, region) and hashed heartbeat (agent) tokens. The plaintext token is shown once in the dashboard; we store a hash.
• QUIC session assignments (POP, region, endpoint).
• Trade-wallet addresses you link so landing telemetry can match fee payers.
• Strategy files and catalog purchases you store in the account library, including parameters you type when instantiating a template.
• Billing records: invoices, coupon codes, USDC amounts, on-chain payment signatures and memos, and whether the current period is paid.
• Transaction-relay telemetry for wallets on your account: signature, POP, slots, landing or execution error, and routing forensics the POP records.
• Operational logs needed to run the control plane (timestamps, IP of API clients, error codes). The public status page shows mesh latency between POPs and validator landing rates without listing visitor IPs.

We do not ask for a password, seed phrase, or private key. Signing a message or a USDC transfer happens in your wallet. We cannot spend from your wallet.

2. How we use it

We use this information to authenticate you, deliver the shred feed, assign a POP, verify prepaid USDC payments, run the dashboard, and operate the CLI login. Catalog purchases license a template; they are not investment advice and they do not grant shred access by themselves.

We do not sell your account data. We do not use it for advertising.

3. On-chain payments

Subscription and catalog payments are USDC transfers you submit. The destination address, amount, and memo reference are visible on Solana. Anyone with the signature can look up the transfer on a block explorer. That is a property of the chain, not a dashboard setting we can undo.

4. Sharing

Infrastructure providers (hosting, RPC, connectivity) process traffic as needed to run the Service. We may disclose information if required by law or to protect the Service from abuse. Open-source clients you install run on machines you control; we do not receive your signing keys from those clients.

5. Retention

Session cookies last until you sign out or they expire. Device codes are short-lived. Agent token hashes last until you replace the token or delete the destination. Billing and landing history are kept while the account exists so invoices and telemetry remain available. You can stop using the Service and sign out at any time; contact us if you need an account removed.

6. Your choices

Disconnect the wallet and sign out to end the browser session. Deny a CLI code you did not start. Replace an agent token to revoke the previous hash. Do not paste device codes or agent tokens into tickets or screenshots.

7. Changes

We may update this policy. The date above is the current version. Continued use after a change means you accept the updated policy.

8. Contact

Questions: hello@pipe.network