Field Engineer Setup Guide — SecureSync

Pre-Installation Checks

Before you begin

Client PC is running Windows 10 or Windows 11 (64-bit) PC has active internet connection (broadband or mobile hotspot, stable) Client has a Google account (personal or business) — verify login before starting Client's Google Drive has sufficient free storage for anticipated folder sizes You have the client-specific install package (built with scripts/package_client.py) Client plan has been confirmed and activated in JYOTVIRA systems before you arrive Security scan: confirm install package does NOT contain config.json, tokens, logs, or .sync files

Security Rules — Do Not Violate

Non-negotiable rules

✗Never commit config.json, tokens, logs, or .sync files to any git branch

✗No universal master PIN — every client has their own restore PIN

✗Never store PINs in plaintext — only cryptographic hash in config.json

✗Restore only to a safe folder — never overwrite originals without client confirmation

✗Use the test folder only for testing — never test on client's real data folders

Installation Steps

Step-by-step setup

Copy install package to client PC

Copy the client-specific install package (built with scripts/package_client.py) to a USB drive or shared transfer location. Never email the package. Extract to a local path (e.g., C:\SecureSync\).

Run the interactive setup wizard

Open Command Prompt as Administrator. Navigate to the extracted folder. Run: DriveMonitor.exe --ai. The wizard will prompt for Google Drive authorization and folder selection.

Google Drive authorization

The wizard will open a browser for Google OAuth. Client logs in with their Google account. Confirm the app is authorized. Token is stored locally in config.json on the client PC — never in the install package.

Configure monitored folders

During the wizard, select the folders to monitor (Documents, Desktop, Tally directory, client-specific folders). Ask the client which folders contain their most important data. Start conservative — you can add folders later.

Set the restore PIN

Run: DriveMonitor.exe --setup-restore-pin. The client chooses their own PIN (6+ characters recommended). The PIN is stored as a PBKDF2-SHA256 hash in config.json. Do not choose the PIN yourself — the client must set it. Do not record the PIN anywhere.

Verify first backup

Run: DriveMonitor.exe --health. Confirm the monitoring agent is running and the first sync has completed. Check Google Drive to confirm a file from a monitored folder appears in the SecureSync backup folder.

Register Windows startup

Confirm SecureSync is registered to start with Windows. The wizard handles this automatically. Verify in Task Manager → Startup Apps that DriveMonitor appears and is enabled.

Mobile app setup

Help the client install the SecureSync mobile app. Log in with their JYOTVIRA credentials (not their Google credentials). Verify the app shows the correct device name and last-sync time.

Client handover

Walk the client through: (a) what the app shows, (b) how to know if backup is working, (c) what to do if something looks wrong (call/WhatsApp JYOTVIRA). Leave the handover checklist below completed and on file.

SecureSync Setup Guide