Backup & Restore

Quran Memorization keeps your data local by default. Google Drive is used only for backup and portability, so daily memorization remains available offline. This guide explains how to connect, create a backup, and restore safely.

Local data remains the source of truth

Normal use — memorizing, recall tests, review, and reinforcement — reads and writes local data. You do not need a network connection for these tasks. Backup is a separate concern for recovery and moving to another device.

Connecting Google Drive

When you choose to back up, the app asks to connect to your Google Drive. Access is limited to the app-specific folder, so backups remain scoped to the app and do not mix with other Drive files.

You can disconnect and reconnect the account later without losing local data. Disconnecting stops future backups but does not delete what is already stored locally.

Creating a backup

A backup captures a coherent snapshot of your local data in a portable format. The app validates the snapshot structure and size before uploading, so an unexpected or incomplete payload is not stored as a backup.

Backup scheduling depends on network availability and is performed periodically when conditions allow. You can also create a backup manually before making significant changes.

Note: A successful backup reflects the state at the time it was created. Later memorization progress will be newer than that backup until the next one is made.

Restore preview

When you choose to restore, the app first shows a preview that summarizes what would change. Review this summary carefully. It is the main place to confirm that you have selected the intended backup, especially if multiple backups exist.

The preview step does not yet change local data. It exists so you can decide with clear information.

Restore confirmation

After the preview, restoring requires explicit confirmation. This is intentional because restoring replaces the current local data.

Important: Restoring replaces the current local data with the selected backup. Any progress recorded locally after that backup was created will be overwritten if you confirm. Before restoring, make sure you have reviewed the preview and that overwriting local progress is what you want.

If additional memorization was recorded after the preview was created, the app will not silently discard that newer progress. Resolve the conflict in favor of the data you want to keep before confirming.

How restoring works

Once confirmed, the app replaces the local dataset transactionally. Either the full replacement succeeds or the previous dataset remains intact. Related records are restored together so ordering and references stay coherent.

Damaged or structurally invalid backups are rejected with an explanatory message and will not produce a partially restored dataset.

After restoring

Verify that the expected Journeys, Chunks, and progress are present after the restore completes. If you were moving to a new device, you can continue memorization from where the backup left off and create a fresh backup once you are satisfied.

Disconnect and reconnect

You can disconnect Google Drive when you no longer want the app to access the backup folder. Local data remains on the device. Reconnecting restores the ability to create and discover backups.

Automatic backup behavior resumes under the same network-constrained conditions after reconnecting and restarting the app where applicable.

Where to go next

• Return to Getting Started for the overall orientation.
• See Start Memorizing for the daily memorization flow.

If you restore on a new device, consider creating a new backup after confirming everything looks correct.