infolio Encrypted Vaults: Manage Passwords, Keys, IDs, and Private Records with Boundaries
Learn how infolio encrypted vaults separate passwords, API keys, IDs, accounts, contracts, and private documents from ordinary knowledge-base pages.
Give passwords, keys, IDs, and private documents a separate entry point.
Use device authentication and AES-256-GCM encrypted sync as added boundaries.
Keep everyday knowledge and sensitive records clearly separated.
Sensitive records should not live in normal notes
Personal knowledge bases often become a mix of notes, accounts, contracts, keys, IDs, and private records. That is convenient, but it weakens the boundary around sensitive information.
infolio encrypted vaults create a separate layer: normal documents for knowledge work, vaults for records that need more protection.
Useful for personal users and indie developers
Indie developers often need to remember test accounts, API-key locations, certificate paths, and cloud configuration. Personal life also creates IDs, contracts, warranties, memberships, and family records.
These records may not need enterprise secret governance, but they should not be scattered across chats, screenshots, and regular notes.
- Centralize test accounts and development keys.
- Keep IDs, contracts, and private family records separate.
- Avoid turning normal documents into a catch-all secret store.
AES-256-GCM encryption for sync data and attachments
infolio encrypts synced structured data on-device with AES-256-GCM and authenticates metadata such as the resource path. Official cloud and custom sync sources receive authenticated ciphertext rather than readable content.
Attachments use chunked AES-256-GCM encryption, which supports streaming and per-chunk integrity checks for larger files. Sync data and attachments use separately derived keys for their distinct purposes.
- Synced structured data uses authenticated AES-256-GCM encryption.
- Attachments are encrypted and verified in chunks.
- Encryption occurs on the device before content is uploaded to a sync source.
Not a replacement for enterprise secret management
infolio vaults are for sensitive records inside a personal knowledge base. They should not replace enterprise secret rotation, team approvals, or production credential governance.
A practical boundary is: personal sensitive records in vaults, production team secrets in dedicated systems.
FAQ
Can infolio vaults replace a password manager?
They are useful for personal passwords, keys, and private records inside your knowledge base, but they are not a replacement for enterprise password management, team permissions, or automatic rotation.
How should sensitive records be handled when syncing?
Put sensitive records into encrypted vaults before syncing. Synced structured data and attachments are encrypted on-device with AES-256-GCM; the sync source moves and stores ciphertext.