> For the complete documentation index, see [llms.txt](https://docs.synoptic.com/s/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.synoptic.com/s/integrations/polymarket-key-privacy.md).

# Polymarket key privacy

This page describes how Synoptic Terminal handles a Polymarket private key when you add an exchange credential. It is the technical privacy note for that flow, not the site-wide legal privacy policy.

Synoptic never stores the raw private key. The key is pasted in your browser, imported into a Privy wallet you control, and then used only through Privy for signing.

## What you paste

Connecting an existing Polymarket account requires the **64-character hex private key** of the signer that owns that account (Magic Link / Google export, or the browser wallet you use on Polymarket). See [Polymarket credentials](https://docs.synoptic.com/s/integrations/polymarket-credentials.md) for how to export it.

Paste it only into Synoptic’s **Add Exchange Credential** form in your own browser session. Do not paste it into chat, email, support tickets, or any other site.

## What happens in the browser

1. You sign in to **Privy** in the credential form. Privy is the wallet provider that will hold the imported key. Synoptic uses Privy so the raw key does not live in Synoptic storage.
2. You paste the key once. The Terminal calls Privy’s `importWallet` in the browser. After a successful import, the form keeps a reference to that Privy wallet (address / wallet id), not the key material.
3. Later orders and CLOB auth signatures are created in the browser by that Privy **embedded** wallet. The Terminal asks Privy to sign typed data; it does not send the private key to Synoptic servers.

If a matching imported wallet is already on your Privy login, you do not paste the key again.

## What Synoptic stores

| Item                                         | Stored?                                                                                                                              |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| Raw Polymarket private key                   | No                                                                                                                                   |
| Privy wallet address / id used as the signer | Yes, on the credential                                                                                                               |
| Polymarket account (funder) address          | Yes, on the credential                                                                                                               |
| Derived CLOB L2 API credentials              | In the proxy, in memory (\~12 hours) and, when configured, in an httpOnly cookie bound to this browser. This is not the private key. |

The trading proxy (`polymarket-user`) **holds no private keys**. The browser signs orders; the proxy attaches L2 credentials and forwards them to Polymarket.

## What Privy stores

After import, Privy custodians the key as an embedded wallet on **your Privy account**. Synoptic does not see Privy’s key material. Signing happens through Privy’s wallet APIs in your session.

Limits that affect privacy and reuse:

* Each Privy login can hold **one** imported private key.
* Synoptic Terminal supports **one** Polymarket credential at a time.

If the wrong key is already imported, use **Switch Privy account** and sign in with a Privy account that does not have an imported key (or that already holds the key you need).

## Session and cookies

CLOB trading uses an L1 (EIP-712) attestation to derive L2 API credentials. That L1 signature is cached in the tab for the current signer and may be persisted as an httpOnly `pm_l2` cookie so a returning browser does not need another Privy signature immediately. Clearing the credential, logging out of Privy, or switching Privy account drops that cache and cookie.

The cookie is not your private key. It is derived trading credentials for this browser origin.

## Your responsibilities

* Export the key only from the official Polymarket / Magic Link / wallet flow.
* Confirm you are on Synoptic (`synoptic.com` or your known local origin) before pasting.
* Treat anyone asking you to paste the key in chat or email as a scam.
* If you believe the key was exposed, rotate it in the original wallet and remove the Synoptic credential.

## Related

* [Polymarket credentials](https://docs.synoptic.com/s/integrations/polymarket-credentials.md) — how to export the key
* [Privy — import a private key](https://docs.privy.io/wallets/wallets/import-a-wallet/private-key)
* Site-wide [Privacy Policy](https://synoptic.com/policy)
