Credentium is a platform for issuing, storing and verifying digital credentials. The credentials we handle describe real people, so we take the security of the platform seriously. If you have found a vulnerability, we want to hear about it and we will work with you to fix it.
How to report
Write to security@credentium.com in Polish or English. Please include:
- a description of the vulnerability and its potential impact,
- the affected address or component (for example the issuer panel, the wallet, the public credential pages, the API),
- steps to reproduce, with proof of concept, requests or screenshots,
- how you would like to be credited, or whether you prefer to stay anonymous.
Please do not put sensitive data in the message. If you need an encrypted channel, ask for one in your first message and we will arrange it.
What to expect from us
- Acknowledgement of your report: 2 business days
- First assessment and severity: 10 business days
- Status updates: at least every 30 days until resolved
- Fix or mitigation: critical: within 7 days, high: within 30 days, medium: within 90 days, counted from confirmation of the vulnerability; low: in the next scheduled release
We will tell you when the issue is fixed. We ask you to agree with us on the date of any public disclosure. Our default is 90 days from your report, shorter if the fix is ready sooner, and extended by agreement if a fix needs more time. We will credit you in our acknowledgements if you wish.
Scope
In scope:
- credentium.com and its subdomains operated by us: the issuer panel (issuer.credentium.com), the wallet (wallet.credentium.com) and the public credential pages (credential.credentium.com),
- the public API and the mobile and web wallet clients provided by Credentium.
You are welcome to test on our sandbox environment (*.sandbox.credentium.com) rather than production wherever the issue can be shown there.
Out of scope:
- denial-of-service, volumetric or load testing,
- social engineering or phishing of our staff, customers or users, and physical attacks,
- vulnerabilities in third-party services we use (for example the identity provider, cloud, DNS or e-mail providers); please report these to the vendor,
- automated scanner output without a demonstrated impact, missing best-practice headers without an exploit, and e-mail configuration findings without impact,
- reports that require a rooted device, an outdated browser or access to the victim's unlocked device.
Rules of engagement
Please:
- test only with your own accounts and your own data,
- stop as soon as you reach personal data or credentials of other people; do not download, copy, modify or keep them, and tell us what you saw,
- do not degrade the service, and do not alter or delete data,
- do not publish details before we have agreed on a disclosure date,
- do not demand payment as a condition of reporting.
Safe harbor
If you act in good faith and follow this policy, we will consider your research authorised, we will not take legal action against you, and we will not report you to law enforcement for it. This does not cover activity that breaks the law in ways this policy does not permit, such as extortion or the use of data you have accessed. If a third party starts proceedings over research that followed this policy, we will make it known that your activity was authorised.
Rewards
We do not run a paid bug bounty. We are glad to thank you publicly and to confirm in writing that you reported the issue.
Contact
security@credentium.com. Machine-readable details are at https://credentium.com/.well-known/security.txt.
Last updated: 21 November 2026