FAQ category
Handle missed triggers, Bluetooth false disconnects, forceful actions, and forgotten vault passwords.
Confirm that the trigger is enabled and its device or camera is available, then use manual Protect Now to test the action itself. Review the in-app trigger history and understandable error message afterward.
Read the full answer →Bluetooth can briefly disconnect because of device sleep, phone background restrictions, radio interference, or the edge of signal range. Observe the pattern, then allow more confirmation time or choose a more stable device.
Read the full answer →Yes. Force-close, force-lock or unmount, restart, and shutdown can interrupt applications and lose unsaved content. They should remain disabled by default and be used only when you accept the consequences.
Read the full answer →Stop repeated guesses and any operation that could overwrite the original vault. Locate the recovery material saved during creation and follow the recovery flow. Decryption should not be promised without the password or valid recovery material.
Read the full answer →