Support
Need help using CryptKB?
Setup, decrypt flow, password vault behavior, and honest platform limits.
CryptKB is intentionally narrow: encrypt locally, insert ciphertext, manually send, and decrypt locally.
If something feels unclear, the most common issue is an iOS platform limit rather than hidden app behavior.
Quick setup checklist
- Install and open CryptKB once so iOS registers the keyboard and Messages extension.
- Enable CryptKB Keyboard in iOS Settings.
- If you want shared settings, enable Allow Full Access for the keyboard.
- Type the message with CryptKB itself so the compose buffer stays in sync.
- Tap Encrypt & Insert, review the payload, then tap Send yourself.
Common questions
- Why doesn’t CryptKB send automatically? Apple does not allow third-party keyboards to tap Send.
- Why isn’t there a custom iMessage long-press decrypt action? Apple does not expose that menu for third-party apps.
- Why is Decrypt local only? Writing plaintext back into the thread can create accidental-send problems, so CryptKB uses a popup instead.
- Can passwords be recovered? No. There is no backend recovery service.
Troubleshooting
Saved passwords and conversation scope
Saved conversation passwords are optional and off by default. To use them:
- Enable Allow persisted conversation passwords in the main app.
- Open CryptKB Messages once in the target Messages thread.
- Return to the keyboard and turn on Persist Password.
- Unlock the saved password with Face ID or device passcode when prompted.
If the keyboard says it needs CryptKB Messages first, that means iOS has not provided enough recipient
context for conversation-scoped password reuse yet.
Contact
Support email:
contactus@midstate.agency
Include your iOS version, whether Full Access is enabled, whether you are using the keyboard or Messages
extension, and the exact error or screen state you reached.