Legal notice and privacy

Legal notice

Tours are made by their creators.

Each tour shown with the Tour Viewer is a file created and hosted by its creator, not by the operator of this website. The creator is responsible for a tour's content; a tour's own details name its creator's contact where given. To report a tour, contact its creator, or the operator at the address above.

Links.

This website links to and loads files from services the operator does not control (see Privacy). The operator is not responsible for their content.

Privacy

In short: no accounts, no advertising, no usage statistics, and the apps set no cookies. The camera, your location and the motion sensors are used on your device; the apps do not send the camera image or the sensor readings anywhere, and your location leaves your device in two ways only, both described below: the map apps ask map services for map images and map data of the area you are in, and the anchor starter writes a placed marker's position into its link. What does leave your device: ordinary web requests, to this website and to the services named below, and, in the Recorder only, error reports.

Responsible for this website and the data described here: the operator named in the legal notice above (support@cs-util.com).

This website (every app)

• Cloudflare (Cloudflare, Inc.) hosts this website. To deliver a page it receives your IP address, the address you asked for, the time and your browser's type.
• Requests handled by the site's worker are also written to a log: the file service (addresses starting with /api/, which the Tour Viewer and the Recorder use to fetch files stored on Google Drive), and addresses that match no page. The log holds the request (for the file service, with the file's identifier), the time and your IP address. The log is deleted after 3 days. It is used only to find faults. The file service passes on to Google only the file identifier, which part of the file is needed and whether your browser's copy is still current (the cache validators).
• We rely on our legitimate interest in delivering this website, keeping it secure and finding its faults.

Tour Viewer (/tour/)

• The tour's file is downloaded from wherever its creator stored it (for example Google Drive, Dropbox, OneDrive or GitHub). That service receives your IP address and the address of this website. For Google Drive the download passes through the site's file service (above). The creator chose the service; its own privacy policy applies. A tour link that gives only a tour's name, not a full address, loads the file from GitHub (raw.githubusercontent.com), with the same data.
• Creators only: the editor and the map after finishing a tour load map images from OpenStreetMap (OpenStreetMap Foundation), which then receives your IP address and the map area shown.

What stays on your phone or computer:

• Up to five opened tours, so a revisit opens faster. The app keeps no offline copy of itself, so opening it still needs a connection, and a tour whose file still carries its creator's walk is kept only in part. Creators can clear them under "Other settings"; anyone can clear them in the browser's site settings.
• A small record per tour link, per printed code and per tour series: who signed it, and when this device first and last saw it - so a changed tour can be noticed. Together these records are a history of the tours opened on this device. They never leave it.
• For creators: how far the setup got for each tour link, the last tour link and the hosting service chosen, the text of the printed poster and the tour name you typed (per tour link), and which on-screen panels you folded.
• For creators: unsaved changes (positions, photos, the walk you recorded), until you save or delete them.

Camera, location and sensors. The camera image is processed on your phone to show the tour and to read printed codes; creators can take photos for their tour. Your location and the phone's motion sensors place the tour where you stand. The app does not send any of this anywhere.

When you create a tour. Everything you place, photograph or record stays on your device until you save the tour file and put it somewhere yourself. A tour file holds your pins, photos and the positions of your codes. It can also hold the walk you recorded (your GPS track with times, a rough 3D shape of the surroundings and the pictures the camera took by itself along the way): the phone and the desktop editor leave it out of the tour file they save unless you tick the switch that keeps it, and offer to save it as a separate file, the debug data, for you to keep; but the desktop editor always keeps it in the file you opened, so if that file is the one you host (for example in a synced Google Drive folder), the walk is public too. "Move the debug data out" in the editor's "Done editing" dialog takes it out of the tour file. Photos are saved as new images [EXIF: to be confirmed].

Recorder (/recorder/)

• Recordings (camera frames, positions from GPS and from the phone's tracking, depth, the reference points you mark and your notes) are kept in the browser's storage for this website and in the folder or file you choose. They leave your device only when you save, share or download them yourself.
• When it reads a printed code that links to a file, the Recorder downloads that file from where the link points; for Google Drive through the site's file service (above).
• Its maps load map images from OpenStreetMap (OpenStreetMap Foundation), which receives your IP address and the map area shown.
• Error reports. When the Recorder runs into an error or logs a warning, it sends a report to Sentry (Functional Software, Inc.), stored in Sentry's US data region, so that we can fix it. A report holds the error message and where in the code it happened, the page address without its query, the browser and device type, and the app's recent log lines, which can include the names you gave to recordings, scenarios and reference points and the names of the folders and files you chose. Before a report leaves your device, the app removes from it the path of links to other sites (the site's name stays), file identifiers and coordinates; it does not remove those names. The app tells Sentry not to store your IP address; the address still reaches Sentry with the connection. For one page load in ten, the app also sends the timings of the page load and of its network requests, with the same removals. Reports are kept for [Retention: number of days, to be confirmed in the error service account before this page goes live]. Error reporting stores nothing on your device. We rely on our legitimate interest in an app that works.

Anchor starter (/starter/)

The starter remembers a placed marker by writing its position (latitude, longitude, height, and a name if you give one) into the page's address. Anyone you send that link to can see the position, and opening the link sends the whole address, position included, to this website like any page request. Nothing else leaves your device.

Minimal example, QR-tracking, physics and wayfinding demos

The minimal example (/minimal/), the QR-tracking demo (/qr-demo/), the physics demo (/physics/) and the wayfinding demo (/wayfinding/) use the camera, location and motion sensors on your device only and contact no service other than this website. A recording you open in the physics demo is read on your device.

Map demo (/osm/)

• The map demo loads map images from OpenStreetMap (OpenStreetMap Foundation); map data such as buildings and paths from public Overpass servers that serve OpenStreetMap data (overpass-api.de and its mirrors at maps.mail.ru and overpass.private.coffee); terrain heights from Mapterhorn (tiles.mapterhorn.com) and from the open terrain tiles of Amazon Web Services; and the map library's stylesheet from unpkg.com. Each of them receives your IP address and the area or file requested.
• It keeps downloaded map data and terrain heights in your browser so that a revisit loads faster, and remembers whether you unfolded its AR readout.

Developer test pages

Test pages that no app links to (/lookdev/ and the pages under it, and the test pages under /recorder/ such as /recorder/ar-hittest-test.html) carry no link to this page. The look-dev pages load map images, map data and terrain heights from the same kinds of services as the map demo (above); the Recorder's test pages contact no service other than this website.

Start page (/) and blog (/blog/)

The start page remembers your colour theme choices in your browser. Neither it nor the blog contacts any other service.

Stored on your device

Everything the apps keep in your browser is kept because you asked the app to do what it needs (strictly necessary storage), never to track you. You can delete it in the browser's site settings.

Your rights.

You can ask the operator for access to, correction or deletion of data about you and for its use to be restricted, you can object to the processing described here, such as the logging, and you can complain to a data protection supervisory authority. As there are no accounts, we can find a log entry about you only from the time of your visit and the IP address you used, so please tell us both.

Changes.

We change this page before we change what the apps do with your data, and anything that needs your consent will ask for it first. If we add error reporting to another app, or usage statistics, this page will name the service, what it receives and for how long before it starts.

Last updated: 2026-10-25.