Privacy Policy

Account information (name, email, username, password or auth tokens). Billing and purchase information (plan, receipts, transaction identifiers) processed via third parties (including but not limited to Whop). Support communications (messages, attachments, troubleshooting details). Community or profile content you choose to submit (e.g., display name, avatar, notes).

Device and usage data (IP address, browser type, device identifiers, app version, pages/screens viewed). Log data (timestamps, feature usage, error logs, performance metrics). Cookies or similar technologies used for authentication, preferences, analytics, and security. Authentication and session activity is logged and may be used as evidence of authorized access in the event of a billing or chargeback dispute (see Section 6.1 of the Terms of Service).

Connection metadata (broker name, connection status, and integration identifiers). Authorization tokens obtained via OAuth through our broker integration provider (currently SnapTrade) — Alertsify does not receive or store your broker username or password. You authenticate directly with your broker through the OAuth flow, and you can revoke Alertsify's access at any time through your broker's security settings. Account and trading data necessary to provide Services (e.g., balances, positions, orders, fills, timestamps) depending on your enabled features. Trade alert and tracking data generated by your activity and configuration.

Data availability depends on your broker, permissions you grant, and features you enable. Alertsify does not control what brokers provide.

Alertsify does not collect detailed financial profile information (such as income, net worth, or investment objectives) for the purpose of providing personalized investment advice or making suitability determinations. If we later offer features that require such data (for example, for regulatory compliance), we will describe those purposes separately. Any broker connection data (including account balances and position information) is used solely to enable user-directed automation features and is not used to construct or recommend portfolios, or to rank, target, or recommend specific Traders or strategies to you. Any rankings you see are based on standardized, formulaic performance metrics applied across the eligible Trader universe.

Track Record is user-initiated. We receive nothing from any Discord server until a user reading a message chooses to submit that one message to us. We do not run a bot inside any server, do not read message history, and do not monitor or subscribe to any channel. When you track an alert, we collect:

• Your Discord user ID, and the server (guild) ID, channel ID and message ID of the alert you tracked, together with the identity of the account that posted it as Discord reports it;
• The text of the tracked alert, retained for parsing and dispute resolution. This is not published — see Section 4.1;
• Market data snapshots tied to that alert: the option chain quotes at the moment it posted and at each subsequent interval we record, and the contract those quotes are for;
• The time you tracked it and how long after the alert posted, and the size you assigned to it;
• Brokerage execution data for the alert, if you have connected a broker and executed it — the fills, quantities, prices and timestamps in your own account;
• Referral attribution: the referral code, if any, on the link through which you installed the Alertsify Signal application, and whether the install granted commands and was later linked to an Alertsify account.

You can track alerts without an Alertsify account. Where you have no account, the record is keyed on a hash of your Discord user ID, and it is attached to your account if and when you create one and link the same Discord identity.

Alertsify may collect, create, use, license, sublicense, sell, publish, distribute, and otherwise commercially exploit aggregated, anonymized, and de-identified data derived from your use of the Services and from platform activity generally, including but not limited to: aggregated trading activity data (e.g., total platform order flow, options volume trends, sector activity, strategy distribution, instrument popularity, and trade timing patterns); anonymized performance and behavioral analytics (e.g., aggregate win rates, average hold times, risk-reward ratios, and auto-execution adoption patterns); de-identified market signal data, trend indicators, and sentiment metrics derived from collective platform activity; and statistical reports, research, benchmarks, indices, and data products based on the foregoing.

"Aggregated, anonymized, and de-identified" means data that has been processed such that it cannot reasonably be used to identify, relate to, describe, or be linked back to any individual user, account, or brokerage. Alertsify will use commercially reasonable methods to strip, hash, or otherwise remove personally identifiable information before any such data is shared, licensed, or sold to third parties.

Potential recipients of aggregated and anonymized data may include, without limitation: institutional investors, hedge funds, quantitative research firms, and asset managers; financial data vendors, analytics providers, and market research firms; academic researchers and financial institutions; and any other third party for any lawful commercial, research, or analytical purpose.

Alertsify retains all rights, title, and interest in any aggregated, anonymized, and de-identified data and any data products, reports, indices, or analytics derived therefrom. Your use of the Services constitutes your consent to Alertsify's collection, creation, and commercial use of such data as described in this Section. This right survives termination or cancellation of your account. For clarity, this Section applies only to aggregated and anonymized data — Alertsify does not and will not sell your personally identifiable information.

Published publicly. The contract a tracked alert named, the time it was posted, the room and the posting account it came from, the market prices we recorded for it, and the result once the position is closed. Aggregate figures for a room or a poster built from those alerts. An open position is shown as open and carries no result until it is over.

Shown to a claimed room owner. Where a room owner has claimed the room's page, the execution activity and results of members who connected a brokerage account and executed that room's alerts. A member can see what the room owner sees about them. This is a disclosure to the claimed owner only and is not published publicly.

Never shown to anyone outside Alertsify. The text of a tracked alert; which individual members tracked or executed any given alert (the public figures are counts and totals, never a list of people); which of a room's alerts were excluded from its record and why; your brokerage credentials, account numbers, account balances, and buying power; and any position or trading activity of yours unrelated to the alerts you tracked.

The exception, for all three categories, is disclosure required by law, subpoena, or court order, disclosure to our service providers acting on our instructions, and disclosure necessary to respond to a copyright notice or a legal claim, as described elsewhere in this Policy.

Alert records are retained indefinitely. The contract, the timestamps, the market prices and the outcome are part of a public historical record, and a record that disappears is not a record. This is the same principle applied to broker-verified Lead Trader performance in Section 5.1 of the Terms of Service.

The text of a tracked alert is retained for 24 months from the date it was tracked, for parsing and dispute purposes, and is then deleted. It is not published at any point. Twenty-four months outlasts the informal-resolution and arbitration timelines in Section 21 of the Terms of Service, so a figure disputed long after the fact can still be checked against what the alert actually said.

Preservation overrides both. Where we receive a formal notice, legal demand, or credible complaint concerning specific content, we preserve the related records — including alert text that would otherwise be deleted — and suspend routine deletion for them until the matter is resolved.