The company behind FactLockCam
FactLockCam is operated by factlockcam LLC , a Florida limited liability company founded by Paul D. Ensor.
- Company
- factlockcam LLC
- Product
- FactLockCam
- Founder
- Paul D. Ensor
- Location
- Florida, United States
- Founded
- 2026
- Website
- factlockcam.com
- Support
- [email protected]
- Platforms
- iOS and Android
Digital photos and videos can be copied, edited, re-saved, stripped of metadata, or challenged later. FactLockCam does not ask an AI model to guess whether an image looks authentic. It records cryptographic information about the exact file at capture, so the original owner and anyone receiving a proof package have something objective to compare later.
How verification worksYou do not have to take our word for it
Important parts of FactLockCam can be checked independently.
- 01
The exact file is fingerprinted
At capture, FactLockCam computes a SHA-256 fingerprint of the exact media bytes. Change those bytes and the fingerprint changes.
- 02
The capture record is signed
FactLockCam creates a capture manifest about the sealed file and signs the record with the owner's signing key. Every signed record discloses how it was signed.
- 03
A public reference can be created
When the device is online, the signed manifest hash can be anchored to Polygon. That public reference can later be inspected independently. It is a hash of the signed manifest, not the photo or video.
- 04
Recipients can verify locally
A recipient does not need a FactLockCam account and does not send the proof package back to us. A .flcproof package can be opened and checked locally in a modern browser. The file check, signature check, and public-record check are presented separately.
Your media is not our business model
FactLockCam is local-first.
Original photos and videos remain encrypted on your device. FactLockCam does not upload your media archive to its servers. We do not share your photos, videos, or identity with third-party AI or machine-learning services. We do not hold the encryption keys required to read your sealed media.
When a public Polygon anchor is created, the public record contains a hash of the signed capture manifest. It does not contain your photo, video, email address, filename, or identity.
Some account and service information leaves the device to operate authentication, subscriptions, proof-ledger metadata, email delivery, and public anchoring. The Privacy Policy names those processors and what they receive.
What a verification shows, and what it does not
A successful FactLockCam verification can show that:
- The inspected file matches the recorded SHA-256 fingerprint.
- The capture manifest matches the signed record.
- The signature corresponds to the recorded signing address.
- When a confirmed transaction exists, the manifest hash appears in the referenced Polygon transaction.
A successful verification does not, by itself, prove:
- The physical truth of everything shown in the scene.
- The identity of every person shown.
- An externally attested exact capture instant.
- That a court will admit the material as evidence.
- That an insurer or other organization will accept a claim.
- That possession of the unlock link is equivalent to cryptographic identity.
Those limits are published because a security product should describe its boundaries as carefully as its capabilities. The full statement is the threat model, not this summary.
Read the full threat modelMeet the founder
Paul D. Ensor
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.
Across more than three decades in technology, one problem has appeared again and again: how do you establish that critical information is intact, trustworthy, and available when someone actually needs it?
Producing or altering convincing digital media is becoming easier. FactLockCam approaches that problem from the opposite direction of a detector. It does not try to decide whether pixels look artificial. It records information about an original file at capture so a later file can be compared with that earlier record.
Paul previously developed and launched ProofLock, an earlier digital-integrity application. That work continued into FactLockCam. FactLockCam is a separate product, operated by factlockcam LLC.
We publish the boundaries
You should be able to evaluate FactLockCam without relying on a sales presentation.
- Threat model What verification establishes, what it does not establish, and the current limits of the signing architecture.
- Privacy Policy What stays on your device, what data is processed elsewhere, which service providers are involved, and how deletion works.
- Verification tools Open a proof package, run the live challenge, or check a proof.json file without sending it to FactLockCam.
- Press kit Product facts, demonstration materials, technical resources, and company information.
- Terms of Service The rules and limitations governing use of the service.
Accountability matters
FactLockCam is not designed around the idea that customers should simply believe us. The goal is to make important claims inspectable.
You can inspect the file fingerprint. You can inspect the signed record. You can inspect the public transaction when one exists. You can read the privacy policy. You can read the threat model. And you can see who built the company.
Trust should be earned with evidence, not requested with a slogan.
