Skip to content

System

Patchwing treats security as a core design principle. These are the main measures we take:

  • All API communication is encrypted with HTTPS/TLS.
  • Patch artifacts are transferred over encrypted channels.
  • Communication between client and server is signature-verified.
  • Every patch artifact carries a SHA-256 hash.
  • The client verifies the hash before applying a patch.
  • If verification fails, the patch is discarded and the app keeps running the original code.
  • If a patch makes the app crash, the system rolls back automatically to the last stable version.
  • Developers can disable or roll back a patch manually at any time.
  • Account passwords are stored bcrypt-hashed.
  • API keys are generated with a secure random source.
  • Patch artifacts are stored in encrypted object storage.

Patchwing's over-the-air update mechanism complies with Apple App Store and Google Play Store policies:

  • Apple: complies with App Store Review Guidelines 3.3.2, which permits feature updates via interpreted code.
  • Google: complies with the Google Play Developer Policy without changing the app's primary purpose.

If you find a security vulnerability, email security@patchwing.net. We commit to responding within 48 hours.