Documentation

Complete reference for Vault3R v4.4.1 (Desktop, Android & iOS) — architecture, security, user guides, encrypted sync, autofill, and API.

Desktop v4.4.1 Android v4.4.1 iOS v4.4.1 Updated Feb 2026

Introduction

Vault3R is a cross-platform, zero-knowledge password manager. All data is encrypted locally on your device — no cloud, no accounts, no subscriptions.

Platforms: Windows 10/11 (WPF / .NET 8), Android 8.0+ (Kotlin / Jetpack Compose) & iOS 16+ (Swift / SwiftUI)
Storage: Local device only (%AppData%\Vault3R on Windows, app-private on Android, app sandbox on iOS)
Versions: Desktop 4.4.1 • Android 4.4.1 • iOS 4.4.1
Last updated: February 18, 2026

Key features

🔐 AES-256-GCM

Authenticated encryption with PBKDF2-SHA256 (200,000 iterations). Per-entry encryption — each password is encrypted independently.

🔄 Encrypted Sync

End-to-end encrypted vault transfer between Desktop, Android & iOS via ephemeral relay. Zero knowledge — the server never sees your data.

⚡ Autofill

Android system-wide autofill for Chrome, Firefox, Edge, Brave, Opera, Samsung Internet. Inline suggestions on Android 11+.

🔑 Quick Unlock

PIN (6-8 digits), biometric (fingerprint/face), or TOTP (Google Authenticator) — without typing the master password.

🛡️ Vault Health

Audit weak, reused, and breached passwords. Integrated Have I Been Pwned (HIBP) check using k-anonymity.

📝 Secure Notes

Encrypted notes with tags, search, and timestamps. Stored inside the vault alongside passwords.

🎨 11 Themes

8 free + 3 premium themes with glow effects. Identical look on Desktop and Android.

📦 Portable Backup

Export/import via .vlt (encrypted), .csv, or .json. Compatible between Desktop and Android.

⏱️ TOTP Generator

Built-in TOTP code generator (RFC 6238). Supports SHA-1/SHA-256/SHA-512 and otpauth:// URIs.

Important: Vault3R stores data locally. If you forget the master password, there is no recovery method for encrypted data.

Installation (Windows)

Requirements

ComponentRequirement
OSWindows 10 (64-bit) or Windows 11
Runtime.NET 8 Desktop Runtime (x64)
RAM4 GB minimum (8 GB recommended)
Disk~50 MB (portable) or ~500 MB (self-contained)

Portable (recommended)

  1. Download Vault3R_portable.zip from the home page.
  2. Extract to any folder (e.g. C:\Tools\Vault3R).
  3. Run Vault3R.exe.
  4. No installation required — the app is fully portable.

Installer

  1. Download Vault3R_Setup.exe.
  2. Run the installer (per-user, no admin required).
  3. Launch from Start menu or desktop shortcut.
Tip: Data is stored in %AppData%\Vault3R, not in the app folder. You can move the executable freely without losing your vault.

Updates

Check for updates: Settings → About → Check for Updates. If a new version is available, the app opens the download page.

Installation (Android)

Requirements

ComponentRequirement
OSAndroid 8.0 (API 26) or higher
Storage~30 MB
OptionalBiometric sensor (fingerprint / face)

Install from APK

  1. Download Vault3R_Android.apk from get.vault3r.pl.
  2. On your phone: Settings → Security → allow installing from unknown sources for your browser.
  3. Open the downloaded APK and tap Install.
  4. Launch Vault3R.
Updates: The app checks for updates automatically at launch. When available, tap Download to get the latest APK.

Installation (iOS)

Requirements

ComponentRequirement
OSiOS 16.0 or higher
Storage~10 MB
OptionalFace ID / Touch ID

Install via sideload (IPA)

  1. Download Vault3R_iOS.ipa from get.vault3r.pl.
  2. Install using AltStore, SideLoadly, or TrollStore.
  3. Trust the developer certificate if prompted: Settings → General → VPN & Device Management.
  4. Launch Vault3R.
