Privacy Policy

You can create an account two ways, and either way we store your name and email address, account creation and update times, and a record of the Terms version you accepted, the Privacy Policy version shown, when you accepted, and your confirmation that you are at least 18.

If you sign up with an email address and a password, we store the address, whether you have confirmed it, and a one-way hash of the password — never the password itself, so nobody at Firmtrack can read it or tell you what it is. Confirming your address and resetting a password each use a single-use token we store until it is used or expires; the link we email carries that token, so treat those emails as you would a password. Changing or resetting your password signs your other sessions out. When you choose a password we check it against Have I Been Pwned's public list of breached passwords and refuse one that appears there. Your password is hashed on our server and only the first five characters of that hash are sent, so the service receives neither your password nor enough of its hash to identify it; if the check cannot be reached we accept the password rather than stop you signing up.

If you sign in with Google instead, Google shares your name, email address, whether the email is verified, and a Google account identifier so we can recognize your account. We do not request Gmail access, keep your Google profile photo, or retain Google's access, refresh, or ID tokens after sign-in. Google's handling of the sign-in is described in its Privacy Policy. The two methods are separate accounts: signing in with Google does not give you a password, and a password account is not reachable through the Google button, even at the same address.

To keep accounts signed in and protect sign-in from abuse, we store session identifiers and expiration times, browser information, and an IP address when available. Sign-in also uses short-lived verification records and database-backed request counters. Session cookies last up to seven days; signing out ends that session. The agreement record is kept with your account. These security records are separate from our cookieless visit analytics.

If you choose Accept, we keep the first campaign labels (UTM parameters) from your visit in session storage until the tab closes or you change your choice. With that choice, joining the waitlist can send those labels with the signup analytics event when Plausible is enabled, and save a referral code with your waitlist record. Before acceptance, we do not save or use these optional campaign details. The privacy preference cookie remembers your choice and its version for up to 180 days. If your browser blocks a preference change, an essential revocation cookie can disable the older choice for up to 180 days; browser storage also synchronizes that choice between tabs. Closing the old notice is not treated as acceptance. Use Cookie preferences in the footer to change your choice. Reject clears browser attribution and stops further optional tracking. Necessary sign-in, security, preferences, and workspace storage continue to work; analytics remain cookieless. Previously saved account referrals, waitlist records, or commission records are not erased by changing browser preferences; contact us about those records.

If you apply to become a Firmtrack affiliate, we store your account identifier, email address, name, public channel link, audience description, promotion plan, requested code, agreement version, and review history. We use these to review your application and operate the program. Review messages are visible to you in your dashboard. Affiliate links carry a promotion code in the destination URL. Only after you accept optional tracking do we set a session cookie containing a validated promotion code and the identifier for your current consent choice, so the referral can follow you through account creation. Old cookies from an earlier choice are not used. You can also explicitly enter a referral code yourself without accepting optional tracking. Either an accepted referral link or a manually entered code can associate your account with an approved affiliate before your first subscription. We retain this attribution to reconcile recurring commissions and include the code in Stripe checkout and subscription metadata. Affiliates see aggregate referred-account counts, not customer identities. Payouts are not automated. Contact support@firmtrack.io for access or deletion requests; financial and attribution records may need separate review before removal.

We send account email — confirm your address, reset your password — to the address on your account through Resend, our email provider. Resend receives the address and the message in order to deliver it. We do not send marketing to an account address.

Our contact form collects your email address and message so we can respond to your inquiry. Resend processes both to forward the inquiry to our support inbox; our email provider holds the resulting correspondence. An inquiry does not subscribe you to the waitlist or marketing. The form uses short-lived, hashed-IP and service-wide abuse counters, and a five-minute confirmation cookie containing no message or email address. Do not include passwords or API keys. Contact us using the details below to request access or deletion of your correspondence.

If you join the waitlist, we collect the email address you type in. We record it, with the time you signed up, and send ourselves a notification about the signup through Resend. We use that address only to send your early-access invite. We do not currently use it for newsletters, rule-change alerts, or pricing updates. The invite carries an unsubscribe link; using it marks your address as unsubscribed so we do not email it again. To stop the form being abused, the app counts requests using a hash of your IP address in a shared security store. The waitlist's per-address counters expire after a minute, and service-wide counters expire within a day. Account and provider operations also use short-lived counters keyed by a hash of your account identifier or by the operation; these shared counters expire within a day. Our host's ordinary access logs record the request the same way they record every other request to the site. If you create an account and use the product, the account data we hold can include trades and notes, the prop firms and accounts you track, and payouts and costs you save to the account. Browser-only drafts and preferences are described below.

