Data Handling
Just A Bill AI is designed around public legislative data. Runs, reports, read models, replay bundles, and sanitized artifacts may be publicly accessible for verification.
Information Collected
The service may collect bill URLs, run metadata, model outputs, runtime attribution, artifacts, feedback text, verification records, account identifiers, credit balances, payment metadata, browser configuration, and operational logs.
Public Data
Public read models and replay bundles are sanitized before publication, but they may include bill text, public sponsor metadata, generated summaries, workflow outputs, hashes, and replay instructions. Do not submit confidential content.
Account, Payment, And Email Providers
Clerk handles sign-in and user identity. Stripe handles checkout and payment processing. Resend may send run-completion emails to funders when notifications are enabled. Supabase stores hosted application records, and Cloudflare serves static pages and may store artifacts in R2.
Retention
Public run records, replay bundles, and feedback may be retained to support auditability, comparison, regression testing, and public verification. Account, payment, and notification records are retained as needed for service operation, accounting, fraud prevention, support, and legal obligations.
Agent Access
The MCP endpoint and public API expose read-only run and policy data unless a tool requires authentication. Authenticated tools may associate actions with the signed-in Clerk user or a personal access token created from account controls.
Deletion And Corrections
Public legislative analysis is generally preserved for transparency. Send feedback for factual corrections, attribution errors, replay issues, or harmful output concerns.