bitwarden/help
1
0
Fork 0
mirror of https://github.com/bitwarden/help synced 2025-12-10 21:33:18 +00:00
Code Issues Releases Wiki Activity

Misc (#631)

Browse Source 
* biometric unlock disabled pending verification of mp

* mention error in autofill main article

* caching faq item

* Org Renewal article + updated org license info

* typo fix

* ~ improvements ~

* pw-protected file send example

* typo fix
This commit is contained in:
fred_the_tech_writer
2021-06-07 15:24:33 -04:00
committed by GitHub
parent 8605f3337e
commit 6cff97b822
8 changed files with 77 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
_articles/faqs/autofill-faqs.md
View File

@@ -29,3 +29,13 @@ order: 10
1. Open Settings in your Android device.
2. Scroll down and tap on Google.
3. Tap on Auto-fill with Google and toggle it off.
### Q: What do I do about 'Biometric unlock disabled pending verification of master password'?
**A:** This most commonly occurs on iOS when you make a change to your device's biometrics settings (e.g. adding another finger to Touch ID). To resolve this error:
1. **If you have [PIN Code]({{site.baseurl}}/article/unlock-with-pin/) verification active**, disable it.
2. Log out of your Bitwarden mobile app.
3. Check that your device settings are [setup to use Bitwarden for autofill]({{site.baseurl}}/article/auto-fill-ios/#keyboard-auto-fill).
4. Log back in to your Bitwarden mobile app.
5. Re-enable [PIN Code]({{site.baseurl}}/article/unlock-with-pin/) verification if you want to use it as a backup for [biometrics]({{site.baseurl}}/article/unlock-with-biometrics/).

12
_articles/faqs/security-faqs.md
View File

@@ -80,7 +80,17 @@ Bitwarden takes user security and privacy seriously. Bitwarden maintains secure,
### Q: How does Bitwarden vet code changes?
**A:** Confidence in the security of our systems is of utmost important to Bitwarden. All proposed code changes are reviewed by one or more non-author members of the team before they can be merged into any codebase. All code goes through multiple test and QA environments prior to production. Bitwarden has implemented a SOC2 report to audit and validate our internal procedures. As mentioned in the report, our team is subject to rigorous background check and thorough interview processes. Bitwarden, being an open-source product, also welcomes peer-review of our code at any point. The team at Bitwarden strives to do everything we can to keep our users comfortable, and keeping their data secure. 
**A:** Confidence in the security of our systems is of utmost important to Bitwarden. All proposed code changes are reviewed by one or more non-author members of the team before they can be merged into any codebase. All code goes through multiple test and QA environments prior to production. Bitwarden has implemented a SOC2 report to audit and validate our internal procedures. As mentioned in the report, our team is subject to rigorous background check and thorough interview processes. Bitwarden, being an open-source product, also welcomes peer-review of our code at any point. The team at Bitwarden strives to do everything we can to keep our users comfortable, and keeping their data secure.
### Q: How long does Bitwarden cache session information?
**A:** Great question! The answer depends on the particular piece of information and client application:
- Offline Vault sessions will expire after 30 days.
- **Except** for mobile client applications, which will expire after 90 days.
- [Two-step Login]({{site.baseurl}}/article/setup-two-step-login) **Remember Me** selections will expire after 30 days.
- Directory Connector [sync cache]({{site.baseurl}}/article/clear-sync-cache/) will be cleared after 30 days.
- Organization invites will expire after 5 days. Self-hosted customers can configure this [using an environment variable]({{site.baseurl}}/article/environment-variables/#optional-variables).
### Questions Regarding Specific Client Apps