Does your organization use Apollo.io? One sensor, and Openwake watches it on its own: the documents re-read daily, every moved clause told.Start free
Trains on customer data
Training posture: unknown · the documents do not say
silence is not a no
“We may use information collected through the Services, including Contributor Database records and Usage Data, to train internal models.”
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.”
AI features
present
“3.1 ARTIFICIAL INTELLIGENCE (AI), MACHINE LEARNING (ML), AND THE MCP SERVER”
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.”
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.”
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”).”
Downstream
Who's behind Apollo.io, as listed in its own subprocessor documents. 1 subprocessor.
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
- privacy policy https://www.apollo.io/privacy-policyHTTP 200 · 2026-09-26
- dpa https://www.apollo.io/dpaHTTP 200 · 2026-09-26
Document changes
- high 2026-09-26 · dpa +9 / −0 lines
show diff
+ Table of Contents+ DEFINITIONS.+ DATA PROCESSING.+ SUBPROCESSORS.+ DATA SECURITY, AUDITS, AND SECURITY NOTIFICATIONS; DELETION AND RETENTION.+ ACCESS REQUESTS AND ASSISTANCE WITH COMPLIANCE.+ ARTIFICIAL INTELLIGENCE AND AUTOMATED DECISION-MAKING.+ CONTROLLER OBLIGATIONS.+ DATA TRANSFERS. - high 2026-09-26 · privacy policy +12 / −0 lines
show diff
+ Table of Contents+ 1. What you should know+ 2. How we collect information+ 3. How we use your information+ 4. How we share your information+ 5. Your choices+ 7. Data retention+ 8. Third-party links and services+ 10. International data transfers+ 11. Information for Residents of the European Economic Area, the UK, and Switzerland+ 12. Changes to this policy+ 13. Contact us
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.