What we store, and what we deliberately don’t.

fivedesks has no user accounts. We do not collect names, email addresses for identification, or any profile of you. We run no advertising and no cross-site trackers. Page views are counted in aggregate by our host’s analytics (Vercel Web Analytics) — cookie-free, and never tied to who you are.

cl_auth — while the site is in its pre-launch, password-gated period, logging in sets one HTTP-only cookie proving the password was entered. It contains no identity and expires after 30 days.

fd_reads — if the free-brief meter is on, a cookie on your device counts which briefs you opened this month so the third one is still free to re-read. It never leaves your browser except to render your own count, it is not tied to any identity, and deleting it simply resets the count. A malformed cookie is treated as a fresh one — the meter fails open, never closed.

The corrections form stores what you write — the correction, the page it concerns, and an email address only if you choose to give one for a reply. We do not store your IP address or browser details with it. “Ask us to cover” taps store the symbol and the search text, nothing else — they are a count of demand, not a record of you.

The pricing page’s “email me when subscriptions open” box stores the email address you give it, for exactly one purpose: telling you once when subscriptions open. We do not use it for anything else, and we do not share it.

The site is served by Vercel and its data lives in Supabase; both process requests to operate the service (their own infrastructure logs are governed by their policies). We do not sell, share, or enrich any of the above — there is nothing to sell.

Everything published here is computed from public records: SEC filings and congressional financial disclosures filed under the STOCK Act. Members of Congress named on the site are named in their own public filings. If something about you is wrong, tell us — corrections are reviewed by a person.