Privacy

This notice describes the Kenshiki Labs website and Pulse iOS app. What is collected or shared depends on the feature you use and the permissions you grant.

Last updated: October 22, 2026

Website

Who we are. This site and the Pulse iOS app are operated by Ontic Labs, Inc., based in Tacoma, Washington, United States. Kenshiki Labs is a trading name of Ontic Labs, Inc. Contact [email protected] with privacy questions.

Browsing and contact. Our hosting service receives ordinary connection information, such as your internet address and requests for pages. If you email us, we receive your address and message. We use contact information to respond and follow up. This marketing site does not make credit decisions.

Messaging requests. The form on Messaging Consent collects your phone number, optional name, opt-in or opt-out choice, and consent confirmation. It sends a timestamped record, including the browser’s user-agent string, through Resend to our consent inbox. This records a request for our team; it does not itself change a messaging subscription. The email and its delivery record are separate from an app schedule.

Browser signal demo. On the browser demo, readings are collected only after you choose Read browser signals. Browser settings, available graphics information, a canvas test, and their digest are computed in the browser and held in the demo’s memory. The demo does not send those readings to a server. Clear results clears the display; it does not change browser privacy settings or information other sites have received.

Cookies, storage, and analytics. The website does not currently run analytics scripts or save a theme preference. If we add analytics, they will be denied by default and load only after you choose to accept.

Vendors and use. Hosting and email providers help operate the site and deliver messages. We do not sell your information. We do not share it except with people at Kenshiki who need it to reply to you and vendors that help operate these services. Their processing is also subject to their policies.

Pulse iOS app

Pulse collects and evaluates evidence about device activity and continuity. Depending on the feature and permissions, this can include motion and activity, location and visits, pressure, magnetic readings, power and thermal state, and network or carrier context.

The app processes evidence on the phone and keeps local records. Local processing does not mean every feature keeps all information on the device: bonding, calls, identity cards, check-ins, vouching, and phone checks have the sharing paths described below. Location can include precise coordinates.

Website bonding. When you approve a supported bond, the app can send a device-signed assertion, device-integrity information, local-authentication status, carrier context, and derived continuity signals for the partner service to evaluate. When passport evidence is included, the payload can contain identity fields such as name, date of birth, nationality, document number, issuing state and expiry, plus passport-verification metadata such as document-authentication results. The partner remains responsible for its decision and retention of information it receives.

Verified calls. Call features can send signed heartbeat information and location, including precise coordinates, for the call. Review the feature’s location and sharing disclosures before approving it.

Identity cards and check-ins. When you publish a card or share a check-in, approved identity information, summaries, notes, photos, and location-corroboration evidence can be sent to Kenshiki’s services for the share. Corroboration evidence can include pressure and altitude-related measurements, uncertainty, and timestamps. People who can open the published card or share link can view what it exposes.

Passport photos. Publishing a passport portrait is separate from running a face comparison. If you enable the portrait for a public identity card or include it in a check-in, the image is uploaded for that page. Keep the audience of the page or link in mind when choosing its contents.

Vouching. A vouch can send face-comparison and liveness results as part of the claim. Those results are distinct from the camera image and face measurements used locally for the comparison.

Face features

Face ID and device passcode. The app uses iOS local authentication where required. Apple’s Face ID authentication templates are handled by iOS; the app receives an authentication result, not those templates. This is separate from the camera-based comparison below.

Camera-based face comparison. When you choose face comparison, the app processes a camera image and depth readings and compares the image with a stored document portrait using an on-device model. The comparison produces an outcome and score. A blink, depth observation, or match score alone is not a guarantee of liveness or identity.

Transient inputs and stored results. The face-comparison flow uses camera images, crops, and comparison inputs transiently on the phone rather than uploading them for comparison. Closing the flow cancels its work. The app retains result information locally, including outcome, score, time, portrait hash, and how liveness was assessed. Stored passport records and portraits are separate local records; the passport database is protected and excluded from device backup.

Use of face data. Camera images and face measurements from this comparison are not used for advertising, marketing, or data mining. Results can be included when you use a sharing feature, as described above. Camera permission can be changed in iOS Settings.

Phone checks and text messages

Optional phone-number protection. If you choose to verify your phone number, Pulse sends the number, verification-code requests, and carrier-record lookups to Kenshiki’s PulseAPI proxy, which uses service providers such as Vonage and Twilio. Two optional checks build on a verified number: a SIM-swap recency check, and a carrier name/address match. The Pulse terms you accept when you set up the app include this authorization: You authorize your wireless carrier to use or disclose information about your account and your wireless device, if available, to Ontic Labs, Inc., doing business as Kenshiki Labs, or its service provider for the duration of your business relationship, solely to help them identify you or your wireless device and to prevent fraud. See our Privacy Policy for how we treat your data. Kenshiki Labs is a trading name of Ontic Labs, Inc.

Text messages. Requested verification codes and scheduled check-in or quiet-morning notifications use Kenshiki’s servers and messaging providers. Sending a text requires the destination number and message information to reach those services. Schedules, delivery records, opt-out information, and consent records are separate from the copy of a contact on the phone. See Messaging Consent for the program, request handling, frequency, and ways to stop messages.

No mobile-number sharing. Mobile phone numbers and text-messaging opt-in data are never sold, and never shared with third parties or affiliates for marketing or promotional purposes. They are used only to deliver the messages described above, through the messaging providers that transmit them on our behalf.

Deletion and contact

Use the app’s erasure controls for the local identity records they manage. Remove active shares and schedules through their feature controls. Deleting an app is not a reliable way to revoke a published link or remove information already held by a server, messaging provider, or recipient.

Withdrawing permission cannot retract copies already received. Website consent emails, service records, and recipient copies have their own handling; contact us about the records or feature involved rather than assuming local erasure removes every copy.

For privacy or deletion questions, email [email protected]. Identify the app feature or website request involved; keep identity documents and passcodes out of the email.

Related policies: Terms and Messaging Consent.