Senvra 1.4

When you save a new Access Key, Senvra can convert that copy into a PIN-protected form. The same local tool can protect a plaintext Access Key you saved earlier. The six-digit PIN is separate from the password that opens the space, and protecting a copy does not change the original Access Key.

The conversion happens locally. PBKDF2-HMAC-SHA256 stretches the PIN, HKDF derives key-masking material, and XOR key masking protects the Access Key copy you store. The protected copy does not need a Senvra account or server to be created or opened.

The protected copy does not include an authentication tag or fixed secret marker that would let someone confirm PIN guesses from the file alone. Every six-digit PIN produces a plausible candidate key; only the space can accept the correct result.

This does not make a short PIN unlimited protection. Store the protected Access Key copy and its PIN in separate places.

Opening a protected copy is also local. Senvra removes the mask with the entered PIN and passes the resulting candidate Access Key to the space. A wrong PIN cannot be confirmed from the saved copy alone; the target space is what accepts or rejects the result.

An Access Key can now be shown and saved as a QR image. Another device can scan it with the camera, or read it from an image selected from Photos. A PIN-protected Access Key still asks for its separate PIN after scanning.

QR transfer reduces the need to copy and paste a long key. It does not make the image public or disposable: anyone who can scan or save that image can copy the Access Key. Senvra shows this warning before saving the image to Photos.

The complete path is explicit: display the key, optionally protect its saved copy, open the QR view, then save only after confirming the image risk. On the receiving device, scan with the camera or choose an existing image from Photos. If the QR contains a protected copy, the separate PIN is still required before the space can be opened.

Guided forms now cover identity, medical, insurance, warranty, and private-link records. Titles are searchable, filters surface due or incomplete records, and related attachments stay with the record.

Each type keeps its own structured fields instead of forcing every important detail into a generic note. Review status, dates, missing information, and attachments can be inspected from one workbench without moving the underlying material to a hosted records service.

Private links are stored as data; Senvra does not fetch previews. Dates organize the record but do not schedule notifications.

The release audit covered 691 unit tests and 127 automated UI tests across iPhone and iPad layouts. Upgrade verification also opened existing public and private data with the previous password and Access Key, then compared identifiers, lengths, and SHA-256 hashes after the in-place update.

Long-running integrity, backup, and restore work continues to expose progress and a persistent result. Committed data stays ahead of background indexing, temporary cleanup, and other maintenance that can be safely retried after interruption.