What we collect
No accounts, subscriptions, or profiles. The site keeps only the operational data needed to serve pages, protect the service, and stay reliable.
- Server logs and request metadata: IP address, browser, device, referrer, path, timestamp, performance.
- Coarse analytics, cron-job logs, and error-monitoring events.
- When ads run, ad networks receive contextual request data.
How we use it
- Keep the site up, measure performance, spot abuse, debug failures, and learn which pages help.
- We do not sell personal information.
- Ads run only on public pages to fund the site, never to profile you.
Third parties
These services may receive request-level data in normal operation, under their own terms and privacy practices.
- Vercel
- Supabase
- Sentry
- Google Analytics
- Source material comes from SupremeCourt.gov, CourtListener, and SCOTUSblog.
- With ads on, third parties including Google may use cookies, web beacons, IP addresses, and browser signals for serving, measurement, fraud prevention, and reporting.
AI-generated content
- Some content is AI-assisted under source-backed prompts and quality checks. It can still be incomplete or wrong.
- Official filings, orders, opinions, and audio remain the authoritative record.
Retention and security
- Logs are kept only as long as reliability, security, and incident response require; windows vary by provider.
- Standard controls: access-limited credentials, hosted infrastructure protections, deployment validation.
- No system is perfectly secure. Avoid sending sensitive information through public channels.
Your choices
- Limit analytics and ads with cookie settings, browser controls, privacy tools, and content blockers.
- Questions and requests go to contact@supremecourtcasetracker.com.
Google explains how it uses data from partner sites at google.com/policies/privacy/partners.