Trimtab trust center
Trust and security
Last updated November 15, 2026.
Trimtab sees how your clients’ devices and Microsoft 365 tenants are set up, so you should know exactly how it’s run. This page answers the questions a vendor security review usually asks. For anything it doesn’t cover, email us and we’ll complete your questionnaire.
- Data location
- United States only
- Microsoft 365 access
- Read-only
- Every sign-in
- Password and authenticator code
- Staff access
- Only when you turn it on
At a glance
The controls Trimtab runs on itself, grouped by area. Each group links to the detail below.
Your data
- Stored in Microsoft Azure, in the US only
- A separate database for each organization
- Encrypted on disk and in transit, with HSTS
Signing in
- An authenticator code on every sign-in, staff included
- Sessions end on the server, after 24 hours at most
- A year of activity log, which owners can export
Trimtab staff
- No access to your data unless you grant it
- Grants expire within 7 days, and can be view-only
- Everything support does is in your activity log
Keys and secrets
- No secret or certificate for Trimtab’s Microsoft apps
- Signing keys held in Azure Key Vault, not exportable
- A daily check on both of Trimtab’s Microsoft apps
Lookout agent
- Reads settings only; no check changes a device
- Outbound HTTPS only, no open ports
- Installs only signed, newer updates
Backups and releases
- Nightly encrypted backups the server can’t read
- Backups can’t be changed or deleted for 30 days
- Automated tests gate every release
Where your data lives
- The Bridge and its data run in Microsoft Azure’s North Central US region (Illinois). Encrypted backups are copied to Azure’s paired US region. Nothing is stored outside the United States.
- Each organization’s results are kept in a separate database. Every request is tied to one organization, and the Bridge refuses to open data when it doesn’t know whose it is.
- Data is encrypted on disk by Azure and in transit with TLS. The Bridge sends HSTS so browsers only connect over HTTPS.
- What Lookout and Microsoft 365 scans collect, and what they never touch, is listed on the privacy page.
Subprocessors
These companies process customer data on Trimtab’s behalf.
| Company | What it does for Trimtab | Location |
|---|---|---|
| Microsoft (Azure) | Hosts the Bridge, its databases, backups, and the Key Vault keys that sign and encrypt | United States |
| Microsoft (Azure Communication Services) | Sends alert, invitation, sign-in reset, and policy acknowledgment emails | United States |
Kit handles sign-ups for product update emails on this website, and Squarespace hosts Trimtab’s DNS records. Neither receives anything from the Bridge. Alerts go to Teams, Slack, a webhook, or a PSA only when you set that up, and they go to the destination you choose. We’ll update this page before adding a subprocessor.
Signing in
- Every sign-in needs a password and an authenticator code, for customers and for Trimtab staff alike. Owners can let their team sign in with their work Microsoft account, and the authenticator code is still required.
- Passwords are stored as scrypt hashes, and device and invitation tokens only as hashes. Sessions end after 8 hours without use and after 24 hours at most. Signing out ends the session on the server, and a sign-in reset, a role change, or disabling an account ends that person’s sessions at once. Repeated failed sign-ins are slowed down, both per address and per account.
- Sign-ins, failed attempts, and every change in an organization are kept in its activity log for a year, with the IP address, and owners can export it.
What Trimtab staff can see
- Trimtab staff can’t open an organization’s data on their own. An Owner or Admin has to turn on support access, for 24 hours, 3 days, or 7 days, and can choose view-only. Everything support does appears in the organization’s activity log under the staff member’s name.
- Staff can’t invite people into an existing organization. A sign-in reset for a locked-out owner goes to that owner’s own email address, never to staff, and the organization’s other owners are told.
- Server administration is by SSH key only, from an allowed network address.
How Trimtab connects to Microsoft 365
A vendor that holds one powerful credential for many tenants is a target: if someone steals it, they can get into every one of them. So here is exactly what Trimtab’s access is, and what it isn’t.
- Trimtab uses one multi-tenant app, “Trimtab M365 Scanner,” which each tenant approves through Microsoft’s own consent screen. It is not a separate app per MSP.
- Its access is read-only: ten Microsoft Graph permissions that can only read, and Exchange Online access that works through the read-only Global Reader role you assign it (M365-026, below, fails if it has any other role). The full list says what each one is used for.
- It can’t manage apps or permissions, reset passwords or MFA, create or change accounts, or change any setting. It never reads email, files, chats, or calendars. Someone who took over the app could read configuration, but couldn’t take over a tenant or give themselves more access.
- There is nothing to steal. The app has no client secret and no certificate. It trusts one identity only, the Trimtab server’s own Azure managed identity, so no credential sits on the server, in a backup, or in a database.
- Trimtab checks both of its Microsoft apps every day: the scanner, and the one behind Sign in with Microsoft. Any added secret, certificate, federated credential, permission, or sign-in address alerts us at once.
- In your tenant, check M365-026 fails if Trimtab’s app holds more than read access, owns other apps, or has a credential added to it, so you can see this for yourself on every scan.
- You can disconnect a tenant from the Bridge at any time. To cut off access entirely, delete “Trimtab M365 Scanner” from the tenant’s Enterprise applications.
Keys and secrets
- Trimtab’s Microsoft apps, the Microsoft 365 scanner and Sign in with Microsoft, have no secret, certificate, or key. Each trusts only the Trimtab server’s Azure managed identity (workload identity federation), so there’s nothing to steal and reuse elsewhere.
- The keys that sign Lookout updates and protect saved alert secrets are held in Azure Key Vault and can’t be exported. Not even the server holds the private keys.
- Saved PSA passwords, API keys, and webhook secrets are encrypted, and a saved secret is only ever sent to the address it was saved for.
Lookout, the device agent
- Lookout only reads settings. No check changes a device.
- It makes outbound HTTPS connections only, and opens no ports. When it checks in, the only things it will do are remove itself or install a Trimtab-signed update.
- Updates install only if the package’s checksum matches, its RSA signature verifies against the public key Lookout already has, and its version is newer.
Backups and recovery
- Every night the Bridge backs up every database and its configuration. The backup is encrypted for a Key Vault key the server itself can’t use, so the server can’t read its own backups.
- Backups are stored in geo-redundant Azure storage, and they can’t be changed or deleted for 30 days, even by Trimtab. Each one is deleted after 120 days.
- A restore tool decrypts the latest backup and checks every database in it. Every release also takes a backup before it deploys.
Changes and releases
- Every release runs an automated test suite. It checks that every page renders, that organizations stay isolated, that sign-in works, and that Lookout check-in and removal work. The release stops if any test fails.
- Changes are listed in the release notes.
- Trimtab’s websites load nothing from other companies: no analytics, no trackers, and no third-party fonts or scripts.
Retention and deletion
- Scan history is kept while your account is active. Activity log entries are kept for a year.
- Ask us to delete a device, a client, or your whole organization, and we’ll do it. Copies remain in the encrypted backups until those age out, within 120 days.
Reporting a problem
If you think you’ve found a vulnerability, see Reporting a security issue, which covers scope and safe harbor. If you believe your data has been exposed, email hello@gettrimtab.com. We’ll tell affected customers promptly if we confirm an incident that involves their data.
Audits and certifications
Trimtab doesn’t have a SOC 2 report or other third-party certification yet. Until it does, this page, the privacy page, and the security documentation describe how Trimtab is run, and we’re glad to answer your security questionnaire.
- SOC 2 Type II reportNot yet
- Security questionnaireAnswered on request
- Vulnerability reporting, with safe harborOpen
Documents
Everything here is public. Nothing sits behind a request form.
- PrivacyWhat Trimtab collects and what it never touchesRead
- Reporting a security issueScope, testing rules, and safe harborRead
- Security documentationHow the Bridge and Lookout are built and runRead
- Release notesEvery change, by versionRead
- security.txtWhere to send a report, in the standard formatOpen