Contact

We're listening

Questions, scan issues, feature ideas — send a note and we'll get back to you.

What to include

A little context up front saves a round trip. Here's what helps most, by reason for writing.

A code that won't scan

Send the code's name and where you printed it — size, material, and the phone you tested with. Those three usually explain it.

A QR type we don't have yet

Tell us what you'd want to encode and what should happen after the scan. It's the fastest way to influence what gets built next.

Product feedback

Something confusing, slow, or missing in the Studio? Specific beats polite — we'd rather hear exactly what got in your way.

Partnerships & press

Integrations, bulk or agency use, and press enquiries all land in the same inbox. Mention which one so it gets routed properly.

Replies go to the email address you enter below, so double-check it before sending. Messages are protected by a captcha to keep the inbox free of spam.

Send a message

All fields are required.

Before you write

These come up most often

A few answers that solve the majority of messages we get.

My code scans on my phone but not on a customer's — why?

Usually contrast or physical size. Aim for a strong difference between the pattern and its background, keep the quiet zone around the code clear, and print at a size where a module is comfortably visible. Re-exporting as SVG helps when a raster export was scaled up.

Can I change where a code points after I've printed it?

Only if it was saved as a dynamic code. The features page explains the difference between static and dynamic in detail.

I didn't get a reply — did the message arrive?

If the form showed a confirmation on the page, it was received. Check the spam folder of the address you entered, and make sure it was typed correctly — that's where replies go.

How do I delete my account and data?

Send a request from the email address on the account and we'll action it. Our privacy policy covers what's stored and why.