Chrome Data Analysis

Chrome Data Analysis

/app/data/chrome_data/ — Chromium Profile Persistence

Executive Summary

The chrome_data/ directory serves as the persistent user data directory for Chromium instances launched by browser_guard.py. This profile stores cookies, browsing history, extension state, and cached data across browser sessions, enabling stateful browser automation.

1. Directory Structure

chrome_data/
├── Default/                        # Default Chrome profile
│   ├── Cache/                      # HTTP response cache
│   ├── Code Cache/                 # V8 bytecode cache
│   ├── Cookies                     # SQLite cookies database
│   ├── Cookies-journal             # SQLite journal file
│   ├── DawnWebGPUCache/            # WebGPU shader cache
│   ├── Extension Scripts/          # Extension JavaScript
│   ├── Extension State/            # Extension storage
│   ├── Favicons                    # Favicon database
│   ├── GPUCache/                   # GPU shader cache
│   ├── History                     # Browsing history
│   ├── History-journal             # History journal
│   ├── Local Storage/              # DOM localStorage
│   ├── Login Data                  # Saved passwords
│   ├── Network Action Predictor    # Prefetch data
│   ├── Preferences                 # Chrome preferences JSON
│   ├── Safe Browsing Cookies       # Security cookies
│   ├── Secure Preferences          # Encrypted preferences
│   ├── Session Storage/            # DOM sessionStorage
│   ├── SharedDictionary/           # Compression dictionaries
│   ├── Shortcuts                   # URL shortcuts
│   ├── Site Characteristics Database/  # Site behavior data
│   ├── Top Sites                   # New tab page tiles
│   ├── Trust Tokens                # Privacy tokens
│   ├── Web Data                    # Autofill data
│   ├── WebStorage/                 # Storage quotas
│   └── shared_proto_db/            # Protocol buffer DB
├── first_party_sets.db             # First-party sets
├── GraphiteDawnCache/              # Graphite cache
├── Local State                     # Chrome state JSON
└── Variations                      # Field trial data

2. Data Categories

2.1 Authentication Data

Encryption: Login Data uses Chrome's encryption (OS keyring on Linux).

2.2 Browsing History

2.3 Storage Data

2.4 Extension Data

2.5 Cache Data

2.6 Configuration Data

3. Operational Role

3.1 Persistence Across Sessions

# In browser_guard.py
launch_options = {
    "user_data_dir": "/app/data/chrome_data",
    # ...
}

Benefits:

• Cookies survive browser restarts
• Login sessions maintained
• Extension settings preserved
• Cache improves subsequent loads
• History available for navigation

3.2 Launch Sequence

1. browser_guard.py starts
2. Checks X11 display
3. Launches Chromium with --user-data-dir=/app/data/chrome_data
4. Chrome reads existing profile
5. Session state restored

4. Security Analysis

4.1 Sensitive Data Exposure

4.2 Multi-Tenant Considerations

Risk: In multi-user environments, shared profile exposes data.

Recommendation: Create isolated profiles per session:

import tempfile
import shutil

# Create temp profile
profile_dir = tempfile.mkdtemp(prefix="chrome_profile_")

# Use isolated profile
launch_options["user_data_dir"] = profile_dir

# Cleanup after session
shutil.rmtree(profile_dir)

4.3 Encryption Status

5. Inter-Module Relationships

chrome_data/
    ├── browser_guard.py (reads/writes)
    │   └── Playwright/CDP
    ├── pdf-viewer/ (extension state)
    │   └── PDF.js settings
    └── logs/ (correlated with History)

6. Maintenance

6.1 Cleanup Operations

# Clear cache
rm -rf /app/data/chrome_data/Default/Cache/*

# Clear cookies (logout all sessions)
rm /app/data/chrome_data/Default/Cookies

# Clear history
rm /app/data/chrome_data/Default/History

# Full reset
rm -rf /app/data/chrome_data/*

6.2 Size Monitoring

7. Troubleshooting

7.1 Common Issues

Document Version: 1.0 Analysis Date: 2026-02-02