Privacy & data limits

When configured, the access form stores a work email, submitted product URL, review state, and hashed IP and user-agent values in Supabase so an operator can review the invitation. If the store is not configured, the form reports that nothing was saved.

Submitting that form asks us to review the invitation and respond about it. It is not consent to general marketing or an automated email sequence.

• Supabase provides authentication and is the business system of record for organization, project, evidence, proposal, and manual Pipeline records.
• Product research starts from submitted or first-party public webpages. The application records source URLs and fetch times so claims can be traced to their evidence.
• The worker can use Firecrawl when that provider is configured to map or fetch permitted public pages. It does not bypass logins, paywalls, or access controls.
• The worker can send bounded public-source evidence to DeepSeek when that provider is configured, for structured extraction, constrained explanations, and proposal drafts. Models do not set match scores, approve work, or send outreach.

PostHog is an optional server-side product-events destination only when a deployment enables it. The event payload is limited to approved operational fields; it is not the business source of truth.

M4 click, conversion, redirect, and attribution tracking are not implemented in this alpha. We do not represent page visits, match scores, or manual Pipeline records as conversion measurement.

Raw public-page snapshots are written with a 30-day expiry timestamp. The repository does not include a scheduled purge worker, so that timestamp is not evidence that raw content has been erased. Workspace records and access requests do not currently have a public self-service export, erasure, or data-subject-request workflow.

Before relying on an automated retention or deletion promise, the service needs a verified operational process. For a factual correction or a request to stop contact, use the process on Contact & corrections.

Email privacy@partnerradar.app for access-request questions, factual corrections, or a request to stop contact. Do not include credentials, customer data, or other sensitive information.