AR Works (ar.works) is operated by Qode LTD, a company registered in England and Wales (company number 17259547) with its registered office at Liberty House, 30 Whitchurch Lane, Edgware, England, HA8 6LE. AR Works is a Qode LTD product. For the personal data described in this policy, Qode LTD is the data controller - except for school-managed student accounts, where the school is the controller and we process data on its behalf (see section 8).
Questions, requests, or complaints: privacy@ar.works.
1. What we collect
- Account data. Your email address, a password (stored only as a bcrypt hash - never in plain text), an optional display name, your preferred language (so the site and our emails reach you in it), and your role, plan, and account status. We also record when your account last signed in, when it was last active, and which days, and which hours of those days, it was active (we keep the hourly record for 35 days), so that unused or unexpectedly active accounts are visible to our administrators and so we can produce internal, aggregate statistics about how AR Works is used (for example, how many accounts are active each week). These are dates and timestamps only - we do not store your IP address or device details against your account, except the technical details you choose to send with a bug report (see Bug reports below).
- Login streak. If you have a personal account (not a teacher or student account), we use the record of the days your account was active (see Account data above) to count how many days in a row you sign in. We store the date your streak counts from: the day of your last streak reward or, for every account that already existed when we introduced the login streak (teacher and student accounts too), the day before that. Only a personal account with a verified email address gets a reward, and a reward changes your account: on Free or a Pro trial it adds 2 days of Pro, and on a paid Pro plan it moves your next payment back by 5 days, which we ask Stripe to do. Stripe then keeps a note on your subscription of the streak that moved the payment. A completed streak can also add bonus 3D scans to your account (1 on Free, 7 on Pro), and we store the date of the last streak that added them.
- Your content. The AR projects you build (scenes, objects, animations, logic) and the media you upload (images, video, audio, 3D models), plus share links for projects you publish.
- Your Asset Library. The images, video, audio and 3D models you upload to your Asset Library, the folders you put them in, and who you choose to share them with. Library files are stored privately: they can be seen only by you, the people you share them with, your school's teachers (if you have a school student account) and our administrators, and they are served only through short-lived links.
- View counts. Each published experience keeps a simple count of how many times it has been opened, and when it was last opened, so you can see it on your dashboard. Nothing about who opened it is recorded - no IP address, device, location, or account.
- "What are you making?" Your dashboard may ask what you are using AR Works for (for example a school assignment or client work). Answering is optional - you can skip it. If you answer, we store your answer with your account. Our administrators can see which accounts gave which answer, and we also count the answers in aggregate (for example, how many people use AR Works for teaching). We use them to improve AR Works. If you are on our mailing list and answered on or after 2 November 2026, we may also use your answer to choose which of our emails we send you. Answers given before this notice was first added (on 2 November 2026) are only ever used in aggregate.
- Updates, news and offers. Whether you are on our mailing list, and when you last chose. If you sign up yourself, the box on the sign-up form sets this: it starts ticked, and you are on the list unless you untick it. Accounts created before that box existed are asked once and join only if they say yes. School student accounts are never on the list. When we send you a mailing, we keep a record of it: which mailing, when, and whether it was delivered, bounced or marked as spam. Marking one of our mailings as spam takes you off the list.
- News posts. When you close a News post from AR Works (the short note shown after you sign in), we store with your account when that post was published, so it stays closed until we publish a newer one.
- Enquiries and support. If you use a contact form ("For schools" or "Contact us"): your name, email address, your message, the language of the page you sent it from, and - for school enquiries - the school name and whether you are a student or a teacher. A demo request also collects your phone number, your role, the number of students and a preferred time, if you give them. If you open a support ticket while signed in: the subject you choose, your messages, and our replies.
- Bug reports. If you use "Report a bug": what you write and, unless you untick "Include technical details", the address of the page you were on (without anything after a ? or #), your browser's user-agent text (its name and version and your operating system), your screen size and the language you use AR Works in. On the website the report is a support ticket on your account. From AR Works Studio it always carries the Studio version, your language, the email address and name you enter and, to stop spam, how long the form was open, and it is sent over the internet to our contact form.
- AREngine device reports. If you send us a device report from the AREngine app (see section 2): a technical description of your device (its maker and model, cameras, motion sensors, screens and connected USB devices, and how AREngine will use them), the app's version, any note you add, your email address if you give one, and the language of the page you sent it from. A report is not linked to an account.
- 3D scan photos. If you scan an object on the website, the photos you take with your phone are uploaded to our file storage. To build the 3D model, they are copied to our own server in Finland (see section 4). They are deleted from that server when the build ends, and from our storage when the model is ready, or when a scan fails or is cancelled. The built model is kept for 7 days unless you save it first. Scan objects only: the photos must not show people. AR Works Studio builds scans on your own computer and sends us nothing.
- Billing data. Payments are processed by Stripe. We store only Stripe customer and subscription identifiers and your subscription status. Your full card details never touch our servers.
- Technical data. IP addresses and request metadata are used transiently for security and rate limiting, and appear in short-lived infrastructure logs at our hosting providers.
- Analytics data (only with your consent). If you opt in to analytics in the cookie banner, we use Google Analytics to understand how the site is used - which pages are visited and how visitors and users move through them. It is off unless you opt in, is never enabled for signed-in student accounts, and is never used for advertising. We ask Google to record the page address without its query string. See the Cookie Policy for the cookies involved.
- Security tokens. Sign-in refresh tokens and password-reset tokens are stored only as cryptographic hashes. Reset links expire after 1 hour and are single-use.
2. Your camera
The AR viewer asks for camera access so it can track your target image and render the AR scene. Camera frames are processed entirely on your device by the in-browser AR engine. They are never recorded, stored, or transmitted to us or anyone else. Denying camera access stops the AR experience but has no other effect. The 3D scan page is different: the photos you take with it are uploaded to us to build the 3D model (see section 1).
In scenes that use hand interaction, the AR viewer also uses the camera to track your hand. This works the same way: on your device only, with nothing recorded, stored or sent. The editor’s Preview can track your hand with your computer’s webcam as well, and only after you turn on Use webcam.
The AREngine app for Android
The AREngine app plays projects made in AR Works on an Android phone. It has no account and no sign-in, and it has no permission to use the internet, so it sends nothing by itself: no usage data, no crash reports, no advertising identifiers and no location. If you choose Send to AR Works on its Device report screen, your browser opens a page on ar.works that shows the report, and when you press Send there we receive it: a technical description of your device (its cameras, motion sensors, screens and connected USB devices, and how AREngine will use them), the app's version, any note you add, your email address if you give one, and the language of the page. The report holds no serial numbers and nothing from your projects. We use it to make AREngine work on more devices, and we keep it as we keep contact-form messages: for as long as needed to respond and follow up.
It uses the camera and the motion sensors only while a project is open, to place the project on a picture or in your room and to follow your hands. Camera frames are processed on the phone and are not stored or sent. The one exception is Record 10 seconds in the app's menu, which only you can start: it keeps a short recording of camera frames and motion readings inside the app on your phone, for troubleshooting.
Projects you open are copied into the app's own storage on your phone. Remove deletes a project's copy, and uninstalling the app deletes everything it stored. If you send us a recording or a question yourself, by email or through our contact form, we handle it as this policy describes.
3. How we use your data
| Purpose | Legal basis (UK/EU GDPR) |
|---|
| Providing the service - accounts, projects, publishing, the AR viewer | Performance of a contract |
| Processing subscription payments and keeping billing records | Performance of a contract; legal obligation |
| Responding to enquiries, contact messages, and support tickets | Steps prior to a contract; legitimate interests |
| Transactional email (e.g. password resets, a warning before an inactive Free project is deleted, an email when we give you a free trial or add days to one, and a reminder before a free Education trial ends) | Performance of a contract; legitimate interests |
| Emailing updates, news and offers about AR Works to people on our mailing list | Consent, if you said yes when asked; legitimate interests, if you left the box ticked at sign-up |
| Security, abuse prevention, rate limiting | Legitimate interests |
| Producing internal, aggregate statistics about how AR Works is used, to help us improve it | Legitimate interests |
| Understanding how the site is used (Google Analytics) | Consent |
We do not show ads, profile you, or sell or rent personal data to anyone. We email updates, news and offers only to people on our mailing list, and you can leave it at any time in your account settings or with the unsubscribe link in any of those emails. We also produce internal, aggregate usage statistics from the account data described above. These statistics are used only by us, and only to improve AR Works - they are never sold, never shared with any third party, and never used to train AI or machine-learning models. The only optional, non-essential processing is Google Analytics, which runs solely on your consent and can be turned off at any time from Cookie settings in the footer.
4. Where your data lives
We use a small number of hosting and infrastructure providers (processors) to run AR Works:
| Provider | What they do | Location |
|---|
| Neon (PostgreSQL) | Database - accounts, projects, enquiries | London, UK (AWS eu-west-2) |
| Cloudflare R2 | Uploaded media files | Western Europe |
| Render | API hosting | Frankfurt, EU |
| Vercel | Website delivery (global edge network) | Global (edge caching) |
| Google (Google Ireland Ltd / Google LLC) | Website analytics - only if you opt in (Google Analytics 4) | EU / US (SCCs, EU-US Data Privacy Framework) |
| Stripe | Payment processing | Per Stripe's own policies |
| Resend | Email delivery - account emails and our mailing list | Per Resend's own policies |
| jsDelivr (CDN) | Serves the AR viewer's open-source libraries | Global CDN |
| Hetzner Online GmbH | Runs the server that builds 3D models from the photos of a 3D scan | Finland |
Application data is stored in the UK/EU. Where a provider (such as Vercel's edge network, Stripe, Resend, jsDelivr when its CDN serves a request, or Google Analytics when you opt in) processes data outside the UK/EEA, transfers rely on recognised safeguards such as the UK Addendum, Standard Contractual Clauses, or an adequacy framework. When your browser loads the AR viewer, the jsDelivr CDN receives standard request data (your IP address and browser details) in order to serve the files.
5. Published projects are public
Publishing a project creates a share link and QR code. Anyone with the link can view the project - its name, content, and media - until you unpublish it. Uploaded media is served from unguessable public URLs from the moment it is uploaded; those URLs are not listed anywhere, but anyone who has a URL can open the file. Please don't upload media containing confidential information or other people's personal data without their agreement.
Files in your Asset Library are different: they are private and have no public address. A file you import from your library into a project is copied, and the copy is project media - it is public with the project once you publish it, like any other project media.
6. Retention and deletion
- Account data is kept for as long as your account exists.
- From 1 December 2026, a project on a Free account that hasn't been edited for 30 days is deleted automatically, along with its media files. We email the project's owner at least 7 days before it is deleted, and nothing is deleted without that email; any edit (or choosing Keep project in that email or on your dashboard) keeps it. A project that is over your plan's project limit can be kept once it is back within the limit. Projects on Pro and Education accounts are not affected.
- An account locked because its email address was never verified is deleted, with everything in it (projects, published links, uploads, scans and library items), 30 days after we send the first of three reminder emails (30, 7 and 1 days before). We delete it only once at least one reminder has been delivered, or when every reminder has bounced: an address that can never receive email can never be verified, so the account is still deleted after the 30 days. A message sent through the form on the locked account's page pauses this until we have helped. Accounts that have ever paid, are on a plan other than Free, or have a free trial are not affected.
- Deleting a project or account removes the database records immediately (projects, assets, share links). Copies of media files in object storage are removed on a best-effort basis and may persist for a short period afterwards.
- Password-reset links expire after 1 hour and can be used once.
- Contact-form messages and support tickets are kept for as long as needed to respond and follow up.
- Stripe retains transaction records in line with its own legal obligations (e.g. tax and anti-fraud rules).
There is currently no self-service account deletion - email privacy@ar.works from your account email address and we will delete your account and content. Students on school-managed accounts should ask their teacher or school.
7. Your rights
Under the UK GDPR and EU GDPR you can ask to access, correct, delete, restrict, or receive a copy of your personal data, and object to certain processing. Contact privacy@ar.works and we will respond within one month. You can also complain to the UK Information Commissioner's Office (ico.org.uk) or your local EU supervisory authority.
8. Children and school accounts
Self-service registration is for users aged 13 or over. Student accounts are different: they are created and managed by a teacher at the student's school, and the school is the data controller for them - we process student data only on the school's instructions. Student accounts need only a login identifier (which can be a school-controlled alias rather than a personal email), a password, and a display name (which can be a non-identifying label such as a class alias); we encourage schools to use non-identifying values for both. Schools can ask us to delete student accounts and content at any time. We never enable Google Analytics for student accounts - analytics is not loaded while a student is signed in.
9. Security
All traffic is encrypted in transit (TLS). Passwords are stored as bcrypt hashes; session and reset tokens are stored only as hashes; sign-in state uses an httpOnly cookie that JavaScript cannot read. Access to accounts and projects is role-based, and the API is rate-limited. No system is perfectly secure - if a breach affects your data we will notify you and the regulator as required by law.
10. Changes to this policy
We will post any changes here and update the date at the top. If a change materially affects how we handle your data, we will tell you through the site or by email before it takes effect.
Qode LTD (company number 17259547), Liberty House, 30 Whitchurch Lane, Edgware, England, HA8 6LE. Email: privacy@ar.works. See also our Terms & Conditions and Cookie Policy.