Information Security Policy
1. Purpose and scope
This policy summarizes the security program of Peck Stelzer Systems LLC for our compliance file-review product (the "Service") and the customer data it touches. Detailed technical commitments for a given customer are set out in that customer's signed agreement.
2. Architecture and isolation
- Single-tenant by design: each customer's deployment is a dedicated, isolated environment. No shared databases, no cross-customer data paths.
- Local-first option: the Service can run entirely on customer-controlled systems with outbound network access disabled at the container level, so documents never leave the customer's environment.
- No telemetry: the review engine sends no usage analytics or diagnostic data from customer environments.
3. Data handling
- Customer documents are processed transiently for review and are not retained beyond the customer's agreement.
- Audit logs are metadata-only — run identifiers, timestamps, rule identifiers, result codes — never document contents.
- Development and testing use synthetic documents; customer production data is not used to build or test the product.
- Customer personal information is used solely to provide the Service to that customer — never for marketing, product development, model training, or any profiling or automated decision-making about individuals.
4. Access control
- Least-privilege access to systems and customer environments; access to customer data is limited to what servicing that customer requires.
- Service authentication uses per-organization credentials with constant-time verification; default or placeholder credentials are refused by the software.
- Multi-factor authentication on company accounts and infrastructure.
5. Encryption
Data in transit to hosted deployments is protected with TLS 1.2 or higher. Data at rest in hosted environments is encrypted using platform-managed encryption. Local deployments inherit the customer's at-rest controls, and we document recommended configurations.
6. AI processing safeguards
- An eligibility gate ensures certain check types (including signature presence and form presence) are never sent to a model — enforced in code, not configuration.
- Document excerpts are minimized and redacted of personal information before any model call.
- The model provider operates under zero-data-retention terms; deterministic rule results always take precedence over model output, and conflicts fail closed.
7. Secure engineering
- Fail-closed design: unreadable files, unknown forms, and unrecognized rule types are flagged for human attention — never silently passed.
- All changes flow through version control and continuous integration with blocking test suites, including adversarial and malformed-input (fuzz) testing.
- Releases follow a documented checklist; deployment artifacts are versioned, built once, and promoted unchanged.
- Minimal dependency surface, monitored for vulnerabilities and patched promptly.
8. Incident response
Suspected security incidents are assessed and contained promptly. We notify affected customers without undue delay, consistent with their agreements and applicable law, and provide the information they need for their own obligations.
9. Vendors
Third-party providers are reviewed before use and limited to the roles listed in our Privacy Policy. Providers who could touch customer data must meet retention and confidentiality requirements consistent with this policy.
10. Personnel and review
Everyone with access to customer data is bound by confidentiality obligations. This policy is reviewed at least annually and upon material changes to the Service. Questions: our contact page.