PinotPulse is built for U.S. credit unions, which means examiner scrutiny is part of the operating model. This page is a plain-language tour of how the platform is secured, where your data sits, who can see it, and what we ship in CI to keep it that way.
We publish the state of every audit and certification track honestly — including the ones still in the observation window. A sophisticated CIO would rather see “in progress” than “trust us.”
Audit observation window in progress. Audit-trail evidence is collected automatically with every regulatory action. Per-organization data isolation is enforced at the database level. Public attestation expected following window completion.
Every table that touches member or institutional data is isolated by organization at the database level. One CU’s data is never visible to another — not by application logic alone, but by the database itself. Cross-organization reads are impossible by construction, not by code review.
Phase-2b consolidation reduced 10 ad-hoc roles to 8 canonical roles plus 4 capability flags. Separation of duties enforced server-side: a loan officer cannot approve their own filing, a trial viewer cannot write through any API path, a board member sees what board members should see — and the rules are in code, not policy PDFs.
Every BSA action — SAR, CTR, OFAC, CIP (§ 1020.220), EDD (§ 1010.610), CDD (§ 1010.230(d)) — writes a paired intent + outcome row with CFR citation. Audit log writes are append-only with cryptographic chaining. SOC 2 CC7.2 evidence is automatic, not retrofitted.
Enterprise cloud infrastructure with blue-green deployment. Managed PostgreSQL with automated backups and point-in-time recovery. Live transaction analytics with streaming ingestion. Hosted in U.S. cloud regions only — your data does not leave the United States.
We do not sell, share, or repackage your data. We do not train models on your member data. We do not store credentials for your core banking system in plaintext or any reversible form. We do not run admin panels with placeholder buttons — if a feature is not live, it is not in the navigation.
A few visible items from our recent release cadence. We publish these because they are the kind of work that matters to a security-conscious buyer.
The platform is under active development. Major regulatory module releases land on a quarterly cadence (the most recent: Reg B + Reg Z + CRA 2024 modernization in 2026 Q2). Security patches and feature ships go out on a continuous cadence. Quality and audit-trail gates run on every change before release.
Request the full PinotPulse trust brief: how data is isolated, where it’s encrypted, our SOC 2 timeline, and how audit-trail integrity is maintained from the database up.
