Privacy Policy

Short version

• We are not building LawLinter to sell personal information.
• Most legislative, voting, lawmaker, committee, bill, law, CBO cost estimate, campaign-finance, lobbying disclosure, and Federal Register data shown here comes from public government source systems.
• Account information is used to operate accounts, subscriptions, API keys, saved preferences, and security controls.
• Essential cookies or browser storage support login, security, theme preferences, and cookie choices.
• Google Analytics may be used for aggregate traffic measurement only after analytics storage is enabled in cookie preferences. Google AdSense or similar neutral display ads may be used only where enabled and allowed by advertising preferences.

Information we process

LawLinter may process the following categories of information:

• Public legislative data from Congress.gov, including bills, laws, amendments, actions, summaries, committees, sponsors, cosponsors, votes, official text links, and related records.
• Public CBO cost estimate links and publication metadata when associated with bills through official Congress.gov records.
• Public campaign-finance data from FEC/OpenFEC when that source is enabled, including candidates, committees, candidate-committee relationships, filings, contributions, disbursements, and aggregate rollups.
• Public lobbying disclosure data from LDA.gov when that source is enabled, including registrants, clients, filings, lobbying activity descriptions, issue areas, lobbyists, government entities, source links, and bill references parsed from public filing text.
• Public Federal Register data from FederalRegister.gov when that source is enabled, including document metadata, agencies, CFR references, docket IDs, official URLs, PDF URLs, raw text/XML URLs, and Regulations.gov links.
• Account data you provide, such as email address, password hash, subscription status, API plan, API key metadata, and account preferences.
• Contact, report-issue, and email delivery data, such as name, email address, message content, source URL, template key, delivery status, unsubscribe or preference state, and provider event metadata.
• API usage data, including key prefix, route, method, status code, timestamps, quota counters, and request metadata needed for security, billing, and abuse prevention.
• Technical logs, such as IP address, user agent, request path, error logs, security events, and performance data.
• Cookie and browser-storage preferences, such as theme choice and whether optional analytics or advertising storage is allowed.
• Aggregate analytics data, such as page views, sessions, traffic sources, device/browser information, and broad location signals when Google Analytics is enabled by consent.

How we use information

• To provide public legislative search, detail pages, text navigation, voting history, affected-sector analysis, and related-record navigation.
• To operate accounts, login sessions, API access, subscriptions, quotas, and administrator controls.
• To send required transactional emails for account security, API access, billing, support, or administrative notices, and to honor unsubscribe or preference choices for optional email.
• To secure the service, prevent abuse, debug errors, monitor ingestion jobs, and keep the platform reliable.
• To provide optional analytics or advertising only where enabled and allowed by your preferences.
• To comply with legal, security, tax, payment, or operational obligations.

Cookies and browser storage

LawLinter separates storage into three categories:

You can reopen cookie preferences from the footer at any time.

Advertising and analytics

LawLinter may use Google Analytics to measure aggregate site usage, top pages, traffic sources, device/browser information, and similar website performance data. Google Analytics is loaded only after analytics storage is allowed in cookie preferences. LawLinter may use Google AdSense or similar services for a small number of neutral display ads on public pages. Those services may use cookies, web beacons, IP addresses, device identifiers, or similar technologies to serve, measure, and control ads. Optional advertising storage is controlled through the cookie preferences panel where required. LawLinter does not currently enable private political sponsorships, campaign ads, remarketing, Google signals, or ad personalization.

Sharing information

We do not sell personal information. Information may be shared only when needed to operate the service, such as hosting, database infrastructure, payment processing, email delivery, analytics, advertising, legal compliance, security investigations, or business administration. Public legislative, CBO cost estimate, campaign-finance, lobbying disclosure, and Federal Register records may be republished, indexed, linked, exported, or made available through APIs because those records originate from public source systems.

Public source data

LawLinter compiles public records from sources such as Congress.gov, the Congressional Budget Office, FEC/OpenFEC, LDA.gov, and FederalRegister.gov. Those records may include names, offices, votes, sponsorships, committee assignments, public contact information, CBO publication links, candidate records, committee records, campaign-finance records, lobbying registrants, lobbying clients, lobbyists, filing records, lobbying activity descriptions, Federal Register document metadata, agencies, CFR references, dockets, and public source links. Because these records come from public government sources, requests to correct or remove the underlying public record may need to be directed to the official source. LawLinter can still correct local display, linking, parsing, or attribution errors where appropriate.

Your choices

• You can use public search and public detail pages without creating an account.
• You can manage optional cookie preferences from the footer.
• You can use browser controls to block or clear cookies and local storage.
• If you create an account, you may request account access, correction, export, or deletion subject to legal, security, billing, and operational retention needs.
• API subscribers can revoke API keys from their account page.
• Optional marketing, product-update, saved-search, or alert emails should include unsubscribe or preference-management controls. Required transactional account, security, billing, and API notices may still be sent when needed to operate the service.

Retention and security

We keep account, API, billing, source-ingestion, and log records for as long as needed to operate, secure, debug, improve, and document the service. API keys are stored as hashes; raw keys are shown only once when created. No system can guarantee perfect security, but LawLinter is designed to minimize unnecessary personal data collection and keep sensitive operational data access-controlled.

Changes

This policy may change as LawLinter adds public pages, account features, API subscriptions, advertising, analytics, CBO context, FEC data, LDA.gov data, Federal Register data, exports, or other services. Material changes should be reflected on this page.

Contact

Privacy requests, account questions, security reports, and corrections to local parsing/display errors can be sent through the contact page.