Help

API keys are used in browser memory by default. Optionally, they can be persisted in IndexedDB when you explicitly enable "Store API key persistently". This is convenient but not fully secure on shared or untrusted devices.

Known Risks

• Browser extensions with broad permissions can access page memory
• XSS vulnerabilities (if any exist) could expose keys
• Physical access to your device allows memory inspection via DevTools
• Shared computers: your session may persist if not properly closed

Recommendations

• Create a separate API key specifically for this tool
• Set spending limits at your provider
• Use a dedicated browser profile with minimal extensions
• For sensitive documents: use Ollama locally (no API key needed)

If you run coOCR/HTR locally (by cloning the repository), you can configure API keys to load automatically.

Step 1: Clone the Repository

git clone https://github.com/DigitalHumanitiesCraft/co-ocr-htr.git
cd co-ocr-htr/docs

Step 2: Create Local Config File

cp config.local.example.js config.local.js

Step 3: Add Your API Keys

Edit config.local.js and fill in your keys:

export const LOCAL_CONFIG = {
    apiKeys: {
        gemini: 'YOUR_GEMINI_KEY_HERE',
        openai: 'YOUR_OPENAI_KEY_HERE',
        anthropic: 'YOUR_ANTHROPIC_KEY_HERE'
    },
    // Optional: set default provider
    defaultProvider: 'gemini'
};

Step 4: Start a Local Server

ES modules require a server. Use any of these:

# Python 3
python -m http.server 8000

# Node.js (npx)
npx serve

# PHP
php -S localhost:8000

Then open http://localhost:8000 in your browser.