Security & Trust

Leadership & accountability

Parallax ORP is built by people who work inside public safety operations, not observers from the outside. Aaron Engelsrud, Founder of Parallax ORP, LLC, is a Firefighter/EMT with Woodbury Fire Department and senior enterprise IT leader with 20+ years building platform operations, analytics, and cloud infrastructure. Product direction, security posture, and compliance roadmap decisions are owned by named leadership — not anonymous marketing copy.

Aaron Engelsrud on LinkedIn

Architecture & tenant isolation

Parallax ORP is a multi-tenant platform with tenant isolation enforced at the architecture level. Agency data boundaries are designed into the data model and access controls — not left to policy alone. Every readiness-impacting change is intended to be traceable through audit trails suitable for operational and compliance review.

The platform is API-native: integrations with CAD, RMS, HR, and scheduling systems are designed to minimize duplicate data entry while maintaining a single authoritative readiness view per agency. Integration credentials are scoped per tenant; cross-agency data access is not part of the platform design.

Role-based access within each agency follows least-privilege principles. Command staff, training officers, field training evaluators, and administrative users see only the readiness domains their role requires — fatigue scores, credential status, training records, and scheduling data are segmented by permission, not exposed as a flat data export to every login.

Encryption & access controls

Data in transit between clients and Parallax ORP services uses industry-standard TLS encryption. Data at rest within our hosting provider's infrastructure is encrypted using provider-managed encryption appropriate to the storage layer. Authentication flows are handled through our hosting provider's identity infrastructure with support for agency-configured access policies.

Administrative access to production infrastructure is limited to authorized personnel on a need-to-know basis. Changes to production configuration follow documented change-management practices. Security questionnaires and penetration test summaries are available on request for agencies in active procurement review.

Data hosting & residency

• Hosting provider: Google Cloud Platform (Firebase Hosting)
• Primary region: United States (us-central1)
• Company: Parallax ORP, LLC, Minnesota, United States

Production infrastructure runs on Google Cloud Platform services. Customer data for U.S. agencies is processed and stored in U.S. regions unless otherwise agreed in writing for a specific deployment. Backup and disaster recovery procedures follow provider-managed replication within the designated region; cross-border data transfer outside the United States is not part of our standard deployment model.

Compliance alignment

Parallax ORP is designed with public-sector security expectations in mind. We align our controls and documentation with frameworks commonly referenced in fire, EMS, and municipal procurement, including:

• CJIS Security Policy — control design informed by CJIS requirements for agencies that operate under CJIS agreements (formal CJIS compliance attestation available as the program matures)
• SOC 2 Type II — on our compliance roadmap; contact us for current status and timeline
• StateRAMP / FedRAMP — evaluated against state and federal procurement needs on a customer-by-customer basis

We do not claim certifications we have not earned. For the latest attestation status, contact security@parallaxorp.com.

Incident response

Parallax ORP maintains an incident response process appropriate to the sensitivity of operational readiness data. When a security event is detected or reported, our team follows a documented workflow: contain the incident, assess scope and impact, remediate the root cause, and notify affected customers within timeframes consistent with contractual obligations and applicable law.

Agency security contacts identified during onboarding receive direct notification for incidents affecting their tenant data. For suspected vulnerabilities or security concerns, report to security@parallaxorp.com — we treat good-faith reports seriously and respond with acknowledgment and status updates through resolution.

Data retention & deletion

Operational data retained within Parallax ORP follows agency-directed retention policies configured during onboarding. When an agency terminates service, we provide a defined data export window and delete tenant data from production systems according to the terms of the applicable agreement. Backup retention follows provider-managed schedules; deleted production data ages out of backups on the provider's standard cycle.

Website inquiry data submitted through our public lead-capture forms is governed by our Privacy Policy. Agencies may request a data processing agreement or sub-processor addendum during procurement review.

Sub-processors

Current infrastructure and communication sub-processors include:

• Google Cloud Platform / Firebase — application hosting, database, authentication, and serverless function infrastructure (United States)
• Resend — transactional email delivery for inquiry notifications and operational alert workflows

Agency-specific platform deployments may include additional integrations (CAD, RMS, HR, scheduling vendors) configured per customer. Those integrations are documented during onboarding and governed by the agency's existing vendor agreements as well as Parallax ORP's integration security controls. We notify customers of material changes to our sub-processor list through contractual channels.

Security contact

For security questionnaires, penetration test summaries, data processing agreements, or procurement documentation:

security@parallaxorp.com

Pilot program & agency validation

Parallax ORP is actively piloting with fire departments in the Midwest United States. Early partners are evaluating readiness visibility, fatigue analytics, and field training documentation in live operational contexts. Named references are available under NDA where partner agencies permit.

"We needed one place to see who was actually ready — not just who was on the schedule. Parallax ORP gave our command staff that view without asking responders to learn another system." — Operations chief, mid-size Midwest fire department (pilot partner, name withheld by request)

Privacy

Website privacy practices are described in our Privacy Policy. General inquiries: hello@parallaxorp.com.