Skip to content

Privacy Policy

Effective: 18 November 2026 · Version 2026-11-18

Operator: Nexlla Group · Nexlla Creative Agency · a cloud-based business with no physical office

This policy explains what QRy collects, why, who receives it, how long we keep it and what rights you have. QRy is designed to collect as little as possible: the free generator runs in your browser, and scan records do not contain IP addresses. It applies to qry.nexlla.com, the QRy API, any QRy mobile app, and scans of QRy dynamic codes.

1. Who we are

QRy is a Nexlla product operated by Nexlla Group ("we", "us") under the Nexlla Creative Agency brand. Nexlla Group is a cloud-based business with no physical office, serving users in the UAE, the GCC and internationally, and you reach us by email. Privacy questions and requests: support@qry.nexlla.com.

We apply the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021, the "PDPL") where it applies to us, and the EU General Data Protection Regulation ("GDPR") and its UK equivalent where we serve people in those places. Our servers are in Lithuania, in the European Union, so the GDPR also applies to the hosting of your data.

2. Our role and our customers' role

  • For account, billing, security and abuse-prevention data, we decide how the data is used and are the controller.
  • For scan analytics, profile, menu and asset pages, and the fault reports sent through an asset page, the customer who owns the code or page decides why it exists and what audience it reaches. For that data the customer is the controller and we process it on their instructions, except where we use it to keep the service safe, investigate abuse or meet the law.
  • Customers are responsible for telling their own audience about scan analytics and profile content where the law requires it.

3. The free generator

Static QR codes are created entirely in your browser, with no account. The content you type, the logo you upload and the files you download are not sent to our servers. A static code contains its content directly, so its scans never reach us and we have no analytics for it.

4. If you create an account

We store:

  • your name, email address, language, notification choice and a hashed version of your password (never the password itself);
  • two-step verification data if you turn it on, the date you confirmed your email, and the date and version of the terms you accepted;
  • your workspace name, plan, subscription status, billing email and our internal notes on the account;
  • the payments we record for you: amount, date, method, reference and period. We never receive card numbers;
  • your dynamic codes: names, destinations, scenario rules, designs, campaigns and status;
  • API keys in hashed form, custom templates and your team list;
  • security records: sign-ins and important account actions with the time and the IP address used;
  • active sessions with their IP address and browser or device details. In a mobile app this also covers the device name, platform, app version and a notification token if you allow notifications;
  • a log of the emails we send you: recipient, subject, template and delivery status, not the message body.

Workspace admins can see the names and email addresses of their team members.

5. When someone scans a dynamic code

For each scan we record exactly these things, and the code's owner can see them in their analytics:

  • the code that was scanned, and the date and time;
  • the country and city, worked out from the IP address using a MaxMind GeoLite2 database on our own server or, as a fallback, the location headers added by Cloudflare;
  • the device type, operating system and browser, worked out from the browser's user agent;
  • which scenario or A/B variant applied, and whether the visitor was redirected or shown a safety notice;
  • a visitor code used to count unique visitors.

The scan record never contains the IP address. The application uses the address while handling the request, to work out location and to limit abuse, and holds it in memory only. It is not written to the database.

The visitor code is a short hash of the IP address, the browser's user agent and the code, made with a secret that changes every day, stays in memory and is never stored. It lets us count a visitor once per day on that code. It cannot be turned back into an IP address and cannot be linked across days or across codes. We still treat scan records as personal data.

Known link-preview bots are not counted, and very rapid repeat scans from one visitor may not be counted. Password-protected codes set one small cookie for 12 hours so the visitor doesn't need to re-enter the password. Dynamic codes set no other cookie.

As with any website, the IP address also passes through Cloudflare and the web server in front of QRy, which deliver and protect the traffic. Our web server's logs for QRy leave the IP address out. Cloudflare's own systems may record it for a limited time. See "Who receives data" below.

The code's owner decides where it leads. Once a visitor reaches the destination, that site's own privacy practices apply and we have no control over them.

6. Profile pages

A profile page shows what the customer chose to publish: names, photos, contact details, links, opening hours and services. Anyone with the link or code can see it and save it as a vCard. Pages ask search engines not to index them, but we can't guarantee that every search engine obeys. We keep a single total of views and record nothing about each viewer. If a profile shows your details and you didn't agree to that, tell us at /report or by email.

Menu pages and asset pages work the same way. A menu page shows the dishes, prices, photos and allergen notes the customer entered. An asset page shows the equipment's name, location, model, serial number and the service history the customer chose to make public. Visiting them records nothing about you beyond the same single total of views.

Every photo uploaded to QRy is checked, then decoded and saved again by our server before it is stored. This removes hidden metadata such as the camera, the date and the GPS position, and limits the picture's size.

