Trust center

Security & Trust Whitepaper

Back to trust center

Effective date

Aug 13, 2026

Last updated

Aug 13, 2026

Version

1.0.0

Entity

Renvo Productions LLC d/b/a respawn.sh

respawn.sh is built to protect the game-server backups it holds and the accounts that manage them. This page summarizes the concrete controls in place today -- it will be kept up to date as the system evolves.

Account security

Passwords are hashed with argon2id and are never stored or logged in plaintext.
TOTP secrets and OAuth tokens are encrypted at the application layer with AES-256 before being written to the database -- not relying solely on the database provider's own encryption at rest.
Every login is checked against the Have I Been Pwned breached-password database using the k-anonymity model: only the first 5 characters of a SHA-1 hash of the password ever leave the server, and the full password never does.
Repeated failed login attempts trigger a temporary soft-lock on the account.
Signups are rate-limited per IP address to slow down bulk account creation.

API keys

API keys are hashed before storage, the same way passwords are. The unhashed key is shown to you exactly once, at creation, and is never displayed or logged again.
Keys can be scoped, named, and revoked individually at any time from the dashboard.

Backups

Backup content is encrypted with AES-256-GCM at the application layer before it is uploaded to object storage, and again in transit over TLS. The encryption key is stored separately from the encrypted data.
All API traffic requires TLS 1.2 or higher; there are no unencrypted HTTP routes in production.

Audit and access

Security-relevant account actions (logins, key creation and revocation, plan and billing changes, organization membership changes) are recorded in an append-only audit log, including the actor, IP address, user agent, and timestamp.
Access to the admin panel requires a separate, hashed PIN with lockout after repeated failed attempts.
Internal staff access to backup content is logged with the accessor's identity, timestamp, and stated purpose.

Questions

If you have a specific security question this page doesn't answer, contact support@respawn.sh.

Back to trust center

Account security

Passwords are hashed with argon2id and are never stored or logged in plaintext.

TOTP secrets and OAuth tokens are encrypted at the application layer with AES-256 before being written to the database -- not relying solely on the database provider's own encryption at rest.

Every login is checked against the Have I Been Pwned breached-password database using the k-anonymity model: only the first 5 characters of a SHA-1 hash of the password ever leave the server, and the full password never does.

Repeated failed login attempts trigger a temporary soft-lock on the account.

Signups are rate-limited per IP address to slow down bulk account creation.

Backups

Backup content is encrypted with AES-256-GCM at the application layer before it is uploaded to object storage, and again in transit over TLS. The encryption key is stored separately from the encrypted data.

All API traffic requires TLS 1.2 or higher; there are no unencrypted HTTP routes in production.

Audit and access

Security-relevant account actions (logins, key creation and revocation, plan and billing changes, organization membership changes) are recorded in an append-only audit log, including the actor, IP address, user agent, and timestamp.

Access to the admin panel requires a separate, hashed PIN with lockout after repeated failed attempts.

Internal staff access to backup content is logged with the accessor's identity, timestamp, and stated purpose.