Google Drive Cloud Backup & Sync Guide

How local SQLite persistence and sandboxed Google Drive appDataFolder JSON sync protect your watchlist and paper portfolio without intermediate app servers.

12.1 How Private Cloud Backup Works

Most trading apps upload your holdings and watchlists to vendor servers. Kuni, US-Market Forecaster flips that pattern: everything writes to a local SQLite database on your phone first, and cloud sync goes straight from your Android device to your personal Google Drive over HTTPS.

When you opt in to Google Sign-In, the app requests only the restricted drive.appdata scope (https://www.googleapis.com/auth/drive.appdata). That permission creates a single hidden appDataFolder container holding an encrypted JSON snapshot of your portfolio trades, watchlist tickers, custom card order, and theme preferences. Google Drive enforces strict sandbox isolation at the API level, so the app cannot list, read, modify, or delete any personal Drive folders, Docs, Sheets, or Photos. No Kuni Online server ever sits in the middle.

12.2 Restoring Data on a New Phone

Moving to a new Android phone or running the app across a phone and tablet restores your workspace automatically:

1. Install the App

Download Kuni, US-Market Forecaster from Google Play on the second device.

2. Sign In with the Same Google Account

Tap Continue with Google and select the account that owns your Drive backup.

3. Hydrate Local SQLite

During the startup check, the client pulls your latest JSON snapshot from appDataFolder and rebuilds local SQLite rows for your simulated portfolio, trade ledger, watchlists, and display preferences.

12.3 Using the App Offline

Because SQLite acts as the primary ledger, losing reception on a flight or subway never blocks paper trading or watchlist edits. Every fill and star toggle commits locally right away, previously cached charts remain viewable alongside the stale-data warning banner, and the Drive JSON snapshot quietly syncs as soon as your network reconnects.