# QRick privacy policy

Last updated: September 13, 2026

QRick creates QR codes locally in your browser. It does not collect, transmit, sell, share, or retain personal data.

## Data QRick handles

When you open the extension, QRick reads the URL of the active tab using the browser's `activeTab` permission. When you use the bookmarklet, it reads the current page URL. If you edit the field, QRick handles the text you enter. This information exists only in the open popup or dialog and is used only to create the displayed QR code and any image you explicitly copy or download.

QRick does not send this information off your device or save it after the popup or dialog closes.

## Permissions

The browser extension requests only `activeTab`. This temporary permission is activated by your click and lets QRick read the address of that tab. QRick has no permission to monitor browsing in the background.

## Storage, networking, and third parties

QRick has:

- no analytics, telemetry, advertising, cookies, or tracking;
- no user accounts or authentication;
- no remote servers or network requests;
- no persistent or synchronized storage;
- no remotely hosted executable code; and
- no sale or sharing of user information.

The bundled [`uqr`](https://github.com/unjs/uqr) library generates QR codes locally and receives no information over a network.

## Clipboard and downloads

QRick accesses the clipboard only when you press **Copy image**. It creates downloaded PNG or SVG files only when you press the corresponding save button. These actions are handled by your browser.

## Changes

Material changes to this policy will be committed to the public repository and reflected in the extension-store disclosures before a release containing those changes is published.

## Contact

Questions and issue reports can be submitted through the [QRick GitHub repository](https://github.com/costinEEST/url-to-qr/issues).