Deleted Database Records Remain Recoverable in SQLite Files Despite DELETE Operations
A routine request to delete personal data often ends with a simple DELETE FROM clients WHERE id = ... command. The application reports success because the row disappears from query results and exports. However, the underlying database file still contains the full record, including names and card numbers, which can be recovered with basic tools such as grep.
SQLite behavior and the secure_delete pragma
SQLite marks the page containing the deleted row as free for reuse but does not overwrite its contents when secure_delete is set to 0. The following sequence demonstrates the problem: a database is created with 200 rows, 46 rows are deleted, and the table reports only 154 remaining rows. Searching the file nevertheless finds the deleted name and card number.
The pragma secure_delete = 1 forces the database engine to overwrite freed space with zeros at the moment of deletion. The same search then returns zero matches. The default value depends on the compile-time flag SQLITE_SECURE_DELETE, which varies across distributions and platforms. Therefore the same application can behave differently on a server, in a mobile build, or on a desktop client.
Other database systems exhibit similar issues
- PostgreSQL marks row versions as dead; physical removal occurs only during VACUUM or VACUUM FULL. Write-ahead logs also retain previous page versions.
- MySQL with InnoDB releases pages without overwriting them and keeps historical values in undo logs and the binary log.
In every major system, executing DELETE is not equivalent to erasing the data from storage media.
Real-world impact on data protection obligations
Companies responding to deletion requests typically confirm only that the row is absent from the live table. When a database file is later seized or leaked, previously deleted records remain readable. Backup copies created before the deletion continue to hold the data for their entire retention period. Replicas used for reporting and analytics frequently receive the record in a daily export and keep it indefinitely. Mobile application database dumps sent to support teams commonly contain every record the user ever deleted.
Recommended controls
For SQLite, enable immediate overwriting with PRAGMA secure_delete = ON and run VACUUM after large deletions. For server databases, the only reliable approach is to encrypt sensitive fields with a key that is destroyed when deletion is requested; old backups then become unreadable. Organizations should also store less data, enforce retention periods directly in the schema, and include backups, replicas, and analytics exports in every deletion procedure.
Related articles
Zero Breach Toolkit Scans Devices for Pegasus, Predator and Other Spyware Traces
Zero Breach Toolkit is a new open-source Python tool that searches for indicators of compromise linked to commercial spyware campaigns including Pegasus, Predator, Graphite and Candiru. It analyzes browsers, system logs, prefetch data, AndroidQF extractions and encrypted iPhone backups across Windows, macOS, Linux, Android and iOS. The scanner assigns confidence levels to matches and explicitly warns that a clean result does not prove a device is free of surveillance software. Developed under the pseudonym archivegenocide, the project is only weeks old, offers reproducible builds and GPG signatures, yet lacks independent validation of detection rates. It draws IOCs from Amnesty International Security Lab, Citizen Lab and the Mobile Verification Toolkit but cannot detect unknown or heavily modified implants. The tool is positioned as a first-step check rather than a replacement for professional forensic analysis.
AWG Router Delivers Script-Free AmneziaWG Cascades with Load Balancing, Speed Limits and Leak Prevention
AWG Router is an open-source Python-based web panel that manages complex AmneziaWG VPN cascades without hundreds of lines of bash scripts. The tool generates nftables rules, ip rules, and tc queues to route Russian networks directly while sending other traffic through foreign AmneziaWG servers or SOCKS5 proxies. It enforces strict leak protection so that traffic never falls back to the entry server’s Russian IP when an upstream tunnel fails. The panel supports per-client routing policies, domain-based rules via SNI inspection, automatic load balancing across multiple exits, and granular speed limits using HTB and fq_codel. All state is stored in resilient JSON files, and the system continues operating even if the panel itself is restarted or updated. The project is released under the MIT license with full source available.
TV Manufacturers Admit They Cannot Fully Disable User Data Collection
The Verge surveyed 11 major television and streaming device makers about their data collection practices, receiving responses from seven companies including Amazon, Apple, Google, LG, Roku, Samsung and TCL. Automatic Content Recognition (ACR) technology, used for targeted advertising and audience measurement, remains a central concern, with Samsung, LG and Amazon disabling it by default. Google enables diagnostic and advertising data collection under standard settings, while Apple stated that Apple TV 4K does not employ ACR. Amazon, Google, Samsung and Roku acknowledged that complete opt-out from data transmission is impossible, with devices caching information offline for later upload. Research from Northeastern University revealed that Vizio continued sending data even after users declined collection, labeling it as operational telemetry. LG was found to potentially store unencrypted voice command transcripts and determine location via nearby Wi-Fi networks when ACR is active.
Personal Data in Russian Franchise Networks: Who Qualifies as Data Operator Under 152-FZ
In typical franchise models, customer personal data is collected at franchisee points, stored in the franchisor’s central system, and used for network-wide loyalty programs and marketing. The key legal question is which party determines the purposes of processing and therefore bears operator status under Federal Law No. 152-FZ. The law defines an operator as the entity that independently or jointly sets processing purposes, data composition, and actions, regardless of contractual labels. Franchisees usually act as operators when concluding contracts with customers, while franchisors become processors unless they pursue independent goals such as running loyalty schemes or sending branded advertising. When a franchisor defines its own purposes, both parties may simultaneously qualify as operators for different processing objectives, requiring separate legal bases and documentation. Proper data-processing instructions must be embedded in the commercial concession agreement and must list specific data categories, actions, security measures, and breach-notification timelines to avoid administrative fines ranging from 150,000 to 500,000 RUB.