Security & Data
Verification data should remain traceable, scoped, and reversible
This ledger separates what the workflow can record from what depends on your runtime and connected provider. It makes no claim of certification and treats privacy controls as operating decisions that must be verified before production use.
Data handling ledger
| Control | Expected record | Status | Review gate |
|---|---|---|---|
| Provenance | Provider, check type, result state, and observed timestamp remain attached to the candidate. | Config-dependent | Reject exports that erase source or checked time. |
| Refresh cadence | Each result carries a freshness window selected for the campaign’s risk and timing. | Operator defined | Recheck stale records before reuse. |
| API credentials | Secrets stay in an environment store, outside prompts, repositories, exports, and screenshots. | Inspect locally | Use minimum scope and rotate exposed keys. |
| Professional data | Inputs are limited to relevant business identity and professional contact context. | Purpose limited | Do not use personal or sensitive data for convenience. |
| Retention | Temporary candidates, logs, exports, and rejected results have named owners and deletion periods. | Operator defined | Test correction, suppression, and deletion paths. |
| Human review | Valid, catch-all, and unknown states remain visible before CRM or sending handoff. | Required | A reviewer approves relevance and lawful use. |
Verification state is evidence about address risk, not proof of identity, consent, deliverability, or commercial interest. Catch-all domains may accept SMTP traffic without confirming an individual mailbox. Unknown results may reflect provider policy, throttling, greylisting, or transient network conditions. Preserve those distinctions so downstream automation does not convert uncertainty into confidence.
Operational trust checklist
- Review the package identity, requested permissions, network destinations, and update path before execution.
- Keep provider keys in scoped runtime secrets and prevent them from entering prompts or logs.
- Document result definitions and the conditions that produce valid, invalid, catch-all, or unknown.
- Apply suppression and opt-out records before a fresh technical verification result.
- Test who can access, correct, export, retain, and delete professional contact data.
- Separate mailbox verification from copy approval, authentication checks, and sending.
Inspect the controls in your own runtime
Begin with masked test records and a non-production credential. Verify data flow, errors, retries, retention, and deletion before connecting a real campaign.
npx -y @okki-global/okki-go-taroball