Trust
Security
If you have found a weakness in Woyra, we want to hear about it, and we will not pursue you for finding it in good faith.
How Woyra is protected
- Every connection is encrypted, and browsers are told never to reach Woyra without it.
- Passwords are stored with Argon2id; API keys only as hashes; stored secrets encrypted under a master key.
- Passkeys and two-factor authentication for every customer who wants them, and required for Woyra staff.
- Staff sessions end after fifteen idle minutes, and dangerous actions ask for the password again.
- Every staff action is written to an audit log, which customers can see for their own account.
- Sending is watched: accounts whose mail bounces or is reported as spam are paused automatically.
Reporting a weakness
Write to security@woyra.io with what you found, how to reproduce it, and what an attacker could do with it. We reply within three working days, keep you told of progress, and credit you here once it is fixed if you would like.
Please do
- Test only against accounts you own, or that you made for testing.
- Stop as soon as you reach data that is not yours, and tell us what you saw.
- Give us a reasonable time to fix a problem before you talk about it publicly; 90 days is the usual.
Please do not
- Flood Woyra with traffic, or test anything that would slow it down for others.
- Send spam or phishing through Woyra to prove a point, or test against people who did not agree.
- Try to trick Woyra staff or customers, or touch our offices or equipment.
- Keep, share or change data that is not yours.
Our promise
If you follow this policy, we treat your work as authorised, will not take legal action against you for it, and will say so if anyone else asks. If something is unclear, ask first at security@woyra.io.
Thanks
The people who have reported weaknesses to us will be thanked here, with their permission.
Abuse sent through Woyra is a different matter: report it here. Machine-readable contact: security.txt.