Note: Sideloaded apps via AltStore require re-signing every 7 days (free Apple ID) or 365 days (paid Apple Developer account).

Features

  • Face ID / Touch ID unlock
  • PIN unlock (6-8 digits with Secure Enclave protection)
  • AutoFill extension (Safari & apps)
  • Encrypted device sync with Windows & Android
  • Secure Notes, TOTP, Vault Health
  • 11 themes (identical to Desktop & Android)

First run

Create a new vault

  1. Open Vault3R.
  2. Click New Vault (or Create Vault on Android).
  3. Enter your master password (minimum 6 characters) and confirm it.
  4. On Android/iOS: set a PIN (6-8 digits) and optionally enable biometrics.

Restore from backup

  1. On the login screen, choose Restore from backup (.vlt).
  2. Select the .vlt file.
  3. Enter the master password from when the backup was created.
Master password: There is no way to recover it. Choose one you will remember. Consider writing it down and storing it safely offline.

Trial & license

Windows — trial mode

  • 7 days free trial from first launch — full functionality.
  • After trial expiry, the app requires a license key to continue.

Activation

  1. Purchase a license at get.vault3r.pl (~$5 USD, Stellar XLM).
  2. The license key (V3R-XXXX-XXXX-XXXX-XXXX-XXXX) will be emailed to you.
  3. In the app: 🔑 Activate License → paste the key → Activate.
License details: One-time payment, lifetime, per-device. Stored in %AppData%\Vault3R\license.lic. Internet required for activation only.

Premium features

  • 3 premium themes: Premium Metal, Premium Dark, Premium Navy (with glow effects)
  • All functionality is identical between trial and licensed (except premium themes)

Android

Android is free during the open beta. Same license key works on Android for premium themes.

Desktop — Main window

The main window is your command center. It contains a sidebar with categories, a toolbar, and the password list.

Login methods

The app automatically selects the fastest unlock method (in order of preference):

MethodWhen usedDetails
TOTPIf configured6-digit code from authenticator app
PINIf set (and no TOTP)6-8 digit numeric PIN
Master PasswordAlways availableFull password (click "← Use Master Password")

Sidebar categories

  • All — every entry in the vault
  • Favorites — entries marked with ⭐
  • Custom categories — auto-generated from entry categories
  • ▲ / ▼ buttons — reorder categories (order is saved)

Password list columns

ColumnDescription
AvatarFirst letter of entry name
NameEntry title
LoginUsername / email
PasswordMasked •••••••• with 👁 (reveal 10s) and 📋 (copy 30s)
URLDomain with 🌐 link button
Category / Tags / NotesMetadata

Toolbar

ButtonAction
➕ AddAdd new password entry
✏️ EditEdit selected entry
🗑️ DeleteDelete with confirmation
⭐ FavoriteToggle favorite
🔑 LicenseActivate license key
⋯ MoreFull menu (see below)

"More" menu

Copy Password, Launch URL, Generate Password, Secure Notes, Vault Health, Settings, Import/Export, Sync Send/Receive, Backups, Change Password, Lock Now, Panic Mode, Logout.

Desktop — Password entries

Adding an entry

  1. Click ➕ Add or use the menu.
  2. Fill in the form: Name, Login/Email, Password (required). Optional: URL, Category, Tags, Notes.
  3. Use the "Gen." button to generate a strong password.
  4. Click Save.

Copying a password

  • Click the 📋 icon next to any password.
  • The password is copied to clipboard for 30 seconds, then automatically cleared.
  • The password is excluded from Windows Clipboard History (Win+V) and cloud sync.

Revealing a password

  • Click the 👁 icon — password is visible for 10 seconds, then auto-hides.

Desktop — Secure Notes

  1. Menu → Secure Notes.
  2. Left panel: list with search. Right panel: editor.
  3. Click New Note → fill title, tags, content.
  4. Click Save — note encrypted with AES-256-GCM.

Notes support searching by title, content, and tags. Each note has timestamps (Created / Updated).

