Trust
Data Security
The security principles and controls used to help safeguard Customer Data and the overall Before the Call platform.
- Document ID
- TRU-003
- Version
- 1.0.0
- Status
- Active
- Classification
- Public
- Owner
- Big Bull Technologies, LLC
- Effective
- 20 July 2026
- Next review
- July 2027
01 Purpose
Big Bull Technologies, LLC (“Big Bull Technologies,” “BBT,” “we,” “our,” or “us”) is committed to protecting the confidentiality, integrity, and availability of Customer information stored within Before the Call (“B4C”).
This document describes the security principles and controls used to help safeguard Customer Data and the overall platform.
02 Security Principles
Our security program is built around several core principles:
- Protect Customer information.
- Reduce the risk of unauthorized access.
- Maintain platform availability.
- Continuously improve security controls.
- Minimize unnecessary collection of information.
- Design security into the development process.
- Respond responsibly to identified risks.
Security is treated as an ongoing operational responsibility rather than a one-time implementation.
03 Administrative Scope
Before the Call is designed to manage administrative information for first responder organizations.
The platform is not intended to store or process:
- Electronic Patient Care Reports (ePCR)
- Protected Health Information associated with patient care
- Computer-Aided Dispatch (CAD) records
- Active emergency communications
- Incident Command records
- Emergency response management information
By limiting the operational scope of the platform, we also reduce unnecessary security exposure.
04 Data Protection
Customer information is protected using a combination of administrative, technical, and organizational safeguards appropriate to the Services.
These safeguards are intended to help protect information against:
- Unauthorized access
- Unauthorized disclosure
- Unauthorized modification
- Accidental loss
- Accidental destruction
Security controls evolve over time as technology and industry practices change.
05 Authentication & Access Control
Access to Before the Call is controlled through user authentication and authorization mechanisms.
Access is granted based on assigned roles and permissions.
Customers are responsible for:
- Managing Authorized Users.
- Reviewing user permissions.
- Removing inactive users.
- Protecting login credentials.
- Using strong passwords.
- Enabling multi-factor authentication when available.
The principle of least privilege should be applied whenever practical.
06 Encryption
Big Bull Technologies uses encryption and other industry-standard security measures where appropriate to help protect Customer information during transmission and storage.
Specific encryption methods, key management practices, and implementation details are not publicly disclosed to reduce security risk.
07 Infrastructure Security
The Before the Call platform is supported by infrastructure designed to promote security, reliability, and availability.
Infrastructure protections may include:
- Network security controls
- Infrastructure monitoring
- Secure configuration management
- Patch management
- Access logging
- Security updates
- Backup systems
- Availability monitoring
Security controls are reviewed and improved as operational needs evolve.
08 Monitoring
We monitor the platform to help identify:
- System health issues
- Performance concerns
- Unauthorized access attempts
- Potential security events
- Operational anomalies
Monitoring helps us maintain service reliability and investigate suspected security issues.
09 Backups & Recovery
Big Bull Technologies maintains processes intended to support the recovery of Customer information in the event of system failures or other operational disruptions.
Backup schedules, retention periods, and recovery procedures are periodically reviewed and may change as the platform evolves.
Backup processes are designed to improve operational resilience but should not replace a Customer’s own recordkeeping or business continuity practices where appropriate.
10 Secure Development
Security is considered throughout the software development lifecycle.
Our development practices include consideration of:
- Secure coding practices
- Change management
- Code review
- Dependency management
- Security updates
- Vulnerability remediation
- Ongoing platform improvements
Security is evaluated as new features are developed.
11 Third-Party Providers
Big Bull Technologies works with carefully selected third-party providers for services such as:
- Cloud infrastructure
- Authentication
- Payment processing
- Communications
- Artificial intelligence
- Monitoring
- Customer support
Third-party providers are evaluated based on operational, security, and business considerations appropriate to the services they provide.
12 Customer Responsibilities
Customers contribute significantly to the security of their own information.
We encourage Customers to:
- Use strong passwords.
- Enable multi-factor authentication when available.
- Limit administrative access.
- Remove former users promptly.
- Review permissions regularly.
- Keep devices updated.
- Report suspected security concerns immediately.
Strong organizational security begins with good administrative practices.
13 Security Limitations
No technology platform can guarantee absolute security.
While Big Bull Technologies continually works to improve the security of Before the Call, Customers acknowledge that no internet-connected service can eliminate every possible security risk.
We continually evaluate improvements designed to reduce risk and improve resilience.
14 Continuous Improvement
Security threats evolve constantly.
Accordingly, Big Bull Technologies regularly evaluates opportunities to improve:
- Authentication methods
- Monitoring capabilities
- Infrastructure resilience
- Administrative safeguards
- Security awareness
- Development practices
- Customer guidance
- Platform architecture
Continuous improvement is a core part of our security program.
15 Contact
Questions regarding data security or this document may be directed to Big Bull Technologies at ashlea@bigbulltech.io.
Customers who believe they have identified a security concern should report it promptly.
16 Related Documents
17 Revision History
| Version | Date | Description |
|---|---|---|
| 1.0.0 | July 2026 | Initial publication. |