Security — Pack Command Center

ℹPack Command Center is pre-launch. The practices below describe how the platform is designed and built. We're being straightforward: we're an early-stage product working toward formal certifications, not claiming ones we don't hold.

Encryption in transit

All traffic between your browser and Pack Command Center is encrypted using industry-standard TLS. Data moving between our application and its infrastructure is likewise protected.

Access controls & permissions

Access to your data is governed by role-based permissions that follow the Organization → Business → Branch → Department → Team → User hierarchy. People see only what their role allows, and you control who can view or manage each part of your organization.

Role-based access at every level of the hierarchy
Least-privilege defaults for new users
Administrative access to production is restricted and logged

Tenant isolation

The platform is designed so that each customer's data is logically isolated from every other customer's. One organization cannot access another's information, and isolation is enforced throughout the application rather than left to configuration.

Secure integrations & credential handling

When you connect an external system, credentials such as API keys are stored securely and are never redisplayed after entry. If you need to change a connection, you re-enter or rotate the credential rather than retrieving the old one. Connectors request only the access needed to import the operational data they cover.

Responsible disclosure

We welcome reports from security researchers. If you believe you've found a vulnerability, please contact us privately with enough detail to reproduce it, and give us a reasonable opportunity to address it before public disclosure. Reach us through our contact page, addressed to Command Center Software LLC, Security. Please do not access or modify data that isn't yours, and avoid actions that could disrupt the service for others.

Roadmap to formal certifications

As we move from early access toward general availability, we intend to pursue independent security assessments and recognized compliance frameworks. We'll describe our progress here honestly and won't represent that we hold a certification until we actually do.

Shared responsibility

Security is a partnership. You help by using strong, unique passwords, managing your team's roles carefully, and keeping the credentials for your connected systems safe. We'll keep hardening the platform on our side.

This page is general information about our security approach, not legal advice or a contractual warranty.