-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lock the app with pin or biometrics #1356
Comments
Is there any update on this feature? |
Is there plan to implement this? |
I lost my phone (it was stolen), and since they will probably be able to access the device since it is not locked (since it remains unlocked when used, or even when it is in the pocket due to the smart-lock). Therefore, if a stranger manages to access Android, either through intrusion or theft. Does that mean that anyone can also access the Anytype app where I have practically my entire life? Shouldn't you have security measures for account access?, such as MFA, and/or Passkeys (in addition to biometrics or PIN). And, shouldn't it also be possible to remotely log out of linked devices? |
The craziest thing is that in the desktop app it is possible to put a PIN (As if it were easier to enter the desktop computer at home), or as if a laptop were easier to steal than a phone. |
If these features are present, the mobile version of Anytype should not even be in Alpha, at most in pre-Alpha, and with many red flags warning about it! |
I will have to go back to https://notesnook.com for many things that require use from the cell phone, I would even hire the paid version, the security is really worth it. |
Have you read a contributing guide?
Clear and concise description of the problem
This feature does exist on desktop but not on mobile.
This feature is also useful for mobile because the app is in many cases used to store very sensitive or personal information.
Suggested solution
Implement a PIN and/or biometric lock on the mobile app.
Alternative
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: