MiniUnlock security, Face ID and setup requirements

What Face ID authorizes

Face ID or the device authentication offered by the iPhone authorizes use of a saved credential. It does not give MiniUnlock a new Mac identity or eliminate the Mac password. The initial setup uses the known password of the computer owner.

In the tested beta flow, cancelling phone authentication left the Mac locked. A later, separately authenticated request succeeded. This behavior must remain part of release testing rather than relying on a successful authentication screen alone.

Where the password travels

The current iPhone implementation uses device-only Keychain and does not sync the saved Mac password to iCloud. After phone authentication, the credential is encrypted for the paired computer. The Mac decrypts it transiently to carry out the authorized action.

The relay transports encrypted messages and operational metadata such as connection state, device identifiers and request timing. The design avoids writing plaintext passwords to application logs and the relay database. It does not claim that the password never exists in plaintext at the authorized endpoint.

Mac permissions and availability

The Mac companion needs Accessibility access for its lock-screen interaction. The computer must already have a logged-in session, remain awake and online, and keep the companion reachable. Permission setup takes place on the Mac before remote use.

A saved pairing is not proof of a live connection. A Mac can become unreachable because of a network change, sleep, an app failure or shutdown. The result of a request must distinguish reachability, accepted authentication and confirmed screen unlock.

What this beta does not cover

• Forgotten-password recovery or Activation Lock removal.
• Preboot FileVault unlock or starting a shut-down computer.
• Automatic approval of OS administrator prompts or website MFA.
• Verified Android or Windows screen unlock.
• An independent security audit or compatibility certification.

Phone-loss recovery, credential revocation, OS coverage and complete retention and support policies are commercial release requirements. Public installers are not being offered before the release checks are completed.

Use the published policies for the current state

The beta security notes describe current credential handling and relay metadata. Commercial terms, final regional pricing, and purchase conditions must be provided before paid public release. No password or payment is collected by this marketing website.

Read the privacy notes and release information linked below. If a failed request leaves the result uncertain, check the actual computer state before assuming success or sending repeated requests.