Openwake · evidence pack

Intercom

https://www.intercom.com · record 239 · read 2026-09-06 · rules/v1 · generated 2026-09-06 03:58 UTC

Facts

Trains on customer data
unclear
No supporting text found in the documents read.
privacy policy · https://www.intercom.com/legal/privacy · confidence 0.20
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 Serviceshyperscalerunstated
“* Customer Personal Data is encrypted at rest using 256-bit encryption, leveraging AWS’ encryption framework’s model C as described in https://d0.awsstatic..pdf”

Sources read

DocumentURLReadContent hashLedger
privacy_policyhttps://www.intercom.com/legal/privacy2026-09-059ebf901f569f35b7…seq 22
dpahttps://www.intercom.com/legal/data-processing-agreement2026-09-06a52573a30be69f44…seq 452
Ledger proof for this record.
seq 510 · key 2f898a895f05b7a0 · 2026-09-06T01:40:51.810Z
hash 447acf6cfecd0c8a3409b0aee7d6beb0996b16cdd7d5d68fe2dfa493e44db201
prev e27450e272b23c6cabcd5041db6d8390465b066264bb777bc21a900076e60d69
payload 7cf897f90372e8ec1eac5b60390f30fe149840d3cf4047cad8fcc81abd2449fc
signature DXnROP2dZiMSvnPOG8In8h3s/e5ORH9bqRMDLvnfOqL8vMXJhm68Jd6lw32UOlkRt3AznNKu6F5deSW7rLUjDw==
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.