Who runs Cairn, and who does not
Cairn is a package an organisation installs on a server it owns or rents. That organisation operates the installation and owns everything on it, and decides who gets an account, which Projects they may open, and how long anything is kept.
The people who build Cairn have no access to it: no account, no remote connection, no key, and nowhere on our side for your data to arrive. Nor does the server contact us — no usage reports, no crash reports, no update checks, no licence checks, because no code in Cairn does any of those things.
What Cairn holds
For each Project: the original Scan files as uploaded, the converted viewing copy the browser draws from, Panoramas associated with each Scan station, imported Models, Control files, Annotations, Measurements, saved views and section boxes — plus the Project's displayed name, its permanent identifier, and whatever coordinate reference has been declared for it, or the record that none has.
Scans are accepted as LAS, LAZ and E57; Models as IFC, DXF, LandXML and OBJ; Panoramas as images with a pose file or carried inside an E57; Control as CSV. Control files are stored with the Project; this version does not check them against a Scan.
About people, Cairn holds only what an account needs: a name, an email address, a password hash and a role. For each Share link: the token, the expiry, an optional password hash, and how many times it has been opened.
What survey data contains by accident
A Scan or a Panorama records whatever was in front of the scanner — people, vehicles, signage, the inside of buildings, property that is not the subject of the survey. Cairn stores what it is given. It does not blur, remove or alter any of it, and has no feature that does. What may be captured, and who may see it, is decided by the organisation that took the Scan.
Where it lives, and what leaves the server
All of it sits in one data folder on the installation. The map behind the Project pins is a file installed on that same server; Cairn never downloads a map. Three things cross the network, and that is the whole list:
- Browser traffic over HTTPS, between the people using Cairn and their own installation.
- A certificate request, where Cairn answers at the organisation's own domain: the bundled proxy obtains and renews that certificate from a public authority, with no Project content involved. An installation on a single workstation makes its own certificate and contacts nothing.
- A diagnostic bundle, if an operator chooses to send one — produced on the machine by a command they run, saved as a file, never transmitted automatically.
Cairn sends no email. There is no mail capability in this version, so nothing is invited, notified or reset by message.
Who can see what
Every permission is decided on the server, for the account the request actually arrives as. A control an audience may not use is not built into the page they are given, and the server refuses the action as well.
| Who | What they can reach |
|---|---|
| Administrator | Every Project. Manages accounts and access, deletes and permanently purges Projects, manages the encryption key. |
| Surveyor | Every Project. Uploads, imports, checks the work, renames a Project, removes data inside one, creates and revokes Share links. Cannot delete a whole Project, purge, manage people or touch the key. |
| Client account | Only the Projects it has been granted. Can navigate, measure, annotate and export a Navisworks viewpoint file. Cannot upload, delete or share. |
| Share link holder | One Project, anonymously. Can navigate, enter every Station View, measure, annotate and take a snapshot. Cannot upload, delete, export a Measurement CSV or reach another Project. The Navisworks viewpoint export is not available to a Share link holder in this version. |
Share links
A Share link opens one Project and nothing else, and its holder is anonymous — a link, not an account. Whoever creates it chooses how long it lasts: any number of days up to a year, thirty by default, or no automatic expiry. It may carry a password, stored salted and hashed. It can be revoked at any time, taking effect on the holder's very next request, and every opening is logged. The holder is served a reduced description of the Project, carrying nothing about any other Project and no credential of any kind; the only thing they can write back is an Annotation. The Navisworks viewpoint export is not available to a Share link holder in this version — a signed-in Client account has it.
Nobody downloads the survey data
No one — not a Client account, not a Surveyor, not an Administrator — can retrieve a Project's original Scans or any point-cloud file through Cairn. The viewer instead streams pieces of the converted viewing copy in order to draw them, which is how a browser shows a Scan at all. Exporting Measurements as a CSV is for Surveyors and Administrators only.
How it is protected at rest
A Project can be created with encryption at rest, chosen at that moment and off unless chosen. Its original Scan files are then encrypted in chunks with AES-256-GCM under a key belonging to that Project, wrapped under the installation's own key.
It is designed against theft of the storage — a disk that walks, a copied folder, an archive that ends up somewhere it should not — and is no defence against a running server somebody has taken control of. It covers the original Scans: the converted viewing copy, Models, Panoramas, Annotations and the Project's description are not encrypted file by file. Whole-disk encryption and the physical security of the machine belong to the organisation.
So does the key. It is created during installation, kept wrapped in the data folder, and opened by a secret the host computer supplies into memory when Cairn starts. A copy of Cairn's data and configuration alone cannot recover it, and Cairn never invents a replacement: if the host cannot supply the secret, Cairn stays locked until an operator restores it from the recovery copy held outside the machine.
What is written down
Cairn keeps a local usage log — one file per day, kept ninety days, then removed. It is kept with the installation's data, so an upgrade keeps it and every backup includes it. Each entry is one line: the time in UTC, the address the request came from, what was done, how long it took, and the Project's stable identifier. It records opening a Project, signing in and out, creating and revoking a Share link, and each opening of one with the first part of the browser's description of itself. It does not record a Project's name or the name of an uploaded file. It does not record the contents of a Project: no point data, no images, no coordinates, no Measurements. It never leaves the installation, because Cairn has no way to send it. An Administrator or a Surveyor can see how often each Project has been opened over the last thirty days.
By default, the diagnostic bundle an operator produces for support excludes Project names and identifiers, coordinates, request addresses, Share link tokens, passwords, encryption keys and the server's configuration. It carries Project names and identifiers only when the person producing it consents for that one bundle, and it asks again every time. It holds installation and version facts, counts of actions and the acknowledgements accepted at setup — for the operator to read before deciding to send it.
Deleting, and how long things stay
- A deleted Project stays recoverable for fourteen complete days, and deleting it requires typing its current name.
- Data removed or replaced inside a Project — a Scan, a Panorama, a Model, or a reset that replaces its contents — stays recoverable for seven complete days, then its storage is reclaimed. A separate, shorter window; it does not extend to fourteen.
- An Administrator also has a permanent purge for when storage is needed urgently. It requires typing a confirmation and cannot be undone.
- A deleted Project leaves a small record behind, including the name it held at that moment.
The sweep that reclaims disk runs when Cairn starts and once a day after, so space comes back on a long-running server rather than only on a restart. Backups are made and kept by the organisation; Cairn signs the archives it writes so a restore can tell a genuine one from a tampered or foreign one, and the detailed map is left out of them because it can simply be reinstalled.
If you run an installation
What the administrator who set this installation up accepted, restated plainly, because it is yours rather than ours:
- Keep the authoritative data elsewhere. Cairn is not a backup system and must not hold the only copy of anything.
- The privacy obligations are yours. Your clients' data is on your machine.
- The encryption key is yours to keep. A recovery copy belongs outside this computer, in your approved password or secrets system. Nobody else has one.
- Share links are yours once sent. Expiry and revocation are your job.
- Deletion windows are as above, and a purge cannot be undone.
- This is a pilot release supplied with no warranty.
How the software is defended is in the Security statement. Where to take a question is on the Support page.
Measurements
Cairn's measurements are for review and coordination. They are not survey deliverables.
A permanent statement about what the product is for, not a caution a later version will remove. Cairn shows it beside the measurement panel to every audience.