Frequently Asked Questions

LPs maintain their own verified banking details within the platform. Sensitive PII is never collected into documents, exchanged over email, or handled by fund staff. Data within the platform is encrypted and access-controlled under SOC 2 Type II audited controls.

Every participant submits a government-issued ID and a biometric selfie match through an integrated identity verification partner. Verified identities are then routed for human approval before the account can transact. Verification is continuous — KYC/KYB and OFAC screening run automatically throughout the relationship.

6lock supports all major payment rails offered by the Federal Reserve: wire, ACH, same-day ACH, FedNow, and RTP. The appropriate rail is selected per transaction and use case.

6lock is built to work alongside fund administrators, and several of 6lock's earliest deployments run through fund administrator workflows. The platform reduces verification workload, automates reconciliation reporting, and gives administrators the same verified, real-time view of money movement that GPs and LPs receive.

No. Separation of duties is enforced by the system. Multi-party approval is required on every capital event, and no individual can both authorize and execute a transaction.

Banking details can be updated only by the verified account holder, inside the platform, with every change logged and re-screened. Instructions cannot be altered in transit because they never leave the platform.

Yes. 6lock maintains SOC 2 Type II compliance with independently audited controls across infrastructure, access, and data handling. The report is available under NDA through the documentation request above.

Submit a request through this page or contact our team directly. We respond to due diligence inquiries directly, including completion of DDQs and security questionnaires.