METENGINE

Privacy Policy for Met Extension

Effective Date: January 31, 2025

Last Updated: January 31, 2025

Version: 2.0

1. Introduction

MetEngine and its affiliates (together, “MetEngine”, “we”, “us” or “our”) respect your privacy and are committed to protecting your personal data. This privacy policy explains how we collect, store, and use information when you use the MetEngine browser extension.

This privacy policy is incorporated by reference into our Terms of Use. By using our services, you agree to the terms of this privacy policy. If you do not agree, please do not use our services.

Table of Contents

  1. 1. Introduction
  2. 2. Important Information and Who We Are
  3. 3. Summary of Data Collection
  4. 4. What We Collect
  5. 5. What We Do NOT Collect
  6. 6. How We Use Your Data
  7. 7. Data Transmission
  8. 8. Data Storage and Security
  9. 9. Data Sharing
  10. 10. Your Rights
  11. 11. Children's Privacy
  12. 12. International Transfers
  13. 13. Changes to This Policy
  14. 14. Contact
  15. 15. Purposes and Legal Basis for Processing
  16. 16. Your Legal Rights
  17. 17. Cookies and Similar Technologies
  18. 18. Third-Party Links
  19. 19. Additional Info for U.S. Residents
  20. 20. Additional Info for EU/UK Residents
  21. 21. Glossary
  22. 22. Changelog

2. Important Information and Who We Are

Purpose. This policy explains how MetEngine collects and processes your data through your use of the MetEngine browser extension.

Controller. MetEngine Labs is the controller responsible for your personal data.

Contact Details:

Changes to this policy. We may modify this policy at any time. Changes will be posted on this page with an updated date. Continued use after changes constitutes acceptance.

3. Summary of Data Collection

MetEngine is a trading analytics extension. We collect the minimum data needed to operate. This policy explains exactly what we collect, why, and how it's protected.

Data TypeCollectedPurposeSent to Server
Invite codeYesLicense activationYes
Device fingerprintYesLicense binding (anti-piracy)Yes (hashed)
Pool/market addresses you viewYesFetch analytics for that pool/marketYes
Wallet addresses displayed on platformsYesFetch smart wallet scoresYes
Your wallet addressNo
Private keysNo
Browsing historyNo
Personal informationNo

4. What We Collect

4.1 License Authentication Data

DataWhat It IsWhy We Collect It
Invite CodeYour license key (e.g., BETA-XXXX-XXXX-XXXX)Verify your subscription
Device FingerprintHashed combination of browser/device propertiesBind license to one device to prevent unauthorized sharing

About Device Fingerprinting:

We generate a SHA-256 hash from these properties:

  • User agent string
  • Screen resolution and color depth
  • Timezone offset
  • Hardware concurrency (CPU cores)
  • Device memory
  • Canvas rendering characteristics
  • WebGL renderer information

Why we use fingerprinting: To ensure one license = one device. This prevents license sharing and piracy. The fingerprint is:

  • One-way hashed (cannot be reversed to identify you)
  • Never shared with third parties
  • Only compared against stored hashes for license verification
  • Not used for tracking across websites

4.2 Platform Data (Functional Collection)

When you use MetEngine on supported platforms, we collect identifiers needed to fetch analytics:

On Meteora (meteora.ag):

DataExampleWhy
Pool address5yuefgb...Fetch LP positions and analytics for that specific pool

On Polymarket (polymarket.com):

DataExampleWhy
Market condition ID0x1234...Fetch smart money positions for that market
Wallet addresses displayed on page0xabcd...Fetch wallet scores for profiles you view

On Hyperliquid (hyperliquid.xyz):

DataExampleWhy
Asset symbolBTC, ETHFetch trading pressure data for that asset

Important clarifications:

  • We only collect identifiers for content you actively view
  • We do NOT collect your personal wallet address unless you explicitly view your own profile
  • We do NOT monitor pages in the background
  • We do NOT collect data from websites outside the three supported platforms

4.3 Session Data

DataStoragePurpose
JWT authentication tokenLocal browser storageMaintain logged-in state
Cached API responsesLocal browser storageReduce network requests, improve performance

5. What We Do NOT Collect

We explicitly do not collect:

  • Your cryptocurrency wallet addresses (unless you view your own profile)
  • Private keys or seed phrases
  • Transaction signing requests
  • Passwords or credentials for any platform
  • Browsing history outside supported platforms
  • Keystrokes, mouse movements, or clicks
  • Location data (GPS or IP-based)
  • Personal identification (name, email, phone)
  • Financial data (bank accounts, credit cards)
  • Communication content (emails, messages)

6. How We Use Your Data

Use CaseData UsedLegal Basis
License verificationInvite code + device fingerprintContract fulfillment
Deliver analyticsPool/market/wallet identifiersContract fulfillment
Prevent piracyDevice fingerprintLegitimate interest
Improve performanceCached responsesLegitimate interest

