Openwake · evidence pack

Cognition

https://cognition.com · record 548 · read 2026-10-13 · rules/v1 · generated 2026-10-23 04:08 UTC

Facts

Trains on customer data
opt_out
“Following an Opt-Out election: (A) Customer Data will not be used for any other purpose, including training language models; and (B) Zero Data Retention will be enabled with our model providers.”
Opt-out mechanism
If you subscribe to a paid Service Tier, you may opt out of this use (“Opt-Out”).
“If you subscribe to a paid Service Tier, you may opt out of this use (“Opt-Out”).”
AI features
present
“You acknowledge that Outputs are generated automatically by machine learning technology and may be similar to or the same as Outputs provided to other customers; no rights to any Outputs generated for or provided to other customers are granted to you under these Terms.”
Model providers named
none named
No supporting text found in the documents read.
privacy policy · https://cognition.com/legal/privacy-policy · confidence 0.20
Retention
not stated
No supporting text found in the documents read.
privacy policy · https://cognition.com/legal/privacy-policy · confidence 0.20
Hosting regions
not stated
No supporting text found in the documents read.
privacy policy · https://cognition.com/legal/privacy-policy · confidence 0.20
Subprocessor notice
15 days
“If Customer objects to a newly added Subprocessor on reasonable grounds relating to the protection of Customer Data, Customer must notify Licensor in writing within fifteen (15) days of receiving notice of the new Subprocessor.”

Subprocessors (2)

NameCategoryLocationQuoted from
Oktaotherunstated
“* Licensor uses single sign-on (SSO) to authenticate to third-party services. Role Based Access Controls (RBAC) are used when provisioning internal access to the Services via Okta;”
Amazon Web Serviceshyperscalerunstated
“* Keys for cryptographic protected are securely managed and stored in AWS KMS;”

Sources read

DocumentURLReadContent hashLedger
privacy_policyhttps://cognition.com/legal/privacy-policy2026-10-13891ec13e7cdd6807…seq 53305
subprocessorshttps://cognition.com/legal/data-processing-statement#subprocessors2026-10-13c5c0db0c4bac7c33…seq 53306
termshttps://cognition.com/legal/platform-terms-of-service2026-10-13761810f6c2c3ae4d…seq 53307
ai_policyhttps://cognition.com/legal/acceptable-use-policy2026-10-138f214bf395fbc544…seq 53308
Ledger proof for this record.
seq 53327 · key 2f898a895f05b7a0 · 2026-10-13T05:19:25.963Z
hash 6e7f16d1b6642f614e6d3da91ff6c684e04f2337bca8a832ed563a33107d71eb
prev 274d5f8a96c350975c8a349e10f3121ce1ec274d37b5b5a120eb70a71efa8da6
payload 763c861c4a3d297fc31cfd030b1e00cced8ca4614080fb9d5c41cf28ad83fea0
signature vM3eNS3BDxc/NiusgK8EWL8Xv4NgaF+8EAGvPXiRIrof2faxrV4vm8uE7s+jwQ6DQXo71bcGXERfdi9UL/jgBA==
anchored 2026-10-13 at head seq 53553 29b831e17d49be9d0c48e24c727cfa82ce9b500faacabb488dae167a42404d31
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.