This may include validating data accuracy, reconciling records across sources, suppressing records associated with opt-out or deletion requests, and generating business-contact and firmographic attributes for use in the Services.
“This may include validating data accuracy, reconciling records across sources, suppressing records associated with opt-out or deletion requests, and generating business-contact and firmographic attributes for use in the Services.”
“3. Online replicas and backups. Where feasible, production databases are designed to replicate data between no less than 1 primary and 1 secondary database. All databases are backed up and maintained using at least industry-standard methods.”
Within thirty (30) days of Apollo making a request available Customer will either: (a) permanently delete the affected individual's data from all systems within Customer's control, including CRM syste
“Within thirty (30) days of Apollo making a request available Customer will either: (a) permanently delete the affected individual's data from all systems within Customer's control, including CRM systems, enrichment workflows, API outputs, AI integrations, and other downstream repositories where data obtained through the Services may reside; or (b) document and retain a separate, independent legal basis for continued processing.”
“We will notify you of any changes concerning the addition of a new Subprocessor at least thirty (30) days before the new Subprocessor commences its Processing of Customer Personal Data (the “Notice”).”
“3. Online replicas and backups. Where feasible, production databases are designed to replicate data between no less than 1 primary and 1 secondary database. All databases are backed up and maintained ”
Ledger proof for this record. seq 28448 · key 2f898a895f05b7a0 · 2026-09-26T05:21:29.318Z hash fd231cdc1b1ef9b7eaafc470c1477646ceb60e508688864f2e96e24f95e93031 prev e3500cbe39bc91453f5253306632c3689a259728ad7f25c03fae04b62eb78b9e payload e8f64c31955632b4b5ba995a7788f89c5c00e14573f392242c45ca3e6a86958c signature pKtyKhS7LH57D+ZZcRtww/tHx7YlmHe+GY+frVfUGXO6RMx4EP7YSMc3vj1Aq4aV4rJg0T1yXZcsQq/SWrsZDQ== anchored 2026-09-26 at head seq 28468 bf0f8c19d80e9e7e77e3a49a367ad2bdfd4e2911477e5776af9cc6028307154b Fetch /v1/keys; for each ledger entry recompute sha256(prev_hash|kind|ref_id|payload_hash|created_at ISO) and verify the Ed25519 signature over that hash. Anchors are committed to git; compare the anchored head with the chain.