Legal
Contact
For general questions, product feedback, partnership notes or anything that does not fit neatly into a legal category, use the form below or email [email protected].
Privacy requests can go to [email protected]. Legal notices or abuse reports can go to [email protected]. Accessibility issues can go to [email protected].
If you are reporting a dangerous QR code, phishing link or misuse involving qrcodeq, include the page URL, screenshot if useful and the decoded destination if you have it.
What to include
For tool bugs, tell us the page you used, the browser, the device and what you expected to happen. For QR or barcode scan problems, include the export format, print size, material if printed and whether the issue happens on one phone or several phones.
Requests we can handle fastest
We can usually respond faster when the message has one clear subject: a broken page, a privacy question, an accessibility issue, a suspected abuse case, a typo in site content or a practical feature request for a generator, scanner, barcode page or bulk export workflow.
Product and tool feedback
A useful product report includes the tool name, the value you tried to encode and the file format you downloaded. If the issue happened after printing, include the print size, paper type and scan distance. A phone model helps too, especially when one device scans and another does not.
For bulk QR reports, send a small sample CSV with private data removed. Tell us which column held the QR value and which column held the filename. If a ZIP export stopped early, include the row count and the browser you used.
Safety and abuse reports
If someone is using a qrcodeq page, image or exported file for phishing, impersonation or payment fraud, send the details to [email protected]. Include the suspicious URL, the page where you found it and any screenshots that show the context.
If you scanned a dangerous public code, do not send passwords, card numbers or private screenshots. A decoded link and a short description are usually enough. If money was taken or an account was accessed, contact your bank or the affected service first.
Privacy and legal requests
Privacy requests should include the email address or contact detail connected to the request. Please do not send unnecessary identity documents in the first message. If we need more information to verify a request, we will ask for the smallest amount that fits the situation.
Legal notices should identify the page, file or conduct involved. Please include your name, organization if relevant and a clear way to reply. Short, specific notices are easier to review than broad claims without links.
Response expectations
We read messages by priority. Security, privacy and abuse issues come first. Product feedback and content fixes may take longer, but they still help us improve the site. We may not reply to every feature idea, duplicate report or sales pitch.