Like any website, our hosting provider logs standard technical information — IP address, browser, and timestamps — as part of serving and securing the site. Some features also write their own diagnostic lines to those logs, and those can contain the content the feature handled: a forwarded or shared receipt's parsed contents, an alert body, the details of a TradingView alert you send us, or a waitlist address if our notification email could not be sent. Because the unsubscribe link carries your address in its web address, opening it also records that address in those same access logs. Treat anything you route through those features as something that may appear in a server log.

Sample workspaces keep your manual trades, notes, fees and payouts in your browser. Settings, goals, guardrails, saved simulation settings, persona choices and local drafts also use browser storage under keys beginning firmtrack:. Clearing that storage removes those local copies; we cannot recover unsaved browser-only records. The demo is filled with synthetic data we generated; it is not anyone's real trading. In a signed-in connected workspace, manual trades, notes, fees and payouts are also saved to your account on our servers, together with the account context and trade records needed to interpret those entries later. The workspace distinguishes local drafts, failed saves and confirmed account saves. Existing browser records upload only when you choose to upload them. Clearing browser storage does not delete confirmed account saves. Preferences are not part of that account-saved ledger. Features listed below, including the assistant, send the described data to their providers when you use them.

The private rule book stays password-protected. Entering that password sets one signed cookie in your browser for up to 30 days so you are not asked again. It records only that the password was entered and when it expires — no personal information. Account sign-in sets a session cookie to keep you signed in, whichever method you used, and the Google button additionally sets a short-lived cookie to secure the redirect back from Google. Starting a Tradovate connection sets a short-lived cookie (ten minutes) that ties the sign-in you started to the one Tradovate sends back. These cookies support access and security; visiting the public pages and interactive demo does not require a Firmtrack account or advertising cookies.

For visit counts we use Plausible, a cookieless analytics tool that stores aggregate numbers only — no cookies, no personal identifiers, no tracking across sites. It records which sections were viewed and which buttons were pressed, not who pressed them.

We also use Vercel Analytics for page-view counts and Vercel Speed Insights to measure how fast pages actually load for real visitors. Both are run by our hosting provider, set no cookies, and do not build a profile of you or follow you to other sites. Speed Insights records timing measurements, not anything you type.

We run no advertising or ad-tracking scripts, and we do not sell analytics data or share it for advertising. Plausible only loads when it is configured, so on a build without it no Plausible script is served at all. The two Vercel tools are part of our hosting and load on every page of the live site.

Some features work by sending your data to a third-party provider. Each one is listed here. A feature that is not switched on sends nothing.

The AI assistant. When you ask it a question, we send your question together with the data needed to answer it — the firms and accounts you track, your computed trade statistics, recent journal notes, tags and trade context, recent conversation messages, and the money picture of your operation (total spend, payouts, net, monthly burn, cost per funded account, and the same figures per firm) — to Anthropic, which runs the model. Under Anthropic's commercial terms it may not train models on that content. This is real data about your accounts leaving our systems. If you would rather it did not, do not use the assistant.

Voice notes, forwarded receipts, and shared screenshots. If you record a voice note, forward a receipt email, or share a receipt screenshot to Firmtrack from your phone, the audio, the email content, or the image goes to Google Gemini to be transcribed or read.

Account receipt forwarding, when enabled. Resend receives the forwarded email. We keep a forwarding-address token linked to your account and store the received email's identifier, subject, extracted receipt fields, dates, and review status. The receipt record contains no raw email body and remains a suggestion; it does not automatically create a purchase or payout. Account data exports include these records and forwarding metadata, but omit the forwarding token. Deleting your account removes these rows from our current application database; provider copies, logs, and backups need separate handling.

Alerts. Alert text goes to whichever Telegram chat or Discord webhook the deployment is configured with — today we set those up ourselves; when alerts become something you connect per account, they will go only to the destinations you chose. If you point a TradingView alert at Firmtrack, we receive whatever that alert contains; we do not send it onward, but it is recorded in our server logs.

Payout verification. If you use it, we send the public wallet address you give us to Etherscan's API to look up recent USDC transfers on Arbitrum. Results link to transactions on the Arbitrum block explorer, Arbiscan. We do not ask for, and cannot use, a private key.

Payments. When billing is switched on, buying a plan happens on a checkout page hosted by Stripe, our payment processor. Your card details go to Stripe and never to us. Stripe tells us that a checkout completed, the email address you gave it, the plan and billing period you chose, the amount, and Stripe's own identifiers for the customer and subscription; we keep that record so we can match a subscription to the person who bought it and answer billing questions. If you are signed in to a Firmtrack account when you buy, we send Stripe your account id with the checkout and Stripe returns it with that record, so the subscription can be tied to your account and not only to an email address; the email you give Stripe may differ from the one on your account. After a checkout completes we email you an acknowledgment of the subscription terms and how to cancel, through Resend. Until billing is switched on, no page on this site can take a payment.

Email and hosting. We use Resend to deliver email and Vercel to host the site. The economic calendar pulls public US government statistics from FRED and sends nothing about you.

