Release 225 · Browser-local portability

தனிப்பட்ட தரவு காப்பு மையம்

Personal Data Backup & Restore Centre

Export or restore only the registered reading, accessibility and listening datasets held in this browser. Import always requires validation, preview and explicit confirmation.

0registered datasets

0datasets with data

0local records

Loading the local data registry…

1. Export a local backup

Choose the datasets to place in a downloadable JSON file. Cache contents and published page bodies are never exported.

Datasets to export

SHA-256 appears here after export when supported.

2. Validate and restore

Select a previously exported OmSaravanaBhava JSON backup. No local data changes until you review the preview and press Apply.

Backup JSON file

No backup loaded.

Validated datasets to restore

Restore mode

No restore has been applied.

Review before backup

The Personal Library provides a read-only view of valid local reading, notes, accessibility and listening records.

Open My Library

Collections are now portable

Release 227 registers devotional collections as the sixth bounded browser-local backup dataset.

Open Collections

Practice plans are portable

Release 228 registers bounded devotional practice plans as the seventh browser-local backup dataset.

Open Practice Planner

Mantra sessions export separately

Phase 16 mantra history is intentionally not merged into the older seven-dataset backup schema. The Mantra Practice exports its own bounded session metadata without sacred text and provides a page-level clear control.

Open Mantra Practice

Daily Darshan exports separately

Phase 17 daily-practice history is not silently merged into the older seven-dataset backup schema. The Daily Murugan Darshan exports bounded completion metadata without sacred text or personal notes and includes its own clear control.

Open Daily Darshan

Data and safety boundary

Only seven explicitly registered local datasets are supported: reading list, reading progress, reading notes, accessibility preferences, audio listening history, devotional collections and devotional practice plans.
Unknown datasets and invalid or duplicate records are ignored during validation.
Selected devotional text, published page bodies, offline cache contents, credentials and unrelated browser-storage keys are excluded.
Merge uses each dataset’s stable identifier and newest valid timestamp. Accessibility preferences are replaced as one bounded object.
No upload, cloud synchronization, analytics, server account or collaborative service is used.
Phase 16 mantra session metadata uses a separate export schema and is not silently included in this older backup format.
Phase 17 daily-practice completion metadata also uses a separate export schema and is not silently included in this older backup format.
A successful import is local operational evidence, not production certification.