Connected App Data Extractor & Forensic Privacy Console for Google Drive
Third-party apps connected to your Google account routinely write files to your Drive — sync states, diagnostic dumps, database backups, cached tokens, and settings — without any clear visibility in standard Google Drive.
DriveVault is a single-file, zero-backend client-side forensics engine that connects directly to Google Drive via OAuth 2.0. It catalogs hidden app-written files, inspects metadata and payloads, flags security identifiers, monitors live modifications, and packages evidence files — all wrapped in an ultra-sleek, cyberpunk glassmorphic dashboard.
| Feature | Description |
|---|---|
| 🔍 Connected Apps Auditor | Clusters and attributes files by their writing application, complete with permission flags, data footprint, last modified date, and automated risk scoring. |
| 📁 File Explorer & Filtering | Tree-structured cluster explorer with real-time in-cluster search and instant MIME type filter tags (JSON, TXT, IMG, BIN). |
| 🧪 Payload Inspector | Inspect file properties, raw JSON metadata, and embedded Monaco Editor views. Binary files feature a windowed hex dump viewer. |
| 🛡️ Vulnerability Diagnostics | Automatically scans metadata and text payloads against sensitive keywords (passwords, tokens, sessions, private keys, device IDs, coordinates). |
| 🤖 AI Forensics & Local Heuristics | Claude-powered forensic analysis explaining payload purpose, writing app, and privacy concerns (falls back to an offline heuristic analyzer if proxy is unset). |
| 📊 Interactive Analytics | Real-time visual metrics: storage by app, file counts, MIME type breakdown, top largest payloads, and modification timelines. |
| 📦 Bulk Evidence Exports | Export full ZIP packages (files + per-file JSON metadata), spreadsheet-ready CSV catalogs, or combined JSON forensics reports. |
| 🔴 Live Diagnostics Watcher | Real-time background watcher polling Drive for live creations and modifications every 30 seconds with instant delta badges. |
| 🔒 Zero-Backend Privacy | Scoped OAuth tokens exist strictly in active JavaScript heap memory. Nothing is ever written to disks, cookies, or remote databases. |
Google enforces strict app-level isolation across its Drive infrastructure:
| Capability | Supported | Technical Mechanism |
|---|---|---|
| Files saved to your main Drive | ✅ | Scanned via drive.readonly + metadata attributes |
| App permission signals & history | ✅ | Introspected via drive.activity.readonly & token introspection |
DriveVault's own appDataFolder |
✅ | Isolated read/write via drive.appdata |
Other apps' private appDataFolder |
❌ | Hard-sandboxed by Google — no API or workaround exists |
ℹ️ DriveVault operates with full transparency: Google prevents any third-party app from reading another application's private
appDataFolder. DriveVault audits all public files, permission records, and activity signals.
git clone https://github.com/satiricalguru/DriveVault.git
cd DriveVaultBecause DriveVault is a self-contained, zero-build web app, serve it with any static web server:
# Python 3
python3 -m http.server 5173
# Or with Node.js npx
npx serve -l 5173 .- Visit http://localhost:5173 in your browser.
- Click Configuration Setup (or the gear icon).
- Paste your Google OAuth 2.0 Client ID and click Save Configuration. Credentials are saved in your browser's
localStorage. - Click Connect Google Account to begin scanning!
👉 For full step-by-step instructions on creating a Google Cloud OAuth Client ID and enabling Drive APIs, see the docs/SETUP.md guide.
| Scope | Purpose |
|---|---|
drive.metadata.readonly |
Read metadata of all files (including app-associated items) |
drive.readonly |
Download and inspect file content locally |
drive.activity.readonly |
Surface automated application activity and actors |
drive.appdata |
Manage DriveVault's own isolated test storage |
userinfo.profile |
Display user display name and profile picture |
userinfo.email |
Display connected account address |
- Runtime: Single-file static web application (zero bundler required)
- UI Framework: React 18 (Babel standalone)
- Styling: Tailwind CSS (CDN) + Custom Glassmorphism Theme
- Editor & Code Viewer: Monaco Editor (
vs-dark) - Visual Analytics: Chart.js
- Archiving: JSZip
- Auth: Google Identity Services (GSI) Token Client Flow
- Typography: Space Grotesk + JetBrains Mono
DriveVault/
├── index.html # Complete standalone web application
├── assets/
│ └── logo.svg # DriveVault branding logo
├── docs/
│ └── SETUP.md # Detailed Google Cloud OAuth setup guide
├── CONTRIBUTING.md # Guidelines for contributing
├── SECURITY.md # Responsible security disclosure policy
├── LICENSE # MIT License
└── README.md
Contributions are welcome! Please see CONTRIBUTING.md for guidelines. Remember: DriveVault is strictly a no-backend, zero-build single-file architecture.
This project is licensed under the MIT License.