Back to CaperQwest · Terms of Service
Privacy notice
Last updated: 2 October 2026
This notice explains how Remidus Ltd collects, uses, stores and shares personal data across CaperQwest: this website, the beta application form, invoices and payments, Qwest Master logins, onboarding, the Control Room, the player app, first-party site analytics, and first-party product research. It is written to meet the UK General Data Protection Regulation (UK GDPR), the Data Protection Act 2018, the Data (Use and Access) Act 2025 and the Privacy and Electronic Communications Regulations 2003 (PECR).
1. Who we are
CaperQwest is provided by Remidus Ltd, a company registered in England and Wales (company number 15130513). Registered office: 167-169 Great Portland Street, London, England, W1W 5PF. Email: enquiries@remidus.com.
CaperQwest is sold to businesses. Individuals use it at work: the person who applies and pays, the Qwest Master who designs and runs a Qwest, and the colleagues who play in Sqwads.
2. Our role, and your organisation's role
- Remidus is the controller for this website and its analytics, beta applications, identity checks, invoicing and payments, Qwest Master accounts, the emails we send, the security of the service, and first-party product research described in section 8.
- The customer organisation is the controller of its own players' gameplay data (Sqwad names, answers, photos and location) and of the Qwest content its Qwest Master creates. Remidus processes that data as its processor under our Terms of Service: to run the Qwest on the customer's instructions, and, where the customer has accepted those Terms, to take de-identified design and play records for the research in section 8. Players who have questions about a Qwest should ask their organiser first. We will help the organiser answer them.
3. Beta applications
When you apply at /apply we collect:
- About you: title, first name, surname, work email, work phone, job title and your department or team.
- About your company: company name, Companies House number and registered address (looked up from the public register as you type), billing address, and VAT number if you give one.
- About your team and events: sector, whether you have run a treasure hunt before and with whom, how designing a hunt yourself sounds, how the price feels, and what you need before you can buy. After the invoice is issued you can optionally answer more: team size and base, what is hardest, what you would use CaperQwest for, and indoors or outdoors. Some of those can also be answered later in the Control Room.
- Your choices: the package you picked, the required consent box and the optional news box.
We use this to decide on your beta application, to prepare and send your invoice, to set up your Qwest Master login, to contact you about the beta, to understand our market, and to join your job, sector and team answers to how you later use the Control Room for the research in section 8. The consent box also covers our use of your company's name and logo, and a mention that you are a CaperQwest beta customer, in our marketing and on our websites. You can ask us to stop that at any time for future materials.
Lawful bases: taking steps at your request before entering into a contract, and performing that contract (application, invoice, login); our legitimate interests in understanding our customers and improving CaperQwest (the survey answers and the research join); and your consent (publicity and optional news emails). You can withdraw consent at any time by emailing us. This does not affect anything we did before you withdrew it. You can object to the research join in the Control Room or by emailing us.
Applications are stored in our own database on our UK server. Our team can see them in a staff-only back office protected by Google sign-in and limited to named Remidus staff.
4. Identity checks
When you press Verify & Continue on the first page of the form, we check that your work email, name, job title and company belong together. We do this to stop people applying, and being invoiced, in someone else's or another company's name. The checks are:
- whether your email domain can receive email, using a public DNS lookup (sent through Cloudflare or Google public DNS; only the domain name is sent);
- whether your company's own website shows its registered name or company number, which UK companies must display;
- whether you are listed as an officer of the company on the public Companies House register;
- a reverse email lookup: we send your work email address to Hunter and, where enabled, People Data Labs. Each returns any public professional profile (name, job title and employer) it holds for that address. We send nothing else to them.
We show you whether your details matched, but never what a lookup returned. A short summary of the result is kept with your application so our team can review any mismatch. The raw lookup and each Verify attempt are deleted after 90 days, and a successful lookup is reused within that time so we don't repeat it. A mismatch never stops you applying on its own: you can correct your details, or tell us they are right and carry on, and a person on our team reviews any flag.
Lawful basis: our legitimate interest in preventing fraud and in invoicing the right company. Hunter and People Data Labs handle the lookup under their own privacy policies. You can object by emailing enquiries@remidus.com.
5. Invoices, payments and Zoho
We issue invoices with Zoho Invoice, run by Zoho Corporation, using its EU data centre. To create an invoice we send Zoho your name, company name, work email, phone number (if given), billing address, VAT number (if given), the package and price, and a note marking you as a CaperQwest customer. Zoho emails the invoice from caperqwest-payments@remidus.com, stores the invoice and payment records, and tells us when an invoice is paid.
- Bank transfer: we match your payment reference against our bank statements. Our bank sees the payer name and account details you pay from.
- Card: where offered, card payments are taken by Stripe on Zoho's payment page. Your card details go straight to Stripe and are never seen or stored by Remidus. Stripe processes them under its own privacy policy, including for fraud prevention.
After you apply we show you an invoice page with your PDF, payment details and, once paid, where to set your password. Its web address is private to you and stops working 14 days after the invoice due date (at least 30 days after it was issued). We keep the application and invoice record after that so we can match your payment.
Lawful bases: performing our contract with your organisation, and our legal obligations to keep accounting and tax records.
6. Qwest Master logins and the Control Room
Once your invoice is paid we create a Qwest Master account in a separate onboarding service. It holds your username, email, name, company, department or team, the Zoho customer number, your Qwest allowance, your access dates and any renewals. You choose your own password through a single-use link that expires after 7 days, or on the invoice page. The activate page and first Control Room sign-in sit under these Terms and this notice.
- Passwords are never stored in readable form. We keep only a salted hash (PBKDF2-HMAC-SHA256 with 600,000 iterations). Set-password links and invoice page links are also stored only as hashes.
- Signing in checks your username and password against that service. Your access period starts at your first successful sign-in. A signed session cookie then keeps you signed in on that browser for up to 7 days.
- Your profile: optional questions in the Control Room (team and event questions) are saved with your account on our website database so we can tailor CaperQwest to you and, unless you object, join them to the research in section 8.
- Renewals and upgrades from the Control Room create a new Zoho invoice using the details on your account. A new invoice uses the Terms in force when it is issued, including data and research.
- Qwest content you create is stored in our Qwest database: Start and End points, stops (title, area, clue, answer type, hint, reveal radius, active flag), map pins, walking routes, scoring settings, story and joining copy, QR bank assignments, announcements, and the host company and team names shown to players. In the Control Room you place Start, End and stops on a Google map by searching or tapping; we store the place name, coordinates and, when Google returns it, a place identifier. Map pins you paste may still be resolved on our server with Google Maps link lookups or OpenStreetMap Nominatim.
- How you use the Control Room: we keep a first-party log of design actions (creating a Qwest, placing Start or End, adding or saving a stop, generating a route, starting a rehearsal or pressing Play) and time spent on tabs and stop cards. We do not store the text of clues or answers in that log. See section 8.
- Player preview (In their shoes) is a rehearsal inside the Control Room. It uses the same player-app data types as a live run, tagged as a rehearsal, and is never treated as Play.
- Results exports (PDF, Excel and CSV) include Sqwad names, scores, times, stop timings, photo counts and average GPS drift. They do not include device identifiers or answers typed by players. Once you download an export, your organisation is responsible for it.
Lawful bases: performing our contract with your organisation; our legitimate interests in securing accounts, running the product and improving it through the research in section 8 (profile answers are optional; you can object to research).
7. Players (Sqwads) and the player app
Players do not create an account and we do not ask players for their name or email. When a Sqwad joins a Qwest with its code on app.caperqwest.remidus.com, we process:
- Sqwad details: the Sqwad name the players choose, and a random device ID that links one phone to that Sqwad.
- Gameplay: answers submitted, whether they were right, hints and skips used, scores, timings (walk-plus-task and time from Reveal Task to done) and which announcements were shown.
- Photos: images submitted for photo stops, stored as files on our server for the Qwest Master to approve and for the results export. People who appear in a photo can be identified from it, so organisers should tell players what photos are for.
- Location: only if a player taps Allow on the browser's location prompt. The phone sends its latitude and longitude while the Qwest runs. We keep only the Sqwad's latest position and time (not a location history) and, for photo stops, where the photo was taken. The Qwest Master can see each Sqwad's last position. The Qwest still works if location is refused. We may also record the first time a Sqwad enters or leaves a stop's reveal radius (stop id, time and distance, not a GPS trail) for scoring and the research in section 8.
- Finish point: after the last stop, the phone shows the End the Qwest Master placed (name, a map preview and a link to open it in Google Maps).
- Camera: used on the phone to scan QR codes. QR scanning happens on the phone and camera images are not sent to us, except photos a player chooses to submit.
- Offline queue: if the network drops, answers and location updates wait on the phone (in browser storage) until it reconnects.
We use this to run the Qwest for the organiser: scoring, leaderboards, photo review, maps and the end-of-Qwest results. We do not use it for advertising, we do not build advertising profiles, and we do not track players outside the Qwest. De-identified timings and radius arrive/leave events may be used for the research in section 8, as authorised in the Terms. Photos, typed answers and raw coordinates are not put in the research store. The organiser's lawful basis will usually be its legitimate interest in running a team activity. Our processing is on its behalf, except where section 8 says Remidus is the controller of the de-identified research copy.
8. Product and design research
Remidus is a research and development company. The CaperQwest beta includes first-party research into how Qwest Masters design hunts and how workplace teams play them. This is not advertising, not a third-party analytics product, and not the website cq_consent cookie. It is not switched on by Accept or Reject on any cookie banner.
When research logging is active for an account, we record:
- Who designed it (firmographics): job title (grouped into a research family), sector, department, team size, organising role, hunt experience and package, joined from the application, optional Control Room profile and onboard account. Exports for external study use a hashed research id, not your name or email.
- How it was designed: Control Room events such as creating a Qwest, placing Start or End, adding, saving or discarding a stop, choosing an answer type, searching or tapping the map, generating a route, opening Preview, and pressing Play; plus time spent on tabs and on a stop card. We do not store clue text, correct answers or QR payloads in this log.
- What was designed: snapshots of the Qwest at Play (stop counts, answer-type mix, radii, Start/End geometry, walk minutes). Place types may be stored so we can group cafés, parks, offices and the like. Coordinates in the research store are rounded.
- How it was played: de-identified timings already produced to run the Qwest (finish rate, first-try rate, hint and skip rates, designed dwell versus actual task time). Arrive/leave radius events use a stop id, a timestamp and a distance, never a breadcrumb trail. Preview / rehearsal Sqwads, demo Qwests and practice Qwests from the tutorial are left out.
We do not put player names, typed answers, photos, QR payloads or a GPS history into the research store. We do not send this stream to a US product-analytics company. We do not use session replay or keystroke capture.
The first time you sign in to the Control Room after this notice, we show a research notice. You can object there, or later by emailing us. Objecting stops new design-event logging for your account and removes your name and email from the research lab. Snapshots already taken for a Qwest you ran may be sealed and detached from your identity rather than rewritten. Lawful basis: our legitimate interests in improving CaperQwest and in honest, aggregated research on quest design and workplace team performance. You can object at any time.
Live Qwest data is still deleted on the schedule in section 14. Research snapshots are kept for 24 months, then identifiers are dropped. When a Qwest Master account is purged, research rows are sealed and detached first so a study pack cannot be re-identified from the live database.
9. Emails we send
We send service emails through Google Workspace (Google's SMTP relay) from caperqwest-reminders@remidus.com and caperqwest-payments@remidus.com, and Zoho sends invoice emails. These include your invoice, payment reminders a week and a day before the due date, a payment thank-you, your username and set-password link, access expiry and renewal reminders, and a notice if an unpaid invoice is voided. A copy of each is kept in the sending mailbox as our record. These emails are part of the service. They are not marketing, and they do not use the optional news box. Service emails include links to this notice and the Terms.
The optional news box starts unticked. If you tick it we may send occasional news about CaperQwest (lawful basis: consent). You can unsubscribe at any time by replying to any news email or by emailing us.
10. Cookies and site analytics
Cookie consent and analytics consent are different. Essential cookies keep this website working: they remember your analytics choice, load the pages and comparison table, run the application and invoice forms, and let you play the homepage video. Rejecting analytics does not turn those off. Analytics cookies (cq_vid and cq_sid) are optional and are only set if you accept.
We ask for your analytics choice the first time you visit this website. That choice is saved in the cq_consent cookie for 12 months, so we don't ask again on that browser. The cookie is set by our server, so browsers such as Safari keep it for the full 12 months. You can change your mind at any time: Change your cookie settings
Control Room and player-app research logging is not a cookie and is not site analytics. It is not controlled by cq_consent or cq_app_consent. See section 8.
Cookies on caperqwest.remidus.com (website, apply form and invoice pages)
| Name | Purpose | Lasts | Type |
|---|---|---|---|
cq_consent | Remembers whether you accepted (on) or rejected (off) analytics. This is not an analytics cookie. It stays on if you reject, so we do not ask again and the rest of the site still works. | 12 months | Strictly necessary |
cq_vid | Random visitor ID, so we can tell a returning visitor from a new one. Only set while analytics is on. | Up to 13 months | Analytics |
cq_sid | Random visit ID. Only set while analytics is on. | 30 minutes without activity | Analytics |
cq_ops | Keeps Remidus staff signed in to the staff back office. Never set for visitors. | 12 hours | Strictly necessary |
We also store cq_consent_saved in your browser's local storage, which only records that your choice reached our server.
Cookies in the Control Room and player app
| Name | Where | Purpose | Lasts |
|---|---|---|---|
caperqwest_control_session | controlroom.caperqwest.remidus.com | Signed session that keeps a Qwest Master signed in. | 7 days |
caperqwest_player_session | app.caperqwest.remidus.com | Signed session that keeps a phone joined to its Sqwad (Sqwad and device ID). | 7 days |
cq_app_consent | both | Remembers whether you accepted or rejected optional third-party content (Google Maps on the player app). In the Control Room, Google Maps is required to design stops, so Maps cookies are treated as essential. | 12 months |
The apps also keep small flags in the phone's browser storage so they work: that you completed the app access and GPS check steps, which announcements and clues you have seen, whether the Qwest has started, the offline queue, which Qwest is selected in the Control Room, and whether you have seen the research notice. The full list is in the apps' cookies policy. These are strictly necessary and are not used for advertising.
What analytics records
While analytics is on, we record the pages you view, the page or link that sent you here (including any campaign tags in the link), your IP address, the approximate location worked out from it (country, region, city) and the network it belongs to, your device type, browser, operating system, language, time zone and screen size, what you click, how far you scroll, and how long you spend on each page. On the beta application form we record which step and which question you reach, how long the form takes, and whether it was sent. We never record what you type into the form through analytics.
We use this to understand how people find CaperQwest and to improve the site and the application form. If you send an application, we link that visit to your application so we know which channels bring applicants. This is our own first-party analytics, stored in a separate database on our server. We do not use Google Analytics or any advertising or social media pixels. Location is looked up on our own server using a DB-IP database file, so your IP address is not sent to anyone for this. Analytics is only seen by the Remidus team. It is never sold, never shared with advertisers and never used to target ads. Visits by Remidus staff and known bots are not recorded.
We keep analytics records for 395 days. IP addresses are deleted from them after 395 days. After that we keep only the approximate location.
Lawful basis: our legitimate interest in running and improving this site. PECR, as amended by the Data (Use and Access) Act 2025, allows cookies used only to collect statistics to improve a website, as long as we tell you clearly and you can easily object. If you reject analytics, we delete the analytics cookies and what we recorded from your browser, and stop recording. If your browser sends a Global Privacy Control signal, analytics stays off unless you turn it on. To ask for a copy of your analytics data or to have it deleted, email enquiries@remidus.com with your IP address or the date and time of your visit.
Content loaded from other companies
Some pages load fonts or code libraries from other companies' servers. This does not set cookies on our sites, but your browser connects to those servers, so they see your IP address and browser details. See section 11.
The homepage video is part of the site working. It is a still image until you press play. Pressing play loads a YouTube player from Google's privacy-enhanced domain (youtube-nocookie.com). That is essential for the video, not analytics. Rejecting analytics does not stop it. Google may then set its own cookies.
11. Third parties we use
We never sell personal data. We share it only with the service providers below, with the customer organisation as described in section 2, with professional advisers, or where the law requires it.
| Provider | What for | Data involved | Location |
|---|---|---|---|
| IONOS | Server hosting for all CaperQwest services and databases | Everything in this notice | UK |
| Zoho Corporation (Zoho Invoice) | Invoices, customer records, payment status | Name, company, email, phone, billing address, VAT number, invoices | EU data centre |
| Stripe | Card payments, if you pay by card | Card and payment details, name, email | UK, EU and US |
| Google (Workspace) | Sending service emails, and staff sign-in to our back office | Your email address and the email contents | UK, EU and US |
| Hunter and People Data Labs | Reverse email lookup during identity checks | Your work email address only | Hunter: EU (France). People Data Labs: US |
| Companies House | Company search and officer check | Company name or number searched | UK |
| Your company's website | Checking it shows the company's registered name | Our server visits your company's own website | Varies |
| Cloudflare and Google public DNS | Checking your email domain receives email | Your email domain name only | Global |
| DB-IP | IP location database, downloaded to our server | None. Nothing is sent to DB-IP | n/a |
| Google Fonts | Fonts on the website and apps | IP address and browser details | Global |
| cdnjs (Cloudflare), jsDelivr, unpkg | Code libraries for animation, QR scanning, maps and charts | IP address and browser details | Global |
| OpenStreetMap Foundation | Map images in the apps and results PDF, and place search when a Qwest Master pastes a pin | IP address, the map area viewed, and place names searched | UK and global |
| Project OSRM (FOSSGIS e.V.) | Walking routes on the map | Approximate start and end coordinates of a route | Germany |
| Google Maps and Places | Required in the Control Room to search for places and to place Start, End and stops. Optional map previews elsewhere if accepted. "Open in Google Maps" links take you to Google. | IP address, search text, place identifiers and coordinates you pick. Google may set its own cookies | Global |
| YouTube (Google) | Homepage video. Essential for playing it, not analytics. The player loads when you press play, whether analytics is on or off. | IP address and browser details. Google may set its own cookies | Global |
Social media links on our pages are plain links. Nothing from those networks loads until you click one. The homepage video is the same: YouTube does not load until you press play, and rejecting analytics does not affect it.
12. Where data is stored and how we protect it
- Website database (SQLite on our UK server): applications and survey answers, identity check results, invoice records and reminders, paid-invoice delivery jobs, invoice page links and Qwest Master profile answers.
- Analytics database (a separate SQLite file on the same server): visits, visitors and events described in section 10.
- Onboarding database (SQLite): Qwest Master accounts, password hashes, access dates and invoice-to-login links.
- Qwest database (PostgreSQL): Qwests, stops, Sqwads, answers, scores, last GPS positions and photo records. Photo files are stored on the server's disk.
- Research store (a separate database on the same UK server): design and play events and de-identified Qwest, stop and run snapshots described in section 8. It does not hold photos, typed answers or a GPS history.
- Zoho Invoice: invoices and customer billing records, as in section 5.
All traffic uses HTTPS with HSTS. Databases are on private storage volumes that are not reachable from the internet. Services talk to each other over a private network using shared secrets. Staff access to the back office needs Google sign-in from an approved Remidus account. Passwords and one-time links are stored only as hashes. Our web server also keeps standard access logs (IP address, time, page requested and browser) for security and fault-finding, on a short rolling basis.
13. International transfers
Our servers are in the UK and Zoho holds our invoicing data in the EU, which the UK recognises as giving adequate protection. Some providers (Google, Stripe, People Data Labs, and the content networks in section 11) may process data in the US or elsewhere. Where they do, we rely on the UK-US Data Bridge for certified US companies, or on the UK International Data Transfer Agreement or Addendum built into the provider's terms.
14. How long we keep data
| Data | How long |
|---|---|
| Analytics visits and events | 395 days. IP addresses removed after 395 days. |
Cookie choice (cq_consent, cq_app_consent) | 12 months |
| Raw identity lookups and Verify attempts | 90 days (a summary stays with the application) |
| Applications that never became a paid customer | Up to 24 months after our last contact, then deleted |
| Customer, invoice and payment records (ours and in Zoho), including the application behind them and service emails | 6 years after the end of the financial year they relate to, for tax, company law and legal claims |
| Invoice page link | 14 days after the invoice due date, and at least 30 days |
| Set-password link | 7 days, or until used |
| Qwest Master account and profile answers | While you have access, and up to 24 months after your last access period ends so you can renew. Deleted sooner on request, except billing records. |
| Qwests, Sqwads, answers, photos and last GPS positions | Until the Qwest Master deletes or resets them in the Control Room (an unplayed Qwest can be deleted; a played Qwest can only be archived). After the login ends they are held for a 30-day renewal grace, then hard-deleted. Practice Qwests from the tutorial are deleted when the tour ends. |
| Research events and de-identified snapshots | 24 months, then identifiers are dropped. Objecting stops new events. A purge seals and detaches remaining rows. |
| Research notice and opt-out choice | While the account exists, and with the account if you ask us to delete it |
| Session cookies | 7 days (Control Room and player app), 12 hours (staff back office) |
15. Your rights
Under UK data protection law you have the right to ask for a copy of your personal data, to have it corrected, to have it deleted, to restrict or object to how we use it, to have it moved to another provider, and to withdraw consent. Some rights depend on the lawful basis. For example, we cannot delete invoice records we must keep by law. We reply within one month, and we may ask you to confirm who you are. Email enquiries@remidus.com.
You can object to product research in the Control Room or by email. Erasure requests cover the research store as well as applications, analytics and onboard accounts, subject to the tax records we must keep.
If you played in a Sqwad, your organiser controls that Qwest's data. Ask your Qwest Master or organiser first, or email us and we will pass it on and help. You can revoke location or camera access at any time in your browser or phone settings, and clearing site data removes the app's cookies and storage from your phone.
16. Children, automated decisions and changes
CaperQwest is a workplace product for adults. It is not aimed at children, and organisers must not use it for players under 16 without appropriate supervision and consent.
We do not make decisions about you based solely on automated processing that have legal or similarly significant effects. Identity checks flag possible mismatches for a person on our team to review. Research charts are descriptive; they are not used to decide whether you keep access.
We will update this notice when CaperQwest changes. The date at the top shows the latest version. If a change significantly affects you, we will tell customers by email.
17. Contact and complaints
Questions or requests: enquiries@remidus.com, or write to Remidus Ltd, 167-169 Great Portland Street, London, England, W1W 5PF. If you are unhappy with how we have used your data, please complain to us first so we can put it right. We acknowledge complaints within 30 days. You can also complain to the Information Commissioner's Office at ico.org.uk or on 0303 123 1113.