Desktop — Password generator

  • Access: Menu → Generate Password or "Gen." in the entry form.
  • Length: 8–64 characters (slider).
  • Symbols: toggle "Include Symbols" on/off.
  • Strength meter: 0–100 score with description (Very Weak → Very Strong).
  • Uses cryptographically secure random number generator (CSPRNG).
  • Every generated password contains at least: 1 uppercase, 1 lowercase, 1 digit (+ 1 symbol if enabled).

Desktop — Vault Health & HIBP

Menu → Vault Health. Automatic analysis of your vault:

CheckDescription
Weak passwordsScore below 51/100 (via PasswordStrengthService)
Reused passwordsSame password used in multiple entries
Missing URLsEntries without a website URL
Breached (HIBP)Passwords found in public data breaches
HIBP privacy: Your passwords are never sent to the server. Vault3R uses k-anonymity — only the first 5 characters of the SHA-1 hash are transmitted. The full hash is compared locally.

Desktop — Settings

SectionOptions
🔒 SecurityAuto-lock timeout: OFF / 1 / 5 / 10 / 30 / 60 min
🎨 Theme11 themes (3 premium require license)
⚙️ SystemStart with Windows (autostart shortcut)
💾 BackupAuto backup on exit (max 50 files, 30-day retention)
📱 Device SyncPair devices, unpair, auto-sync toggle
🔑 PINSet/remove PIN (6-8 digits)
🔐 TOTPGenerate secret, QR code, verify, remove
ℹ️ AboutVersion info, check for updates

Desktop — System tray

Closing the window hides the app to the system tray (first time: a tooltip explains this).

Tray optionAction
OpenShow main window
LockLock the vault
PanicHide & lock immediately
LogoutReturn to login screen
ExitFully close the app (with optional backup)

Double-click the tray icon to open the app.

Desktop — Keyboard shortcuts

ShortcutAction
Ctrl+Alt+LLock Now
Ctrl+Alt+UUnlock
Ctrl+Alt+PPanic Mode (hide + lock)
EnterSubmit login / unlock form

Android — Unlock methods

MethodPriorityDetails
BiometricsHighestFingerprint or face recognition (AndroidKeyStore)
TOTPHighCode from authenticator app
PINStandard6-8 digit PIN
Master PasswordFallbackAlways available
Note: PIN and biometrics only unlock a locally stored copy of the master password. The vault is always encrypted with the master password for full desktop compatibility.

Android — Autofill service

Enable autofill

  1. Go to Android Settings → Passwords & autofill (or Security → Autofill service).
  2. Select Vault3R as your autofill provider.
  3. Login fields in apps and browsers will now show Vault3R suggestions.

Supported browsers

Chrome, Firefox, Edge, Brave, Opera, Samsung Internet, DuckDuckGo Browser.

Features

  • Inline suggestions (Android 11+) — credentials appear in the keyboard area
  • Save prompt — after manual login, Vault3R offers to save credentials
  • In-context password generator — generate and fill a strong password

Android — TOTP codes

  • Add TOTP to any entry: enter a base32 secret or scan an otpauth:// QR code.
  • Dedicated TOTP screen with all codes, formatted as XXX XXX.
  • Visual countdown (30s cycle) — tap to copy.
  • Supports SHA-1, SHA-256, SHA-512 algorithms.

Android — Quick Settings tiles

Vault3R adds a tile to Android's notification shade (swipe down from top):

  • Tap tile → opens Vault3R instantly
  • Quick access without finding the app icon

Android — Vault Health

Menu → Vault Health. Same checks as desktop:

  • Overall score: 0–100% with color coding (red / yellow / green)
  • Weak passwords, reused passwords, missing URLs

iOS — Unlock methods

After creating a vault, set up quick unlock:

  • Face ID / Touch ID: Settings → Enable Biometrics. Uses Secure Enclave to protect the master key.
  • PIN (6-8 digits): Keychain-backed with brute-force lockout after 5 failed attempts.
  • TOTP: Google Authenticator compatible 6-digit code.
Security: iOS uses the Secure Enclave for biometric authentication. The master key is never stored in plaintext — it is protected by the device's hardware security module.

