GreenBar Systems
Security & Compliance Brief
One-page summary for internal review · Last updated July 2026 · Full detail at greenbarsystems.com/security
Overview
GreenBar builds two kinds of tools. Clearing (and the rest of the local-first suite) runs entirely on the customer's own computer — GreenBar operates no cloud for these tools and stores none of the customer's financial data. AP Assurance is a cloud accounts-payable product built for team review, so its architecture and controls are different by design. This brief covers both.
Clearing — local-first architecture
- Runs fully offline on Windows, macOS, and Linux. No account or sign-in to a GreenBar server.
- GreenBar operates no cloud for Clearing and stores none of the customer's financial data.
- Learning from user corrections stays on the local machine, per client — never pooled into a shared model.
- Installers are code-signed as Greenbar Systems LLC; auto-updates are signed and verified before being applied.
- Optional connections (bank feed via Plaid, accounting-system sync) are opt-in and run directly between the customer and that service.
AP Assurance — cloud architecture
- Tenant isolation: Postgres Row-Level Security enforced at the database layer on every tenant-scoped table; a single sanctioned code path (
withOrg()) is the only way any route or job reaches the database. - Document security: every upload and email attachment is scanned via ClamAV before any processing begins; PDFs are sanitized (scripts, embedded files, and XFA forms stripped) before storage.
- Email authentication: SPF, DKIM, and DMARC are evaluated on every inbound message; inbound-email notifications are cryptographically signature-verified.
- Fraud controls: remit-to drift detection, duplicate invoice detection, PO/three-way matching, and prompt-injection hardening on the AI extraction step.
- Audit trail: append-only (UPDATE/DELETE blocked at the database rule level), 7-year retention target, approvals sealed with the approver's identity and timestamp.
- Access control: role-based access (Owner/Admin/Reviewer/Approver) enforced server-side; mutating endpoints require idempotency keys and optimistic-concurrency headers.
- Data in transit: TLS between browser and AP Assurance; inbound email over encrypted SMTP; webhook notifications signature-verified.
Certifications and roadmap
We are building toward SOC 2 Type II certification. Many required controls — immutable audit logging, tenant isolation, incident-response hooks, least-privilege access — are already implemented. We expect to engage an auditor and begin the observation period in 2027.
Contact
Full technical detail, our responsible-disclosure policy, and a completed security questionnaire on request: security@greenbarsystems.com.