Privacy Policy

• Account: email address, and optionally firm name, phone, primary practice area, and preferred jurisdictions collected during onboarding.
• Billing: Stripe payment tokens and last-four card digits (Stripe holds the actual card). Subscription status, plan, and billing history.
• Product usage: alert profiles you build, decisions viewed, matches delivered, links clicked in briefs, session/login timestamps, and error logs.
• Communication: emails you send to our support, help, or billing addresses.

We do not collect the content of your case files, matters, or client data. We only see the alert profiles you configure and the decisions we deliver to you.

• To provide the service (deliver alerts, render the dashboard, enforce plan limits).
• To bill you and maintain payment records the IRS and Stripe require.
• To measure product usage in aggregate (feature adoption, performance) — not to sell or share individual behavior.
• To notify you of material product changes and terms updates.
• To respond to support requests.

We rely on a small set of vetted subprocessors. Each has a contractual obligation to process data only for our purposes.

• Vercel— web hosting + serverless functions (United States).
• Neon— managed Postgres for account, alert-profile, and decision data (United States).
• Stripe— payment processing and customer portal (United States, PCI-DSS).
• Resend (delivery backed by Amazon SES) — transactional email (magic-link authentication and alert briefs).
• Cloudflare— DNS and edge routing.
• OpenStreetMap— base map tiles for the alert-profile geographic bounds editor.

We do not sell your data. We do not share it with data brokers or marketing networks. We do not run behavioural advertising pixels.

We use privacy-friendly product analytics (Plausible) that measures page views and session counts in aggregate without individual tracking cookies or cross-site profiles. We use session cookies for authentication only. We do not deploy third-party ad cookies.

You can access, export, or delete your personal information at any time. Email privacy@hearingbrief.com and we will action the request within 30 days.

• Access / export: a JSON bundle of your account data, alert profiles, and delivered matches.
• Correction: update your account and onboarding fields directly in the dashboard.
• Deletion: we delete your account record and personally-identifying information from production databases within 30 days of request. Aggregate, de-identified usage metrics may be retained for capacity planning.
• Opt-out of product email:transactional alerts can be paused from the dashboard; billing and legal-notice emails are required as long as your subscription is active.

Meeting transcripts, agenda references, and extracted decisions we produce are retained indefinitely as part of the searchable corpus. That corpus is a record of public meetings and does not contain your personal information.

Your account, alert profiles, and delivery logs are retained while your subscription is active, plus 90 days for billing and audit reasons after cancellation. Payment records are retained for seven years per U.S. tax law.

All traffic to hearingbrief.com is served over TLS. Passwords are not stored — authentication is magic-link only. Payment card data is stored by Stripe, not by us. Database backups are encrypted at rest. We restrict administrative access to a small number of operators and log admin actions.

HearingBrief is a professional tool sold to attorneys, developers, and civic professionals. We do not knowingly collect personal information from anyone under 18.

If you are a California resident, you have additional rights under the CCPA/CPRA (right to know, right to delete, right to opt out of sale — we do not sell). If you are in the EEA/UK, you have GDPR rights (access, rectification, erasure, restriction, portability). Ramara LLC is the data controller. Email privacy@hearingbrief.com to exercise any of these rights.

We update this page when practices change. Material changes are emailed to your account address at least 14 days before they take effect. The date at the bottom of this page always reflects the current version.