Skip to content

Security and Data Handling

Shuttermap is designed with security and data protection as core considerations. This page outlines what data Shuttermap stores, how it is protected, and the steps taken to safeguard user access.

The information below is intentionally high level. It is meant to provide transparency without exposing implementation details that could compromise security.

Data Stored by Shuttermap

Shuttermap currently stores data related to inspection planning and coordination, including:

  • Team and project configuration
  • Assets and assignments
  • Shot sheets and shot definitions
  • User-uploaded 3D asset models
  • Metadata required to support planning and review workflows

This data exists to support inspection planning, execution tracking, and review.

User-Uploaded 3D Models

Custom asset models uploaded by users are stored securely in managed object storage.

These models:

  • Are accessible only to authorized team members
  • Are used solely for inspection planning and visualization
  • Are not shared between teams

Models may be processed or optimized to improve performance and reduce data footprint before being stored.

Image Data

At this time, Shuttermap does not store captured drone imagery.

In the future, Shuttermap may support image storage and review as part of inspection workflows. If and when image storage is introduced, it will follow the same security and access principles outlined on this page.

Authentication and Access Control

Shuttermap uses authenticated user accounts to control access to data and functionality.

Access is governed by:

  • Secure authentication using industry-standard identity services
  • Role-based access control at both the team and project levels
  • Authorization checks on all application APIs

Users can only access data associated with teams and projects to which they have been explicitly granted access.

Data Protection Practices

Shuttermap applies multiple layers of protection to user data, including:

  • Encrypted communication between clients and servers
  • Isolated data access between teams
  • Access controls enforced at the application level
  • Managed infrastructure services designed for secure operation

Security measures are designed to scale with the platform as new features and data types are introduced.

Shared Responsibility

While Shuttermap takes responsibility for securing the platform and its infrastructure, users are responsible for:

  • Managing access to their teams and projects
  • Protecting their account credentials
  • Ensuring compliance with any organizational or regulatory requirements relevant to their inspection data

Questions or Concerns

If you have questions about data handling or security practices, please contact Shuttermap support before uploading sensitive or proprietary information.