iOS — AutoFill extension

Vault3R includes a Credential Provider extension for system-wide AutoFill:

  1. Go to iOS Settings → Passwords → AutoFill Passwords.
  2. Enable Vault3R as a provider.
  3. When a login form appears in Safari or any app, tap the key icon and select from your vault.
Supported: Safari, Chrome, Firefox, Edge, and all apps using ASAuthorizationController.

iOS — Device sync

Identical to Android sync. Pair with Desktop or Android via QR code, then send/receive encrypted vault snapshots through the ephemeral relay.

  • TLS certificate pinning (SPKI SHA-256) protects relay connections
  • AES-256-GCM encryption with unique pairing key per device pair
  • Push notifications when a sync is available from a paired device

Encrypted device sync

Vault3R is a local-first password manager. Sync uses an encrypted ephemeral relay — no cloud storage, no accounts, zero knowledge.

┌──────────┐ ┌──────────┐ │ Desktop │──── AES-256-GCM ────────────►│ Relay │ │ (sender) │ encrypted vault │ Server │ └──────────┘ └────┬─────┘ │ 10 min TTL │ auto-delete ┌─────────┼─────────┐ ┌────▼─────┐ ┌────▼─────┐ │ Android │ │ iOS │ │(receiver)│ │(receiver)│ └──────────┘ └──────────┘ decrypt with pairing key

How it works

  1. Pair devices (one-time): scan QR code to share a 256-bit pairing key.
  2. Send: vault is encrypted with the pairing key (AES-256-GCM) and uploaded to relay.
  3. Receive: receiver downloads and decrypts. Blob auto-deletes from relay.
  4. Data is merged, not overwritten — new entries added, existing preserved.
