SOC 2 Type II
In preparation · targeted Q4 2026
We are actively preparing for our SOC 2 Type II audit, on track for the next 4–6 months.
The institutions that hold the deepest relationships carry the heaviest duty to protect them. GuardKin gives a private bank or trust company a premium estate-readiness offering with a boundary your infosec and fiduciary teams can actually verify — not take on faith.
Sensitive content is sealed with keys the server never holds. "What can your platform see?" has a structural, audit-able answer — not a policy promise. Your security review gets a data-flow it can actually check.
Advisor visibility is consent-scoped to planning metadata; content stays with the client. The institution holds the relationship without holding the client’s secrets — exactly the line a fiduciary duty asks you to keep.
The moment your platform most often loses the next generation is the wealth transfer. GuardKin is the premium readiness offering that earns the heir’s trust before the assets move, and a clean executor handoff after.
A Trust Center, subprocessor register, security architecture write-up, and honest compliance status — assembled the way an enterprise InfoSec questionnaire expects, so a review moves in days, not quarters.
Structural figures only. We publish no invented institutional logos, AUM, or cohort numbers — pilot results will be labeled as such, with consent, when they exist.
Everything an enterprise InfoSec review asks for is public and structured — so the assessment moves quickly and on the record.
Documented residency, retention, deletion, and export posture — the table your due-diligence team will ask for, published on the security page.
Read the detailIR, BCP/DR, and SLA commitments laid out for an enterprise relationship, with disclosure handled through a published security.txt.
Read the detailEvery vendor in the data path is named in a public register, so your vendor-risk process has a real list to assess — not a black box.
Read the detailIn preparation · targeted Q4 2026
We are actively preparing for our SOC 2 Type II audit, on track for the next 4–6 months.
Content keys never reach us
Sensitive content is encrypted client-side. Our servers store only ciphertext.
Independent review · scheduled
Cryptographic design under independent review — scope on record, findings on completion.
We design pilots around an institution’s real procurement and fiduciary requirements. Tell us what your review demands, and we’ll show you exactly how the architecture answers it.