Data sources & retention

• Serper.dev (Google Search)
  What we collect: Public web snippets, news headlines, scholar citations, knowledge-graph metadata.
  Legal basis: Public web; per Serper.dev Terms of Service.
  Retention: Raw snippets: 180 days (rolling). Synthesized payloads: indefinite.
• LinkedIn (via public Serper indexing)
  What we collect: Publicly-indexed profile titles + snippets. Pano never authenticates to LinkedIn or scrapes the site directly.
  Legal basis: hiQ v. LinkedIn precedent (public web); we honor LinkedIn's user-export rights.
  Retention: Snippets: 180 days. Org-chart layered facts: indefinite.
• SEC EDGAR (sec.gov)
  What we collect: Filings, 8-Ks, S-1/S-4s referenced in M&A signal extraction.
  Legal basis: Public-domain government filings.
  Retention: Indefinite.
• Issuer press releases / IR pages
  What we collect: Press releases linked from /news endpoint and IR-team pages used for leadership-page extraction.
  Legal basis: Public domain; press releases are explicitly distributed.
  Retention: Indefinite for derived signals; 180 days for raw text.
• Crunchbase (planned, Wedge 3+)
  What we collect: Investor relationships, funding rounds, board seats. Used as a fallback when Serper snippets lack structured data.
  Legal basis: Crunchbase Enterprise API license (per-tenant).
  Retention: Per Crunchbase contractual terms.
• User-supplied watchlists
  What we collect: Customer-defined cohorts (slugs only). NEVER PHI/PII.
  Legal basis: Customer ownership; processed under DPA.
  Retention: Until customer deletes the watchlist.

• Raw web snippets180 days rolling
  Re-derivable from Serper on demand. Bounded retention reduces blast radius.
• Derived M&A / C-Suite signalsIndefinite
  Analyst-grade outputs the customer paid for; deletion-on-request honored within 30 days.
• Audit logs (Supabase)365 days
  SOC 2 control window.
• Slack/email digest payloads90 days
  Sufficient for re-delivery + dispute resolution; minimizes secondary copy of customer data.
• User authentication tokensSession lifetime + 14 days
  Standard Supabase Auth refresh-token window.

• Protected Health Information (PHI) — Panopticon is not a HIPAA-covered entity or business associate. Do not paste PHI into any Pano surface.
• Personally Identifiable Information (PII) beyond what is already public (e.g. an executive's name and title in a press release).
• Customer financial account numbers, credentials, or cryptographic secrets.
• Any data behind a paywall or authentication where Pano lacks an explicit license.

Panopticon is targeting SOC 2 Type II by Day 100 of the Op 1 plan. Current controls in place: Supabase audit logs (365-day window), service-role-only RLS on all customer-data tables, encrypted secrets in environment variables, idempotent delivery for all outbound channels, and 14-day backup retention. Full attestation packet available on request.