Why OSINT.PH processes search results in memory and never writes personal data to disk, and the engineering decisions behind it.
Most intelligence platforms store everything. Every search, every result, every profile discovered is written to databases, indexed, and cached. This creates a liability: a breach of the platform means a breach of every investigation ever conducted on it.
We took the opposite approach.
When an operator runs a search on OSINT.PH, the query flows through our search pipeline:
At no point are search results written to disk. There is no results database. There is no search history table. When the operator closes their browser tab, the results are gone.
We store only what is necessary for platform operation:
We explicitly do not store:
Investigation boards, where operators map connections between entities, use client-side encryption. The encryption key never leaves the operator's device. Our servers store only encrypted blobs that we cannot read.
If our database were compromised, the attacker would find encrypted data with no way to decrypt it.
This architecture was designed with Philippine law in mind:
The obvious trade-off is that operators cannot go back to previous searches. There is no search history to review, no saved results to revisit. If an operator needs the same data again, they run the search again.
We believe this is the right trade-off. The risk of storing sensitive intelligence data far outweighs the convenience of search history.
When you use OSINT.PH, your searches are yours alone. We cannot see your results. We cannot replay your investigations. And if we are ever compromised, your investigation data is not at risk, because it was never here to begin with.