Legal
Vulnerability Disclosure Policy
Last updated
If you have found a security vulnerability in Unitpost, we want to hear about it. This policy says how to report it, what you may test and how, what we do with your report, and how we protect you when you research in good faith.
Report vulnerabilities to security@unitpost.com.
01How to report
Email security@unitpost.com, in English or Russian. A useful report includes:
- the affected URL, API endpoint, MCP tool, SDK or CLI version;
- the steps to reproduce it, with the requests and responses that show it;
- what an attacker could do with it, as you understand it;
- how to reach you, and the name you would like credited, if any.
Keep personal data out of the report beyond what is needed to show the problem. If you need to send something sensitive, say so in a first email and we will agree on a way.
Spam or abuse sent through Unitpost is not a vulnerability: report it as the Acceptable Use Policy describes, to legal@unitpost.com.
02Scope
In scope:
- unitpost.com and its subdomains that we operate (the website, the dashboard, the MCP server);
- the public REST API under /api/v1 and our SMTP relay;
- our SDKs, CLI and agent skills, as published by us.
Out of scope:
- services we use but do not run (hosting, database, payment and messaging providers): report those to the provider;
- our customers’ own domains, websites and the content of the messages they send;
- findings without a demonstrated security impact, such as a missing header on a page with nothing sensitive, clickjacking of a page with no action to click, self-XSS, version banners, or email-authentication (SPF, DMARC) policy suggestions on their own;
- denial of service, and findings that need a compromised device or account to begin with.
03Rules for testing
- Test only against accounts and workspaces you own or are allowed to use. Never access, change or delete another customer’s data. If you reach data that is not yours, stop, keep no copy, and tell us.
- Do not send email or SMS to anyone who has not agreed to receive it, and stay within your plan’s sending limits. Test sends to your own addresses and numbers are fine.
- No denial-of-service or load testing, and keep automated scanning slow enough that it cannot degrade the service for others.
- No social engineering, phishing or physical attempts against our staff, offices or customers.
- Show the vulnerability with the least access and data you need, then stop.
- Keep the details confidential until we have fixed it, as described under Public disclosure.
04What we commit to
- We confirm that we received your report within 3 business days.
- We send our first assessment within 10 business days, and keep you updated as we work on it.
- We aim to fix confirmed vulnerabilities within 90 days, sooner for severe ones.
- We tell you when it is fixed, and credit you publicly if you want us to.
05Safe harbor
If you make a good-faith effort to follow this policy, Work Reactor Inc. considers your research authorized. We will not pursue or support legal action against you for it, and will not report it to law enforcement. If a third party takes legal action against you over research done under this policy, we will make it known that you acted with our authorization.
If you are unsure whether something you plan to do is allowed, ask us at security@unitpost.com before you do it.
06Public disclosure
We ask you to give us a chance to fix the problem before you share it. We will agree a disclosure date with you; unless we agree otherwise, you may publish 90 days after your report, or as soon as the fix is out if that is earlier.
07Rewards
We do not run a paid bug bounty at this time. With your permission, we thank the people who report valid vulnerabilities by name.