Openwake · evidence pack

Intercom

https://www.intercom.com · record 708 · read 2026-10-22 · rules/v1 · generated 2026-10-23 04:11 UTC

Facts

Trains on customer data
unclear
“We use publicly available online information as part of our AI model training.”
privacy policy · https://www.intercom.com/legal/privacy · confidence 0.30
Opt-out mechanism
* You have the right to opt-out of marketing communications we send you at any time.
“* You have the right to opt-out of marketing communications we send you at any time.”
privacy policy · https://www.intercom.com/legal/privacy · confidence 0.50
AI features
present
“* Artificial intelligence: We, our service providers and the third parties we work with may use artificial intelligence (AI) and machine learning technologies, including generative AI, to facilitate the processing of personal information described in this Privacy Policy.”
privacy policy · https://www.intercom.com/legal/privacy · confidence 0.55
Model providers named
none named
No supporting text found in the documents read.
privacy policy · https://www.intercom.com/legal/privacy · confidence 0.20
Retention
30 days
“Customer may request to Intercom to delete all Customer Personal Data, and Intercom will proceed to delete the data as soon as reasonably practicable and within a maximum period of 30 days from Customer’s written request.”
Hosting regions
United States
“6.1The Intercom Services and Sites, and our messenger domains are provided and hosted in the United States.”
privacy policy · https://www.intercom.com/legal/privacy · confidence 0.50
Subprocessor notice
20 days
“If Customer reasonably objects to the appointment of a new Sub-processor within twenty (20) days of receiving such notice, on reasonable grounds relating to the protection of the Customer Personal Data, then Intercom will work in good faith with Customer to find an alternative solution.”

Subprocessors (1)

NameCategoryLocationQuoted from
Amazon Web ServiceshyperscalerUSA
“* Physical Access Control. Intercom’s services and data are hosted in AWS’ facilities in the USA, EU or Australia, as applicable, based on the applicable data hosting region) and protected by AWS in a”

Sources read

DocumentURLReadContent hashLedger
privacy_policyhttps://www.intercom.com/legal/privacy2026-10-22ce0015ad670d8d6c…seq 64167
dpahttps://www.intercom.com/legal/data-processing-agreement2026-10-2246e52e0f6120df2d…seq 64168
Ledger proof for this record.
seq 64183 · key 2f898a895f05b7a0 · 2026-10-22T05:19:28.048Z
hash a2128e21b1b23dcdde53a581b24b6547e3dbc09ca532f9cafd247ade2dcd3025
prev f0bde867294d7e705583967428354c114808031c0edb0f149219fbfbcb915d30
payload 58c139c57fd2803f8500aa01d031e98870cb911c2c23c751cff123582f5387a6
signature 4Zj+estScyNDfqr3PNE512bzpD3o/Rs7s1QaeUXrqTPe9nOgb9dHeSkDHrWLMHMw/HttNl9Zrdq5kgRoWlTmDw==
anchored 2026-10-22 at head seq 64204 68332ccffa8b4c79780bf1a01284351ca72309d4c1746ababe798f1ed346c99d
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.