Security without mystery

• HTTPS and a restrictive Content Security Policy protect browser traffic.
• Passwords are bcrypt-hashed; OAuth and fulfillment credentials are AES-256 encrypted at rest.
• Production secrets are supplied at runtime and are not embedded in application images.
• PostgreSQL tenant records are scoped by authenticated user or team ownership in application services.
• Rate limits, request-size limits, CSRF origin checks, and constant-time webhook verification protect APIs.

PrintMind uses short-lived signed sessions, account lockout after repeated login failures, and role checks for team and administrative actions. Customers can revoke connected marketplace access at the provider and remove integrations in PrintMind. Authenticator-app multi-factor authentication is available in account settings, with single-use recovery codes and session revocation after security changes. Customers should still use a unique password and secure the email account tied to PrintMind.

Production services run in isolated containers with health checks and encrypted infrastructure backups. Restore procedures and incident-response runbooks are maintained operationally. No public recovery-time or recovery-point guarantee applies unless it appears in a signed Enterprise order form.

Dependency, secret, static-analysis, type, test, and container-build checks run in Forgejo Actions before release. PrintMind does not claim a current independent penetration-test certification. Report a suspected vulnerability privately to [email protected]; include the affected URL, reproduction steps, and impact. Please avoid privacy violations, destructive testing, or service disruption. We will acknowledge a valid report and coordinate remediation in good faith.

Review the Data Processing Addendum, Subprocessor Register, and Privacy Policy. Security questions for a vendor review can be sent to [email protected].