Security
How to report a security issue in Altrady, and the rules for testing.
Reporting a vulnerability
Found a security issue in Altrady? Email [email protected]. Please include:
- The affected URL, endpoint or app version
- Clear steps to reproduce it
- What an attacker could do with it
You can write in English or Dutch. We aim to reply within 5 working days and will keep you updated until the issue is fixed.
Scope
altrady.com, app.altrady.com, api.altrady.com and the Altrady desktop and mobile apps.
Rules for testing
- Test only with your own account and your own data. Never access, change or delete data of other users.
- Do not create throwaway accounts, and do not send fake API keys, credentials or other data our apps never send. Our systems detect this and ban the account automatically.
- No denial of service, high-volume automated scanning, spam, social engineering or physical attacks.
- Stop and report as soon as you have shown the issue. Do not use it further.
- Give us reasonable time to fix the issue before you share it with anyone.
What we do not accept
- Reports from automated tools without a working proof of concept
- Missing security headers, cookie flags or SPF, DKIM and DMARC settings without a concrete impact
- Clickjacking on pages without sensitive actions, self-XSS and version disclosure
- Rate limits on endpoints that do not handle sensitive data
Rewards
Altrady does not run a paid bug bounty. We do not pay for reports and do not reply to requests for payment. Valid reports get a reply and our thanks.
Good faith
If you follow this policy in good faith, we will not take legal action against you for your research.