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 payment history, your billing details if you add them, and any API keys you create. API keys are stored as one-way hashes; we cannot read a key back, and we record when each was last used. 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.

When you use AriaQR inside Canva, Canva tells us who is asking with a signed token that carries an opaque Canva user and team identifier. It does not give us your name or email address, and we do not ask for them.

A free code made in Canva is generated and handed straight back to your design. We keep neither your image nor the code afterwards; the working files are deleted as soon as the code is returned. The identifier is used only to limit how many codes can be made in an hour.

A live code made in Canva is an ordinary AriaQR code, handled as described on this page: we keep the image so the code can be restyled, and codes that are never activated are deleted, image and all, after seven days. We store the Canva identifier with the code so the app can list your live codes and show when one has been activated. Payment happens on ariaqr.com, not inside Canva, as described under payments on this page.

“Enhance with AI” is optional and only runs when you click it. Your image is sent to Google’s AI image model through our media service to sharpen and restore it, and the result is shown next to the original for you to accept or discard. Google processes the image under its Cloud API terms, which do not allow it to be used to train Google’s models. The temporary copy we hold for the enhancement is deleted within a day; only a version you accept becomes part of your code. Faces and other recognisable features can change during enhancement, which is why nothing is applied automatically.

Business accounts can build a landing page for their codes. We store what the brand puts on it: the words, the brand colours and fonts, links, and the photos and logo it uploads. Uploaded photos are re-encoded when they arrive, which removes hidden metadata such as the location a photo was taken. A page stays until its owner deletes it; deleting a page also deletes its photos and its visitor statistics.

If the brand uses the AI designer or the rewrite button, the brief or the text is sent to Google’s AI model through our media service to write the page. Google processes it under its Cloud API terms, which do not allow it to be used to train Google’s models. The AI never receives the brand’s photos.

People who visit a brand’s page are counted the same way as scans: the time, device, operating system, an approximate location from the network address, whether they came from a QR code or a shared link, and which buttons they tap. We do not store their IP address, we set no cookies on those pages, and we do not run our own Google Analytics there. The brand sees these numbers in aggregate. A brand page may embed a YouTube, Vimeo or Google Maps player if the brand adds one; those services apply their own policies when the visitor presses play or opens the map.

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.

Rupee payments are processed by Razorpay and dollar payments by PayPal. Card, UPI and bank details are entered with them and are never seen or stored by us. From each payment we keep what an invoice needs: the amount, currency, date, the provider’s payment reference, the email the receipt went to, and the approximate location the payment came from (country, region, city), which sets the place of supply for GST. Invoices carry a sequential number and are kept for as long as the law requires us to keep accounting records, currently eight years in India, even if you delete your account.

If you enter billing details (name, company, tax ID, address, billing email) they are stored on your account and printed on your invoices; you can change or clear them at any time. Receipts and invoices are emailed to the address on the payment, with the PDF attached.

Promo codes you use are recorded against the purchase so the offer can be honoured and its use counted.

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 Razorpay and PayPal 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, their analytics and its API keys; invoices are kept for the legal retention period with the account reference removed. 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.co. See also our terms and refund policy.