1. Security Approach
QRINTEX products are positioned for organizations that need long-term verifiable evidence, integrity assurance and controlled deployment models. Security is treated as a lifecycle practice across design, implementation, deployment and operation.
2. Website Security
The public website is a marketing and information site. It does not currently provide customer login, production evidence verification, payment processing or administrative customer portals. The demo request flow uses a local browser form and opens the visitor’s email client to send the request.
3. Product Security Principles
QRINTEX product implementations should be assessed under the architecture, threat model and deployment environment agreed with each customer. Standard security principles include:
- Controlled deployment models, including on-premises or isolated network options where required.
- Least-privilege access and role separation for administrative workflows.
- Cryptographic controls appropriate to the evidence, signature or approval use case.
- Auditability and tamper-evident records for security-relevant operations.
- Secure key handling with HSM, TPM, secure element or equivalent controls where applicable.
- Preparation for post-quantum migration where long-term assurance requirements justify it.
4. Responsible Disclosure
If you believe you have found a security vulnerability in the QRINTEX website or a QRINTEX product, please contact us at executives [at] sixg [dot] technology.
Please include enough information to reproduce and understand the issue, such as affected URL, product or version if known, steps to reproduce, impact, screenshots or proof-of-concept details that do not expose sensitive data.
5. Testing Rules
When reporting vulnerabilities, do not:
- Access, modify, delete or exfiltrate data that does not belong to you.
- Disrupt services, degrade availability or perform denial-of-service testing.
- Use social engineering, phishing, physical attacks or attacks against third-party providers.
- Publish vulnerability details before we have had a reasonable opportunity to investigate and remediate.
6. No Security Warranty
Security information on this page is provided for transparency and general orientation. It does not create a warranty, certification, compliance statement or service level. Product-specific security commitments must be agreed in writing.
7. Changes
We may update this Security page from time to time. The “Last updated” date indicates the latest version.