Security guarantees:
• Relay server only stores opaque ciphertext (cannot read content)
• Channel ID derived via HMAC-SHA256 (server can't link channel to key)
• Max 10 MB per transfer, 10 minute TTL
• Random nonce per transfer (replay protection)

Device pairing

Pair desktop ↔ Android

  1. Desktop: Settings → Device Sync → Pair New Device → QR code appears.
  2. Android: Settings → Device Sync → Scan QR Code → scan the code.
  3. Confirmation is automatic (polling up to 5 minutes).
  4. You can pair multiple devices — each gets its own key and channel.

Manage paired devices

  • View all paired devices in Settings → Device Sync.
  • Unpair individual devices or unpair all.
  • Pairing keys are protected with DPAPI (Windows) or EncryptedSharedPreferences (Android).

Import / Export

FormatImportExportEncryptedNotes
.vltVault3R native format, compatible Desktop ↔ Android
.jsonJSON with encrypted entries
.csvPlaintext! Supports Vault3R, Bitwarden, LastPass, KeePass formats

Import from another manager

  1. Export a CSV from your current password manager (Bitwarden, LastPass, KeePass, etc.).
  2. In Vault3R: Menu → Import → select the CSV file.
  3. Vault3R auto-detects the format, separator, and encoding.
  4. Choose Merge (add to existing) or Replace (overwrite).
CSV warning: CSV files contain passwords in plain text. Delete the CSV file after importing.

Backup & Restore

Auto-backup (Desktop)

  • Settings → Backup → enable Auto backup on exit.
  • Creates encrypted backup on every app close.
  • Location: %AppData%\Vault3R\Backups\
  • Retention: max 50 files, 30-day rolling window.

Manual backup

  1. Menu → Backups.
  2. Click Create Backup.
  3. Encrypted .vlt file created instantly.

Restore

  1. In Backup Manager, select a backup file.
  2. Choose restore mode:
    • Overwrite — replace current vault entirely (requires confirmation).
    • Merge — add entries from backup, keep existing ones.

Security overview

AspectImplementation
Data encryptionAES-256-GCM (authenticated encryption with associated data)
Key derivationPBKDF2-HMAC-SHA256, 200,000 iterations
File integritySHA-256 hash with constant-time verification
TOTP secret protectionDPAPI (Windows) / EncryptedSharedPreferences (Android)
PIN protectionAES-256-GCM + PBKDF2 (150,000 iterations)
Pairing key protectionDPAPI (Windows) / AndroidKeyStore
Relay encryptionAES-256-GCM with pairing key (end-to-end)
Password hashingPBKDF2-HMAC-SHA256, format: v2$pbkdf2-sha256$...
Random number generationCryptographic CSPRNG (RandomNumberGenerator)

Encryption details

Encryption versions

VersionAlgorithmIterationsPrefixStatus
v1 (legacy)AES-256-CBC + PBKDF2100,000noneDecrypt only
v2 (current)AES-256-GCM + PBKDF2200,000v2:Default
v3 (optimized)AES-256-GCM + pre-derived key200,000*v3:Optional

* v3 runs PBKDF2 once at vault open, then reuses the derived key for all operations.

v2 encryption scheme

Input: plaintext, masterPassword, contextSalt (e.g. "entry", "note") 1. salt = RandomBytes(16) 2. key = PBKDF2-HMAC-SHA256(masterPassword, salt, 200000, 32 bytes) 3. nonce = RandomBytes(12) 4. aad = UTF8(contextSalt) // Additional Authenticated Data 5. (ct, tag) = AES-256-GCM.Encrypt(key, nonce, plaintext, aad) 6. output = "v2:" + Base64(salt[16] + nonce[12] + tag[16] + ciphertext[N])

Password verifier

1. salt = RandomBytes(16) 2. hash = PBKDF2-HMAC-SHA256(password, salt, 200000, 32 bytes) 3. verifier = "v2$pbkdf2-sha256$200000$" + Base64(salt) + "$" + Base64(hash) Comparison: CryptographicOperations.FixedTimeEquals() — timing-attack resistant

Vault file format (VLTDB)

The vault is stored as a binary file with gzip compression and SHA-256 integrity verification.

OffsetSizeContent
05 bytesMagic: "VLTDB" (ASCII)
51 byteVersion: 0x01
61 byteCompression: 0x01 (gzip)
74 bytesPayload length (uint32 LE)
1132 bytesSHA-256 hash of uncompressed payload
43N bytesGzip-compressed JSON payload

Payload structure

{ "verifier": "v2$pbkdf2-sha256$200000$base64salt$base64hash", "entries": ["v2:BASE64(salt+nonce+tag+encrypted_entry_json)", ...], "notes": ["v2:BASE64(salt+nonce+tag+encrypted_note_json)", ...], "settings": { "autoBackupEnabled": true, "autoLockMinutes": 5, "categoryOrder": ["Banking", "Social", "Email"] } }

Each entry and note is encrypted individually (per-entry encryption). Corrupting one entry doesn't affect the rest.

PIN / TOTP / Biometric unlock

PIN (Desktop & Android)

ParameterValue
AlgorithmAES-256-GCM + PBKDF2-HMAC-SHA256
Iterations150,000
PIN length6-8 digits (min. 6 since v4.3.6)
Storagepin.dat (salt + nonce + tag + ciphertext)

The PIN encrypts the master password locally. Correct PIN → decrypt → master password → open vault.

TOTP unlock (Desktop)

ParameterValue
StandardRFC 6238 (TOTP), HMAC-SHA1, 6 digits, 30s
Secret protectionDPAPI (ProtectedData.Protect, CurrentUser scope)
File formatv2: version + DPAPI-wrapped secret + salt + nonce + tag + ciphertext
Clock tolerance±1 window (90 seconds total)

Biometrics (Android)

  • Hardware-backed AndroidKeyStore + BiometricPrompt
  • Master password encrypted with biometric-gated AES key
  • setUserAuthenticationRequired(true) — requires auth per operation

Brute-force protection

Exponential backoff

AttemptLockout
1–3None
45 seconds
510 seconds
620 seconds
740 seconds
8+60 seconds (max)

Persistence (since v4.3.6)

Lockout state is saved to disk (lockout.json). Restarting the app does not reset the counter. The state auto-clears after 10 minutes of cooldown.

Clipboard security

Desktop (Windows)

  • Atomic clipboard write via Win32 API (no race conditions with clipboard monitors)
  • Auto-clear after 30 seconds (only if clipboard hasn't been changed by user)
  • Excluded from Windows Clipboard History (Win+V) via ExcludeClipboardContentFromMonitorProcessing
  • Excluded from Cloud Clipboard (cross-device sync)

Android

  • ClipboardClearService (foreground service) clears after 30 seconds
  • Notification shows countdown

Architecture — System overview

┌──────────────────────────────────────────────────────────────────┐ │ Vault3R Ecosystem │ │ │ │ ┌──────────────┐ relay.php ┌──────────────────┐ │ │ │ Desktop │◄──── E2E enc ────►│ Android │ │ │ │ (WPF/.NET) │ AES-256-GCM │ (Compose) │ │ │ └──────┬───────┘ └────────┬──────────┘ │ │ │ │ │ │ │ Shared vault format: vault.vlt.db (VLTDB) │ │ │ Shared crypto: AES-256-GCM + PBKDF2-SHA256 │ │ │ │ │ │ ┌──────┴─────────────────────────────────────┴──────────┐ │ │ │ Backend (PHP) │ │ │ │ • Licenses (generate / consume / verify) │ │ │ │ • Relay (ephemeral vault transfer, 10 min TTL) │ │ │ │ • Payments (Stellar XLM via Horizon API) │ │ │ │ • Trial (file-based, per-device) │ │ │ └────────────────────────────────────────────────────────┘ │ └──────────────────────────────────────────────────────────────────┘
ComponentTechnologyVersion
Desktop (Windows)C# / WPF / .NET 84.3.6
AndroidKotlin / Jetpack Compose / Material 34.3.4
Backend (Web/API)PHP 7.4+ / MySQL

Architecture — Desktop services

ServicePurpose
CryptoServiceCore cryptography: AES-GCM, PBKDF2, password generation, batch encryption
DatabaseServiceVault management: CRUD, merge, import/export, VLTDB format (~2750 lines)
DevicePairingServiceMulti-device pairing: QR, DPAPI-protected keys, channel IDs
VaultRelayServiceEncrypted vault transfer via relay (E2E AES-256-GCM)
ClipboardServiceSecure clipboard: Win32 atomic write, auto-clear, history exclusion
PinServicePIN quick-unlock (AES-GCM + PBKDF2 150k)
TotpLockServiceTOTP unlock with DPAPI-protected secret (v2 format)
TotpServiceTOTP code generator (RFC 6238, SHA-1/256/512)
LockoutPersistenceServiceBrute-force state persistence to disk
AutoBackupServiceAuto-backup on exit (max 50, 30-day retention)
LicenseServiceTrial (7 days) + license key activation via API
PasswordStrengthServicePassword scoring (0-100) with strength categories
ThemeService11 themes (8 free + 3 premium with glow effects)
CsvImportExportServiceCSV import: Vault3R, Bitwarden, LastPass, KeePass, generic
StartupServiceWindows autostart (shortcut in shell:startup)
DialogServiceUnified dialog system (Info/Warning/Error/Confirm)

Architecture — Android modules

PackagePurpose
crypto/AES-256-GCM, PBKDF2, legacy CBC compatibility
vault/VaultRepository: data layer with caching
vlt/VLTDB binary format (read/write)
autofill/AutofillService (~1100 lines): Chrome, Firefox, Edge, Brave, etc.
unlock/BiometricHelper, PinManager, TotpUnlockManager
relay/DevicePairingManager, RelayClient, RelayEncryption (E2E)
ui/screens/10 Compose screens: passwords, notes, settings, health, sync, TOTP
ui/theme/Material 3 + 11 themes (identical to Desktop)
tile/Quick Settings tile service
update/Auto-update checker via latest.json

Architecture — iOS modules

ModulePurpose
CryptoServiceAES-256-GCM, PBKDF2-SHA256 (200k iterations) via CryptoKit
VaultRepositoryData layer: VLTDB read/write, entry caching
UnlockStorageKeychain-backed PIN/biometric/TOTP state
VaultRelayServiceE2E encrypted sync via ephemeral relay + TLS cert pinning
AutoFillExtensionASCredentialProviderViewController for Safari & apps
PinnedURLSessionSPKI SHA-256 TLS certificate pinning
AppUpdateServiceAuto-update checker via latest-ios.json
ThemeManager11 themes with glow effects (identical to other platforms)

Architecture — Backend API

EndpointMethodPurpose
/api/consume-license.phpPOSTOne-time license activation (status 0→1, device binding)
/api/verify-license.phpPOSTVerify active license + device match
/api/generate-license.phpPOSTGenerate key after payment confirmation
/api/check-payment.phpPOSTCheck Stellar XLM payment via Horizon API
/api/relay.phpPOSTEphemeral vault storage (E2E encrypted, 10 min TTL, 10 MB max)
/api/trial-check.phpPOSTPer-device trial status (file-based)
/api/get-price.phpGETCached XLM/USD price (CoinGecko proxy)

File locations

Windows

FilePath
Vault database%AppData%\Vault3R\vault.vlt.db
PIN data%AppData%\Vault3R\pin.dat
TOTP config%AppData%\Vault3R\totp_unlock.dat
License%AppData%\Vault3R\license.lic
Theme%AppData%\Vault3R\theme.json
Lockout state%AppData%\Vault3R\lockout.json
Auto-backups%AppData%\Vault3R\Backups\
Pairing keys%AppData%\Vault3R\paired_devices.json

Android

FileLocation
Vault databaseApp-private internal storage: files/vault.vlt.db
PreferencesEncryptedSharedPreferences (AES-256-GCM)
Biometric keyAndroidKeyStore (hardware-backed)

Troubleshooting

ProblemSolution
"Too many failed attempts"Wait for lockout to expire (5–60s). Restarting the app does not reset the counter (since v4.3.6).
Windows SmartScreen warningClick "More info" → "Run anyway". This is expected with self-signed certificates.
.NET 8 not installedDownload from dotnet.microsoft.com.
Vault won't openFile may be corrupted. Restore from a backup (%AppData%\Vault3R\Backups\).
Forgot master passwordNo recovery possible. Restore from a backup you can unlock, or create a new vault.
CSV import failsEnsure the CSV uses a supported format: Vault3R, Bitwarden, LastPass, or KeePass.
Autofill not working (Android)Check Settings → Passwords & autofill → verify Vault3R is selected as the autofill provider.
Biometric not workingEnsure you have a fingerprint/face registered in Android system settings.
Sync timeoutBoth devices need internet access. Relay blob expires after 10 minutes.
Forgot PINUse "Master Password" to unlock, then reset the PIN in Settings.
App installed, "Install blocked"Android Settings → Security → allow installing unknown apps for your browser.

FAQ

Q: Where is the vault stored?
Windows: %AppData%\Vault3R\vault.vlt.db. Android: app-private internal storage.
Q: Can I use the same vault on desktop and phone?
Yes — use Encrypted Device Sync (recommended) or manually transfer a .vlt backup file.
Q: Does the relay server see my passwords?
No. The vault is encrypted end-to-end with your pairing key before upload. The relay only handles opaque ciphertext.
Q: Can I restore a backup on another computer?
Yes — export a .vlt file and import it on the other machine with the correct master password.
Q: Does logout create a backup?
No — auto-backups only run on real app exit (Exit from tray or close with exit flag).
Q: I clicked "X" and the app still runs. Is that normal?
Yes — the window minimizes to the system tray. Use tray menu → Exit to fully close.
Q: Is my data sent to any server?
Only during sync (encrypted, ephemeral, zero-knowledge) and license verification. Passwords, entries, and notes never leave your device unencrypted.
Q: What happens if I lose my phone?
Your vault is encrypted. Without the master password (or PIN/biometric), data cannot be accessed. The vault file is also in app-private storage (allowBackup=false).
Q: How is the HIBP check private?
Vault3R uses k-anonymity. Only the first 5 hex characters of the SHA-1 hash are sent to the API. The full comparison happens locally on your device.