Privacy Policy

Effective date: February 22, 2026 · Last updated: March 1, 2026

Ghast AI ("we", "our", or "the Extension") is a browser extension that provides an AI assistant for Web3 activities. This policy explains what data Ghast AI collects, how it is used, and how it is protected.

1. Data We Collect

1.1 Google Account (Optional)

If you choose to sign in with Google, we request:

• Email address — for account identification
• Display name and profile picture — for personalization

Your Google access token is used only for the initial authentication exchange and is never persisted to disk. Only a session token is stored locally in your browser.

1.2 Wallet Data

When you create or import a wallet:

• Wallet address (public) — stored locally for display and transaction purposes
• Private key — encrypted with AES-256-GCM using a password-derived key (PBKDF2, 600,000 iterations) and stored locally. Never transmitted, logged, or accessible to any remote server.
• Recovery phrase (if applicable) — encrypted with the same method and stored locally

An automatic lock mechanism clears the decrypted private key from memory after a configurable inactivity timeout (default: 10 minutes).

1.3 Conversation & Memory Data

Ghast AI maintains several memory files to personalize your experience:

These files are stored in your browser's local storage. If you configure 0G decentralized storage, they are also persisted to the 0G Storage KV network, identified by your wallet address. You can view, edit, and delete these files at any time.

1.4 Usage Metrics (Optional)

If you configure a backend connection, anonymous usage metrics may be synced:

• Model name used, input/output token counts
• Tool names invoked (e.g., "browser_navigate", "check_balance")
• Timestamps

Not included: conversation content, messages, personal data, or wallet balances. Backend sync is entirely optional and disabled by default.

1.5 Web Page Context

When you browse supported Web3 sites (block explorers, DeFi protocols), the Extension's content script may extract:

• Contract addresses, transaction hashes, and on-chain data displayed on the page
• DeFi metrics (APY, TVL, volume) from supported protocols
• Page titles and sanitized URLs

URL parameters that may contain sensitive data (tokens, API keys, passwords, session IDs) are automatically stripped before processing. You can disable this by setting Capture Mode to "off" in the Extension settings.

1.6 Browser Automation

When the AI uses browser automation tools, it operates in a dedicated managed tab and captures:

• Semantic page structure (text content, interactive elements) — up to 8,000 characters per snapshot
• Scroll position and viewport dimensions

Full HTML source, screenshots, and raw page data are not captured. Browser automation only activates for sites where you have granted host permissions.

2. How We Use Your Data

• AI Conversations: Your conversation history and memory files are used as context for the AI model to provide relevant, personalized responses.
• Transaction Signing: Your decrypted private key is used locally to sign transactions you explicitly approve. Transactions are simulated before execution and require your confirmation.
• Scheduled Tasks: Heartbeat and cron tasks use your configured checklists and prompts to perform periodic AI evaluations.
• Notifications: Browser notifications are used to alert you about heartbeat findings, task completions, and transaction results.

3. Third-Party Services

3.1 0G Compute Network

AI inference requests (system prompt + conversation context + tool definitions) are sent to the 0G decentralized compute network. Requests are routed through the 0G proxy endpoint and processed by decentralized compute nodes. We do not control or store data on these nodes.

3.2 0G Storage KV (Optional)

Memory files can be persisted to the 0G decentralized storage network, identified by your wallet's stream ID. Data on 0G Storage is accessible to anyone with your stream ID. Do not store sensitive personal information in memory files if you enable 0G sync.

3.3 Telegram (Optional)

If you configure Telegram integration, messages are sent directly to the Telegram Bot API using your provided bot token. We do not intermediate or store these messages.

3.4 Google APIs

Used solely for OAuth2 authentication. We request only userinfo.email and userinfo.profile scopes.

3.5 Companion App (Optional)

The Extension can communicate with a locally installed companion desktop application ("Companion") that you install separately on your machine. The Companion expands the Extension's capabilities beyond the browser sandbox.

Data exchanged with the Companion:

• Configuration data — URL, access token, and version (via Chrome Native Messaging for auto-discovery)
• Shell commands — When you ask the AI to run commands on your machine, the command text and working directory are sent to the Companion for execution. Command output is returned to the Extension.
• MCP tool calls — When MCP tool servers are configured, tool names and arguments are sent to the Companion, which routes them to the appropriate MCP server. Results are returned to the Extension.
• Code agent prompts — When you use AI code agents (Claude Code, Codex), the task prompt and working directory are sent to the Companion, which spawns the agent locally. Agent output events (text, tool calls, status) stream back to the Extension.
• Approval requests — High-risk commands may require your approval. Approval metadata is exchanged between the Extension and Companion.

Security:

• All Companion communication is loopback only (localhost:41591) — no data leaves your machine.
• Every request requires a Bearer token for authentication.
• The Companion supports workspace-scoped permissions to restrict command execution to designated directories.
• Code agents and shell commands run with your local user permissions, not elevated privileges.

3.6 Web Search APIs (Optional)

When the AI performs web searches, queries are sent to Brave Search or DuckDuckGo. Search queries originate from your conversation context.

3.7 GitHub (Skill Repository)

Skill definitions are fetched from the public Ghast skill repository on GitHub. No personal data is transmitted; only skill metadata and definitions are downloaded.

4. Data Storage & Security

• Local-first: All data is stored in your browser's local extension storage (chrome.storage.local). Uninstalling the Extension deletes all local data.
• Encryption: Private keys and recovery phrases are encrypted with AES-256-GCM. The encryption key is derived from your password using PBKDF2 with 600,000 iterations and SHA-256.
• No centralized database: We do not operate servers that store your conversations, wallet data, or personal information.
• Content Security Policy: The Extension enforces a strict CSP that prevents code injection and limits network access to declared origins.
• No remote code execution: The Extension does not use eval(), Function(), or dynamically load remote scripts.

5. Data Sharing

We do not sell, rent, or share your personal data with third parties. Data is only transmitted to:

• 0G Compute nodes (for AI inference) — only conversation context, no private keys
• 0G Storage KV (if enabled) — only memory files you choose to sync
• Google APIs (if signed in) — only for authentication
• Telegram API (if configured) — only messages you send/receive
• Your configured backend (if any) — only anonymous usage metrics
• Local Companion (if installed) — commands and tool calls stay on localhost

6. Data Retention

• Local data: Persists until you delete it or uninstall the Extension.
• 0G Storage: Persists on the decentralized network per 0G's retention policies. Deletion requires overwriting with empty content.
• Google session: Session token expires after logout or is invalidated by the backend.
• Companion data: Command outputs and code agent logs are ephemeral and cleared when the Companion process exits. Configuration persists in ~/.trapezohe/companion.json.

7. Your Rights & Controls

• View all data: Memory files are visible and editable in the Extension's Memory tab.
• Delete data: You can delete individual memory files, clear all conversations, or uninstall the Extension to remove all local data.
• Disable features: Capture Mode, backend sync, Telegram, heartbeat, 0G storage sync, and Companion can each be independently disabled.
• Export data: Memory files can be viewed and copied as plaintext.
• Revoke Google access: Sign out from the Extension settings or revoke access from your Google Account permissions.
• Companion permissions: You can set workspace-scoped restrictions in the Companion's configuration to limit file system access.

8. Children's Privacy

Ghast AI is not intended for use by children under 13. We do not knowingly collect personal information from children.

9. Changes to This Policy

We may update this privacy policy from time to time. Changes will be reflected in the "Last updated" date above. Continued use of the Extension after changes constitutes acceptance of the updated policy.

10. Contact

For privacy-related questions or concerns, please open an issue on our GitHub repository or contact us at [email protected].