Offline Functionality Policy

01 Purpose

The Before the Call (“B4C”) mobile application is designed to remain useful even when internet connectivity is limited or temporarily unavailable.

This policy explains how offline functionality works, what information may be stored locally on a user’s device, how synchronization occurs, and the limitations of offline operation.

02 Our Philosophy

Whenever reasonably practical, Before the Call is designed to allow Authorized Users to continue working with supported features while offline and automatically synchronize changes once connectivity is restored.

Offline functionality is intended to improve reliability — not replace real-time connectivity.

03 Supported Offline Features

Depending on platform capabilities and Department configuration, offline functionality may include:

• Viewing previously synchronized department information
• Completing assigned station duties
• Viewing schedules and calendars
• Reviewing downloaded documents
• Completing checklists
• Recording attendance
• Recording notes
• Completing inspections
• Drafting meeting notes
• Viewing selected training materials
• Creating administrative records awaiting synchronization

Available offline functionality may expand as the platform evolves.

04 Local Device Storage

To support offline functionality, B4C may temporarily store selected administrative information on the user’s device. Examples include:

• Recently viewed records
• Assigned tasks
• Downloaded documents
• Pending form submissions
• Cached department information
• User preferences

Only the information reasonably necessary to support selected offline features is stored locally.

05 Synchronization

When internet connectivity becomes available, B4C attempts to synchronize eligible information with the platform. Synchronization may include:

• New records
• Updated records
• Completed tasks
• Attendance events
• Inspection results
• Administrative notes
• Checklist completion
• Other supported administrative data

Synchronization timing may vary depending on device settings, network availability, battery optimization, and operating system behavior.

06 Conflict Resolution

Occasionally, the same information may be modified on multiple devices before synchronization occurs.

When synchronization conflicts are detected, B4C may:

• Preserve both versions for review
• Prompt the user to resolve the conflict
• Apply system-defined conflict resolution rules
• Notify authorized administrators when appropriate

Departments remain responsible for reviewing official administrative records.

07 Location-Based Features

Certain location-based administrative events may continue to be recorded while the device is temporarily offline, subject to operating system capabilities and granted permissions.

When connectivity is restored, eligible location events may synchronize with the platform.

Offline operation does not guarantee that every location event will be captured or transmitted.

08 Security

Information stored locally is protected using reasonable administrative and technical safeguards appropriate to the operating system and application architecture.

Users are encouraged to:

• Enable device screen locks
• Keep operating systems updated
• Use biometric authentication when available
• Report lost or stolen devices promptly

Additional information is available in:

• APP-005 — Device Security
• TRU-003 — Data Security

09 User Responsibilities

Users are responsible for:

• Maintaining secure access to their devices
• Synchronizing data when connectivity becomes available
• Reporting synchronization issues
• Reviewing submitted administrative records
• Protecting locally stored information

Departments should not rely solely on offline storage as a permanent recordkeeping solution.

10 Limitations

Offline functionality depends on several factors, including:

• Device capabilities
• Operating system behavior
• Available storage
• Battery level
• Department configuration
• Application version

Some features require an active internet connection and may not be available while offline. Examples may include:

11 Continuous Improvement

Big Bull Technologies continually evaluates opportunities to improve offline functionality by expanding supported features, improving synchronization reliability, and enhancing the overall user experience.

12 Changes to This Policy

Big Bull Technologies may update this Offline Functionality Policy periodically.

Material changes will become effective on the published Effective Date after reasonable notice has been provided through the Services, our website, email, or another appropriate communication method.

13 Contact

Questions regarding offline functionality may be directed to Big Bull Technologies.

Big Bull Technologies, LLC
Email: ashlea@bigbulltech.io

14 Related Documents

• APP-001 — Mobile Application Permissions
• APP-005 — Device Security
• LOC-002 — Station Presence Verification
• TRU-003 — Data Security
• LEG-008 — Support Policy

15 Revision History