INDUSTRIAL DATA TRUST
Data security & facility confidentiality.
Industrial capture can reveal equipment, processes and facility constraints. Ownership, access, hosting, sharing, retention and public use should therefore be agreed before capture—not assumed after delivery.
Who owns customer scan data?
Axial Spaces’ standard project position is that the customer retains ownership of its facility and source capture data, subject to the signed project agreement. Axial Spaces retains ownership of its pre-existing software, viewers, templates, methods and general know-how. Any project-specific licence needed to process, host or deliver the work should be stated in the scope.
The signed agreement controls. If your procurement terms require different ownership or licensing language, resolve that before capture.
What is active by default, and what must be confirmed?
| Topic | Current project practice | Confirm in the scope |
|---|---|---|
| NDA | Axial Spaces can review a customer NDA before access or capture. | Parties, permitted use, term and any site-specific handling rules. |
| Storage | The working and delivery platforms are identified for the project. Axial Spaces does not advertise one universal certified-cloud tier. | Storage location, service providers, transfer method and customer IT requirements. |
| Access | Access is limited to people and service providers needed to perform the agreed work. | Named recipients, subcontractor approval, account roles and customer administrators. |
| Private or password hosting | Available only when the selected delivery platform supports the required control and it is included in the scope. | Authentication method, user management, expiry, support and hosting term. |
| Redaction | Sensitive areas can be excluded during capture; image or scene redaction may be scoped where technically practical. | What must never be captured, what may be masked and how the customer will review it. |
| Retention and deletion | There is no claimed universal automatic-deletion period for every project. | Source-data retention, archival copies, processor constraints and deletion timing. |
Where is scan data stored, and who can access it?
The working storage and delivery path are documented for the project before capture. Access is limited to Axial Spaces personnel and necessary service providers performing the agreed work, plus customer recipients authorized in the sharing plan.
Because hosting requirements differ, the site does not claim a universal storage region, security certification or private-hosting control. If a project requires a particular platform, region, authentication model or customer-managed environment, that requirement must be confirmed as technically available and written into the scope.
How are sharing permissions handled?
The project should name who may receive source files, exports, browser links and downloadable material. Public-link, private-link and password-protected options are not interchangeable; the selected viewer and hosting platform determine which controls are actually available.
Axial Spaces confirms the chosen sharing method before publishing a deliverable. Customers should treat forwarded links and downloaded files according to their own internal information policy.
Can sensitive areas or objects be excluded?
Yes—capture exclusion is the most reliable first control. Identify restricted rooms, screens, documents, people, labels, prototypes or production details during pre-capture planning. The route can then avoid those areas where site conditions allow.
Image or scene redaction can be discussed where technically practical, but it should not be assumed to work identically across raw imagery, point clouds, Gaussian splats, videos and exported files. The redaction target and customer review step must be scoped explicitly.
How long is source data retained?
Retention is agreed by project because source data may be needed for processing, revisions, exports or later facility updates. The scope should state which source and delivery files are retained, the planned period and whether continued hosting is included.
Deletion requests can be sent to axialspaces@gmail.com. Completion depends on the signed agreement and any legal, backup or service-provider constraints disclosed for the project; Axial Spaces should confirm the outcome rather than implying that every copy disappears instantly.
Can a customer facility appear in a portfolio?
Not without documented customer approval. Portfolio permission is separate from permission to process and deliver the project. Approval should identify what may be shown, whether the customer may be named, which areas or assets are excluded and whether the example must be anonymized.
How are capture dates and versions tracked?
Published facility-twin examples should identify the capture date, version, included areas, important exclusions and whether the record is current or historical. This prevents an older capture from being mistaken for today’s plant conditions.
Capture once. Reuse it until the facility changes. Update it when the plant changes.
CONFIDENTIALITY STARTS IN THE BRIEF
State the restrictions before the scanner arrives.
Include NDA, restricted-area, hosting, access, retention and public-use requirements in the first project conversation.
Scope My Facility Project