File format custody, registration archives, and air-gapped workflows
A typical industrial reality capture project generates raw scanner files, high-dynamic-range panoramic imagery, unified E57 and Autodesk ReCap (.rcp/.rcs) point clouds, and native Revit (.rvt), IFC, or AutoCAD (.dwg) deliverables. Throughout registration and modeling, project files remain isolated in per-client workspaces and are never ingested into third-party generative training sets or public viewer portals.
For pharmaceutical GMP suites, semiconductor fabs, defense contractors, and critical utility substations in New York, New Jersey, and Connecticut that prohibit external cloud links, we support completely offline processing workflows. Field data moves directly from scanner media to encrypted local workstations, and final deliverables are handed over on hardware-encrypted drives.
When spherical 360-degree imagery or virtual tours are requested, we can exclude photography entirely and run geometry-only LiDAR capture, or blur personnel, whiteboards, control room HMIs, and proprietary tooling labels before final handoff.
Confidentiality
We sign client NDAs as a matter of course and can work under your form rather than insisting on ours. Where no NDA exists, we still treat project data as confidential by default.
Client names, site imagery, and project details are not used in marketing without written permission. That is why our projects page is honest about being under construction rather than filled with work we cannot show.
Restricted and regulated sites
Pharmaceutical, defence-adjacent, utility, and government facilities frequently impose specific handling rules: no cloud storage, no personal devices, data transfer only via a nominated channel, deletion on a defined schedule, or personnel restrictions.
These are workable requirements and we would rather agree them in the scoping conversation than discover them at the gate. Some restrictions genuinely change cost and schedule, and we will say so rather than agreeing and then quietly working around them.
Storage and transfer
Project data is held on access-controlled systems with restricted access limited to personnel assigned to the project. Deliverables are transferred by secure link or by a client-nominated method.
Large datasets are frequently delivered on encrypted physical media where transfer size or client policy makes that the better route.
Retention and deletion
Absent a contractual schedule, we retain project archives so a future phase can reuse the registration and control instead of paying for it again. That archive is an asset to you, not a liability, but it is your call.
On written request we will delete project data and confirm deletion. Where a retention obligation conflicts with a deletion request, we will explain the conflict.
Personnel and incidental capture
Scanning records whatever is in the field of view, including staff who happen to be present, screens, and documents. Where this matters, we schedule around occupancy or scrub identifiable detail from deliverables.
Ask for that in scoping and it costs almost nothing; ask afterwards and it is a reprocessing job.