Sandw0rm.
beta

Terms and Conditions

1. Acceptance of Terms

By accessing or using Sandworm, you agree to comply with these Terms and Conditions. If you do not agree, do not use the service. These terms may be updated periodically, and continued use constitutes acceptance of any changes.

2. Description of Service

Sandworm is an open-source analytics tool that enables users to query blockchain data (including Sui, Etherium, EVM chains,and potentially other blockchains) using an SQL-like language. It also provides a public gist for sharing and discovering queries.

3. Use of the Service

  • Sandworm is for informational purposes only and does not guarantee data accuracy.
  • Users must not use the tool for illegal activities, including hacking, unauthorized scraping, or fraudulent transactions.
  • Queries shared in the public gist must not contain malicious code, copyrighted material, or personally identifiable information.

4. Open Source License and Contributions

Sandworm is open-source, and contributions are subject to its respective license (e.g., MIT, GPL). The platform is provided "as is," and contributors bear no liability for third-party modifications or misuse.

5. User-Generated Content

By submitting queries to the public gist, users grant Sandworm a non-exclusive, royalty-free right to display and distribute them. Sandworm reserves the right to remove or moderate content violating these terms.

6. Disclaimers and Limitations of Liability

  • Sandworm does not provide financial, investment, or legal advice.
  • The team is not responsible for losses resulting from reliance on queried data.
  • Blockchain data may be incomplete, inaccurate, or outdated.

7. Authentication and Security

Sandworm uses Firebase for authentication, which may involve third-party social logins. Users are responsible for securing their accounts and should not share login credentials.

Privacy Policy

1. Information We Collect

  • Authentication Data: When users log in via Firebase (including Google, GitHub, or other social logins), authentication tokens are stored.
  • Usage Data: We collect anonymous usage analytics to improve the platform.
  • Cookies: Cookies are used for authentication, session management, and performance tracking.

2. How We Use Your Data

Authentication data is used solely for managing user access. Usage analytics help optimize the tool but do not personally identify users. Public queries shared in the gist are visible to all users.

3. Data Sharing and Security

We do not sell or share personal data with third parties. We take reasonable measures to secure user data but cannot guarantee complete security.

4. Third-Party Services

Firebase authentication follows Google’s Privacy Policy. Queries may interact with third-party APIs (e.g., blockchain explorers), which have their own privacy policies.

5. Blockchain and Public Data

Queries return publicly available blockchain data; we do not control blockchain records. Users should not store sensitive data in public queries.

6. Your Choices

  • Users can manage authentication settings via Firebase.
  • Clearing cookies may impact authentication and performance.