Privacy policy

Information the extension handles

• Chart identifiers and scan settings. On supported GMGN token charts, the extension reads the chain and public token address from the current page URL and sends those identifiers, together with your minimum historical market-cap threshold, to the research backend. These identifiers reveal which supported token charts you investigate. The extension does not send the full page URL, unrelated URL parameters or your browser-wide history.
• Access credentials. Requests to the backend include the shared private-group access token bundled with the extension. This credential authorizes the research service; it is not your GMGN password, a wallet secret or a personal login.
• Connection information. The hosting service necessarily processes your IP address and standard request metadata to deliver HTTPS responses and limit abuse. Routine HTTPS access logging is disabled. Operational error or security logs may contain IP addresses and connection details. The extension does not request GPS location.
• Local preferences. Your chosen threshold, panel position and collapsed state are saved in the browser's local extension storage. The threshold is also sent with scans. Panel position and collapsed state stay in the browser.
• Public blockchain research. The backend retrieves and caches public token, wallet, transfer, liquidity-pool and bridge records, including reported creators and historical market-cap peaks. These records can concern third-party wallets and are not a statement about the extension user's holdings or identity.

The extension does not connect to your wallet, request private keys or recovery phrases, sign transactions, place trades, or collect payment-card information. It does not read saved passwords, cookies, emails, private messages, clipboard contents or unrelated tabs. There is no advertising or third-party analytics SDK in the extension.

How information is used

Chart identifiers and settings are used to investigate the selected token, display relevant research and revalidate cached results when you visit a chart or request a refresh. Access credentials, connection information and provider-level request counters are used to authenticate access, deliver the service, prevent abuse and enforce request budgets.

The shared cache lets group members reuse research about the same public wallets and tokens. Scan results are not stored under individual browser accounts. They may be returned to other authorized group members researching the same tokens. The service does not maintain an account-based list of each member's chart visits.

Service providers and sharing

The backend runs on DigitalOcean. It queries GMGN, Mobula and LI.FI for relevant public records. Relay may also be queried when that integration is configured. Providers receive the public chain, token, wallet or transaction identifiers needed for their queries, the backend's network information and any required provider authentication. Provider credentials stay on the backend.

Provider requests are made by the backend; it does not forward the extension user's IP address or group access token to these research APIs. If token images are available, the browser may load them from GMGN's image service, which receives the normal connection information for that image request. Images use a no-referrer setting.

Independent providers apply their own privacy and retention practices. The backend does not send them your browser-wide history, private wallet secrets or GMGN login credentials.

We do not sell user data. We limit use of information to providing and supporting the extension's disclosed research functionality and necessary service security. We do not use or transfer it for advertising, unrelated profiling, creditworthiness or lending decisions. Information may also be disclosed where legally required or necessary to address abuse or security threats. Our use and transfer of user data follow the Chrome Web Store Limited Use requirements.

Storage and retention

Preferences remain locally until you clear extension data or remove the extension. Backend research uses a persistent shared cache. Scan snapshots are eligible for pruning after 30 days without a newer save, or when the cache exceeds 2,000 scan keys. Provider responses are eligible for pruning after 30 days without use and may be removed earlier to manage cache size. Pruning runs at service startup and when completed scans are saved. Refreshed or reused public research can remain longer.

Two rotating local database backups may retain earlier cache entries until those backups are replaced. Provider-level monthly quota counters and service configuration are stored separately. Operational/security log retention follows the host's log rotation and maintenance settings; we do not promise a fixed deletion interval for those logs. Independent research providers have their own retention periods.

HTTPS protects information in transit. Access to the research API is restricted by the group credential. Shared cache files and backups are protected by host access controls; the application does not separately encrypt them at rest.

Your choices and privacy requests

You can disable the extension to stop its chart investigations, clear its local data, or remove it. Removing the extension does not remove shared backend research or records already held by independent providers. Public blockchain transactions cannot be erased from their underlying networks.

For privacy questions or requests about information under the publisher's control, contact the publisher through the support/contact details on the woodland.family Chrome Web Store listing. If you received a private build, contact the group administrator who supplied it. Identify the relevant public token or transaction when useful; never send passwords, private keys, recovery phrases or API credentials. There is no individual-account deletion tool because the current service uses a shared group credential and public research cache.

Changes and scope

This policy describes the current extension and backend. Any material change to data handling will be reflected here with an updated effective date, and additional disclosure or consent will be provided when required. Feedback you choose to send separately through Telegram or the Chrome Web Store is handled through those services and is not collected from browser pages by the extension.