
Last updated: March 2026
Draft — This document is subject to legal review and may be updated. Please check back for the final version.
We collect the following types of data:
We do not sell, rent, or share your personal data with third parties for marketing purposes.
We use the following third-party services to operate LiquiLab:
Your data is stored in a PostgreSQL database hosted on Railway in the EU region. Data is encrypted in transit (TLS/HTTPS) and at rest. We apply the principle of data minimization — we only store what is necessary to provide the Service.
LiquiLab uses the following cookies:
| Cookie | Purpose | Duration |
|---|---|---|
| next-auth.session-token | Authentication session | 30 days |
| ll_test_session | Beta tester session | Session |
| ll_pass | Placeholder access | Session |
| ll_role | Role override (development only) | Session |
We do not use third-party tracking cookies or advertising cookies.
Under the General Data Protection Regulation (GDPR), you have the right to:
To exercise any of these rights, contact us at privacy@liquilab.io. We will respond within 30 days.
We retain your account data for as long as your account is active. Upon account deletion or request, we will remove your personal data within 30 days, except where retention is required by law (e.g., billing records). Anonymized, aggregated analytics data may be retained indefinitely as it cannot be linked back to individuals.
Wallet addresses and liquidity positions are publicly visible on the Flare Network blockchain. LiquiLab aggregates and presents this publicly available on-chain data — we do not create or reveal private information. The public nature of blockchain data means that your wallet activity is visible to anyone with access to the blockchain, regardless of whether you use LiquiLab.
We implement the following security measures to protect your data:
For privacy-related inquiries: privacy@liquilab.io
For general support: support@liquilab.io
We may update this Privacy Policy from time to time. Material changes will be communicated via email to registered users. The "Last updated" date at the top of this page indicates when the policy was last revised. Continued use of the Service after changes constitutes acceptance of the revised policy.