Terms of Service.
Plain words, binding clause.
These Terms are the legal agreement between you and Heldqr. They are written in plain language because legal-by-obfuscation is exactly the pattern this product was built against. The continuity clause in §06 is the load-bearing one: it is the binding version of the commitment shown on the homepage and at /continuity.
v0.1 ships pre-lawyer-review. The continuity clause itself is final language; the surrounding sections will be tightened by counsel before the indexing gate flips. If you spot something genuinely wrong, write to legal@heldqr.com.
What Heldqr provides.
Heldqr is a service for creating and resolving QR codes. A static QR code encodes a URL directly. A dynamic QR code encodes a short URL on heldqr.io that we resolve to your destination URL — so you can change the destination without reprinting the code.
The hosted service runs on infrastructure operated by Heldqr. Resolver source code and the canonical redirect data are committed to a public continuity arrangement, described in §06 below and in full at /continuity.
Your account, your responsibility.
You are responsible for the destination URLs your codes resolve to and for keeping your account credentials safe. We do not police destination URLs proactively, but we will suspend codes that resolve to malware, phishing pages, or content that violates the laws of the jurisdiction you operate in. Suspension means the code resolves to a 410 Gone notice, not deletion — you can update the destination and have it un-suspended.
Fees, what they cover, and refunds.
Pricing is published at /pricing. The free tier is genuinely free — no trial, no credit card, unlimited dynamic codes. The Pro tier is a recurring monthly subscription. The Business tier is a recurring monthly subscription with team features.
The fair-use caps that apply to every tier are published at /fair-use; the numbers there are part of these Terms by reference.
Your data, what we keep, what we don't.
The continuity plan is the reason we collect as little as we do. We have to be able to publish a redirect-only data dump in a wind-down event without lawyer review (see §06), so we don't collect things we'd be nervous to publish.
The continuity clause. This is binding.
If Heldqr stops operating as a going concern — for any reason: shutdown, insolvency, acquisition that changes the terms of these Terms, founder inability to continue — the following obligations apply, in order. They survive any change of ownership and they bind any successor entity.
The plain-language version of the same commitment lives at /continuity, with the operational runbook that backs it.
The public continuity arrangement is mirrored at github.com/heldqr/continuity-repo, where the data export schema, the resolver-source license, and the wind-down artifacts are committed in advance.
What these Terms do not promise.
Honest commitments require honest limits. The continuity clause is the strongest promise in this document; everything outside its plain text is best-effort.
Changes, jurisdiction, contact.
These Terms are versioned at the top of the page. Material changes get 30 days' notice to active customers by email. The continuity clause in §06 cannot be weakened by a change to these Terms — only strengthened or restated.
Governing law and dispute resolution: to be confirmed at lawyer review before the public-indexing gate flips. The current operating entity is based in Belgium, and the most likely outcome is Belgian law and Brussels jurisdiction. This sentence is a placeholder, flagged here so it is not silently shipped.
>Legal-by-obfuscation is the pattern this product was built against.
— Heldqr · v0.1 · 2026-04-24
The continuity clause is short, plain, and binding. That's the point.