Your data, your control

Readylytics stores everything locally on your device—no cloud account, no data leaving your phone. But that also means you’re responsible for backing up your data. The app makes this easy with encrypted, password-protected backups, flexible retention settings, and full control over what syncs from Health Connect.


Local encrypted backup

Your supported local records, calculated summaries, and preferences can be backed up to a local folder on your device, encrypted with AES-256 (bank-grade security).

Find it: Settings → Data & Backup → Local Backup

What gets backed up:

Not included: Raw sleep-stage rows, raw step records, weight, body fat, blood pressure, and oxygen-saturation records are not exported by the current local backup format. A backup does not modify or replace the original data managed by Health Connect.

Cache and diagnostics are never backed up. The app’s internal cache — including the diagnostic-log, crash-report, and logcat-capture export directories — is excluded from both Android auto-backup and device-to-device transfer (data_extraction_rules.xml / full_backup_content.xml). These plaintext exports are transient on-device diagnostics; they are pruned on startup and never included in a Readylytics backup.

Create a backup

  1. Set a backup directory — Choose a folder where the app can store backups (e.g., Documents/Readylytics Backups).
  2. Set a password (optional but recommended) — Encrypts the backup file. Without a password, the file is stored unencrypted.
  3. Tap “Create Backup Now” — The app creates a timestamped backup file.

Automate backups

Don’t want to remember to back up manually?

Find it: Settings → Data & Backup → Backup Schedule

The app will create backups in the background. Each backup is timestamped, so you can keep multiple versions.

Restore from backup

Lost your settings after reinstalling the app? Restore them in seconds.

  1. Go to: Settings → Data & Backup → Available Backups
  2. Select the backup you want to restore.
  3. Enter the backup password (if you set one).
  4. Tap “Restore” — The supported local records, summaries, and preferences are restored; the app may restart to apply changes.

Backup manifests v5, v6, and v7 all restore into the current v7 entities. When restoring a v5 or v6 backup, Readylytics normalizes legacy heart-rate and HRV composite IDs to (sourceRecordId, timestampMs) so records retain their current stable identity.

Changing your backup password

If you want to change the backup password, the app will automatically re-encrypt all existing backups with the new password the next time it backs up. No manual steps needed.


Data retention

The app can store unlimited historical health data, but if you’re concerned about device storage, you can set an automatic data retention window.

Find it: Settings → Data & Backup → Data Retention

Retention window (180–1095 days, default 365):

Retention disabled:

Why use retention:

Why keep it off:

If you enable retention after years of data, the oldest entries will be pruned. This is irreversible, so consider a backup first.


Health Connect sync

Readylytics pulls sleep, heart rate, HRV, and workout data from Health Connect (Android’s native health data hub). You control when and how often this sync happens.

Find it: Settings → Data & Backup → Health Connect Sync

Sync on app open

Controls whether the app syncs with Health Connect automatically when you launch it.

Background sync

For continuous health monitoring, enable background syncing.

Find it: Settings → Data & Backup → Background Sync

Manually resync Health Connect data

Missed data? Reconnected a device? Force a full resync.

Find it: Settings → Data & Backup → Resync Health Connect Button

Tap to trigger a fresh sync from Health Connect. This pulls the latest data across all connected devices.


Device filtering

If you own multiple health trackers or watches (e.g., Apple Watch, Oura Ring, Garmin), they might all sync to Health Connect. You can filter which device feeds each data type.

Find it: Settings → Data Sources → Device Selection

Data categories:

For each category, choose:

Example use case: Your smartwatch’s HRV is noisy, but your fitness tracker’s is clean. Filter sleep vitals to use the fitness tracker only.


Full historical resync

Every Health Connect has a data history. By default, Readylytics pulls recent data. But if you change how data is filtered, enable a data type you previously disabled, or suspect data loss, you can trigger a full historical resync.

Find it: Settings → Data & Backup → Resync All Historical Data

What it does:

Why use it:

When it runs:

Impact:


Health Connect permissions

Readylytics asks for permission to read specific data types. You grant or revoke permissions in Android’s Health Connect app, not in Readylytics.

Requested permissions:

Permission revocation: If you revoke access:

  1. Open Health Connect (Android system app)
  2. Tap AppsReadylyticsManage permissions
  3. Toggle off any data type

Readylytics will detect missing permissions and show a recovery flow directing you back to Health Connect.


What about my raw data?

Health Connect is your single source of truth. Readylytics only reads from it; it never writes. Your original data is always safe in Health Connect, even if something goes wrong in Readylytics.

To see or export your raw data:

  1. Open the Health Connect app.
  2. Browse each data category (Sleep, Heart Rate, Workouts, etc.).
  3. Tap any entry to see raw values.
  4. Use Health Connect’s export features to download CSV or other formats.

Readylytics adds interpretive layers (scores, baselines, trends), but the raw numbers come straight from your devices via Health Connect.


Cloud backup and device transfer exclusions

To safeguard your sensitive health information and ensure the cryptographic security of the local database (which uses Android Keystore keys that cannot be transferred off the device), Readylytics explicitly excludes all database files, preferences, encryption keys, and local backup files from Android Auto Backup and OEM device-to-device transfers.

Manual Release Verification Checklist

During release validation, the following checks should be performed:

  1. Bmgr Verification: Run adb shell bmgr backupnow app.readylytics.health followed by inspecting the backup sets to confirm that no databases, DataStores, Tink keysets, or backup ZIPs are included in the backup data.
  2. OEM D2D Transfer: Manually verify that local app data is not transferred during a device migration, and that a fresh install correctly prompts the user to restore from their manually-exported local backup file.

Privacy at a glance

For full details, see our Privacy Policy.


← Back to home