01
What We Collect
- Screenshots of your current tab — captured only when you click to log an asset
- The URL and title of the page you are on, and the output URLs the page exposes — for tool detection and evidence records
- Your text input — prompts and creative notes you type into the log form
- File uploads — AI-generated images, video, or audio you upload to the extension
- Your Clerk authentication token — JWT, stored in browser local storage
- For node-based tools such as ComfyUI, the generation request you submit (workflow, seed, model, and parameters) — held locally in your browser until you choose to log it
- Your review decisions — Approve, Flag, or Reject, and any reason you give
- Timestamp and tool name associated with each logged session
- The extension version number, sent once when the extension is installed
02
How We Use This Data
- Tool detection — we analyze the URL to identify which AI tool you are using and pre-fill the log form
- Evidence logging — your asset metadata and screenshots become part of your tamper-evident evidence package
- Attestation — you manually attest to authorship level and creative decisions via the dashboard
- Export — your data is packaged into a ZIP containing a structured timeline, attestations, and a cryptographic proof anchored via OpenTimestamps
- Storage — we store your data in Supabase (PostgreSQL) and Backblaze B2 (file storage)
- Retention — your data persists until you delete your account or request removal
03
Who We Share Your Data With
- Backblaze B2 — your files (screenshots, assets) are uploaded to Backblaze for durable, encrypted storage
- Supabase — your project, asset, and attestation metadata is stored in a Supabase PostgreSQL database
- Clerk — your authentication token is validated by Clerk's identity service
- No third parties — we do not sell, trade, or share your data with advertisers or analytics platforms
04
Security & Compliance
- All data in transit is encrypted with TLS (HTTPS)
- At-rest encryption is provided by Backblaze B2 and Supabase
- Your authentication token is stored in browser local storage — not accessible to third-party scripts
- The extension has no permission to read your passwords, emails, or other sensitive browser data
- The extension does not collect your browsing history. It reads pages and requests only on the supported AI tool sites listed in our Chrome Web Store listing, and nothing leaves your browser until you log an entry
- We use this data only to provide evidence logging. We do not use or transfer it for advertising, for creditworthiness or lending decisions, or for any purpose unrelated to the extension's single purpose
