CPIFY / SECURITY

Security.

Our current security boundaries, local-only use, and planned encrypted sync.

Security promises should be verifiable

CPify Desktop is designed around OS-backed credential protection and explicit SSH host-key trust. The standalone website does not receive or display saved desktop SSH passwords, private keys or terminal output.

What this website stores

Website accounts store the profile name, email, hashed login password and operational metadata such as email-verification status. The release catalog contains public artifact metadata. There is no active cloud vault, licensing API or decrypted credential collection in this phase.

What's still planned

End-to-end encrypted sync requires a versioned client-side protocol, recovery-key design, known-answer tests, token and device revocation, and independent security review. No zero-knowledge service is represented as active today.

Report a problem

Security disclosures: [email protected]. Replace this placeholder address with a monitored production mailbox before launch.