We do NOT use your data for:

  • Advertising or marketing
  • Selling to third parties
  • Building user profiles for targeting
  • Credit assessment or lending decisions
  • Any purpose unrelated to delivering analytics

7. Data Transmission

7.1 Our Servers

All data is transmitted to MetEngine servers over encrypted HTTPS connections:

EndpointData SentPurpose
extension.metengine.xyzInvite code, device fingerprint, session tokenAuthentication
api.metengine.xyzPool addresses, market IDsFetch analytics data
dca.metengine.xyzToken addressesFetch pressure data

7.2 Third-Party APIs

We also communicate with platform APIs to enrich data:

ServiceData SentPurpose
gamma-api.polymarket.comMarket IDsFetch public market metadata
clob.polymarket.comMarket IDs, wallet addressesFetch public order book data

Note: These are official platform APIs. We only request publicly available data.

7.3 What We Do NOT Send

  • Your browsing activity outside supported platforms
  • Your cryptocurrency wallet private keys
  • Any data to advertising networks
  • Any data to data brokers

8. Data Storage and Security

8.1 Local Storage (Your Browser)

DataRetentionSecurity
Session tokensUntil sign out or expirationChrome Storage API (encrypted at rest)
Cached responses24 hours maximumAutomatically purged
User preferencesUntil uninstallChrome Storage API

8.2 Server Storage (Our Infrastructure)

DataRetentionSecurity
License recordsSubscription duration + 90 daysEncrypted database
Device fingerprintsSubscription duration + 90 daysSHA-256 hashed, not reversible
API request logs30 days rollingNo personally identifiable information

8.3 Security Measures

  • All transmissions use TLS 1.3 encryption
  • Device fingerprints are one-way hashed before transmission
  • No plain-text storage of sensitive data
  • Regular security reviews
  • Principle of least privilege for server access

9. Data Sharing

We Share Data With:

RecipientDataPurpose
Our backend infrastructureHashed device ID, license codeAuthentication only
Platform APIs (Polymarket)Public identifiersEnrich analytics data

We Do NOT Share Data With:

  • Advertisers
  • Data brokers
  • Analytics companies
  • Marketing platforms
  • Any third party for commercial purposes

Legal Disclosure

We may disclose data if required by:

  • Valid court order
  • Law enforcement request with proper legal process
  • To protect our legal rights

We will notify you before disclosure when legally permitted.

10. Your Rights

10.1 Access Your Data

View what the extension stores locally:

  1. Open Chrome DevTools (F12)
  2. Go to Application → Storage → Extension Storage
  3. Select the MetEngine extension

10.2 Delete Your Data

Local data: Sign out from the extension popup, or uninstall the extension.

Server data: Email hello@metengine.xyz with subject “Data Deletion Request” including your invite code. We process requests within 30 days.

10.3 Opt Out

The extension only collects data necessary for core functionality. To opt out:

  • Disable or uninstall the extension
  • Contact us to revoke your license

11. Children's Privacy

MetEngine is not intended for users under 18. We do not knowingly collect data from minors. Contact us if you believe a minor has used our service.

12. International Transfers

Our servers may be located outside your country. By using MetEngine, you consent to data transfer to jurisdictions where data protection laws may differ from your own.

13. Changes to This Policy

We will:

  1. Update this page with a new “Last Updated” date
  2. Notify users via the extension popup for material changes
  3. Maintain a changelog of significant updates

Continued use after changes constitutes acceptance.

14. Contact

17. Cookies and Similar Technologies

The MetEngine browser extension does not use cookies. We use Chrome's Storage API to store session tokens and cached data locally on your device.

18. Third-Party Links

Our extension may display links to third-party websites (such as Solana explorers or trading platforms). We are not responsible for the privacy practices of these third parties. We encourage you to read their privacy policies.

19. Additional Information for U.S. Residents

If you reside in California or another U.S. state with privacy laws, you may have additional rights. We do not “sell” or “share” personal information as defined under these laws. We do not use personal information for “targeted advertising.”

20. Additional Information for EU/UK Residents

If you reside in the EU or UK, you have additional rights under GDPR/UK GDPR. The legal bases for our processing are set out in Section 15. You have the right to lodge a complaint with your local data protection authority.

21. Glossary

TermDefinition
Personal dataAny information relating to an identified or identifiable person
ControllerThe entity that determines the purposes and means of processing
Legitimate interestOur business interest in operating and improving our services, balanced against your rights
Device fingerprintA hash of device characteristics used to identify a specific device

22. Changelog

VersionDateChanges
2.0Jan 31, 2025Complete rewrite with explicit data collection, GDPR structure, legal bases
1.0Jan 15, 2025Initial policy

MetEngine Labs

Transparent analytics for informed trading.