Last updated: October 2026.
QR Plus provides QR Code creation and management features with different behavior according to content type and functionality. Our operations preserve that distinction when handling publication, destination changes, metrics and campaign continuity.
This document describes how those processes work on the platform. Usage conditions, limits and resource lifecycle follow the Terms of Use and applicable plan.
1. Static codes and dynamic features
We generate static codes with information embedded in the image itself. Reading that content does not require an active QR Plus account, although an external address or resource remains dependent on its respective service’s availability.
For dynamic features, we manage the code’s association with a destination or platform-provided content. That operation is linked to the account, feature and service conditions; destination editing exists in types that support it. Pix operates as a static code.
2. Publishing and changing content
We handle content publication and changes according to functionality available for each QR Code type. In supported dynamic features, a destination update changes the platform-managed association while preserving the code image already distributed.
Data embedded directly in a static code remains in the generated image. This difference defines QR Plus’s role in subsequent changes and continuity of associated services.
3. External destinations and services
Dynamic feature resolution considers the configuration linked to the code and service conditions. When a destination belongs to an external website, application or provider, its operation remains distinct from infrastructure under QR Plus responsibility.
This separation is considered when reviewing access failures, availability and data processing. Accessing content through a QR Code does not give the platform control over every action performed by the destination service.
4. Abuse and usage restrictions
We apply request validation, usage limits and protection against improper automation in protected flows. Reports of fraud, phishing, unlawful content and rights violations are reviewed under the Terms of Use.
Handling may involve restrictions on content, accounts or resources and preservation of information relevant to the event. Measures are tied to case context and applicable service conditions.
5. Metrics and campaign continuity
We provide records and statistics according to the feature used, under the processing conditions described in the Privacy Policy. Measurements reflect technical events and may be affected by device, network and application behavior.
We manage platform resource lifecycles according to the plan, limits and usage rules. Business requirements concerning campaign duration and service continuity are reviewed within engagement scope by the responsible team.
6. Business support
Our team handles campaign questions and supplier qualification through the contact page, connecting the assessment to the features involved and service conditions.