How WindChat protects you

We design WindChat so everyday messaging stays private from advertisers and casual eavesdropping. Here is what is built into the product today:

  • All traffic uses HTTPS/TLS between your device or browser and windchat.net.
  • Native apps encrypt API request and response bodies with AES-256-GCM so message payloads are not sent as plain JSON on the wire.
  • Each native API call is signed with HMAC-SHA256 (API key, timestamp, and signature) to reduce replay and tampering.
  • Accounts use phone verification with one-time codes and passwords stored with bcrypt — never as plain text.
  • Login, registration, password reset, and OTP sending are rate-limited and can temporarily lock abusive IPs.
  • On Apple platforms we can require App Attest and DeviceCheck so only genuine app builds talk to the API (when those checks are enabled).
  • Session tokens live in the iOS Keychain on phones and in HttpOnly cookies on the website — not in easy-to-steal browser storage.
  • Secrets and runtime chat data are stored outside the public website folder so they are not served as ordinary files.
  • We do not embed third-party advertising or analytics SDKs in the WindChat apps.

WindChat is not end-to-end encrypted: the service processes messages to deliver them. Optional server-side encryption for stored chat data can be enabled by operators. Full details are in the Privacy Policy.

Native apps talk to WindChat over encrypted /api/ endpoints on this domain. This page is the public website home.