Privacy Policy

Contract Renewal Radar uses public procurement records and the minimum business information needed to operate a customer's contract radar.

Public records

Contract records, award history, vendors, values, and dates come from linked public government sources. Contract Renewal Radar stores source fingerprints and verification state so a customer can distinguish official evidence from our analysis.

Customer information

A customer profile may contain a company name, business contact, service capabilities, certifications, contract-size preferences, and operating constraints. The product does not need consumer information, employee rosters, credentials for government portals, or proposal documents.

Accounts, billing, and alerts

An essential authentication cookie keeps signed-in accounts secure. Azure Communication Services delivers account confirmation, password recovery, email-change confirmation, and source-backed radar messages to the customer's account email. Stripe processes subscription checkout and payment details. Contract Renewal Radar stores Stripe customer, subscription, Checkout session, checkout-attempt, and webhook-event identifiers; webhook event types; billing lifecycle timestamps; and the resulting access status. It does not store full payment-card details. Customers can turn radar alerts off in their fit profile.

Shared briefs

A published brief uses an expiring, revocable link. The raw access token is not stored. Anyone who receives the link may be able to view the brief until it expires or is revoked, so customers should treat it as confidential business information.

Deletion and export

The operator can export a customer's profile and briefs. Deleting a customer removes customer-specific records and revokes shared briefs while preserving public contract history.