Lattice

lattice.comunclaimedrecord 688 · read 2026-10-20 · rules/v1evidence pack ↗
Does your organization use Lattice? One sensor, and Openwake watches it on its own: the documents re-read daily, every moved clause told.Start free
Trains on customer data
Training posture: unknown · the documents do not say
silence is not a no
Not stated in the documents we could read. An absence here is an unknown, not a no.
Opt-out mechanism
You can opt out of allowing us to collect this information either by refusing access to the information or by disabling your Location setting on your device.
“You can opt out of allowing us to collect this information either by refusing access to the information or by disabling your Location setting on your device.”
privacy policysource ↗confidence 0.50
AI features
present
“This may include analyzing your usage and interactions using AI-powered tools.”
privacy policysource ↗confidence 0.55
Model providers named
OpenAI
“OPENAI * Services provided: AI models in support of Lattice’s AI-powered features”
subprocessorssource ↗confidence 0.60
Retention
not stated
Not stated in the documents we could read. An absence here is an unknown, not a no.
Hosting regions
not stated
Not stated in the documents we could read. An absence here is an unknown, not a no.
Subprocessor notice
not stated
Not stated in the documents we could read. An absence here is an unknown, not a no.

Downstream

Who's behind Lattice, as listed in its own subprocessor documents. 22 subprocessors.

Model providers

  • OpenAIunstated

Hyperscalers

  • Amazon Web Servicesunstated
  • Google Cloudunstated

Other subprocessors

  • Atlassianunstated
  • Cloudflareunstated
  • Datadogunstated
  • Fivetranunstated
  • Gongunstated
  • Intercomunstated
  • Lookerunstated
  • Loomunstated
  • Mailgununstated
  • Pendounstated
  • Qualtricsunstated
  • Segmentunstated
  • Sentryunstated
  • Slackunstated
  • Splunkunstated
  • Twiliounstated
  • Zendeskunstated
  • Zoomunstated
  • Zscalerunstated

Reviewer notes

Extracted by deterministic rules (rules/v1), no language model. Coverage is limited to recognisable clauses and a gazetteer of common subprocessors; absent values mean 'not matched', not 'not present'. no training clause matched

Documents read

Document changes

Fact changes

No changes recorded yet. Changes appear here when a later reading differs from an earlier one.

Corrections

No correction requests. Anyone may dispute a fact with a source; requests and resolutions are public and ledger-entered.

Facts are as stated in Lattice's public documents on the date read. This is a record, not legal advice. Work for Lattice? Claim this profile · Something wrong? Request a correction.