Privacy Policy

This policy covers the JuiceBot Everywhere browser extension and its extension-specific JuiceBot API services. It supplements any other JuiceBot terms or privacy notices that apply to your JuiceBot account.

JuiceBot Everywhere may collect or process:

• Account information: Telegram account ID, username, display name, extension session details, and a generated device identifier.
• Authentication information: a one-time link code, short-lived access tokens, a rotating refresh token, device fingerprint, and optional local extension lock information. Private keys and seed phrases are never requested or stored by the extension.
• Financial and trade information: wallet addresses and labels, balances, positions, token and chain selections, quote and trade amounts, buy or sell direction, trade status, transaction hashes, explorer links, and Juice points awarded when available.
• Website and browsing context: publicly rendered page content is processed to detect token contract addresses, stock symbols, and chain context. The detected identifier and the current page origin and path may be sent to JuiceBot to resolve the asset. Full page text, complete browsing history, form entries, passwords, and private messages are not sent to JuiceBot.
• Security and usage information: hashed IP address, user-agent string, hashed device fingerprint, request timestamps, extension actions, cap events, failed authentication events, API errors, endpoint status, and abuse-prevention signals.
• Local preferences: token detection settings, enabled sites, buy presets, widget position, lock state, pending trade state, and a short-lived adapter configuration cache stored in Chrome local storage.

Page access is limited to supported HTTPS sites and to other HTTPS sites that you explicitly enable. The extension processes rendered content only to provide its token-detection and trading features.

• Link and authenticate the extension to your JuiceBot account.
• Detect and resolve assets shown on enabled pages.
• Display wallet balances and positions, prepare quotes, submit trades, and report trade status.
• Enforce server-side spending caps and send Telegram security and trade notifications.
• Prevent abuse, investigate security events, troubleshoot errors, and maintain service reliability.
• Comply with applicable law and enforce JuiceBot terms.

Information is shared with JuiceBot backend services and service providers only as needed to operate JuiceBot, host infrastructure, authenticate accounts, resolve assets, deliver Telegram notifications, route trades, submit blockchain transactions, provide customer support, and monitor reliability and security.

JuiceBot does not sell extension user data, transfer it to data brokers, use it for personalized advertising, or use it to determine creditworthiness or lending eligibility.

The use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Information received from Chrome extension APIs is used only to provide or improve the extension's disclosed, user-facing functionality.

• One-time link codes expire after a short period and are single-use.
• Access tokens expire quickly. Refresh tokens rotate and are invalidated when the extension session is revoked.
• Extension trade and security logs are retained for at least 90 days for fraud prevention, security, and trade support, and may be kept longer where required by law or an active investigation.
• Locally cached adapter configuration expires after its configured cache period.

You can disable detection globally or for individual sites, remove optional site access, and revoke the extension session from the extension popup or the Telegram /extension menu. Revocation invalidates the server-side session and its refresh tokens. You can remove locally stored extension data by uninstalling the extension or clearing its data in Chrome.

Extension API calls use HTTPS. JuiceBot uses short-lived access tokens, refresh-token rotation, hashed device and IP identifiers, idempotency keys, server-side spending caps, and Telegram notifications to protect extension sessions and trade activity. Wallet signing and trade execution remain within JuiceBot's server-side wallet system.

We may update this policy when the extension, our data practices, or legal requirements change. The latest version will remain available at this URL with its effective date shown above.

For privacy questions or extension support, contact JuiceBot through the official JuiceBot Telegram channel.