Policy
Privacy Policy
Supreme Court Case Tracker is a public-interest site focused on tracking Supreme Court cases. This policy explains what operational data we collect, why we collect it, and how we handle third-party infrastructure and source integrations.
Information We Collect
We do not provide user accounts, paid subscriptions, or personalized profiles. The main information this site stores is operational data needed to serve pages, protect the service, and improve reliability.
That may include server logs, request metadata, coarse analytics events, cron-job execution logs, and error-monitoring events. Those records can contain IP address, browser, device, referrer, requested path, timestamp, and performance metadata.
How We Use Information
Operational and analytics data is used to keep the site available, measure performance, detect abuse, debug failures, and understand which public pages and feeds are most useful.
We do not sell personal information or build advertising audiences from site activity. If we add newsletter or contact features later, this policy will be updated before those features go live.
Third-Party Services
The site relies on third-party infrastructure and data providers, including Vercel for hosting, Supabase for storage, Sentry for monitoring, and SupremeCourt.gov, CourtListener, and SCOTUSblog for source material.
Those providers may receive request-level data as part of normal site operation. Their separate terms and privacy practices govern how they process data on their systems.
AI-Generated Content
Some summaries and analysis on this site are generated or assisted by AI systems. We use source-backed prompts and quality controls, but AI output can still be incomplete or incorrect.
Official court filings, orders, opinions, and audio remain the authoritative record. This site is designed to improve public access, not replace original legal materials.
Retention And Security
Operational logs and monitoring data are retained only as long as reasonably necessary for reliability, security, and incident response. Retention windows may differ by provider and deployment environment.
We use standard technical controls such as access-limited credentials, hosted infrastructure protections, and deployment validation. No internet-facing system is perfectly secure, so please avoid sending sensitive information through public contact channels.
Your Choices
You can limit some browser-based analytics and tracking through your browser settings, privacy tools, and content blockers. Because this is a public-information site without accounts, we may not be able to identify or delete browsing data tied only to shared infrastructure logs.
Questions about this policy can be directed to the project maintainer through the repository issue tracker or the contact channel published with the project.