Privacy
Your surveys stay on your phone.
There is no account, no cloud sync, and, in the released app, no copy of your work on our side (beta builds differ; see §5). This notice says exactly what that means, and is honest about the few things that do leave the device.
1. The short version
- Luxwork has no account and no sign-in. We do not ask for your name, email or phone number to use it.
- Your surveys, photographs and reports are stored on the device in the app's own storage. There is no cloud sync — in the released app we do not receive them and cannot read them (beta builds differ; see §5).
- Data leaves the phone only when you export or share it, and it goes wherever you send it.
- There is no analytics, no advertising identifier and no tracking — only crash and error reporting, described in §5.
- Beta builds installed through TestFlight differ in two ways: a crash report can also carry a survey's readings and layout, but never who or where the survey is for, and we see each tester's name and email (§3 and §5).
- This website sets no cookies and runs no analytics scripts or third-party code. Our servers keep a log of requests, including your IP address, for 90 days (§8).
- If you join the beta list on this website, we keep your name, work email and a few answers until 30 days after Luxwork launches at the latest. If you join it through one of our LinkedIn ads instead, LinkedIn passes us the same kind of details from its form (§8). If you also tick the box for Luxwork emails, we keep your email address for those until you unsubscribe (§8).
- If your business does lighting surveys, we may have written to it about testing Luxwork. We hold only business details we found publicly, we delete them 12 months after we last wrote, and we stop the moment you ask (§9).
2. What the app stores on your device
| What | Where it is kept |
|---|---|
| Surveys — readings, the plan or grid, site and area references, notes, and the finished report | The app's private storage on the device |
| Photographs you take or attach to a survey | The app's private storage on the device |
| Your surveyor details — the name that prints on a report, and your declared knowledge status | The device keystore (iOS Keychain / Android Keystore) |
| The signing key used to sign each survey record, so any change to the record breaks the signature check | The device keystore. The private half never leaves the device and is not known to us |
| Details of the meters you use, including calibration dates you enter or import | The app's private storage on the device |
Deleting a survey in the app removes it. Removing the app removes everything it holds. Because none of it reaches us in the released app, and a beta crash report (§5) holds too little to rebuild a survey from, we cannot restore it for you — which is why the app tells you plainly which surveys have never been exported.
3. What leaves the device, and when
When you export or share
Exporting hands the file to your phone's own share sheet. Where it then goes — email, a cloud drive, a colleague — is your choice and is governed by whichever service you send it to. Luxwork does not send a copy anywhere else.
Rule-set updates
The app downloads a signed catalogue of rule sets so that the requirements it judges against can be corrected or extended without a new release. This is a download only: nothing about you, your surveys or your device is sent with the request, and the catalogue is checked against a key held in the app before it is trusted.
App updates
The app checks for over-the-air updates through Expo's update service, which is a download of new application code. No survey content is included in that exchange.
Beta testing through TestFlight
Before launch, beta builds of Luxwork are installed through TestFlight, which Apple runs under its own privacy policy. Apple holds your Apple ID email and your name. We see the same name and email in App Store Connect, Apple's service for app developers, and use them only to invite you and run the test. We delete them 30 days after the pilot ends.
If you send feedback through TestFlight, it reaches us the same way, along with any screenshot you attach, so check a screenshot before you send it. Apple can also pass us crash logs from a beta build. We delete feedback and those crash logs 30 days after the pilot ends, the same as your name and email.
Lawful basis: legitimate interests (UK GDPR Article 6(1)(f)) in running a test with people who have agreed to take part.
4. What we deliberately do not do
- No product analytics, usage tracking or behavioural profiling in the app. On this website we count visits from our own server log (§8), and that is all.
- No advertising identifiers, ad networks, or data sold or shared with brokers.
- No social media SDKs, no embedded chat widget, no fonts or scripts loaded from third parties on this site.
- No location tracking. The app does not record where you are.
On Android, the operating system has historically required the “fine location” permission before an app is allowed to scan for Bluetooth devices. Luxwork asks for it for that reason only, so it can find your meter. It does not read your position and does not store one.
5. Crash and error reporting
When the app fails, it can send a technical report so the fault can be found and fixed. This is the only telemetry in Luxwork, and it is deliberately narrow:
In the released app
- It is processed by Sentry, our error-monitoring provider, on their EU infrastructure.
- It carries the shape of the failure — the error, where in the code it happened, the app version, the operating system, the device model, the app update channel and update id, the names of the screens the app moved between, and, for a handled error, a code for the step that failed.
- It is configured not to attach personal information, and by design it must never carry a site name, address, drawing number, area reference, client name or any reading. Nothing in a report identifies which survey was involved.
- There is no session recording or screen replay.
In beta builds (TestFlight)
Beta builds send crash reports in the same way. To help us reproduce a fault during testing, a report from a beta build can also carry technical data about the survey that was open:
- the readings, with when and how each was taken: the time, the height and tilt of the meter, and whether the value came from the meter or was typed in;
- the grid and plan layout: where each point sits, the size and shape of the area in metres, and which points were left out, by a coded reason;
- the survey settings, such as the maintenance factor, control regime, installation status, the date the lighting was last maintained and the timings of an emergency lighting test;
- the rule set, by its reference in our library (requirements you set up yourself are recorded only as your own, without their names);
- the meter model, as a code, for a meter connected by Bluetooth, and a count of photographs.
It never includes site names, addresses, level or area names, client or project references, the surveyor's name, notes, comments, photographs, meter serial numbers or IP addresses. The app picks the survey data field by field and keeps only numbers, codes and times, so no text you have typed can travel with it.
These reports go to Sentry in its EU data region, as they do from the released app. Sentry keeps each crash report, from a beta build or the released app, for up to 30 days and then deletes it. The released app never sends any of this survey data.
Lawful basis for beta builds: legitimate interests (UK GDPR Article 6(1)(f)) in finding and fixing faults during testing. Testers are told about this before they install a beta build.
Lawful basis: legitimate interests (UK GDPR Article 6(1)(f)) in keeping the app working. You may object at any time by writing to privacy@ubervisor.app.
6. Your phone's own backup
If iPhone or iPad backup is switched on it already includes this app's files. Android's own app backup covers the app's folder but is capped at around 25 MB per app, so larger survey sets are dropped without warning. Those backups are operated by Apple and Google under their own terms; Luxwork has no visibility of them and makes no promise about them.
7. Your rights
Under UK GDPR you have the right of access, rectification, erasure, restriction, objection and portability. In practice, for almost everything Luxwork holds, you exercise those rights directly on your own device: the data is yours, on your phone, and you can read, correct, export or delete it without asking us.
For anything we do hold (an email you send us, a crash report, your name and email if you test Luxwork through TestFlight, your beta sign-up, on this website or through LinkedIn, your choice to get Luxwork emails, our record of having contacted your business, or a line in this website's server log), write to privacy@ubervisor.app and we will respond within one month.
If you are unhappy with how we have handled your data, you can complain to us at the same address. We acknowledge every complaint within 30 days and tell you what we found and what we did. You can also complain to the Information Commission, the UK's data protection regulator (still known as the ICO), at ico.org.uk/make-a-complaint.
8. This website
luxwork.app is a set of static pages. It sets no cookies, and it embeds no analytics scripts, no advertising pixels, no third-party fonts and no chat widget. Nothing on the page reports back about you. The one form on the site is the beta sign-up on the home page. It sends what you type to us when you press its button, and nothing before that. If you arrive through one of our links or ads, the page reads the campaign name from the link you arrived by and sends it with the form only if you sign up. Nothing is stored in your browser.
Server logs
Like almost every website, the servers that deliver these pages keep a record of each request. We keep that log. Here is what that involves:
- What is in it: the date and time, the page you asked for (including any tag on the link, such as
utm_source=linkedin), the page that linked you here, your browser's user-agent string, your IP address, and the country Amazon CloudFront works out from that address. There are no cookies in it, because the site sets none. - What we use it for: counting visits (how many, which pages, and which links brought people here) and diagnosing problems with the site. Nothing else. We do not use it to identify you, to build a profile of you, or to follow you to other sites, and we do not combine it with any other information we hold.
- Who gets it: only us. It is kept in a private Amazon Web Services storage bucket in London (eu-west-2), which AWS runs for us as our processor. It is not shared with or sold to anyone else.
- How long we keep it: 90 days. After that it is deleted automatically.
The pages reach you through Amazon CloudFront, a network of servers that handles each request on its way through, usually at a location near you. The log itself is kept in London.
Lawful basis: legitimate interests (UK GDPR Article 6(1)(f)) in running the site and knowing whether people can find it. You may object at any time by writing to privacy@ubervisor.app. If you want to see what the log holds about you, tell us your IP address and roughly when you visited. The log has no name or email address in it, so that is the only way we can find your lines.
Beta sign-up list
Before launch, you can ask to test Luxwork using the form on the home page. Here is what happens to what you send:
- What we keep: your name, your work email, your role, the meter you would use if you chose one, and your confirmation that you have an iPhone or iPad. We also keep the wording you agreed to and when you agreed, so we can show what you signed up for. If one of our links or ads brought you to sign up, we record which one it was, by its campaign name only, and delete that with your beta details.
- What we use it for: to invite you to test Luxwork and to ask you about the beta. When we invite you, we ask for the email address of your Apple ID, and from then on the TestFlight part of §3 applies too.
- Where it is kept: on UberVisor's own systems in the UK, in a database on Amazon Web Services in London (eu-west-2), which AWS runs for us as our processor. The form sends it to waitlist.ubervisor.app, our own server, which is also in London. We do not keep your IP address or browser details with it.
- How long we keep it: we delete it 30 days after Luxwork's public launch, or sooner if you ask. If Luxwork has not launched a year after you signed up, we delete it then.
- How to leave: use the link in any email we send you about the beta, or email privacy@ubervisor.app. Leaving the beta list does not stop Luxwork emails if you asked for them; those have their own unsubscribe link.
Lawful basis: your consent (UK GDPR Article 6(1)(a)), given with the box on the form. You can withdraw it at any time in the ways above.
Beta sign-ups through LinkedIn
We also run ads on LinkedIn from Luxwork's LinkedIn page. Some of them open a short LinkedIn form so you can join the beta list without leaving LinkedIn.
- What LinkedIn passes to us: your first and last name, your work email, your job title and your company, as you leave them on the form. LinkedIn fills these in from your profile, and you can change them before you send the form. We also get your answer to “Which lux meter do you use?” if you give one, whether you ticked each box, when you sent the form, and which of our ads and forms it came through.
- What we use it for: to invite you to test Luxwork and to ask you about the beta, the same as a sign-up on this website. If you tick the box for Luxwork emails, the Luxwork emails part below applies to your email address.
- Where it goes: we download the sign-ups from LinkedIn and add them to the same beta list, in the same London database. We delete the downloaded file once it is added. We don't upload anything about you to LinkedIn.
- LinkedIn's own copy: LinkedIn keeps what you send through its form, and data about the ads you see, under its own privacy policy. For that copy LinkedIn is a separate controller, not our processor. You can ask LinkedIn about it through linkedin.com/legal/privacy-policy.
- How long we keep it: the same as the beta list above. We delete it 30 days after Luxwork's public launch, or sooner if you ask. If Luxwork has not launched a year after you signed up, we delete it then.
- How to leave: use the link in any email we send you about the beta, or email privacy@ubervisor.app. Luxwork emails have their own unsubscribe link.
Lawful basis: your consent (UK GDPR Article 6(1)(a)), given with the box on the LinkedIn form. You can withdraw it at any time in the ways above.
We choose who sees these ads by job title, skills, industry and location. We don't give LinkedIn a list of people. This website still has no LinkedIn tag or pixel, so a visit here tells LinkedIn nothing.
Luxwork emails
The beta form has a separate box for occasional emails about Luxwork. It is not ticked unless you tick it, and you can join the beta without it.
- What we send: news about Luxwork, such as new features, launch news and offers. We expect to send one a month at most.
- What we keep: your email address, the wording you agreed to and when you agreed. We do not keep your name, role or meter for these emails.
- How we send them: through Amazon Simple Email Service in London (eu-west-2), which AWS runs for us as our processor. The list is kept in the same London database as the beta list.
- Who else gets the list: nobody. We do not sell it or share it.
- How to stop them: every email has an unsubscribe link, and one click is enough. You can also email privacy@ubervisor.app. Unsubscribing deletes your address from this list. It does not take you off the beta list; that has its own link.
- How long we keep it: until you unsubscribe or ask us to delete it. It is not deleted with the beta list.
Lawful basis: your consent (UK GDPR Article 6(1)(a), and regulation 22 of the Privacy and Electronic Communications Regulations for the emails themselves). You can withdraw it at any time with the unsubscribe link.
9. Businesses we contact about Luxwork
Before launch, we write to a small number of UK firms whose own websites say they carry out lighting surveys or lux testing, or that they install, test or maintain lighting, including emergency lighting, to ask whether they would like to test Luxwork. If we have contacted your business, here is what we hold and why.
- What we keep: your business's name, website, town or region, the lighting services its website describes, and its general contact details: a shared email address such as info@, its main phone number, its website contact form or its LinkedIn company page. For a limited company we also keep its Companies House number. We note when and how we contacted the business and what came of it. We don't record the names, personal email addresses or mobile numbers of the people who work there, even when a website shows them.
- Where we got it: from your business's own website, the Companies House register, and public trade and professional directories.
- What we use it for: to invite your business to test Luxwork, and to follow up once if we hear nothing. We use it for nothing else. We don't add it to any other list, and we don't sell or share it.
- How we get in touch: we email or message limited companies and other incorporated businesses only. We don't email or message sole traders or ordinary partnerships unless they have asked us to. We may phone any business after checking the Telephone Preference Service and the Corporate Telephone Preference Service, or write to it by post.
- If you reply: we keep your reply, with your name and anything else you tell us, in our email and use it to answer you. If you go on to join the beta, the beta sign-up list part of §8 applies from then on.
- Who else handles it: our email, including any reply you send us, runs on Microsoft 365, which Microsoft provides to us as our processor. The list itself is kept on UberVisor's own computers in the UK. Nobody else gets it.
- How long we keep it: we delete it 12 months after we last contacted your business. If you ask us to stop, we delete it straight away, apart from the short note described below.
Your right to object. You can tell us at any time to stop contacting your business. Reply “no thanks” to any message from us, tell us on the phone, or email privacy@ubervisor.app. We will stop, and we won't ask why. We then keep only the email address, phone number or web address you asked us not to use, and the date you asked, so that we never contact you again. We keep that note for as long as we contact businesses about Luxwork.
Lawful basis: legitimate interests (UK GDPR Article 6(1)(f)) in finding UK surveyors to test Luxwork before it launches.
10. Children
Luxwork is a professional tool for workplace lighting surveys and is not directed at children.
11. Changes
If what the app does with data changes, this page changes with it and the version at the top is raised. Material changes will be described in the app's release notes.
12. Contact
UberVisor Ltd, registered in England & Wales, company number 17279799. Registered office: 204C High Street, Ongar, Essex CM5 9JJ. Email privacy@ubervisor.app.