Emergency Safety & Legal
Kill The Call maintains permanent, tamper-proof emergency logs when a 911 call is detected. This page explains what is recorded, where it is stored, and how authorized law enforcement can access those records.
When Kill The Call detects an outbound 911 call on the device, it immediately activates Emergency Mode. Emergency Mode does three things simultaneously:
1. Suspends call blocking for 60 minutes — all inbound calls ring through without restriction, ensuring that Public Safety Answering Point (PSAP) callback calls are never blocked regardless of their originating number.
2. Creates a permanent emergency log entry — a timestamped record of the event is written to an unencrypted on-device database that cannot be deleted by the user or by any app function.
3. Captures GPS coordinates — a single location snapshot is taken at the moment 911 is detected, recording the device's precise position with accuracy that may exceed carrier-provided location data.
Emergency Mode is displayed to the user via a persistent notification showing the suspension window and expiry time. The user may manually re-enable blocking after a minimum 30-minute window to ensure adequate callback time.
Every Emergency Mode activation creates a record containing the following fields:
The CSV export header row is structured as follows:
Emergency logs are stored exclusively on the user's device in an unencrypted SQLite database located in the app's private data directory. They are never transmitted to MyChatVault LLC servers or any third party under any circumstances.
The database file is stored at: Android app private data directory / emergency_log.db
Because Kill The Call does not have server-side visibility into these records, MyChatVault LLC cannot independently produce emergency logs. Records exist solely on the user's device. In response to valid legal process, MyChatVault LLC will provide technical documentation of the database schema and file location to assist authorized forensic extraction.
These logs exist on your device only. For your protection only. We cannot see them. We cannot delete them. We cannot produce them. Only you — or authorized law enforcement with your device — can access them.
There are two pathways for law enforcement to access emergency log records:
The device owner can voluntarily export a court-ready CSV from within the app at Settings → Emergency Logs → Export for Legal Proceedings. The export includes all logged fields, the SHA-256 integrity hash, a chain of custody statement, and export timestamp. This is the fastest path to obtaining records and requires no legal process if the user cooperates voluntarily.
With a valid search warrant or court order authorizing access to the device, forensic examiners can extract the emergency log database directly. The database is unencrypted SQLite and accessible via standard mobile forensic tools (Cellebrite, MSAB XRY, Oxygen Forensics, etc.). Contact [email protected] for the current database schema and file path documentation to assist extraction.
In response to a valid court order or warrant directed at MyChatVault LLC, we will provide full technical documentation of the log format, database schema, field definitions, and SHA-256 integrity verification procedure to assist forensic teams. We cannot produce the logs themselves as they do not exist on our servers. Direct all legal process to [email protected].
For technical documentation requests, legal process responses, or forensic assistance inquiries contact:
[email protected]
Please include your jurisdiction, agency name, case number, and nature of request. MyChatVault LLC will acknowledge all valid legal process within 3 business days. Emergency situations involving imminent threat to life should contact local law enforcement directly — do not rely on email for time-critical matters.
Every emergency log record is assigned a SHA-256 integrity hash computed at the moment of creation from the complete record contents. This hash is stored alongside the record and included in every CSV export.
To verify that a log export has not been altered since creation, recompute the SHA-256 hash of the data fields and compare against the stored hash value. A match confirms the record is intact and unmodified — meeting the standard for digital evidence admissibility under Federal Rules of Evidence 901(b)(9) and comparable state rules.
Every court-ready CSV export includes a chain of custody header stating the export timestamp, the exporting device's model and Android version, the Kill The Call version, and the SHA-256 hash of the complete export file itself.
GPS accuracy at time of capture — typically 2–5 meters on modern Android devices — may significantly exceed the accuracy of carrier-provided 911 location data, which relies on cell tower triangulation at 100–300 meter accuracy. Kill The Call emergency location records may provide more precise placement than PSAP dispatch records.
Emergency logging is disclosed to users during app onboarding and in the app's Terms of Service (Section 14). Users are informed that:
• Emergency logs are created automatically when a 911 call is detected
• GPS coordinates are captured at the moment of detection (requires ACCESS_FINE_LOCATION permission, which users may grant or deny during onboarding)
• Logs cannot be deleted by the user or by any app function
• Logs may be accessible to authorized law enforcement with appropriate legal process
• MyChatVault LLC has zero access to these records
If the user declines the ACCESS_FINE_LOCATION permission, GPS coordinates are not captured and the location fields in the emergency log will be empty. All other fields are still recorded.
The permanent nature of these logs is presented to users as a protective feature, not a surveillance mechanism. Records exist for the user's benefit — to document their emergency situation in a form that can assist law enforcement and legal proceedings on their behalf.