What we keep, and why.

You can make and buy a picture code without signing in: the code is yours through a secret link shown once at generation. If you sign in, with an email code or Google, we store your email address, the name and picture Google gives us if you used Google, the list of codes on your account, your plan status and any API keys you create (stored as hashes, never the key itself). We do not ask for anything else and we do not build a profile of you.

The free classic codes need a sign-in, because the renewal reminder is sent to that email.

Your image is used to generate your code and for nothing else. While a code exists we keep the source so you can restyle it without uploading again. Codes you generate but never activate are deleted, image and all, after seven days. Free classic codes store no image. We never use your images to train models or for advertising.

Each dynamic code carries a short AriaQR link that redirects to the destination you chose. We store the destination, the code’s settings and, for activated codes, the print-ready master. Activated picture codes are kept for as long as you want them live. Free classic codes live for a year from their last renewal; if nobody renews, they pause, and are deleted a month later.

When someone scans a code we record a pseudonymous event: the time, the kind of device and operating system, the browser, the language, and an approximate location worked out from the network address at that moment (country, region, city and sometimes postal code). We do not store the scanner’s IP address, we set no cookies, and we do not identify the person. Unique-visitor counts use a one-way hash that is rotated daily. Code owners see these events in aggregate and can export them.

A code owner may switch on an optional precise-location prompt; the scanner’s phone then asks for consent in its own dialog, and nothing is recorded unless they agree.

We read the country a request comes from, as provided by our hosting provider, to show prices in the right currency. The pricing page lets you override it. We do not keep this.

Payments are handled by our payment provider. Card and bank details are entered with them and are never seen or stored by us. We receive confirmation that a payment succeeded, the amount and currency, and for the quarter plan the subscription status.

Two kinds. Strictly necessary storage makes the site work: your sign-in session, your in-progress code during checkout, and your cookie choice. Analytics cookies come from Google Tag Manager and Google Analytics, which we use to understand traffic and to measure advertising. In Europe these stay off until you accept them in the bar at the bottom of the page; you can decline, and your choice is remembered. Scanning a code never sets a cookie, as described above.

Sign-in codes, receipts, plan reminders before a quarter ends, renewal reminders for free codes, and the alerts you switch on yourself for a code. No newsletters unless you ask for one.

We do not sell data. We use Vercel for hosting and storage, Resend to send email, Google for sign-in and site analytics, and our payment provider for payments, each only to the extent needed to run AriaQR, or where the law requires it. Hosted links are checked against Google Safe Browsing to keep phishing off the service; that check sends the destination URL, not anything about you.

You can ask what we hold about you or a code, ask for a copy, or ask us to delete it. Deleting an account removes its codes, their masters and their analytics. Write to us at the address below and we answer within a few days.

AriaQR is not directed at children under 13, and we do not knowingly collect their data.

If we change how we handle data, we update this page and the date above.

Privacy questions: info@realityrift.com. See also our terms and refund policy.