Security and data handling designed for sensitive contact data.
Application-level controls include encrypted sensitive blobs, private object storage, hashed API keys/sessions, RBAC, audit logging, HMAC cache keys, and signed webhooks.
Clean formatting, strip invalid characters, and resolve country destination codes.
Separate duplicates and fresh hits. Only charge for un-cached fresh verification.
Exact billable units frozen before paid job starts. Zero price surprises.
Details in our security documentation.
Details in our security documentation.
Details in our security documentation.
Details in our security documentation.
Details in our security documentation.
Details in our security documentation.
Details in our security documentation.
Details in our security documentation.
Frequently Asked Questions
Preflight normalizes inputs, detects invalid syntax, removes duplicate entries, and checks for eligible cached results before calculating your maximum frozen quote.
Every verification result contains freshness metadata, checked-at timestamps, and cache TTL indicators.
Cached results are used within your tenant isolation scope when within the service TTL. Fresh requests can be forced on demand.
Accounts use integer micros with zero-sum double-entry ledger accounting. Quotes are frozen at preflight, reserved atomically, and reconciled upon job completion.
Yes. Configure webhook endpoints with HMAC-SHA256 signature verification to receive real-time job completion events.
Data is processed strictly to fulfill your requested jobs. Sensitive payloads are encrypted at rest using AES-256-GCM.
Check your data before you process it.
Run a preflight first. See counts, routing and cost before processing.