Security

Security and privacy, by default

What Sura does to protect your account, your apps and your data. All of it applies to every plan, Free included.

Account access

  • Sign-in with GitHub or Discord (OAuth 2.0 with PKCE and protection against forged requests). We never see or keep a password.
  • HttpOnly, Secure and SameSite session cookies.
  • Sensitive actions (deleting the account, exporting data, ending sessions, disconnecting a provider) ask for a recent identity confirmation.
  • An alert for sign-ins from a new device, and the list of your sessions and devices to end what you do not recognize.
  • A log of the account activity: sign-ins, links, confirmations and exports.

Your data and secrets

  • Environment variables and webhook addresses are encrypted (AES-256-GCM), each value tied to its owner.
  • Session and API tokens are kept only as a cryptographic digest, never in plain text.
  • Access to your repositories is read-only, and we do not keep GitHub tokens.
  • Backups of databases and volumes are kept off the server the app runs on.

Platform

  • Isolation between the apps of different customers, with memory and CPU limits per plan.
  • Rate limiting per address, HTTPS-only connections and security headers on the dashboard.
  • Payment is handled by Stripe: the card is collected and kept by it, not by us.

Privacy (LGPD)

  • You can export all your account data, as JSON, and delete the account whenever you want.
  • We do not use advertising or tracking tools, and we do not sell personal data.
  • If an incident with relevant risk happens, we notify you and the ANPD, as the LGPD requires.

Found a flaw?

If you found a vulnerability, contact us through the details in the Privacy Policy before disclosing it. Do not test the security of Sura or of other customers without written authorization (Terms of Service, section 5).

Read the Privacy Policy