1. Confirm release availability and requirements
Start with release status, then compare your Mac with the development requirements: Apple Silicon, macOS 15 or later, and a camera. The present development package is not notarized and should not be treated as a public paid release.
Keep your normal Mac password available throughout any future evaluation. Lunlo does not handle FileVault/pre-boot login or the first login after a restart.
2. Keep account sign-in separate from local authorization
The intended account flow uses email sign-in and a verified membership status. The native app then has a separate local vault authorization step using macOS authentication. A successful account login does not by itself unlock the encrypted password store.
Your Mac login password belongs only in the native app's local setup on your own Mac. Never enter it on this website or into a billing form. Read how account access and password entry are separated.
3. Understand each permission before granting it
Camera access allows enrollment and recognition. Accessibility access allows the app to type the stored Mac password. The optional Space-key trigger checks keyboard-listening access, which macOS may already satisfy through Accessibility. The permissions guide explains what each permission supports. Choose permissions for the functionality you intend to evaluate rather than treating every system prompt as one combined setup approval.
Apple documents how to review camera permissions and Accessibility permissions. Permissions do not resolve the preview's disabled account configuration.
4. Inspect enrollment before enabling unlock
In a future configured build, select the intended camera and follow native enrollment. Use the Face Lab view to inspect recognition and liveness results in your actual lighting, at your usual screen distance and with the appearance you normally use at the Mac.
Face Unlock is off by default in the development implementation. A visible recognition result helps inspect the workflow; it does not establish protection against photos or replayed video.
5. Evaluate one controlled attempt at a time
Once a configured release is available and its prerequisites are satisfied, evaluate on a Mac and account you are authorized to access. The app is designed for deliberate scanning in an existing locked session and one password-submission attempt per lock session.
If an attempt cannot complete, use normal password entry and review troubleshooting before changing settings. Keep service failures, local vault authorization, recognition results and password-entry behavior separate when describing what happened.
Before evaluating the app, understand its Mac permissions and how its saved password relates to your Mac login password.