AR product pages show the product's name, description, price, photos and 3D model as the customer entered them. For each page we keep daily counts of views, taps on "View in your space" and AR session starts. These are counts only: no IP address, device identifier or visitor identifier is stored.

When a customer uses 3D scanning, the product photos they take are decoded and saved again to remove metadata such as the location, sent to the 3D scan provider named under "Who receives data", and deleted from our server once they have been sent. The finished 3D model is stored with the customer's account.

7. Fault reports on asset tags

Anyone who scans an asset tag can report a fault without an account. We store exactly this:

  • the asset, the date and time, and the description you write;
  • a photo, if you add one. It is decoded and saved again, which removes its metadata (camera, date, GPS position), and it is reduced in size. It is never published: only the asset's owner can see it, inside their account;
  • your phone number, only if you choose to give it, so the owner can call you about the fault.

We don't store your name or your IP address. The application uses the address in memory only, to limit abuse, as for scans. Descriptions that contain links or email addresses are refused, and abusive ones are kept out of the owner's main list and don't trigger a notification.

The report goes to the asset's owner, who can see it in their dashboard and app, mark it resolved, hide it or delete it. The owner's admins get an email saying a fault was reported (without your phone number or text) and, if they allow notifications in the QRy app, a push notification. That notification doesn't contain your description, but when you left a phone number it carries it so the owner can tap "Call reporter". The owner decides what to do with your report; contact them, or us, about it.

We erase the phone number 30 days after the report, and delete the report and its photo 12 months after it was made, or sooner if the owner deletes it.

8. Abuse reports and support

When you report a code we store the link or code, the reason, your description and your email address if you give one. We don't store the reporter's IP address. When you email us, we keep the correspondence for as long as we need it to deal with your request and any follow-up.

9. Why we use data, and our lawful bases

  • To create your account and provide the service: performance of a contract with you.
  • To send account, security, billing and service emails: performance of a contract. Non-essential notices can be turned off in your settings.
  • To secure the service, stop phishing and other abuse, keep audit records and defend legal claims: our legitimate interest in a safe service and in protecting people from harm.
  • To produce scan analytics for the code's owner: on the customer's instructions and relying on the customer's lawful basis, and on our legitimate interest in a measurable service with data kept to a minimum.
  • To meet tax, accounting and legal duties and answer lawful requests: legal obligation.
  • Anything else that needs your consent: only with your consent, which you can withdraw at any time without affecting what came before.

Where the PDPL applies, we rely on the corresponding cases in which it allows processing without consent, such as performing a contract, meeting legal obligations and establishing or defending legal claims, and on your consent otherwise.

We don't sell personal data, we don't use advertising or tracking cookies, and we don't build advertising profiles. We don't send marketing emails today. If that changes we will ask for consent where the law requires it, and every such email will let you unsubscribe.

10. Automated link screening

Links are checked automatically by our rules, our blocklist and Google Safe Browsing, when they are saved and again regularly after that. A link may be refused, blocked, or shown to visitors behind a safety notice, without a person looking at it first. This assesses links, not people. If you think a decision is wrong, write to us and a person will review it.

11. Who receives data

