Kenshiki
Try the live demo

Trust & review

Built to be reviewed

A lender should not have to make decisions harder to explain just to add a new check. Kenshiki records what was asked, what was checked, what came back, and why it was used while the decision is being made.

Review flow

Prepare. Propose. Prove.

Every check follows the same path: decide what is allowed, ask only for the needed answer, and save the record while the decision is still live.

Kenshiki's Prepare–Propose–Prove flow: bind the allowed question and proof rule, ask an approved source for a bounded answer, then seal a replayable record.

  1. 01

    Prepare

    Bind the lender's question to an approved proof rule, policy version, and provider boundary before any check runs.

    Boundary
    Allowed question
    Proof
    Defined in advance

  2. 02

    Propose

    Ask for a narrow bounded result from the approved source environment instead of collecting a raw private-data feed.

    Boundary
    Provider-side check
    Output
    Bounded answer

  3. 03

    Prove

    Seal the bounded result, timestamp, policy version, and explanation into a reviewable record for underwriting, compliance, and examiner review.

    Record
    Inspectable
    Use
    Replayable later

The source, result, and lender policy stay clear enough for people to inspect.

Decision-time review

Review has to be built into the decision, not rebuilt later.

The question, result, and explanation have to be captured while the decision is being made. Otherwise review becomes guesswork.

Zero-data-movement architecture Kenshiki ships only algorithm payloads and geofences to a provider-side execution enclave. Raw trajectories stay inside the provider environment, and only scored evidence returns. DEPLOYMENT BOUNDARY RAW TRAJECTORIES NEVER CROSS KENSHIKI LABS DATA PROVIDER (MNO / AGGREGATOR) 1. SHIP PAYLOAD 3. RETURN SCORES Outbound Payload Algorithm IP (Coherence Logic) Land Use Geofences Returned Evidence Packet HOME .92 WORK .85 PLAY .44 SHOP .65 TRAVEL .11 Execution Enclave Raw mobility data never leaves this environment. 2. CARRIER-SIDE COMPUTATION SCORE EXTRACTION
Kenshiki ships only algorithm payloads and geofences to a provider-side enclave. Raw trajectories never cross the boundary — only scored evidence returns.

Policy on paper

Write a standard and hope the system followed it.

Static policies are necessary, but they do not prove what happened in a specific decision.

Kenshiki

Set the rule before the check runs.

The question, allowed data, rule, result, and explanation become part of the decision record.

Standards

Built for regulated teams

Built with the review frameworks lenders already face in mind, including FFIEC cybersecurity guidance, SR 26-2 model-risk guidance, and the federal banking and credit-union obligations lenders already carry.

SOC 2 readiness

ISO/IEC 42001 aligned

AIGP-certified staff

NIST AI RMF aligned

GDPR / CCPA aligned

Vendor review

What your review team can inspect.

Procurement and security reviews move faster when the paperwork is ready. Kenshiki shares documentation during a scoped evaluation rather than asking anyone to take a badge on faith.

Data processing agreement

Available on request, covering roles, scope, and the data limits that keep raw private data out of places it does not need to go.

SOC 2 Type II readiness

Readiness is underway. We share current controls and readiness status under NDA so your team can assess where we are today.

Security review package

We support standard vendor-security questionnaires and can provide architecture, access-control, and data-handling documentation under NDA.

Privacy and lending obligations

Controls are mapped to obligations lenders already carry: safeguards, consumer privacy, fair lending, and reporting duties.

Decision limits

Kenshiki supplies a check. The institution still decides.

Kenshiki is built for regulated lending environments where how evidence is allowed, limited, explained, and saved matters as much as the result itself.

Use determines the rule.

A result’s obligations depend on how it is used. The allowed question, purpose, consent basis, and lender policy should be set before the result can affect an action.

Move as little raw data as possible.

Where possible, the lender receives only the answer needed, not a broad private-data feed.

Keep the lender in control.

The institution keeps credit policy, fraud policy, pricing, reviews, notices, and final decision authority.

Make the record understandable.

Every check should preserve the question, source, rule, result, explanation, and review path.

Privacy posture

Presence without location tracking.

Checking that a real applicant is present should not require a lender or vendor to reconstruct where the applicant has been. Pulse returns a narrow result and keeps raw phone history out of the lender’s system.

What the phone checks Read Pulse

FAQ

Common trust questions

Does Kenshiki replace the lender’s credit decision?
No. Kenshiki supplies a result and record a lender can inspect; it does not replace the lender’s credit policy or final decision authority.
Does Kenshiki collect or store an applicant’s raw private data?
No. Kenshiki is designed to return the result needed for the decision, not a broad feed of raw private data.
How does Kenshiki make a decision easier to review?
It preserves what was asked, what was checked, what result came back, and why the lender used it, so a reviewer can understand the decision later.
Can Kenshiki certify a lender’s compliance?
No. Compliance remains the institution’s legal responsibility. Kenshiki provides controls and records that can support review, not a legal certification.
Is this a hidden second credit score?
No. Signals should be tested, limited by lender policy, and explained in plain language. A signal that cannot be controlled should not be used in a decision.

What this is not

Trust is not a claim we ask you to take on faith.

Not an automatic approval engine.
Kenshiki supplies evidence a lender can inspect. It does not replace the lender’s credit policy or final decision authority.
Not a raw-data sharing scheme.
The product direction is limited evidence, not broader exposure of sensitive source data.
Not a certification page.
Certifications, legal opinions, and data-processing terms require their own evidence and agreements.
Try the live demo Get the SDK See the platform Request a briefing