Kryo is waiting at startup
Kryo checks the network and service configuration before choosing the native app or optional web content.
View startup steps →Kryo / Technical support
Find practical answers for Kryo’s on-device cryptographic and encoding tools, startup connection, WebView, camera, and photo access.
Select the closest issue. Each answer keeps native tools, optional web content, and device permissions separate.
Kryo checks the network and service configuration before choosing the native app or optional web content.
View startup steps →Web pages run inside the system WebView and may depend on cookies, JavaScript, certificates, or their own server.
Check WebView help →Photo access begins only after you choose a picture or camera action on the feedback screen.
Review permission help →Character encoding, hidden spaces, key format, salt, iteration count, and output format can all change a result.
Compare inputs →Faster diagnosis
A short, reproducible report makes it easier to identify the cause without exposing sensitive content.
Include Kryo version, device model, operating-system version, and whether you were using a native tool or web content.
List what you tapped, what you expected, and what happened. Mention whether the issue is repeatable.
Remove passwords, private keys, recovery phrases, personal data, and confidential input before attaching an image.
These checks solve the most frequent setup and output questions.
Kryo needs a working connection to retrieve its startup configuration. Confirm that Wi‑Fi or mobile data works in another app, disable a restrictive VPN or DNS filter temporarily, and reopen Kryo. When the connection returns, Kryo retries the configuration flow automatically.
The page may reject embedded browsers, use an unsupported sign-in flow, rely on a failing script, present an invalid certificate, block your network region, or be unavailable on its own server. Try the same address in Safari or Chrome and confirm that the device date and time are correct.
Kryo does not add a title bar or loading bar to optional web content. The website controls its own interface and availability.
On iPhone or iPad, open Settings → Privacy & Security → Camera and allow Kryo if camera access was denied. The system photo picker normally exposes only the images you choose. On Android, review Kryo under Settings → Apps → Permissions and try the system picker again.
Compare the exact UTF‑8 input, capitalization, line endings, leading and trailing spaces, key, salt, iteration count, and whether the expected output is hexadecimal or Base64. For PBKDF2, leaving the salt blank intentionally generates a new random salt, so each result will differ.
Use SHA‑256 or SHA‑512 for general hashing, HMAC‑SHA256 for keyed message authentication, and AES‑256‑GCM or ChaCha20‑Poly1305 for authenticated encryption. PBKDF2‑HMAC‑SHA256 derives keys from passwords. MD4, MD5, SHA‑1, and Hyper are available only for compatibility and should not protect new security-sensitive data.
No. Proper encryption does not provide a recovery shortcut. Kryo cannot decrypt AES‑GCM or ChaCha20‑Poly1305 data without the correct password and cannot recreate a lost RSA private key.
No. Native cryptographic and encoding operations run on the device. Optional websites shown in WebView are separate: information entered there is handled by the website operator under that website’s policy.
The current app version shows a local success confirmation only. It does not yet upload the description, email address, or selected images. For assistance now, email the support address below.
Direct support
Email the Kryo team with a safe description of the issue. You can also use this address for accessibility and privacy questions.