Legal · Last updated April 26, 2026

Privacy notice

This notice describes what data is collected when you use the Invia interface at invia.markets and the documentation at docs.invia.markets (together, the Interface), and what is necessarily public when you interact with the Invia smart contract on Solana (the Protocol). It is intentionally short. We collect as little as possible.

1. What we do not collect

  • No accounts. The Interface has no sign-up, no login, and no user accounts. Your wallet address is your identity on the Protocol.
  • No personal information. We do not ask for your name, email, phone number, address, government ID, or any other identifying information to use the Interface.
  • No KYC. The Protocol is permissionless and the Interface does not perform identity verification.
  • No tracking pixels. The Interface does not embed third-party analytics scripts that build cross-site profiles.

2. What is collected automatically

The web servers that host the Interface receive standard HTTP request data from any visitor:

  • IP address of the requesting client.
  • User-agent string (browser and operating system).
  • Request path and timestamp.
  • Referrer header, when present.

These are written to short-lived web-server logs and used only to diagnose abuse, debug outages, and produce aggregate counts of traffic. Logs are rotated and discarded; we do not build long-term profiles from them.

3. What is necessarily public when you use the Protocol

Solana is a public blockchain. Any transaction you sign and broadcast is permanently visible on chain to anyone, including:

  • Your wallet address.
  • The mints, sizes, prices, and counterparties of every offer you create or fill.
  • The timestamps of every action.

We do not control the visibility of on-chain data and cannot remove, redact, or hide it. Anyone with a block explorer can reconstruct your complete trading history from your wallet address.

4. RPC providers

To read the chain and submit transactions, the Interface connects to one or more Solana RPC providers. The provider sees:

  • The IP address from which a request originates.
  • The chain queries the Interface makes on your behalf.
  • The signed transactions submitted for inclusion.

We currently use Helius as the primary RPC provider. Their handling of this data is governed by their own privacy policy. You may configure the Interface to use a different RPC endpoint by editing the source and self-hosting.

5. Wallet providers

When you connect a wallet, the wallet extension or app handles signing locally. We do not receive your seed phrase or private key. The wallet provider may collect connection telemetry under its own terms.

6. Cookies and local storage

The Interface does not set tracking cookies. It may use the browser's localStorage to remember UI preferences (for example, watchlist entries or display density). This data stays in your browser and is not transmitted to us.

7. No sale or sharing

We do not sell, rent, or share any data we collect with third parties for marketing, profiling, or any commercial purpose.

8. Security

The Interface is served over HTTPS with a publicly auditable Let's Encrypt certificate. The Protocol itself enforces all settlement guarantees on chain and does not rely on the Interface for safety. Even if the Interface were compromised, your funds remain controlled by your wallet's signing key.

9. Children

The Interface is not directed at people under 18 and we do not knowingly collect data from them.

10. Changes

Material changes to this notice will be reflected in the "Last updated" date at the top of this page.

11. Contact

Privacy questions can be sent to hello@invia.markets.