Cookies and storage
Everything Deference stores in your browser, and why.
At a glance
- Reading
- Reading this site sets no cookies.
- Signing in
- Signing in sets two: one keeps you signed in, one tells the site's navigation that you are.
- Dashboard
- The dashboard adds two preference cookies, for your time zone and the sidebar layout.
- Tracking
- Deference runs no analytics, advertising or cross-site tracking.
1 Cookies Deference sets
| Name | What it does | Lasts | Kind |
|---|---|---|---|
| __Host-df_session | Keeps you signed in. It is encrypted, and page scripts cannot read it. | 7 days | Required |
| df_signed_in | Tells the site's navigation that you are signed in. It holds no account data. | 7 days | Required |
| df_tz | Shows times in the dashboard in your time zone. | 1 year | Preference |
| sidebar_state | Remembers whether the dashboard sidebar is open. | 7 days | Preference |
2 Kept on your device
| Name | What it does | Where |
|---|---|---|
| theme | Light or dark, if you choose one in the dashboard. | Dashboard |
| docs-code-tabs | The language you picked in code samples. | Docs |
| deference.lastSignIn | Which sign-in method you used last, and when. Never your email or address. | Sign-in |
| cookie-notice | That you dismissed the dashboard's cookie notice. | Dashboard |
These stay in your browser's local storage and are never sent to us. They last until you clear site data.
3 Stored by Privy and wallets
When you open sign-in or the dashboard, Privy's code keeps your sign-in in local storage under names that start with privy:. That includes an access token for about an hour, a refresh token for 30 days, the method you used last, your wallet connections and a client analytics ID. The tokens and the analytics ID are sent to Privy, and Privy's privacy policy covers them.
If you connect an external wallet, its connector stores the connection until you disconnect. Mobile wallets connect through WalletConnect, which stores its own entries.
4 No banner, one notice
The public site sets no cookies until you sign in. It keeps two choices on your device: the code-sample language in the docs and the sign-in method you used last.
The dashboard sets two preference cookies, for your time zone and sidebar layout, and names them in a short notice the first time you open it.
If we add analytics or tracking, we will ask first, and declining will take one click, the same as accepting.
5 Your browser decides
Your browser can block or clear any of this. Blocking cookies stops sign-in, and clearing site data signs you out and resets your choices.
We do not track you across sites, so Do Not Track and Global Privacy Control have nothing to switch off.