Privacy and Microsoft permissions.

What MailTrace does

MailTrace helps users build an investigation timeline from mailbox communications they choose to investigate.

What permissions are requested

• openid: Used to sign the user in.
• profile: Used to read basic profile information for the signed-in user.
• email: Used to identify the signed-in email address.
• offline_access: Used so the backend can maintain access after sign-in without repeated reconnection.
• User.Read: Used to confirm the signed-in Microsoft user identity.
• Mail.Read: Used to read mailbox messages selected or matched for investigation reconstruction.

What MailTrace does not request

• Mail.Send
• Mail.ReadWrite
• Mail.ReadWrite.Shared
• Application permissions
• Permission to send emails
• Permission to modify or delete emails

What MailTrace stores

• Selected or matched email metadata
• Subject
• Sender
• Recipients
• Timestamps
• Body text needed for investigation timeline reconstruction
• Generated events and timeline entries
• Participants and domains

What MailTrace does not do

• It does not send emails.
• It does not delete emails.
• It does not modify the mailbox.
• It does not read mail as a background daemon.
• It does not use application-wide tenant mailbox access.
• It does not sell user data.

User control

• The user signs in with Microsoft.
• The user activates a trace or investigation scope.
• The user can revoke app access from Microsoft account settings or Entra consent settings.

MVP note

MailTrace is currently an MVP. Users should only connect accounts they are comfortable testing with.