trustyourinbox

Found a security bug? Tell us first.

Report it privately and we fix it and pay a discretionary cash reward for a valid finding. A finding above informational is credited here if you want the credit. Send it through the form or in one email, with the steps to reproduce it. Test on a free account of your own: we do not provide test accounts.

Six hosts in scope. The tenant boundary matters most.

The product is multi-tenant, so a way to read or change another workspace's data is the finding we care about most, and the one that pays most. These hosts and issue classes are the whole scope.

Hosts

  • trustyourinbox.comThe marketing site and the free tools
  • app.trustyourinbox.comThe signed-in dashboard
  • api.trustyourinbox.comThe REST API under /v1
  • mcp.trustyourinbox.comThe MCP server and its token auth
  • support.trustyourinbox.comThe support portal: tickets and attachments, signed in
  • docs.trustyourinbox.comThe product documentation, signed in

Issue classes

  • Cross-tenant access. Reading or writing another workspace's data.
  • Authentication or session bypass, or privilege escalation to staff or operator.
  • Remote code execution, SQL injection, SSRF.
  • Stored or reflected XSS, and CSRF on an action that changes state.
  • Insecure direct object references and broken access control.
  • Exposed secrets, tokens or credentials.

Out of scope. Not bugs, or not ours.

A report in the first list is closed as out of scope. A report in the second is informational. It pays the Low reward when we ship a fix for it, and nothing when we do not. It is never credited on this page.

Closed as out of scope

  • Denial of service, volumetric or load-generating attacks of any kind.
  • Social engineering or phishing of our team, customers or vendors.
  • Physical attacks, or anything aimed at people rather than systems.
  • Automated scanner output with no working proof of concept.
  • Rate limits on the free tools. They are there on purpose.
  • Mail sent as a domain we monitor. Seeing that is the product, not a bug in it.
  • Self-XSS, or login and logout CSRF.
  • Vulnerabilities in a vendor we use. Report those to Cloudflare, Clerk, Stripe or Neon directly.

Informational

  • Sessions that stay valid after a password change or a sign-out.
  • Missing security headers or best-practice findings with no demonstrated impact.
  • SPF or DMARC records on our own domains.
  • Account enumeration, telling from sign-in or password reset whether an email address has an account.
  • Missing rate limits outside sign-in, sign-up and password reset.
  • Banner and version disclosure, such as a server or library version in a response.
  • Reverse tabnabbing from a link that opens a new tab.
  • Clickjacking on a page with no sensitive action.

Eight rules. Then you are covered.

Follow these and the safe harbor below applies. They come down to one idea: test what is yours, stop at proof, and give us time to fix it.

  1. Act in good faith. Do not access, change or delete data that is not yours.
  2. Test against your own account, workspace and domains. Never pivot into another tenant.
  3. Sign up for that account yourself. It is free. We do not provide test accounts, credentials, plan upgrades, trial extensions or seeded data for research.
  4. Paid-plan features are in scope only on a plan you pay for.
  5. Stop at proof of concept. Do not pull out more data than the issue needs to show.
  6. Do not degrade service. No high-volume automated testing against production.
  7. Give us reasonable time to fix before any public disclosure. 90 days is the norm.
  8. One vulnerability per report, unless you need to chain issues to show impact.

Safe harbor. For research done in good faith.

The research exception to the Acceptable Use Policy, which otherwise bans probing for vulnerabilities. It holds as long as you stay within scope and the rules above.

  • If you make a good-faith effort to follow this policy during your research, we will consider it authorized. We will not pursue or support legal action against you for accidental, good-faith violations.
  • If a third party brings legal action against you for research that complied with this policy, we will make it known that your actions were authorized.
  • The narrow research exception here overrides the Acceptable Use Policy's general ban on probing for vulnerabilities, as long as you stay within scope and the rules above.

Rewards and credit. Discretionary, and paid.

We pay cash for a valid vulnerability, at one of four severities. Which severity a finding gets, and the reward within it, are at our discretion. A clean write-up with a working proof of concept is worth more than a vague one.

Severity

  1. Low. Little impact on its own. For example, an open redirect, or text you control showing as a link in an email we send.
  2. Medium. Harm that needs someone else to act, such as opening a link. For example, stored or reflected XSS, or CSRF on an action that changes state.
  3. High. Serious harm inside one workspace. For example, a member doing what their role does not allow, SSRF that reaches an internal service, or an exposed secret or token that opens access.
  4. Critical. Harm across workspaces or to our systems. For example, reading or changing another workspace's data, bypassing authentication, acting as our staff, or running code on our servers.

Payment and credit

  • One reward per root cause, to the first valid report of it.
  • Paid after the fix is live, by a method we agree with you.
  • A valid finding above informational is credited on this page, by name or handle, if you want the credit. An informational finding is not credited.

How to report. And what happens next.

Use the form below or email security@trustyourinbox.com. We acknowledge every report within two business days, confirm the issue and its severity, and keep you posted through the fix. Once it is patched and any reward is settled, you are clear to disclose.

An email asking for a test account, credentials, an upgrade or a longer trial gets no account. Sign up free and test your own.

Here is the file at /.well-known/security.txt, where a scanner or a researcher looks first.

trustyourinbox.com/.well-known/security.txt
# We do not provide test accounts. Sign up free and test your own.
Contact: mailto:security@trustyourinbox.com
Expires: 2027-09-01T00:00:00.000Z
Policy: https://trustyourinbox.com/bug-bounty
Acknowledgments: https://trustyourinbox.com/bug-bounty
Preferred-Languages: en
Canonical: https://trustyourinbox.com/.well-known/security.txt

A good report includes

  • What the issue is and what it lets someone do.
  • The steps to reproduce it, with a working proof of concept.
  • The URL, API call or screenshot it affects.
  • Your name or handle, if you would like the credit.

Send a report

It goes to a private queue only we read. You get an email confirmation right away, and every reply after that comes by email.

One line that names the finding, for example: SSRF through the MTA-STS checker.
What the issue is and what it lets someone do, then each step from a fresh account.
A request and its response, a script, or a link to a video.
Where the confirmation and every reply go.
Leave it empty if you do not want the credit.
A profile to link from your name.

Test what is yours. Start with a workspace of your own.

Free for one domain, no card. The rules ask you to test only your own account and domains; this is where you get them.

  1. Monitoring
  2. Quarantine
  3. Reject