Security at Pengwiz

Last updated August 3, 2026

Infrastructure

• Hosted on Amazon Web Services; traffic is TLS-encrypted end to end.
• Data is encrypted at rest by our managed database and storage providers.
• Production access is restricted to network-allowlisted operators; schema changes go through reviewed, non-destructive migrations.

Authentication

• Sign-in is handled by Clerk. We never store passwords; multi-factor authentication is available on every plan.
• API keys are scoped to a user, can be read-only, are shown once at creation, and can be revoked at any time. Key creation and revocation are recorded in the org audit log.

Tenant isolation

• Every organization-scoped request passes a single membership guard before any handler runs — one choke point instead of per-route checks that can be forgotten.
• Financial data (rates, billing config, margins) sits behind a separate permission that only the organization owner can grant.

Auditability and portability

• Security-relevant changes — membership, roles, permissions, API keys, exports — are recorded in an append-only org activity log visible to admins.
• The organization owner can export everything the organization owns as a single JSON file from Settings, any time, no support ticket needed.

Credentials we hold for you

Integration secrets (Slack webhooks, share tokens) are write-only: once saved they are never displayed again, are excluded from exports, and every share link can be revoked from the page that created it.

Compliance

We are not yet SOC 2 audited — at our size and price we would rather tell you that plainly than gesture at a badge. The practices above are in place today, and a formal audit is on the roadmap as the customer base grows.

Reporting a vulnerability

Found something? Email hello@pengwiz.comwith details and we will respond within two business days. Good-faith research against your own account is welcome; please never access another customer’s data.