Privacy Policy

Parquet is a thin frontend over a set of permissionless Solana programs. There is very little for Parquet to keep private because there is very little Parquet collects in the first place. This page describes what data exists, where it lives, and what is already public regardless of what Parquet does.

On-chain data is public, forever

Solana wallet addresses, transactions, positions, orders, deposits, withdrawals, liquidations, staking events, referral events, and fee events are public blockchain data. Anyone with a Solana RPC connection can read them, index them, and link them to other on-chain activity by the same wallet. This is a property of the blockchain itself, not of Parquet. Once a transaction is signed and confirmed, it is permanently public and cannot be deleted, redacted, or hidden by Parquet or anyone else.

No KYC, no accounts, no PII

Parquet does not collect identity verification (KYC) information. There is no signup, no email, no phone number, no government ID. Parquet does not maintain user accounts, balances, or credentials off-chain. Your wallet address is your only identifier, and Parquet does not attempt to link wallet addresses to any operator-collected personal information.

What the indexer stores

The Parquet indexer subscribes to Solana program logs and stores decoded events plus aggregated price rows so the frontend can render history, stats, staking, leaderboards, OHLCV charts, and the payout queue. The data in the indexer is derived from public on-chain events; the indexer does not add anything that was not already public. Retention follows a rolling prune policy: raw event and tick rows are pruned once the aggregated OHLCV buckets that depend on them have been built and are no longer needed for live queries.

Public API

The indexer exposes a public read-only HTTP API. Anyone can query positions, orders, stats, OHLCV, queue state, leaderboards, and other wallet-keyed data without authentication. API responses expose wallet-level activity that is already visible on-chain; Parquet exposes nothing that is not derivable from a public RPC. If you do not want a wallet's activity to appear in queryable form, do not use that wallet on Parquet, and be aware that any other public indexer can produce the same view from the chain directly.

Logs and operational data

Parquet's services (frontend hosting, indexer, price relayer, keeper, push relay) generate operational logs that may record request paths, response codes, timestamps, IP addresses, and user-agent strings as a normal part of running an internet-connected service. These logs are kept for short operational windows (typically days to weeks) for debugging and abuse mitigation, then rotated out. They are not used to build user profiles, are not sold, and are not shared except where strictly required to run the service.

Third parties may see your traffic

Parquet's frontend is served by a third-party static host. The read-only indexer and price API are exposed over the public internet behind a tunneling provider. On-chain transactions are routed through one or more Solana RPC providers, the choice of which is governed by your wallet, your browser settings, or the public RPC URL bundled into the frontend. Price data is sourced from third-party licensed market-data providers and a decentralized on-chain oracle. Each of these third parties may collect IP addresses, request metadata, or other technical telemetry under their own privacy policies, which Parquet does not control. If this matters to you, review their policies and consider routing your traffic through a VPN, a custom RPC, or a wallet that supports private RPC configuration.

Cookies and local storage

The Parquet frontend uses browser local storage to remember UI preferences and to set a flag once you have acknowledged the first-connect risk disclaimer. It does not use tracking cookies or third-party analytics tags that follow you across sites.

Mobile push notifications

If you use the Parquet mobile app and enable notifications, the app registers a push-notification device token with Parquet so it can deliver risk and liquidation alerts (for example, when a position approaches its liquidation price). That token is a per-device handle issued by the mobile platform's push service; Parquet stores it in a small device-token registry alongside the wallet that registered it, used only to route alerts to that device. It is not linked to any operator-collected identity, and it is removed when you disconnect the wallet in the app or revoke the token. This device token is the only off-device data the mobile app collects beyond the on-chain and indexer data described above.

What you should assume

Assume that any wallet you use on Parquet can be observed, indexed, and analyzed by anyone, indefinitely. Assume that an address used once on Parquet is permanently associated with whatever Parquet activity it produced. Do not connect a wallet you expect to remain unlinkable from your Parquet trading; use a fresh wallet if pseudonymity matters to you, and be aware that on-chain heuristics may still link wallets you believed to be separate.

Changes to this policy

This policy may change. The current version is always the one published at this URL. Continued use of Parquet after an update constitutes acceptance of the updated policy.

Last updated: 2026-06-28