Openwake · evidence pack

Vanta

https://www.vanta.com · record 198 · read 2026-09-05 · 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.vanta.com/privacy · confidence 0.20
Opt-out mechanism
For more details about how Vanta uses these technologies, and your opt-out opportunities and other options, please see Vanta’s Cookie Policy.
“For more details about how Vanta uses these technologies, and your opt-out opportunities and other options, please see Vanta’s Cookie Policy.”
privacy policy · https://www.vanta.com/privacy · confidence 0.50
AI features
none stated
No supporting text found in the documents read.
privacy policy · https://www.vanta.com/privacy · confidence 0.20
Model providers named
none named
No supporting text found in the documents read.
privacy policy · https://www.vanta.com/privacy · confidence 0.20
Retention
1095 days
“8.3 Vanta shall maintain records sufficient to demonstrate its compliance with its obligations under this DPA, and retain such records for a period of three (3) years after the termination of the Agreement.”
dpa · https://www.vanta.com/legal/dpa · confidence 0.50
Hosting regions
not stated
No supporting text found in the documents read.
privacy policy · https://www.vanta.com/privacy · confidence 0.20
Subprocessor notice
10 days
“4.4 If Customer does not object to the engagement of a third party in accordance with Section 4.2 within ten (10) days of notice by Vanta, that third party will be deemed a Sub-Processor for the purposes of this DPA.”
dpa · https://www.vanta.com/legal/dpa · confidence 0.55

Subprocessors (0)

NameCategoryLocationQuoted from
None listed.

Sources read

DocumentURLReadContent hashLedger
privacy_policyhttps://www.vanta.com/privacy2026-09-059730fecd0ffbbd34…seq 130
dpahttps://www.vanta.com/legal/dpa2026-09-05ead8c7c6fcc61a1a…seq 191
Ledger proof for this record.
seq 405 · key 2f898a895f05b7a0 · 2026-09-06T01:39:47.420Z
hash e42cd227ccd005438db53e840f70afffafefb1bf8d74ac36e9c374ebde20261a
prev 6886804d44f30b5a712244334f63e1f1ac31cb1fbc0e697945fb76e869a7e54b
payload 0eec75ae8f3ef929f9b92dff163ae4053b7c9695cbf7c9342a60cd9ce3a60879
signature HfSkPmqBFhNL61xNLQ1gj3P2w2tlKpqV1rE8b4EWvoIls69C8/RZHbRACJLVMgvxWy1x+k8gEc5wD39zwtvYCQ==
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.