The exact original bytes must match.
YOUR CAMERA. YOUR ORIGINAL.
Human creativity
deserves evidence.
Capture a moment on Android. Bind the original to a signed record, an optional watch pulse observation, and a blockchain commitment you can check.
Check a capture ↗Evidence of provenance. No claim of impossible AI detection.
HEARTCLICK CAMERA● ORIGINAL
＋
Your point of view.
Your original bytes.
Your original bytes.
CRYPTOGRAPHIC CAPTURE RECORD
CHECK THE FILE, NOT THE PROMISE
Verify an original.
Choose the .heartclick.json proof and its original JPG or MP4. Files stay in your browser for the check.
A pulse observation is not human identity.
Local key-level claims are not server attestation.
A camera can capture a screen or an AI-created scene.
Signed capture details
Share the public proof.
Publish the signed proof, without uploading the media. It includes the declared time, signing key and any attached watch model/pulse range.
OPTIONAL · BASE SEPOLIA TEST NETWORK
Put this commitment on-chain.
Your wallet signs a zero-value self-transaction containing the proof digest. Test gas is needed. This does not certify human authorship or the recording time.
STRONGER CLAIMS REQUIRE STRONGER EVIDENCE
Four checks.
No magical badge.
Direct camera workflow
HeartClick has no gallery import, beauty filter or generative effect in capture mode. The camera hardware may still process images.
Bound to the session
A foreground Wear OS app can sign fresh sensor observations with the capture nonce and exact file hash. The wearer and creator may differ.
Check the original
A Keystore signature detects a change in the signed original. A different or self-signed key is not a trusted identity.
A public commitment
A confirmed transaction shows when a digest entered the chain. It cannot prove what happened in front of the lens.
Made for sharing.
Honest about the copy.
Social apps may recompress media or strip metadata. HeartClick keeps the original and can make a labelled QR share copy. Only the matching original passes the original-file check. Keep both the original and its proof.
Current builds are development builds. Hardware attestation, Play Integrity, release signing, device revocation and physical phone/watch validation must be completed before a trusted-device certification service can launch.