Browse free without an account
Published findings, methodology, status, and most public pages are readable without signing in. We do not put a wallet wall in front of the public record.
Privacy
Read free. Identity only when you act.
This notice explains how Public Ledger treats browsing, accounts, and optional wallets in plain language. It is product honesty for a public-records and funding surface — not legal advice, not a privacy policy template with fake law-firm letterhead, and not a promise that every future feature is already built.
Where a concern sits
Public loopShared → in review → finding published. Start with a guided public-money concern; agents research, people gate publish.
- Shared
A public-money concern is described and enters the platform as a review lead — not a legal filing or verdict.
Next stage - In review
Agents research public records; people confirm short gates. Nothing becomes a published finding without human review.
Upcoming stage - Published
Source-backed results that clear review appear on Findings. Review leads with sources — not courtroom verdicts.
Upcoming stage
This shows the public review loop on Public Ledger — not a government FOIA request and not a ticket number.
Principles
Trust-critical doors should match how the product actually works today — free public browse, email when you contribute, no invented compliance theater.
Account only when you act
Email sign-in (one-time code via Privy) is the supported path for pledges, lead history, workspaces, and scoped agent tools. Google and Apple may be founder-gated until enabled — we do not pretend dead buttons are live.
Public records are public
Source-backed findings cite government and open data. Linking or quoting public material is not a claim that we own those records, and it is not a substitute for the underlying agency source.
Not a law firm
Public Ledger is an evidence, coordination, and funding layer. It is not a law firm, does not give legal advice, and does not create attorney–client privilege. Secure whistleblower intake stays gated until independently reviewed.
What we handle
Categories of information that can appear when you use the site. Scope grows only when features ship — not when marketing wants a longer policy.
Public browse traffic
Like most sites, infrastructure may log IP address, user agent, referrer, and path for security, rate limits, uptime, and abuse prevention. We use this operationally — not to build a secret dossier of casual readers.
Account identity (when you sign in)
If you create an account, Privy authenticates you (email code today; other methods only when enabled). We store a profile linked to that auth subject so pledges, leads, and workspace actions stay attributable to you.
What you submit
Concerns, sources, comments, FOIA drafts, and similar inputs are stored so humans and agents can work the trail. A normal public concern is not confidential or privileged. Do not submit secrets you are not allowed to share.
Wallet (only when relevant)
A wallet is optional for reading. On-chain actions ($FOIA funding, rewards settlement, or other crypto rails) may require wallet connection. Wallet addresses are public on the chain you use; treat them as public identifiers.
Operational and product analytics
We may measure product health (errors, latency, conversion funnels) to keep the site working. We avoid inventing dark-pattern tracking claims. If third-party processors change, this page should be updated to match reality.
Processors and infrastructure
Core stack for identity, data, and hosting. Names here should track production reality.
Privy
Primary authentication path. Email one-time codes (and other methods when enabled) create a session so we can attach actions to a profile. Wallet connection is optional until you need on-chain product surfaces.
Supabase and application hosting
Application data and storage live in managed Postgres/storage. The public web app runs on our production host for publicledger.ai. Access to secrets and operator tools is restricted to authorized operators.
AI research tooling
Agents may process public sources and user-provided material to draft research and workspace outputs. People gate publish and sensitive sends. AI outputs are not legal conclusions.
On-chain rails (when used)
$FOIA and related chain activity, when live for a given action, are visible on the public ledger of the network in use (e.g. Base). Chain transparency is a feature of public blockchains, not a Public Ledger “tracking pixel.”
Your choices
Practical options without fake rights language we cannot honor.
Read without joining
Use findings, methodology, and status with no account. That is intentional product design, not a loophole.
Sign in only for tools
Email join unlocks contribution surfaces. You can leave when you are done browsing.
Corrections and context
Government entities and subjects of review should be able to provide context or corrections through published process — see methodology for review posture, not private backchannels for scrubbing the record.
Questions about this notice
Use the public concern flow for product or process questions, or platform status for operational health. We will not invent a fake counsel hotline on this page.
Limits and honesty
What this page is not
This is not legal advice, not a certified compliance audit, and not a guarantee of any regulatory regime. Public records work can surface sensitive civic topics; that does not turn casual submissions into privileged whistleblower channels. Reward eligibility, token value, and enforcement outcomes are never guaranteed. For how claims are scored and labeled, read methodology. For access without a wallet wall, see get access.
Last updated: August 11, 2026. We will revise this page when product reality changes — not to pad theater language.
Next step
Trust should be readable before it is joinable.
If you only came to check the privacy door, leave with findings and methodology open. Account tools wait until you choose to act.