Apollo.io

www.apollo.iounclaimedrecord 222 · read 2026-09-05 · rules/v1evidence pack ↗
Trains on customer data
unclear
We may use information collected through the Services, including Contributor Database records and Usage Data, to train internal models.
privacy policysource ↗confidence 0.30
Opt-out mechanism
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.
privacy policysource ↗confidence 0.50
AI features
present
3.1 ARTIFICIAL INTELLIGENCE (AI), MACHINE LEARNING (ML), AND THE MCP SERVER
privacy policysource ↗confidence 0.55
Model providers named
Replicate
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.
dpasource ↗confidence 0.60
Retention
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.
dpasource ↗confidence 0.50
Hosting regions
not stated
Not stated in the documents we could read. An absence here is an unknown, not a no.
Subprocessor notice
30 days
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”).
dpasource ↗confidence 0.55

Downstream

Who's behind Apollo.io, as listed in its own subprocessor documents. 1 listed.

Model providers

  • Replicateunstated

Hyperscalers

  • none listed

Other subprocessors

  • none listed

Reviewer notes

Extracted by deterministic rules (rules/v1), no language model. Coverage is limited to recognisable clauses and a gazetteer of common subprocessors; absent values mean 'not matched', not 'not present'. training-adjacent sentence found but not classifiable by rules

Documents read

Document changes

No document changes yet. These appear when a later reading of a page differs from the previous one; no model involved.

Fact changes

No changes recorded yet. Changes appear here when a later reading differs from an earlier one.

Corrections

No correction requests. Anyone may dispute a fact with a source; requests and resolutions are public and ledger-entered.

Facts are as stated in Apollo.io's public documents on the date read. This is a record, not legal advice. Work for Apollo.io? Claim this profile · Something wrong? Request a correction.