Last updated: October 2026.
Security at QR Plus involves protecting communications, verifying access and handling operations performed on the platform. These guidelines present our approach to those subjects and the information we make available for business assessments.
This content complements the Terms of Use and Privacy Policy. Configuration details, operational evidence and conditions specific to an engagement are handled by the responsible people according to their purpose and sensitivity.
1. Scope of protection
We handle security according to each service’s function: account access, code creation, content publication, redirection and support. This distinction connects protective measures to the operations and information actually involved, without attributing identical technical behavior to every feature.
Platform protection concerns services under our operation. Published content and external destinations have their own characteristics, which we consider when reviewing events and determining responsibilities.
2. Communications and operational integrity
We use HTTPS to protect communications with our services. In applicable operations, we check request validity and the authorization required to perform them, reducing improper calls and processing of data incompatible with the feature used.
These checks are combined with usage rules and handling of invalid inputs. Internal conditions for applying controls are kept confidential to preserve service protection.
3. Identification and access
We verify identity and access conditions before making protected resources available. The account association and applicable authorizations define permitted operations, considering the feature and service conditions.
Access information and internal data receive handling appropriate to their sensitivity. Requests involving restricted information are reviewed for purpose and authorization.
4. Abuse prevention and handling
We apply request validation, usage limits and mechanisms against improper automation in protected flows. These measures help curb abusive use and are considered alongside the review of events reported through official channels.
We handle reports of fraud, phishing, unlawful content and rights violations under the Terms of Use. Reviews may result in resource restrictions, preservation of relevant information and other actions appropriate to the event.
5. Failures and security events
Handling an event considers the affected service, observed impact and available information. Relevant records support technical routing, identification of appropriate measures and follow-up on the request.
Communication follows the nature of the case and applicable responsibilities. We protect third-party data and information that could compromise the service during investigation or disclosure of explanations.
6. Service changes and dependencies
When reviewing requirements and changes, we consider their effect on features, access and information handling. Supporting service dependencies also form part of this assessment according to their operational role.
Using a provider does not automatically transfer that provider’s certifications or guarantees to QR Plus. Information about responsibilities and specific conditions is tied to the service being assessed.
7. Documentation and business assessment
We provide public documents for consultation and review requests for additional information during supplier qualification. Our responses connect requirements to the product and engagement scope, allowing an objective explanation of QR Plus’s role.
Internal documents and technical evidence are shared after review of relevance, authorization and confidentiality. These public guidelines describe our security approach; specific supporting evidence is handled within the corresponding assessment process.
8. Security contact
Our team receives security questions and business requirements through the contact page. Routing considers the subject, affected feature and conditions needed for handling while protecting sensitive case information.