This policy covers the public QR creation tools at PactQR. It describes the current implementation, including the difference between generating a code here and opening the destination encoded in it.
QR inputs and logos are processed locally
The generator uses your browser to prepare the payload, render the code and create downloads. Website addresses, phone numbers, contact details, message drafts, WiFi credentials and selected logo files are not uploaded by the generator to a PactQR server.
The public tools do not require an account. We do not maintain a saved QR generation history or a cloud library of your inputs. Leaving the page can lose the current work, so keep any export you need. This policy does not promise that browser recovery features, extensions or your device's own backup software will not retain local information.
Files you download and share
Exported PNG, SVG, PDF and contact files are saved through your browser to a location you choose or your configured download folder. You control those copies. Delete them through your device's file controls when you no longer need them.
A QR image exposes its encoded content to anyone who can read or photograph it. A WiFi password is readable from its code. Contact fields are readable from a vCard. BCC recipients in a mailto payload are also readable from the pattern. Local generation does not make a shared image confidential or recall copies already received by other people.
Page requests and technical records
Loading the website requires requests to its hosting infrastructure. The hosting service can receive technical information such as an IP address, request time, requested page, browser information and error details for delivery, reliability and security.
These page requests are separate from the form fields used to generate a code. Do not put a secret in a page URL you share or request. We do not state a fixed log-retention period here because it has not been verified for every infrastructure record; we also do not claim that visiting the site creates no server records.
Analytics, advertising and browser preferences
Analytics are not enabled in this release, and the public QR tools do not use an advertising tracker to collect generation inputs. There is no PactQR scan counter in the static code: scanning its payload does not route through our service.
Ordinary browser caching and site preferences may retain application assets or a presentation preference. They are different from a stored QR history. You can review or clear the site's data using your browser's privacy settings. Clearing site data does not remove downloaded files, printed copies or records held by external destinations.
External destinations and source links
Opening an encoded website or social link contacts that destination. It can apply its own cookies, sign-in rules, request logging and privacy policy. A forms.gle or wa.me address is operated by its respective platform, even though PactQR adds no redirect of its own.
Mail and SMS payloads can be handed to an application on the scanning device. Sending a message, making a call, saving a contact or joining a network is then governed by that device and the relevant service. Following a documentation link on this site also contacts the linked provider. PactQR does not receive the contents of messages sent through those applications.
Control and deletion
Remove a current input by clearing its field or leaving the tool. Delete downloaded exports using your device's file controls and clear site data through your browser if desired. There is no stored PactQR input history for us to retrieve or delete.
We cannot erase copies that you have printed, sent to others or imported into another application. Use the destination provider's controls for data it holds. The Contact page explains the current lack of a public request channel; this limitation also applies to requests about technical records held by the site's infrastructure.
Changes
We will update this page when the described data handling changes and revise the date above. Read the About page for how the tools work and the Terms of Service for their scope.