Privacy Policy

This policy explains what data Highground Research handles, what stays local in your browser, what is stored server-side for monitoring features, and how notification delivery works.

Last updated: March 13, 2026

1. Privacy approach

Highground Research uses a mixed model. Some features are local-first and keep your data in browser storage on your device. Other features, especially account-based monitoring and alerts, require server-side storage so the product can remember your account, rules, and delivery settings.

We try to keep collection limited to what is needed to operate the feature you chose.

2. Data that stays local on your device

When you use Personal Analytics, your imported Kalshi trade CSVs and the derived local analytics database are designed to stay in your browser storage by default. Local preferences such as parts of your UI state may also be stored in browser storage on your device.

Unless a feature clearly tells you otherwise, this local analytics data is not uploaded to our servers just because you imported it.

3. Data we store on our servers

For account and monitoring features, we may store:

  • Your account identifiers from WorkOS, such as user ID, email, and name if available.
  • Your monitoring rules, monitored market links or identifiers, delivery selections, and related timestamps.
  • Your alert history and delivery records.
  • Your notification endpoint records, such as account email and browser push subscription details.
  • Your phone number and verification status if you choose to use SMS-related features when available.
  • Basic operational and security records such as IP-based request identifiers, rate-limiting data, and service logs.

For features like the Smart Money Scanner, we also store publicly available market data, on-chain wallet addresses, wallet PnL estimates, holder snapshots, and derived scores. This data comes from public blockchain records and third-party market APIs, not from your private accounts or files.

4. How we use data

We use data to:

  • Authenticate you and keep your account session working.
  • Save and evaluate monitoring rules you create.
  • Send alerts by email, browser push, or SMS when enabled.
  • Prevent abuse, enforce rate limits, debug issues, and keep the service secure.
  • Improve the reliability and usability of the product.

5. Third-party processors and data sources

We use third-party services and data sources to operate parts of the product. Based on the current implementation, these may include:

  • Kalshi and Polymarket APIs as sources of public market data, event metadata, and on-chain holder information.
  • WorkOS for authentication and account session handling.
  • Brevo for transactional email delivery.
  • Twilio for SMS delivery and phone verification when SMS is enabled.
  • Browser push infrastructure and the browser vendor push services used by your device.
  • Hosting, database, caching, and rate-limiting infrastructure providers needed to run the app.

These providers process data on our behalf or as part of delivering the feature you asked to use. Their handling of data is also subject to their own policies and terms.

When you enable notifications, the relevant provider may receive the destination and message content needed to deliver the alert, such as your email address, phone number, browser push subscription details, and the alert text itself.

6. We do not sell your data

We do not sell your personal data for money. We also do not treat your imported local Personal Analytics CSV data as something to sell or broker to data buyers.

7. Cookies, browser storage, and push permissions

The service uses cookies for authentication and session management. These cookies are functional and required for account-based features to work. We do not use advertising or tracking cookies.

Local analytics data is stored in browser-managed storage (such as OPFS or IndexedDB), and monitoring setup drafts or preferences may be stored in session or local storage on your device.

If you enable browser push, your browser and device will also maintain a push subscription. You can disable notifications in your browser or device settings at any time.

8. Retention

Local browser data remains on your device until you delete it, your browser removes it, or your environment changes. Server-side account, monitoring, endpoint, and alert records may be kept for as long as they are reasonably needed to operate the service, maintain security, handle disputes, or comply with legal obligations.

9. Your choices and account deletion

  • You can avoid account-based features if you do not want server-side monitoring storage.
  • You can remove local browser data by clearing relevant browser storage.
  • You can revoke browser notification permission in your browser or device settings.
  • You can stop using monitoring alerts or change delivery settings at any time inside the product.
  • You can request deletion of your server-side account and associated data by contacting us through the channel listed in the Contact section below. When an account is deleted, monitoring rules, notification endpoints, alerts, and delivery records linked to that account are removed.

10. Security

We use reasonable measures intended to protect the data we handle, but no system is perfectly secure. You should also protect your devices, accounts, browser profiles, and email accounts, especially if you use them for market monitoring or alerts.

11. Age requirements

As stated in our Terms and Conditions, the service is intended for users who are at least 18 years old. We do not knowingly collect personal data from anyone under 18 through the service.

12. International use

If you use the service from outside the country where the app is operated or hosted, your data may be processed in other jurisdictions where our providers operate infrastructure.

13. Changes to this policy

We may update this privacy policy from time to time. When we do, we will post the updated version here and update the last updated date.

14. Contact

For privacy questions, deletion requests, or data concerns, contact Highground Research through @KenobiOnKalshi.