Trust center
Do not trust a badge. Inspect the boundary.
This page separates currently inspectable evidence, pilot commitments, and credentials Avarent does not claim.
Last reviewed: August 12, 2026
Methodology
PublicMetric definitions, screening thresholds, interpretation limits, human-review expectations, and primary regulatory references.
Review methodologySynthetic-first pilot
AvailableAn evaluation can begin without production integration or raw applicant records. Scope expansion requires an explicit data plan.
Review pilot stagesSecurity review
Public starting packetWebsite data flow, service providers, access assumptions, retention questions, incident contact, and explicit open items are available before sensitive data.
Open diligence packetSOC 2
Not claimedAvarent does not represent that it currently holds a SOC 2 report. We will not use ambiguous “aligned” language as a substitute.
Regulatory approval
Not claimedAvarent is not a regulator, law firm, or certification body and does not guarantee that use of the product makes an institution compliant.
Customer proof
Not fabricatedWe do not publish customer logos, testimonials, or outcome statistics without permission and evidence.
Company transparency
Continuity and contracting are reviewable risks.
Avarent was founded by two 17-year-olds. That may increase an institution’s perception of execution, continuity, and contracting risk; hiding it would create a larger trust problem.
Before any pilot, Avarent will document the legally authorized signatory, named technical and escalation owners, written scope, success criteria, artifact export, access revocation, deletion expectations, and an explicit exit path. If a requested assurance or qualified advisor does not exist, we will say so.
Start with the public packet.
Inspect the current data boundary and open items before emailing George or Lucas with follow-up questions.