[P1] Implement encrypted backup export and restore #32

New issue

Closed

opened 2026-07-18 00:03:00 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-07-18 00:03:00 +00:00

(Migrated from github.com)

Goal

Back up or migrate Local Recall data without creating plaintext archives.

Requirements

Export encrypted records, encrypted indexes or rebuild metadata, schema versions, and a sanitized manifest.
Never include active key material by default.
Optional GPG recipient encryption for portable exports.
Restore into an empty or explicitly selected profile with integrity and compatibility checks.
Detect duplicate records and conflicting schema versions.
Support export by time range as well as full backup.

Acceptance criteria

Archive inspection reveals no captured text, titles, thumbnails, prompts, or credentials.
Restore reproduces searchable records after the required key is made available.
Corrupted, truncated, or wrong-recipient archives fail safely.
Export and restore operations are audited without logging archive content.

Depends on

## Goal Back up or migrate Local Recall data without creating plaintext archives. ## Requirements - Export encrypted records, encrypted indexes or rebuild metadata, schema versions, and a sanitized manifest. - Never include active key material by default. - Optional GPG recipient encryption for portable exports. - Restore into an empty or explicitly selected profile with integrity and compatibility checks. - Detect duplicate records and conflicting schema versions. - Support export by time range as well as full backup. ## Acceptance criteria - Archive inspection reveals no captured text, titles, thumbnails, prompts, or credentials. - Restore reproduces searchable records after the required key is made available. - Corrupted, truncated, or wrong-recipient archives fail safely. - Export and restore operations are audited without logging archive content. ## Depends on - #10 - #11 - #31