On your phone
Keep your own evidence.
Build a record of your phone's activity over time. Identity checks anchor that history; your evidence stays in your custody.
For people. For the applications they use.
Identity starts with the person.
Kenshiki Pulse is an iPhone app that builds a signed history of your device’s activity, anchored by identity checks. Keep your evidence with you, or evaluate the iOS Identity SDK for your application.
iOS SDK evaluation · Android workflow preview
The person behind the proof
An identity check is the start. Keep the person in the picture.
A password can be phished. A face can be faked. Pulse builds evidence from what a phone lives through: motion, places, rhythm, and time. Signed events connect that history to the identity established at the start.
The record stays with its owner. Your phone builds the history; you keep the evidence.
When you share
Choose the moment.
Send a check-in to someone who needs to know you are there. You choose when to share it; the check-in expires after an hour.
In an application
Build the check.
Use SDK capture, storage, signing, and continuity in your app. Define what your service checks before it allows an action.
The gap fraud exploits
More checks. The same gap.
A valid password, code, or key can return without the person it belongs to. More checks of the same factor do not close that gap. The cost of scams and payment errors makes the stakes clear.
$12.5B
consumer fraud losses reported to the FTC
Reported losses in calendar 2024. Reports do not capture every victim.
$68B
estimated U.S. scam losses in Gallup's survey
Survey-based estimate for calendar 2025, including losses not reported to authorities.
$186B
estimated improper federal payments
Fiscal 2025 payment errors. Improper payments are not all fraud.
Different measures and reporting periods. These figures are not additive.
Gallup estimated 15.1 million scam victims in 2025: about 1 in 18 adults, or one person every 2 seconds on average.
Gallup Stop Scams Coalition Poll 2025
A key returning is not a person returning.
A sign-in can recognize what you hold. The decision also needs evidence of who is there. Pulse connects the two.
Build with Kenshiki
The evidence belongs to your user. The integration belongs in your app.
Use the iOS Identity SDK to capture evidence, keep it on the user’s device, sign events, and evaluate continuity. Explore simulated native workflows in the Android reference app. Your app owns the experience; your service owns its access decisions.
The SDK is available for evaluation. The verifier, user-held presentation, and federation adapter are planned additions. Choose one decision, the evidence it needs, and how you will test it.