Security & Data

Seamless AI data controls in a reviewable ledger

Use this operating checklist to document provenance, refresh cadence, permission scope, runtime behavior, retention, deletion, and the human gates that surround prospecting data.

Control ledger

Control areaRequired recordVerification methodStatus language
ProvenanceProvider, source context, field, and collection dateTrace a sample result back to its evidenceVerified / Config-dependent / Not disclosed
Refresh cadenceObserved date, expiry rule, and recheck triggerTest a known changed company or roleCurrent / Stale / Unknown
CredentialsSecret location, owner, scope, and rotation pathInspect runtime configuration without exposing valuesMinimum scope / Excess scope / Unknown
RuntimeNetwork calls, retries, logs, and output destinationsRun a sandbox task and review its activityObserved / Config-dependent
Retention & deletionStorage location, access, suppression, retention, and deletionCreate and delete a test record across destinationsVerified / Partial / Not tested
Human reviewReviewer, acceptance criteria, decision, and timestampAudit a rejected and an approved resultApproved / Rejected / Pending

Evidence checklist before production

Package review

  • Record the package version and test date.
  • Inspect installation prompts and requested permissions.
  • Confirm update and uninstall procedures.

Data review

  • Separate sourced facts, inferences, and unknowns.
  • Retain event dates and field-level provenance.
  • Test correction, suppression, and deletion.

Outreach review

  • Check role relevance and sensitive personalization.
  • Apply opt-out, suppression, and regional rules.
  • Require a named approver before sending.

Limitations

  • No claim of universal coverage or accuracy.
  • No guarantee of consent, delivery, replies, or fit.
  • Provider terms and data rights remain configuration-dependent.

This checklist is an operating control, not a claim of SOC 2, ISO, GDPR certification, or a legal conclusion. Validate current package behavior, provider documentation, and applicable regional requirements with qualified reviewers.

Verify the ledger in a sandbox

Use a known cohort that includes one clear match, one exclusion, one ambiguous identity, and one stale event.

npx -y @okki-global/okki-go-taroball