How does text encryption work?
New encryptions are produced in HC2 format. PBKDF2-SHA-256 derives separate encryption and authentication keys from the password; the text is encrypted with AES-256-CBC and authenticated with HMAC-SHA-256. This is designed for broader interoperability across browsers including iPhone/Safari. Older AES-256-GCM based HC1 messages remain decryptable.
Why does the password matter?
The security of encrypted text depends not only on the algorithm but also on how difficult your password is to guess. Use a long, unique password. Hesapica does not store your password and cannot recover a forgotten one.
How should I share an HC1 / HC2 message?
You can send the encrypted output beginning with HC1 or HC2 through a messaging app, email, or another channel. When possible, share the password through a separate trusted channel. Altering or truncating the encrypted text will cause decryption to fail.
🌍 Multilingual and Unicode text support
Unicode support lets you encrypt text in Turkish, English, German, French, Spanish, Arabic, Russian, Greek, Chinese, Japanese, Korean and other languages represented in Unicode. Non-Latin scripts, accented characters, special characters and emojis are preserved during encryption and decryption.
You can also mix multiple languages in the same message. The tool processes the characters as UTF-8 without translating or rewriting your text.
Encryption and decryption use the Web Crypto API in your browser. This page is not designed to send plaintext or passwords to a server. Device security, malicious browser extensions, screenshots, and weak password choices are outside the tool’s control.