Security policy
Last updated 5 October 2026 · version 2026-10-05
The short version
- Found a security problem in https://1codigoqr.com? Please tell us at security@1codigoqr.com.
- We reply within 3 working days and keep you posted until it is fixed.
- If you act in good faith and follow this policy, we will not take legal action against you.
- We cannot pay bounties yet, but we gladly credit you when the fix is out.
How to report a vulnerability
Email security@1codigoqr.com with:
- what the problem is and where it is (the URL, API endpoint or part of the open-source code);
- the steps to reproduce it, or a proof of concept;
- what an attacker could do with it, as far as you know;
- how you would like to be credited, if at all.
Please write in English or Portuguese. Do not share the details with anyone else until we have fixed the problem or agreed with you that it can be published. Our machine-readable contact details are in security.txt.
Scope
In scope:
- https://1codigoqr.com, including the account area, the QR code generator, the short links and the pages we host for dynamic QR codes;
- the public API under https://1codigoqr.com/api/v1/;
- the open-source code we publish, such as the qrcore Django app (django-1codigoqr-qr).
Out of scope:
- the content that account holders put on their hosted pages or link to (please use the abuse report form instead);
- the services of our sub-processors, such as our hosting, storage and email providers: please report to them directly;
- denial-of-service attacks, load testing, spam, and social engineering of our staff or users;
- findings from automated scanners without a demonstrated impact, missing security headers with no exploitable effect, and clickjacking on pages without sensitive actions;
- reports that need a compromised device, an outdated browser or physical access.
Rules for testing
- Use only accounts you created yourself, and test only against your own data.
- Do not access, change or delete other people's data. If you reach someone else's data by accident, stop, do not keep a copy, and tell us.
- Do not degrade the service for others: keep automated requests slow and few.
- Do not use QR codes or short links you create to attack other people (for example phishing), even as a test.
Safe harbour
If you make a good-faith effort to follow this policy, we consider your research authorised. We will not take legal action against you or report you to the authorities for it, and if a third party does, we will make it known that you acted in line with this policy. This does not authorise breaking the law or anyone else's rights, and it cannot bind third parties.
What happens next
- Within 3 working days: we confirm we received your report.
- Within 10 working days: we tell you whether we can reproduce it and how serious we think it is.
- Fixes: we aim to fix critical problems within 7 days and others within 90 days, and keep you informed along the way.
- Disclosure: once it is fixed, we agree with you when and how the details can be published.
If personal data was put at risk, we also meet our duties under the GDPR, such as telling the supervisory authority and the people affected when the law requires it.
Rewards and credit
We do not run a paid bug bounty yet. With your permission, we credit everyone who reports a valid problem by name (or nickname) in our changelog when the fix is released.
Contact
Página Comum · security@1codigoqr.com