Skip to main content
Traversal is built on a foundation of strict data privacy. Your data is never shared with other customers, never used to train models, and never processed beyond the scope of your own investigations.

​
Core privacy principles

No cross-customer data use

Your data is never used for cross-customer training, model improvement, or service optimization.

In-context processing only

Any data processing is limited to in-context use for your organization only. Data from your investigations does not leave your context.

Strict isolation

All customer data is protected through strict tenant isolation, access controls, and privacy safeguards.

Read-only by design

Traversal cannot modify your systems or data. All integrations use read-only access only.

​
What data Traversal accesses

Traversal only accesses what is necessary to perform investigations. All access is read-only.
Traversal reads metrics, logs, traces, and alerts from your connected observability tools. This data is used in-context to perform root cause analysis and is not retained beyond the investigation.
Traversal requests read-only API access to your repositories to correlate deployment events and code diffs with incidents. Traversal has no write privileges to your codebase.
Traversal runs as a Slack app installed by a workspace administrator, and can only see channels the app has been added to. Within those channels it:
  • Reads conversation context — messages, threads, reactions, pinned items, shared files, and link previews — to understand the incident and any follow-up questions (app_mentions:read, channels:history, groups:history, im:history, mpim:history, channels:read, groups:read, im:read, mpim:read, reactions:read, pins:read, links:read, files:read).
  • Resolves requester identity — display name and email — to attribute requests and reports (users:read, users:read.email).
  • Posts back into Slack — investigation results, replies, reactions, uploaded report files, direct messages, and slash-command responses (chat:write, im:write, reactions:write, files:write, links:write, commands, incoming-webhook).
  • Joins channels it is invited to (channels:join).
These are messaging-surface permissions only. They do not grant Traversal any write or data-plane access to your connected systems.
Traversal runs as a Microsoft-approved Teams bot (an Azure AD app plus Azure Bot) installed by a Teams administrator. Your organization decides where it participates — it acts only on mentions, configured triggers, or Workers your team has enabled. In those conversations it:
  • Reads conversation context — the content of messages that mention or trigger the bot, thread context, and channel/team names, plus any attached files or images (ChannelMessage.Read.All, Team.ReadBasic.All, Channel.ReadBasic.All; Chat.Read.All only where 1:1 and group chats are in scope).
  • Resolves requester identity — the sender’s Azure AD user ID, display name, and email — to attribute requests (User.Read.All).
  • Reads membership, where enabled — who belongs to a channel or team (ChannelMember.Read.All, TeamMember.Read.All).
  • Posts back into Teams — authenticates as its registered app and posts investigation results into the originating channel or thread.
These are messaging-surface permissions only. They do not grant Traversal any write or data-plane access to your connected systems.
No agents are deployed in your environment. Traversal operates without sidecars or background processes running in your infrastructure.

​
Compliance alignment

Traversal aligns with the following compliance frameworks: Traversal also undergoes regular third-party penetration testing.
Visit the Traversal Trust Center to request compliance reports or review security documentation.

​
Contact

For questions about data privacy, compliance requirements, or to request detailed documentation, contact security@traversal.com.