Connection credentials depend on the platform. TopstepX uses your username and API key; Tradovate uses its own sign-in page; when available, Rithmic uses the username and password your firm issued plus its system name. We store the platform username and keep API keys, session tokens, and Rithmic passwords encrypted so that the database alone cannot read those secrets. We ask the platform, on your behalf, for the accounts, names, balances, and executions (fills) it makes available under your login, and keep copies so your workspace can show them. Availability depends on the platform's approvals and completed deployment setup. A TopstepX key is sent only to that platform's API host (api.topstepx.com). For Tradovate you sign in on Tradovate's own page (trader.tradovate.com); we never receive your password, only a session token, which we store encrypted and send only to Tradovate's API hosts (live.tradovateapi.com and demo.tradovateapi.com) to read your accounts and fills and to keep the session alive. When Rithmic connections are available, you enter the firm-issued login and system name in the signed-in connection form; we check those credentials with Rithmic before saving, encrypt the password, and send the credentials only to Rithmic's connection servers to read your accounts, fills and balances, never to place an order. Configured connections are used when you connect, when you press sync, and through scheduled background syncs. We use connection credentials only to read; we never place, change, or cancel an order with them. If you open the assistant while your connected accounts are selected, the finished statistics it receives are computed from these records, together with the recent journal and conversation context described above.

You can correct what we inferred about an account (its stage and size), leave an account out of your workspace, or disconnect a platform at any time from your account page. Disconnecting deletes the stored connection credentials and the source account and fill records for that connection. Your account-saved manual records and the account context and trade records retained with them remain as saved history; disconnecting is not an account-data deletion request. Saved history is excluded from active account risk calculations. To request deletion of your account data, use the contact below. Browser drafts and sample-workspace records remain on your device until you clear them.

Firmtrack does not ask for your TopstepX or Tradovate passwords: those platforms connect with an API key or their own sign-in page, described above. When Rithmic connections are enabled, the signed-in connection form accepts the firm-issued username and password; we store the password encrypted on our servers as described above. An earlier version of the demo could save platform logins in plain text in your browser; the current version automatically removes that legacy Firmtrack storage entry without reading or copying it.

Joining our Discord server is optional, and shares nothing with us beyond what Discord shows any server owner — your Discord username and the roles you pick. Running the /link command is also optional: we email a six-digit code to the address you enter and, once you confirm it, store that address alongside your Discord user ID so community roles can reflect your Firmtrack account. We store a one-way hash of the code, never the code itself, and it expires in ten minutes. We also keep a record of which early-access perks — founding member, beta tester — an email address has been granted, a ledger of link attempts used only to rate-limit abuse, and an audit trail of the bot's own actions that holds IDs and counts, never message content. Support tickets you open are stored with their messages so we can follow up on them.

Run /unlink at any time to delete the stored address and remove the roles it granted. Our bot never messages you first.

We do not sell your personal information, and we do not share it for cross-context behavioural advertising.

Firmtrack never asks for passwords or API keys by email, chat, or support message. A Rithmic password is entered only in the signed-in connection form when that integration is available. TopstepX uses an API key and Tradovate uses its own sign-in page. Do not send credentials to anyone who contacts you claiming to be Firmtrack.

We keep waitlist emails until you ask us to delete them. If you unsubscribe, we keep the address marked as unsubscribed so we can honor that choice, unless you ask us to delete it instead. Account data is kept while your account is open and for a reasonable period afterwards, unless you ask us to delete it sooner. If you start an email sign-up and never confirm the address, we delete that unconfirmed account, so an address you never finished using does not stay registered to you; sign up again any time. Billing records, including your consent to the subscription terms, are kept for at least three years after the subscription ends, because the law requires us to be able to show them. Server logs are kept on our hosting provider's normal schedule.

We use encryption in transit, keep credentials in encrypted configuration rather than in our code, and limit who can reach production. No service can promise perfect security. If a breach affects your personal information, we will notify you as required by law.

Email firmtrack.team@gmail.com at any time to see what we hold about you, correct it, take a copy, or have it deleted, and we will act promptly. Depending on where you live you may have additional rights — including, in several US states, the right to know, delete, correct, and opt out of sale or sharing (we do neither), and to not be discriminated against for exercising them. Ask us and we will honour them regardless of whether the law requires it of a company our size.

Firmtrack is for adults and is not directed at children. We do not knowingly collect information from anyone under 18. If you believe a child has given us information, email firmtrack.team@gmail.com and we will delete it.

As Firmtrack changes its features and data flows, this policy will change with it. The date at the top changes whenever it does, and we will flag material changes rather than quietly editing the page.

Firmtrack LLC, 4601 E. Douglas Ave. Ste 150, Wichita, KS 67218. Privacy questions: firmtrack.team@gmail.com. See also our terms of service.