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 429 · key 2f898a895f05b7a0 · 2026-09-06T01:39:47.464Z hash 2cf188239663fe8f4537efa2be1f60c8c05a4b97abe15400fc67e6ee0a28960d prev 32ab1a37fcc0f53d535626cb9ac6a54931cda3a746ea99d5bee64e585de2eed1 payload 9fe8a54b22ba08f2d3d57d761a0585ff275a651b3a320990b0f97f9415fd99d7 signature xPKHhy4t2mzhz+cqyyqnYfOR8jyk0gMcYipwAVX3gf32EvcQ6YkBzMV1MHlFcOuZpQLU7ZExh/3tK+dfvpI4Bg== anchored 2026-09-06 at head seq 564 231a9dea0f93915bd7110e6786e00908325db3031635ace53c1023f850e0c49c 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.