Skip to content

feat: package metadata, grouped Dependabot config, README FAQ #41

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.

Sign up for GitHub

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

Merged
TheStreamCode merged 3 commits into from
Sep 22, 2026
Merged

feat: package metadata, grouped Dependabot config, README FAQ #41

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
490465f
feat: add package metadata, grouped Dependabot config, README FAQ
TheStreamCode Sep 22, 2026
5b1ea8e
revert: drop dependabot.yml from PR, keep c00f050 decision
Sep 22, 2026
2f44b71
chore(deps): align deps to installed Expo SDK 57 patch versions
Sep 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 41 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,6 +95,47 @@ The source of truth for shipped changes is the [changelog](CHANGELOG.md) and the
verification results are recorded in dated release and audit documents instead of being
duplicated here.

## FAQ

**I forgot my master PIN. Can it be recovered?**

No — not by anyone. Keysoft has no account, server, or recovery back door, so
there is no server-side material that could reset or reveal the PIN, not even
through [support](mailto:keysoft@mikesoft.it). The only way back into a locked
vault is a previously exported encrypted backup plus the passphrase chosen at
export; without the PIN or that backup pair, the vault is unrecoverable by
design. See the [security architecture](docs/security.md), and keep backup
files and their passphrase somewhere safe — you own both.

**Biometric unlock stopped working. What now?**

Unlock with your master PIN, then re-enable biometrics in Settings
(“Biometric authentication”). Biometric unlock stores only the derived vault
key in SecureStore behind device authentication, so adding or removing a
fingerprint/face, changing the PIN, or a SecureStore failure disables it and
falls back to PIN login — the vault itself is unaffected. Details live under
[“Biometric Authentication”](docs/security.md#biometric-authentication) and in
the [architecture notes](docs/architecture.md).

**How do I back up and restore my vault?**

In Settings, “Export data” writes a versioned `KS1-PW1` encrypted backup file
protected by a passphrase you choose, and “Import data” restores it: pick the
backup file, enter the export passphrase, and records merge by ID. Imports up
to 10 MiB are accepted and validated before anything is written. Keep both the
file and its passphrase — losing either is the same as losing the vault. The
format and validation rules are documented under
[“Backup Encryption”](docs/security.md#backup-encryption).

**Why does Expo Go behave differently from the installed app?**

Expo Go builds use a documented PBKDF2 fallback because the native Argon2id
module is unavailable there; production builds always derive keys with
Argon2id. If a vault requires Argon2id and the native module is missing, login
fails with a native-KDF diagnostic instead of silently accepting a weaker
check. See the [security architecture](docs/security.md) and the
[development guide](docs/development.md).

## Developer Quick Start

Requirements:
Expand Down
Loading
Loading