Dynamic QR codes, built for Europe

QR codes that evolve with your business.

Create editable QR links with privacy-aware scan insights and an independently deployable redirect edge.

Creator concept

Create your QR

Start with the destination you want to share.

Static codeDynamic code
Core colour#003399
Continue in the dashboard
Design previewyour-site.eu/campaign
QRDude mascot leaning beside the QR creator
  • No full IPs in scan analytics
  • No scan-based ad profiles
  • Verified custom domains

European by design

  • EU Built for EU deployment
  • AVG Designed around data minimisation
  • IP Data-minimising analytics
  • DNS Your domain, verified

One QR code. More control after it leaves the screen.

QRDude gives teams a durable layer between printed media and the destinations that inevitably change.

01

Dynamic destinations

Change where a printed code leads without replacing the code itself.

02

Privacy-aware insights

See aggregate scan trends without storing full IP addresses or full referrer URLs.

03

Your own domain

Put a verified branded domain in front of every route and keep the relationship yours.

04

Independent redirect edge

Synced routes keep resolving from a dedicated database and cache if the dashboard is offline.

Mistakes happen. Be ready.

A destination changed after 5,000 flyers went to print. What happens next?

QRDude thinking about a broken printed linkWait, is it broken?

The static link trap

The campaign is printed. Then the destination changes.

×

With a static QR

Reprint every code

The destination is encoded directly, so the print itself has to change.

New print run required

With QRDude

Update one route

Change the destination in the dashboard. Existing printed codes keep their job.

No reprint needed
Smart links. Less data. Built for Europe.
QRDude holding the European Union flag

European by design

Sovereignty you can explain.

QRDude separates the dashboard from a dedicated redirect edge, limits the data collected per scan, and keeps the stack independently deployable.

01

Independently deployable

The control plane and redirect edge can be operated as separate services with separate data stores.

02

Less data per scan

Full IP addresses are discarded before scan analytics are stored; referrers are reduced to their hostname.

03

No scan-based ad profiles

QRDude uses scan analytics for route performance, not advertising profiles.

04

Verified domain control

DNS ownership is checked before a customer domain can become active.

GDPR is known as the AVG in the Netherlands. Compliance and actual data residency also depend on production providers, retention and your configuration.

When the dashboard pauses, synchronized links keep moving.

A signed synchronization path sends route changes to an edge service that never calls the dashboard while serving a scan.

01DashboardDesired routes
signed sync
02Redirect edgeOwn DB + cache
edge redirect
03DestinationYour live URL

Frequently asked questions.

01What is the difference between a static and dynamic QR code?

A static code contains its final destination. A dynamic code points to a QRDude route, so you can update the destination later without reprinting the code.

02Is QRDude GDPR / AVG compliant?

No SaaS product makes an organisation compliant by itself. QRDude is GDPR-conscious by design and supports data-minimising use of dynamic QR codes. Your lawful basis, retention, configuration and provider choices remain part of your own assessment.

03Does QRDude store a scanner's full IP address?

No. Analytics retain only an IPv4 /24 or IPv6 /48 network. Referring URLs are reduced to the originating hostname, so paths and query strings are not stored as scan analytics.

04How does the architecture support EU-sovereign deployment?

QRDude is independently deployable, separates the dashboard from the redirect edge, and is designed for EU-region deployment. Actual data residency still depends on the hosting, backup, email and observability providers used in production.

05Do redirects stop when the dashboard is unavailable?

Once synchronized, routes are served from the edge's own PostgreSQL database and acceleration cache. The current release targets one production edge node and does not claim multi-region failover.

Start with your own domain

Make every printed link easier to change—and easier to trust.

QRDude giving a thumbs up