Security

This page is maintained by Vyronex to describe the security practices currently in place for the Vyronex platform. It is not an independent certification.

Authentication & Access

• Email and Google sign-in via a managed identity provider.
• Passwords are stored as salted, one-way hashes by our identity provider — never in plain text.
• Row-Level Security policies scope every database read and write to the signed-in user.

Data in Transit & at Rest

• All traffic to Vyronex is served over HTTPS/TLS.
• Uploads and generated packs are stored in private object storage; downloads use short-lived signed URLs.
• Encryption at rest is provided by our storage and database providers.

Application Security

• Server functions run in an isolated edge runtime with least-privilege credentials.
• Webhook and public API endpoints verify signatures or shared secrets before processing.
• Dependencies are monitored and updated on a regular cadence.

Payment Security

Payments are handled by our payment processor. Vyronex does not store full card numbers or CVV codes on our systems.

Incident Response

If we confirm a security incident affecting your data, we will notify affected customers without undue delay and provide details on scope, impact, and remediation.

Reporting Vulnerabilities

If you believe you have found a security vulnerability, please email security@vyronex.fun with reproduction steps. Please give us a reasonable time to address the issue before public disclosure.