Vulnerability disclosure
Found a security issue? Tell us.
We welcome reports of vulnerabilities in SwengleIO and work with the people who send them.
Updated 5 November 2026
How to report
Email security@swengle.com (also in our security.txt). Include:
- what you found and where (the URL, endpoint hostname, library and version, or API call);
- the steps to reproduce it, and what an attacker could do with it;
- your name or handle, if you want to be credited.
Keep secret keys, client tokens, passwords and other people's data out of your message. If a report needs them to make sense, describe them instead; if you have seen someone else's data, say so and don't keep a copy.
Scope
- This website, swengle.io;
- the Console and its API at console.swengle.io;
- Notifiers endpoints (
*.api.swengle.io) and their relay hosts; - the SwengleIO client libraries.
Out of scope: the cloud providers and other services we use (report to them directly), findings from automated scanners without a demonstrated impact, missing best-practice headers without an exploit, denial of service, social engineering of our staff or customers, and physical attacks.
Rules for research
- Test only against an account, organization and endpoints of your own. Never access, change or delete data that isn't yours, and stop as soon as you reach any.
- Don't degrade the Services for others: no denial-of-service or load testing, no spam, and stay within the limits your plan sets.
- Testing that follows these rules, against your own account, organization and endpoints, is authorized under this policy. Anything beyond them, such as testing other parts of our infrastructure, social engineering of our staff or physical testing, is intrusive testing that needs our written authorization first, as our Terms of Service require. If you are unsure whether a test is allowed, ask us first at security@swengle.com.
- Give us a reasonable time to fix an issue before you disclose it publicly, and agree the timing with us.
What we do
- We reply to confirm we've received your report, and keep you told how it is going.
- We investigate every report, fix what we confirm, and tell you when it is fixed.
- If you want, we credit you when we disclose the issue.
- We won't take legal action against research done in good faith that follows this policy, including the testing it authorizes.
We don't run a bug bounty and don't pay for reports.
More
How we handle security and reliability is in our Trust center. To report abuse of the Services or suspected unauthorized access to your account, use the same address.