Privacy Policy

Controller: the operator of TokenLume (tokenlume.com)

Contact: [email protected] (privacy requests) or [email protected] (general).

Depending on how you use TokenLume, we may process:

• Account data — email address and credentials managed through Better Auth (password hashes are handled by the auth library; we do not store plaintext passwords).
• Preferences — settings such as display currency and notification preferences stored in your account.
• Saved wallets — Cardano addresses you choose to save for read-only portfolio views (public blockchain identifiers, not private keys).
• Watchlists & alerts — tokens, pools, or conditions you configure, plus delivery settings for notifications.
• Notifications — records of in-app and email notifications we send when enabled.
• Contact form — name, email, topic, message, and optional reference you submit (stored as ContactRequest records).
• Security events — limited audit entries in SecurityEvent for security-relevant actions (for example sign-in adjacent activity). These may include IP address and user agent where needed to investigate abuse; we do not store passwords, session tokens, or wallet signing material in these logs.
• Product usage events — aggregated first-party telemetry in ProductEvent (for example page views of public product areas, signup funnel steps, wallet profiler opens, watchlist/alert creation). Events may optionally link to your account id when you are signed in. We do not store passwords, session tokens, or private keys in these records. We do not use third-party advertising analytics cookies for this purpose.

Public blockchain data — balances, transactions, and token metadata retrieved for addresses you view or save are already public on the Cardano ledger. Processing that data to show analytics is generally not personal data about you unless it can be linked to your identity (for example when you save a wallet to your logged-in account).

• Provide the service (account, watchlists, alerts, saved wallets) — performance of a contract or steps at your request (Art. 6(1)(b) GDPR).
• Security & abuse prevention (SecurityEvent, rate limits on contact submissions) — legitimate interests (Art. 6(1)(f) GDPR).
• Respond to contact & privacy requests — legitimate interests / legal obligation where applicable (Art. 6(1)(f) or (c) GDPR).
• Transactional email (password reset, alerts, notifications when enabled) — performance of contract / legitimate interests (Art. 6(1)(b) or (f) GDPR).
• Product improvement (first-party ProductEvent aggregates) — legitimate interests (Art. 6(1)(f) GDPR). We do not sell this data or use it for third-party advertising profiles.

We do not use your data for third-party advertising profiles. We do not set analytics or marketing cookies; product telemetry is first-party event posts without a separate analytics cookie.

We use service providers that process data on our instructions, including:

• Hosting — application, PostgreSQL database, and Redis cache infrastructure used to run TokenLume.
• Resend (when configured) — outbound email delivery for contact notifications, account email, and alerts. Mail is sent from operational aliases on tokenlume.com (for example [email protected], [email protected]); inbound contact mail is handled separately and mailbox credentials are not stored in the application.
• Blockfrost / Koios — read-only Cardano network queries for wallet and on-chain data (typically wallet addresses or asset identifiers you request).
• Market data providers — aggregated pricing, liquidity, and reference data shown in markets and intelligence views (no account credentials are shared).

Public blockchain indexers receive only the queries needed to fetch ledger data. They do not receive your account password.

We retain account-related data while your account is active and for a limited period afterward where needed for security, backups, or legal obligations. Contact requests are kept as long as needed to handle your inquiry and maintain an audit trail. Security events are retained for a limited security window and then deleted or aggregated. ProductEvent telemetry is retained for a limited product-analytics window (default ~90 days) and pruned by the worker. You may request deletion subject to exceptions (for example ongoing disputes or legal holds).

Under GDPR you may have the right to access, rectify, erase, restrict, object, and port certain personal data, and to withdraw consent where processing is consent-based. You may lodge a complaint with Agencia Española de Protección de Datos (AEPD).

You can delete your account yourself under Settings (Delete account). You may also email [email protected] or use Contact (topic: Privacy).

Some processors may be located outside the European Economic Area. Where required, we use appropriate safeguards (such as Standard Contractual Clauses) for those transfers.

TokenLume is not directed at children under 16. We do not knowingly collect personal data from children.

We may update this policy when our product or legal requirements change. The "Last updated" date at the top reflects the current version.