QR for Keeps

Acceptable use

A short link that cannot be switched off is a useful thing to print and a useful thing to abuse. These are the rules for dynamic codes on QR for Keeps. Static codes never touch our servers after you download them, so this policy is about the redirects we operate.

Do not point a code at

What we do about it

When a Google Safe Browsing API key is configured, every new or edited destination is checked before it is saved. A match is rejected. If the key is missing or Google is down, the save is allowed and the code is marked unchecked — we do not take the whole product offline because a lookup failed. The operator can still disable a code by hand.

Destinations have to be public http or https addresses. Private networks, localhost, and link-local addresses are refused, both so the checker cannot be used to poke at internal systems and so a printed code is actually a public link.

Creating codes, asking for sign-in emails, running the checker, and filing reports are rate limited. A paused code stops redirecting until the owner turns it back on. A code disabled by the operator stays off, and the owner cannot reverse that from the dashboard. The credit spent on an abusive code is not returned.

Scan totals are for the account that owns the code. We do not sell them. The optional chart is a count per day, not a list of people.

Tell us

Use the abuse report form. Include the short address and what you saw. We read reports and we would rather switch a bad code off the same day than debate it for a week. The ten-year pledge does not cover a code that breaks these rules.