Privacy Policy

Last updated: October 12, 2026

Data stored in your browser

PerpsX stores the following data locally to operate the trading interface. This data is not uploaded to a PerpsX account database by these storage mechanisms. Browser storage is not encrypted by PerpsX.

Storage keyContents
perpsx:storage-notice-dismissedWhether you dismissed the local-storage notice.
perpsx:sentry-consentYour optional error-reporting consent choice.
perpsx:settingsWallet address and trading, notification, and display preferences.
perpsx:audit-logUp to 200 wallet-linked events: session open/renew/close, order place/cancel, position close, deposit, withdrawal, and settings updates.
perpsx:accountsUp to 20 account profiles containing address, label, role, and last-used time.
polyperp:perps-credentialsPolymarket API session credentials, stored in browser localStorage as plaintext. Anyone with access to this browser profile may be able to read them.
polyperp:perps-accountWhich Polymarket account your connected wallet trades as, so it is not looked up again on every visit.
polyperpThe app persists the current token and user object through its client state store.
perpsx:watchlistMarkets you starred on the Markets page.
sessionStorageA per-order idempotency key used to avoid duplicate order submissions.
px_rw_refRewards only: a referral code from a link you opened, until you join Rewards.
px_rw_synced:<address>Rewards only: identifiers of up to 600 fills already sent to Rewards, so they are not sent twice.
px_rw_session (cookie)Rewards and sync only: an HttpOnly sign-in cookie holding your wallet address, valid for 30 days.
px_chart_drawings:<market>, px_chart_indicatorsChart drawings and indicator choices.
perpsx:price-alerts:v1Your price alerts.
px_twap_jobsProgress of TWAP orders, so an interrupted one can be resumed.
px_sync_metaSync only: when each synced item last changed on this device.
px_rw_nonce (cookie)Rewards only: a single-use sign-in challenge, valid for 10 minutes.

Rewards program (optional)

If you join PerpsX Rewards, PerpsX stores the following on its own server database: your wallet address, your referral code and who referred you, the fills your browser reports (trade ID, market, side, price, size, time, and whether you were the maker), and your points, achievements, and streak history. The public leaderboard shows a shortened form of your address and your points. You can leave Rewards in Settings, which deletes this data from the database.

This server database (also used for email alerts and sync) is a Postgres database hosted by Neon on Amazon Web Services in the us-east-1 region (Northern Virginia, United States). Daily backups of this database are kept in a private Cloudflare R2 storage bucket for up to 120 days, so data you delete is gone from backups once those copies expire, at most 120 days later.

Email alerts (optional)

If you add an email address in Settings → Alerts, PerpsX stores it on its server with your wallet address, the alerts you chose, and a record of which alerts were sent so none is sent twice. We email only after you confirm the address with the link we send. Emails are delivered by Resend. Price alerts are checked on our server against your synced alerts and public prices; liquidation warnings are sent when PerpsX, open on one of your devices, sees a position near liquidation. Every email has an unsubscribe link, and Remove in Settings deletes the address and its history.

Sync across devices (optional)

If you turn on sync in Settings → Privacy, PerpsX stores your chart drawings, price alerts and indicator choices on its server under your wallet address, using the same sign-in cookie as Rewards. No trading credentials, keys or balances are synced. Turning sync off on a device keeps the server copy; "Delete synced data" removes it.

Third-party services

Privy provides identity and embedded-wallet services. Polymarket provides market data, trading APIs, and WebSocket feeds. Neon hosts the PerpsX server database, and Cloudflare stores its backups. Sentry receives reports of errors that happen on PerpsX servers so we can fix them; before a report leaves our servers we remove IP addresses, cookies, request contents, wallet addresses, email addresses and keys, and these reports are not linked to you. Errors that happen in your browser are sent to Sentry only if you turn on optional error reporting. These providers process information under their own terms.

Wallet and network data

Your public wallet address and blockchain transactions are visible on the public Polygon network. PerpsX does not receive your wallet private key. Polymarket and your wallet provider handle their respective service data.

Activity on PerpsX

To run and protect the service, PerpsX records what happens in the app on its server: when a wallet connects, when an order is placed, fails (with the error type), fills or is cancelled, when a position is closed, and deposits and withdrawals. Each record has the wallet address, the market, side and size, and the time. We do not record your IP address, device or browser details with these records. Page views are counted per hour without any address, cookie or identifier. The PerpsX team uses these records to see how the product is used, find problems, and prevent abuse. The team can restrict a wallet that abuses PerpsX: a restricted wallet cannot open new positions or use Rewards, sync or email alerts here, but can always close positions, withdraw, and download or delete its data. Restrictions, internal team notes about a wallet, and every team action are kept in an access-controlled audit log.

Retention and deletion

Browser data remains until it expires, is replaced, or you clear it in Settings or your browser. The audit log is capped at 200 entries. Clearing browser data may end your trading session and remove preferences or local records.

Your choices

You can review or clear locally stored PerpsX data and change optional error-reporting consent in Settings. If you signed in with your wallet, Settings → Privacy also lets you download everything our server holds about your address (Rewards, email alerts, synced preferences, activity records) and delete it. A restriction, if any, is kept after deletion so that it can still be enforced. You can also clear site data in your browser. On-chain records cannot be edited or deleted by PerpsX.

Changes and contact

We may update this policy when the product or its data handling changes. The date above identifies the latest revision. For privacy questions, contact the PerpsX team through the channels listed on this site.