Paul D. Ensor
Founder, FactLockCam / factlockcam LLC
FactLockCam was founded by Paul Ensor after a career spent working with complex enterprise data systems, databases, high availability, disaster recovery, data integrity, and resilient information architecture.
For more than 30 years, the same problem has shown up in different forms: how do you know that critical information is intact, trustworthy, and available when it matters? That work covered enterprise data architecture, database engineering, data integrity, high availability, disaster recovery, and the design of resilient production systems.
FactLockCam applies that experience to trust in digital media. It is an on-device evidence camera operated by factlockcam LLC, a Florida limited liability company. At capture it fingerprints the exact bytes of a photo or video, creates a signed capture record, and, when the device is online, can anchor a hash of that record to the public Polygon network.
A recipient can later inspect a FactLockCam proof package locally in a browser and check the file, the signature, and the public record as three separate results. Nothing in that check requires sending the package back to FactLockCam.
The distinction that matters is what FactLockCam does not claim. It does not look at an image and guess whether it was generated by AI. It does not claim that cryptography establishes the physical truth of a scene, identifies every person shown, promises that a court will admit the material, or decides whether somebody's story is true. It records information about an original file so that a later file can be compared with that earlier record.
Before FactLockCam, Paul developed and launched ProofLock, where that background in data integrity and resilient systems was first applied to digital provenance. FactLockCam is the current product. It is operated by factlockcam LLC. This page does not describe a legal merger of the two companies.
- 01 30+ years in technology
- 02 Enterprise data
- 03 Data integrity
- 04 High availability and disaster recovery
- 05 Digital provenance
- 06 FactLockCam
Why I built FactLockCam
Producing or altering convincing digital media is becoming easier. A detector tries to decide whether pixels look artificial. FactLockCam starts earlier: it records the exact file at capture, signs that record, and, when the device is online, publishes a hash of the record where someone else can look it up later.
The product publishes its threat model, privacy architecture, verification process, and limits so a customer or a recipient can evaluate them without a sales presentation. Security products should publish their limitations as clearly as their capabilities.
What I believe
Digital trust should come from evidence that can be independently checked, not from asking someone to trust a company, a screenshot, or an algorithmic opinion.View Paul on LinkedIn