Legal

Privacy Policy

Last updated October 16, 2026

Qwick Tools gives businesses a few everyday tools: QR codes you can change after printing and address autocomplete for website forms. This policy explains what information those tools handle, why, and who else touches it.

The Short Version

We don't sell or rent your information. Not to advertisers, data brokers, or anyone else.
No ads and no ad trackers. We don't run third-party analytics, advertising pixels, or tracking cookies.
We collect what the tools need to work. QR scans are counted, not tracked. What people type into the address search isn't saved.
Cloudflare protects the site. It sees traffic to keep the site fast and secure; details are below.

What We Collect

If You Have an Account

Accounts are set up by invitation. We keep your name, email address, and password. Your password is stored only as a one-way hash, so nobody, including us, can read it. We also keep the groups you belong to and simple preferences, such as the group you last selected.

What You Create

We store what you add to your tools: QR code titles, the web addresses they lead to, any center images you upload, and the websites you allow to use address autocomplete.

When Someone Scans a QR Code

A Qwick QR code opens a short link that sends the visitor on to its destination. Each visit adds one to a counter for that code in a 15-minute window. We don't store the visitor's IP address, device, browser, location, or any identifier with that count, and the redirect asks browsers not to send our address along to the destination.

When Someone Uses Address Autocomplete

The text a visitor types into an address field is sent to us so we can suggest matching addresses. We use it to answer that request, and we don't store it in our database or write it to our request logs. We do record when each allowed website last used it.

Request Logs

Like most websites, our servers keep basic request logs: the time, the page or endpoint requested (without the text after a question mark, such as address searches), the response status, how long it took, Cloudflare's request ID, and the approximate country Cloudflare attaches to the request. We use these logs to keep the service running and to spot abuse.

Address Data

The addresses we suggest come from public open data sources, not from our users. They describe places, not people, and we don't attach names to them. See Data Sources for where they come from.

How We Use Cloudflare

We use Cloudflare for two things:

Network and security. Every request to getqwick.com, including QR short links and the address autocomplete script, passes through Cloudflare's network before it reaches our servers. Cloudflare provides DNS, encrypted HTTPS connections, caching, and protection against attacks and abusive traffic.
File storage. QR code images and uploaded center images are kept in private Cloudflare R2 storage. They aren't publicly listed. Our app fetches them and serves them only to people who are allowed to see them.

What Cloudflare Sees

To route and protect traffic, Cloudflare processes request information such as your IP address, the page requested, browser and device details sent with the request, and routing data. From that traffic it also produces security signals, such as threat scores, error rates, and request volumes. For our site, Cloudflare acts as a service provider that processes this information on our behalf.

What Cloudflare Says It Does With It

Cloudflare's privacy policy states: "We will not sell or rent your personal information."
It uses this traffic information to provide, secure, and improve its services, and to detect and block malicious activity.
It may combine data into aggregated, non-identifying statistics, such as overall attack trends across its network.
Cloudflare's advertising and marketing cookies apply only to people visiting cloudflare.com itself, not to visitors of sites like ours.
Data may be processed in the United States and in the Cloudflare data centers that serve your connection.

Security Cookies and Error Reports

If Cloudflare needs to check whether traffic is automated, it may set a short-lived, strictly necessary cookie such as __cf_bm, which expires after 30 minutes of inactivity, or cf_clearance after you pass a challenge. Cloudflare says these cookies don't track people from site to site and aren't linked to your Qwick Tools account.

Browsers may also send Cloudflare a Network Error Logging report when a connection to our site fails. Cloudflare uses these reports to find network problems and says it doesn't store personal information from them.

What We Don't Use

We don't use Cloudflare Web Analytics or any Cloudflare advertising or marketing features on getqwick.com.

For full details, see Cloudflare's Privacy Policy and Cloudflare's cookie list.

Cookies and Storage

Our own cookies are only the ones the site needs:

sessionid keeps you signed in. It's set only when you sign in.
csrftoken protects forms from being submitted by other websites.
messages briefly holds a one-time notice, such as "Saved", while the next page loads.

When you're signed in, your browser also remembers whether the sidebar is open. That setting stays on your device. The address autocomplete widget sets no cookies on the websites that use it.

How We Use Information

We use information only to:

Run the tools you use, such as redirecting QR codes, showing scan counts, and suggesting addresses.
Keep accounts and the service secure, and prevent abuse.
Fix problems and understand how the service is performing.
Respond when you contact us.

We don't build advertising profiles, we don't send marketing email, and we don't sell, rent, or trade personal information.

We share information only with:

Service providers that help us run Qwick Tools, such as Cloudflare and the companies that host our servers. They get only what they need to provide their service to us.
Members of your group, who see the QR codes and scan counts that belong to that group.
Authorities, when the law requires it.

How Long We Keep It

Account information is kept while your account is active. Deleting an account removes it.
QR codes, their images, and their scan counts are kept until you delete the code. Deleting a code deletes its scan counts and stored images too.
Request logs are short-lived and kept only as long as we need them to run and protect the service.
Address search text isn't stored.

Security

We take this seriously. Connections use HTTPS, and browsers are told to always use it. Passwords are hashed, stored files are private, sign-in forms are protected against cross-site attacks, and our pages block scripts from other sites. Access to production systems is limited to the people who run the service. No system is perfect, but we work to keep yours safe and will tell affected users promptly if something goes wrong.

Your Choices

You can ask us to show you, correct, export, or delete your personal information at any time. Contact the person who set up your account. Depending on where you live, laws such as the GDPR, PIPEDA, or the CCPA may give you additional rights. We honor them, and we don't treat you differently for using them.

Websites Using Our Tools

When a business adds address autocomplete to its website or prints our QR codes, that business decides to use our tools for its visitors and customers. We handle what those visitors type or scan only to provide the tool, as described above. Each business is responsible for its own privacy notice. Questions about a particular website should go to the business that runs it.

Qwick Tools isn't meant for children, and we don't knowingly collect personal information from anyone under 13.

Changes and History

If we change this policy, we'll update this page and the date at the top. For significant changes, we'll also tell account holders before they take effect.

October 16, 2026: API keys are no longer offered, so we no longer store them or record when they were last used.
October 13, 2026: First published.