Openwake · evidence pack

Navan

https://navan.com · record 333 · read 2026-09-17 · rules/v1 · generated 2026-10-23 04:21 UTC

Facts

Trains on customer data
unclear
No supporting text found in the documents read.
privacy policy · https://navan.com/privacy · confidence 0.20
Opt-out mechanism
For more details about how we use these technologies, and your opt-out opportunities and other options, please see our Cookies Policy.
“For more details about how we use these technologies, and your opt-out opportunities and other options, please see our Cookies Policy.”
privacy policy · https://navan.com/privacy · confidence 0.50
AI features
present
“Navan Services may support integration with external, third-party artificial intelligence assistants, local applications, and development tools via open protocols such as the Model Context Protocol (MCP).”
privacy policy · https://navan.com/privacy · confidence 0.55
Model providers named
none named
No supporting text found in the documents read.
privacy policy · https://navan.com/privacy · confidence 0.20
Retention
not stated
No supporting text found in the documents read.
privacy policy · https://navan.com/privacy · confidence 0.20
Hosting regions
not stated
No supporting text found in the documents read.
privacy policy · https://navan.com/privacy · confidence 0.20
Subprocessor notice
15 days
“From time to time, Navan may engage new subprocessors and, in accordance with this DPA, upon request will provide Customer notice of any new subprocessor at least 15 days in advance of providing that subprocessor with access to the Customer Personal Data (the “15-day notice period”).”
dpa · https://navan.com/dpa · confidence 0.55

Subprocessors (0)

NameCategoryLocationQuoted from
None listed.

Sources read

DocumentURLReadContent hashLedger
privacy_policyhttps://navan.com/privacy2026-09-164cf8c8e9a53e4bd2…seq 11000
dpahttps://navan.com/dpa2026-09-17fd3b5af57bb7cac4…seq 12451
Ledger proof for this record.
seq 12466 · key 2f898a895f05b7a0 · 2026-09-17T05:21:55.403Z
hash d88591e1f7be4735763fa4f2aac03b781698fbc47b290d218d3cd68ba0c22b5e
prev cb6cad1e92c62042bd5b6281ca69f774e80d8b05d329c332de79d60ad33a7967
payload 7ddb22418a3aa42839e240bc0b8f6f2fbc5dd5de9077a5a8ee3efefd9ee32d83
signature gZQ5wnIFkabo+FOaHzgtTXa0FnoBqyGJMenni5WjTciHvNvT19HSc3sE3AfY4fSdDtuTq7PF+OVIz8T733SFCA==
anchored 2026-09-17 at head seq 12488 310de7dd74be73d19e1b64b099c94eefddf0701a84f83f2656ac440b8edeefc9
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.