# Report a security problem

> Found a way to see data that is not yours, or a link that still works when it should not? Where to send it, what to include, and what we do next.

Canonical page: https://finocket.com/help/report-a-security-problem
Last updated: 2026-08-16
Area: Modules & features

If you think you have found a security problem in Finocket (a way to see someone else's data, a page that lets you do something you should not be able to, a link that works when it should have expired), please tell us before you tell anyone else.

> Not sure whether it counts? Send it anyway.
>
> We would far rather read ten reports that turn out to be nothing than miss the one that was real. You do not need to prove it is exploitable, and you do not need to know the right words for it.

## Where to send it

Email **support@dmstfy.com**. The same address is published at [/.well-known/security.txt](https://finocket.com/.well-known/security.txt) in the format security researchers expect, and the full policy is at [Security & Responsible Disclosure](https://finocket.com/legal/security).

## What to tell us

- What you did, step by step, and what happened instead of what you expected.
- The screen, link or address involved.
- Roughly when it happened, so we can find it in our logs.
- A screenshot if you have one, but see the warning below.

> Do not send us someone else's data
>
> If you reached information belonging to another business, stop there and describe what you saw rather than collecting more of it to prove the point. Blank out anything identifying in a screenshot. One example is enough for us to reproduce it; a folder of exports is not, and it puts that business at more risk.

## What happens next

1. We acknowledge your email.
2. We tell you whether we think it is a real vulnerability, and why.
3. We keep you updated while we fix it, and tell you when it is fixed.
4. We credit you if you would like that, and stay quiet about you if you would not.

There is no paid bug-bounty programme. We would rather say so plainly than let you spend a weekend on it expecting a reward that is not there.

## If it is your account rather than a bug

If you think someone else has got into *your* account (an unfamiliar sign-in, entries you did not make), that is urgent and different. Change your password first, then write to us with roughly when you noticed. Security alerts about new sign-ins and password changes are the one kind of notification that cannot be switched off, so check those too. See [Notifications](https://finocket.com/help/notifications).

## Please do not

- **Run load or denial-of-service tests.** Real businesses invoice and file returns through this service; taking it down is an outage for them.
- **Phish our staff** or try to talk your way into an account.
- **Post it publicly first.** Give us a reasonable chance to fix it.

Follow that and we treat your research as authorised: we will work with you and will not pursue legal action over it.

## Frequently asked questions

### Is there a bug bounty?

No. There is no paid programme, and we say so plainly rather than let you spend a weekend on it expecting a reward that is not there. We will credit you publicly if you would like that.

### What if I am not sure it is a real problem?

Send it anyway. We would rather read ten reports that turn out to be nothing than miss the one that was real, and you do not need to prove it is exploitable.

### Someone else has got into my account. Is that the same thing?

No, that is urgent and different. Change your password first, then write to us with roughly when you noticed. Alerts about new sign-ins and password changes are the one kind of notification that cannot be switched off.

### Can I test how much load the system takes?

Please do not. Real businesses invoice and file returns through Finocket, so a load or denial-of-service test is an outage for them rather than a demonstration.

---
This is the Markdown copy of https://finocket.com/help/report-a-security-problem, published by Demystify Systems LLP. It is not a separate page: cite the canonical page.
