Skip to content
Verdict

Privacy policy

Structure required

Section titled “Structure required”

1. Who we are and how to contact us

Section titled “1. Who we are and how to contact us”

2. Our roles

Section titled “2. Our roles”
  • Verdict is a processor for customer-supplied data: rosters, threads and ICP text.
  • Verdict is a controller for its own index of public business data and for account data.

3. Data we collect

Section titled “3. Data we collect”
  • Account data: email, organization, members, billing records (cards are handled by Stripe, never by Verdict).
  • Customer-supplied data sent in API requests.
  • Public business data in the index, from open-licensed sources only. Officer names from registers such as Companies House are public-record data, handled per the source’s rules.
  • No LinkedIn data from any source.

4. How we use it

Section titled “4. How we use it”
  • Counsel to draft. Outcomes and feature hashes may be pooled across opted-in orgs for calibration; no record, name, email, domain or text is ever pooled.

5. Retention

Section titled “5. Retention”
  • Decisions and outcomes: life of the org plus 90 days.
  • Request logs: 30 days, with emails, phone numbers and names redacted before storage.
  • Customer-supplied text: never stored past the request, except redacted in the 30-day log.
  • Raw public source files: kept indefinitely (public data).
  • Org deletion: within 30 days, confirmed by email.

6. Subprocessors

Section titled “6. Subprocessors”
  • See the subprocessors page.

7. Your rights and how to exercise them

Section titled “7. Your rights and how to exercise them”
  • A documented request path exists (docs/security/DSAR.md, to be written in WP16). Counsel to draft the public text.

8. International transfers

Section titled “8. International transfers”
  • Verdict runs in the US only. Counsel to draft.

9. Changes to this policy

Section titled “9. Changes to this policy”
  • Counsel to draft.