Privacy Policy

What Lorepedia does

Lorepedia provides token thesis context, narrative search, and related market or social information. The Chrome extension adds an optional overlay on supported trading pages and includes an optional Wallet Verify flow.

Data Lorepedia may process

• Supported page URLs checked locally to determine whether the extension should run.
• Supported page content needed to detect the current token and show Lorepedia context.
• Public wallet addresses shown on supported portfolio pages when a user uses Wallet Verify.
• Wallet selections a user explicitly chooses to verify with Lorepedia.
• A Lore User ID generated for an extension installation so Lorepedia can manage access, account status, product eligibility, subscriptions, and abuse prevention.
• If a user separately enables ad measurement, aggregate sponsored-content impression and click events. These events contain only the event type, placement, and ad ID; they do not include wallet addresses, token addresses, page URLs, or the Lore User ID.
• Basic technical logs such as request timing, service errors, or similar operational records generated by the website or API.

How Wallet Verify works

Wallet Verify is optional. After the user accepts the in-extension notice, the extension may read public wallet addresses displayed on supported pages. The extension only submits the wallets the user selects for verification.

Lorepedia aims to send only the minimum information needed for the feature. Wallet Verify is designed around the selected wallet addresses, the supported source, the Lore User ID, and related operational metadata rather than full portfolio page URLs.

Supported Wallet Verify pages currently include URLs that begin with gmgn.ai/portfolio, trade.padre.gg/wallets, and axiom.trade/portfolio.

Why Lorepedia processes this data

• To provide the extension overlay and token context on supported pages.
• To verify selected wallets when the user chooses Wallet Verify.
• To map wallets to a Lore User ID for access control, account operations, user management, feature eligibility, and subscription handling.
• To maintain service reliability, investigate abuse, and debug operational issues.
• To measure aggregate sponsored-content performance only when the user enables the separate ad-measurement setting.

Data sharing and storage

Wallet verification submissions and extension installation records may be stored in Lorepedia systems, including PostgreSQL-backed application storage used for account and verification management.

Chrome Web Store disclosures should match the real product behavior. If the extension uses install registration or wallet verification storage, those flows count as collection and storage.

User choice

• The extension requires an in-product notice and acceptance before enabling the related extension flow.
• Wallet Verify is optional and only sends wallets the user selects.
• Sponsored content can be turned off in the extension settings. Ad measurement is off by default and can be enabled or disabled separately.
• Users can stop using the extension by disabling or uninstalling it in the browser.

Contact

For product or privacy questions, use the official Lorepedia links below.