Reporting a security issue
Last updated November 10, 2026.
Trimtab checks other people’s security, so its own has to hold up. If you think you’ve found a vulnerability in Trimtab, we want to hear about it, and we won’t treat good-faith research as an attack.
How to report
Email hello@gettrimtab.com with “Security report” in the subject. Please include:
- What you found and where (the URL, page, or file)
- Steps to reproduce it, and what an attacker could do with it
- Any proof-of-concept code, screenshots, or requests and responses
- How you’d like to be credited, if at all
If the details are sensitive, say so in a first email without them and we’ll arrange a secure way to send them. Machine-readable contact details are in security.txt.
What’s in scope
| Part | Where |
|---|---|
| The Bridge, the Trimtab dashboard | app.trimtabsec.com, including its API and Lookout check-in |
| Lookout, the device agent | The package downloaded from docs.trimtabsec.com, its update process, and the bulk deployment script |
| Microsoft 365 scanning | How Trimtab connects to, signs in to, and reads from a tenant |
| Websites | www.gettrimtab.com and docs.trimtabsec.com |
We’re especially interested in anything that lets one organization see another’s data, gets past sign-in or the authenticator code, runs code on a device through Lookout, or reaches a Microsoft 365 tenant in ways Trimtab shouldn’t.
What’s out of scope
- Denial of service, load testing, or anything that degrades the service for others
- Phishing, social engineering, or physical attacks on Trimtab or its customers
- Services Trimtab uses but doesn’t run, such as Microsoft Azure, Microsoft 365, Kit, and Squarespace. Report those to the provider.
- Reports from automated scanners with no demonstrated impact, such as a missing header or a version number
- Sending spam through the sign-up form
Testing rules
- Trimtab is invite-only. Ask us for a test organization rather than using someone else’s account.
- Only access data you need to show the problem. If you reach another organization’s data, stop, don’t keep or share it, and tell us right away.
- Don’t change or delete data that isn’t yours, and don’t run anything that changes a device or a Microsoft 365 tenant you don’t own.
- Give us a reasonable time to fix the problem before you tell anyone else about it.
Safe harbor
If you follow this policy, we consider your research authorized. We won’t take legal action against you or report you to law enforcement for it, and if someone else does, we’ll make it clear that you acted with our permission. If you’re unsure whether something is allowed, ask us first.
What to expect from us
- We’ll confirm we received your report within 3 business days.
- We’ll tell you whether we can reproduce it, and how serious we think it is, within 10 business days.
- We aim to fix confirmed issues within 90 days, sooner for serious ones, and we’ll keep you posted along the way.
- Once it’s fixed, we’ll describe the issue in the release notes and credit you if you’d like.
Trimtab doesn’t offer a paid bug bounty.