SignalDesk Privacy Policy

Last updated: March 13, 2026

This Privacy Policy explains how SignalDesk ("SignalDesk," "we," "us," or "our") collects, uses, stores, and shares information when you use the SignalDesk website and application (the "Service").

By using the Service, you acknowledge this Privacy Policy.

1. Scope

This Privacy Policy applies to information processed through the SignalDesk app and website, including account access, watchlists, alerts, wallet tracking, signal features, and subscription/billing flows.

2. Information We Collect

2.1 Account and Authentication Data

We use a third-party authentication provider (currently Clerk) to manage sign-in and account identity.

Depending on your sign-up method and profile, this may include:

• email address
• authentication provider user ID
• basic profile information you provide to the auth provider
• session/authentication status

We do not need your password for day-to-day operation if authentication is handled by the provider.

The basis on which we may process these data is: contract / service performance and, where applicable, legal obligation.

We retain this data until the service is terminated.

2.2 Information You Enter Into the App

We collect and store data you actively provide in order to use the Service, including:

• watchlists
• alert rules
• onboarding responses
• delivery settings
• wallet tracking entries
• preferences and app configuration

Examples include:

• tokens or symbols you want to monitor
• thresholds and trigger settings for alerts
• Telegram delivery settings
• tracked wallet addresses
• subscription or onboarding selections

The basis on which we may process these data is: contract / service performance and legitimate interests.

We retain this data until the service is terminated.

2.3 Alert and Notification Data

To provide alerting features, we store operational alert data such as:

• generated alerts
• delivery channel (for example in-app or Telegram)
• delivery status and attempts
• acknowledgement/snooze/delete state
• alert timestamps and related metadata

The basis on which we may process these data is: contract / service performance and legitimate interests.

We retain this data until the service is terminated.

2.4 Wallet Tracking Data

If you add wallet addresses for monitoring, we process:

• the wallet address itself
• associated chain/network
• optional labels or notes
• detected transaction activity used for wallet alerts

The basis on which we may process these data is: contract / service performance and legitimate interests.

We retain this data until the service is terminated.

2.5 Signal and Validation Data

SignalDesk stores operational signal data and related scoring/validation information, including:

• signal scores and states
• signal history
• validation outcomes and credibility metrics
• model/scoring inputs derived from market, chain, and related data sources

This includes data used to display features such as:

• live and delayed signal views
• signal history
• hit-rate / early validation metrics
• credibility summaries

The basis on which we may process these data is: legitimate interests.

We retain this data until the service is terminated.

2.6 Usage and Operational Data

We may collect limited app usage or operational event data to run and improve the Service, such as:

• first sign-in / activation events
• rule creation events
• subscription status events
• alert interaction events
• request logs and diagnostics

The basis on which we may process these data is: legitimate interests.

We retain this data until the service is terminated.

2.7 Payment and Subscription Data

If you use paid features, billing is processed through a third-party payment processor (currently Stripe).

We may store or receive limited billing-related metadata, such as:

• subscription status
• checkout/session references
• customer or subscription identifiers
• payment state needed to manage access

We do not intend to store full raw payment card details ourselves.

The basis on which we may process these data is: contract / service performance, legitimate interests, and where applicable legal obligation.

We retain this data until the service is terminated.

3. How We Use Information

We use personal data and app data to:

• provide the Service
• authenticate users
• store your watchlists, alert rules, and preferences
• generate and deliver alerts
• monitor wallet activity you ask us to monitor
• display signal, validation, and credibility features
• provide subscription-gated features
• troubleshoot bugs and improve reliability/performance
• protect the Service against misuse or unauthorized access
• comply with legal obligations

4. Cookies, Sessions, and Local Storage

4.1 Essential Authentication Cookies

The current app uses essential authentication/session cookies through Clerk and related auth/session handling.

These cookies are used to:

• keep you signed in
• identify your authenticated session
• protect access to account-specific routes and APIs

These cookies are considered essential for the app to function.

4.2 Local Storage / Similar Browser Storage

The app also uses browser storage such as localStorage for limited app-state purposes, for example certain subscription/UI state handling.

4.3 Analytics Cookies

Based on the current application setup, we did not identify a clear non-essential analytics-cookie or marketing-cookie implementation that would automatically require a cookie-consent popup solely for the current auth flow.

If non-essential analytics, advertising, retargeting, or similar cookies are added later, this policy should be updated and any legally required consent mechanism should be implemented.

5. How We Share Information

We do not sell your personal data.

We may share information with service providers and infrastructure providers that help us run the Service, such as providers for:

• authentication
• hosting and database infrastructure
• payment processing
• messaging delivery
• market/news/chain data inputs

Examples from the current stack may include:

• Clerk
• Vercel and related hosted infrastructure
• Stripe
• Telegram (if you connect Telegram delivery)
• market/news/chain data providers used by the product

We may also disclose information when required by law or to protect rights, security, or the Service.

6. Security

We use reasonable technical and organizational measures to protect information, including authenticated access controls and HTTPS/TLS in normal operation.

However, no method of storage or transmission is perfectly secure, and we cannot guarantee absolute security.

7. Your Rights

Depending on your jurisdiction, you may have rights such as:

• access to your personal data
• correction of inaccurate data
• deletion of your data
• restriction of processing
• objection to certain processing
• data portability
• withdrawal of consent where processing is based on consent

You may also be able to use in-app account deletion/export tools where available.

For privacy-related requests, contact:

support@byteandblock.com

8. International Transfers

If infrastructure or providers process data in countries outside your own, your data may be transferred internationally. Where required, we rely on appropriate safeguards or legal mechanisms.

9. Children

SignalDesk is not intended for children. We do not knowingly provide the Service to children below the age permitted under applicable law.

10. Changes to This Policy

We may update this Privacy Policy from time to time. If we make material changes, we may notify users in-app, by email, or by updating the effective date.

11. Contact

For questions or requests relating to privacy or data protection, contact:

support@byteandblock.com