Only the following, and only as needed:

  • Hosting (Hostinger, on servers in Lithuania (EU)): stores the database, uploaded images and backups, and runs the web server in front of QRy.
  • Cloudflare: its network sits in front of the site to deliver and protect traffic, so it handles every visitor's IP address and request, and can supply a country or city for that request.
  • Cloudflare R2 (off-site backups): an encrypted copy of our nightly backup is stored in Cloudflare's R2 storage, so the service can be recovered if our server is lost. It is encrypted before it leaves our server, and Cloudflare can't read it.
  • Google Safe Browsing: receives the destination links being checked. It doesn't receive account details or the IP addresses of people scanning.
  • MaxMind: we download its GeoLite2 location database and run it on our own server. No visitor data or IP address is sent to MaxMind.
  • When you use 3D scanning: KIRI Engine (KIRI Innovations), which receives only the product photos you take for a scan (with metadata such as location removed) to build the 3D model. Finished models are deleted from its servers after 3 days.
  • Email: messages go out through our own mail server, then pass to the recipient's email provider.
  • Push notifications: if you allow notifications in a QRy app, they are delivered through Google Firebase Cloud Messaging (and Apple's push service on iPhone). They carry the notification's text, the screen it opens and its quick actions, such as the reporter's phone number on a fault-report notification.
  • The customer who owns a code or profile: receives its scan analytics. The customer who owns an asset tag receives the fault reports sent through it.
  • Authorities, courts and professional advisers: where the law requires it, or where we need to protect people, our rights or the service. This includes reporting serious abuse.
  • A buyer or successor of the business, if it is sold or reorganised, under the same protections.

We don't share personal data with anyone for their own marketing.

12. International transfers

QRy is hosted in Lithuania, in the European Union, so the data we store sits on servers in the EU and the GDPR applies to that hosting. Our team and providers operate in several countries, and Cloudflare and Google run global networks, so personal data may also be processed outside your country, including outside the UAE and the European Economic Area. Where the law requires a safeguard, we rely on an adequacy decision or on protections such as the provider's data processing terms and standard contractual clauses. Write to us for details of the safeguard that applies.

13. How long we keep data

An automatic job runs every day and removes:

  • scan records: after about 25 months;
  • feedback left through a feedback code (a star rating and an optional comment, with no IP address or contact details): after about 25 months, or sooner if the code's owner deletes it;
  • fault reports on asset tags, with their photos: after 12 months, or sooner if the owner deletes them. The reporter's phone number goes after 30 days;
  • security and audit records: after about 24 months;
  • email logs: after about 12 months;
  • the hashed copy of confirmed email addresses: after about 24 months;
  • password reset and email confirmation records: after 30 days;
  • closed abuse reports: after about 24 months. Open reports stay until they are handled;
  • website sessions once they expire, and mobile app sessions 30 days after they expire or are revoked.

Account, workspace, code and profile data stays while your account exists. It is not deleted automatically when a subscription ends or is cancelled, so you can come back. You can delete your account or workspace yourself in Settings, or ask us to, and we may delete it as the Terms of Service describe. A workspace with disabled content, or a report that is recent or that we've confirmed, can't be deleted from Settings while we deal with it. A report we haven't reviewed holds deletion for up to 14 days; after that the deletion goes ahead and the records about that report are kept. Sign-ups that are never confirmed by email are removed after 7 days.

When an account or workspace is deleted, its personal data goes: users, codes, scan history, profiles and images. Log entries keep only the action and time, unless they are needed for an abuse case, and abuse reports and their records stay for that purpose. Payment records stay for as long as tax and accounting law requires, without your name, the workspace link or our notes and references, so only the amount, date, period and a payment category remain. Short links and profile link names are never given to anyone else, and once you confirm your email, we keep a scrambled (hashed) copy of your email address for 24 months, even after you delete your account, so the free trial can't be repeated. The address can't be read back from it.

Deleting a dynamic code from your dashboard stops and archives it. Its scan history stays until the 25-month period ends, and its short link is not reused while that record exists. Ask us if you want the history removed sooner. Deleting a profile, menu or asset page removes the page with its menu items, service history and fault reports, and images that nothing uses any more are deleted automatically by a daily job.

We take daily backups and keep the newest 14 on the server. An encrypted copy is also kept off-site in Cloudflare R2: daily copies for about 14 days, weekly copies for about 2 months and monthly copies for about 6 months. Deleted data leaves those backups as they are replaced, and we restore backups only to recover from an incident.

14. Your rights

Depending on where you live and the law that applies, you can:

  • ask what we hold about you and get a copy;
  • correct inaccurate data;
  • delete your account or workspace in Settings, or ask us to delete data;
  • restrict how we use it, or object to that use;
  • receive your data in a portable format, or have it sent to another provider where that is possible;
  • withdraw consent;
  • ask for a person to review an automated decision.

To use a right, email support@qry.nexlla.com from your account address and tell us what you want. We may need to confirm who you are. We answer within 30 days, and if a request is complex we will tell you if we need longer, as the law allows. These rights have legal limits: we can keep what we need for legal duties or to establish or defend claims. You can change most account details, and export a code's scan data as CSV, yourself in the dashboard.

If you scanned a code: scan records don't contain your name or IP address, so we usually can't tell which ones are yours. You can also contact the code's owner.

If a customer controls your data, we will pass your request to them or help them answer it.

You can complain to the UAE Data Office, or to the data protection authority where you live or work.

15. Children

QRy is not for children. Accounts are for people aged 18 or over, and we don't knowingly collect personal data from anyone younger. If you believe a child has given us personal data, or that a profile shows a child's data without proper permission, write to us and we will remove it. Anyone can scan a QR code, so customers must make sure that what they publish suits its audience.

16. Security and breach notice

Connections use HTTPS. Passwords are hashed with scrypt, sessions and API keys are stored hashed, two-step verification is available, sensitive actions are rate limited and logged, and access to production data is limited to the people who run the service. No system is perfectly secure, and we can't promise that data will never be exposed.

If a personal data breach is likely to put people's rights at risk, we will notify the relevant authority and the affected people as the applicable law requires and within its time limits (under the GDPR, the authority within 72 hours of becoming aware, where notice is required). If a customer controls the affected data, we will tell the customer without undue delay.

17. Changes and contact

We'll post changes here with a new date, and email account holders about important ones. Questions or requests: support@qry.nexlla.com.

See also: Terms of Service · Acceptable Use Policy · Cookie Policy