Privacy Policy

VERSION 2.15 · EFFECTIVE NOVEMBER 3, 2026 · QUANTGPT LLC, A FLORIDA LIMITED LIABILITY COMPANY

• 1. Who we are and scope
• 2. What we collect
• 3. Why we use it, and our legal bases
• 4. Who we share it with
• 5. Your AI provider and the plug-in
• 6. Brokerage data
• 6A. Portfolios you import
• 7. Security and enforcement logs
• 8. Cookies and telemetry
• 9. How long we keep it
• 10. Security and breach notice
• 11. Your rights
• 12. International transfers
• 13. Children
• 14. Mobile apps
• 15. Changes
• 16. Contact

// 1. WHO WE ARE AND SCOPE

This policy is issued by QuantGPT LLC, a Florida limited liability company with its principal office at 15350 N Florida Ave, Tampa, FL 33613 ("QuantGPT", "we", "us"), which is the controller of the personal data described here. It covers quantgpt.co and its subdomains, the QuantGPT terminal, the plug-in and API, our mobile applications, and our emails (together, the "Service"). It does not cover third-party services you connect to the Service, such as your AI provider or your broker, which have their own policies.

// 2. WHAT WE COLLECT

We collect the minimum we need, and we list it by where it comes from.

We do not collect precise location, contacts, photos, health data, or government identifiers. We do not buy data about you from data brokers.

// 3. WHY WE USE IT, AND OUR LEGAL BASES

If you are in the European Economic Area, the United Kingdom, or another place that requires a legal basis for processing, the basis for each purpose is shown.

Apart from the ad measurement described in Section 8, we do not use your data for advertising. We do not build profiles for marketing, and we do not sell or rent your data. We do not make decisions about you by automated means that have legal or similarly significant effects; enforcement decisions are reviewed by a person.

// 4. WHO WE SHARE IT WITH

We share personal data only with providers who process it for us under contract, and only as needed:

• Stripe (payments and billing portal). Stripe is an independent controller of the payment data it collects. See stripe.com/privacy.
• Vercel (the previous host of quantgpt.co, on standby until it is retired).
• Google (Google Analytics on quantgpt.co, under the conditions in Section 8; advertising features off).
• Cloudflare (hosting for quantgpt.co and its functions, cookieless web analytics, storage for the waitlist and unsubscribe records, encrypted, and DNS, security, and bot protection in front of the terminal).
• Your brokerage, only if you link it, and only in the direction of us reading from them. We do not send your data to your broker.
• Discord, only if you link your Discord account: our bot gives your Discord account the QuantGPT or QuantGPT Pro role that matches your plan, and takes it away when the plan ends, you unlink, or you delete your account. Discord learns that role, nothing else from your account, unless you turn on the Discord copy of your signal alerts: then our bot sends you each daily digest as a direct message, and Discord carries that message.
• Resend (email delivery), to send waitlist and service emails. Resend receives the recipient address and the message.
• Advertising partners, for advertising measurement only, and only as described in Section 8: page and waitlist events from the partner's pixel on quantgpt.co, and a sign-up, trial, and first payment report for each account, whether or not it arrived from one of our ads. Each partner uses this data under its own privacy policy.
• Our data providers, in the narrow case where they exercise their contractual right to verify compliance with data license terms, or where we reasonably believe their data has been extracted or redistributed in breach of our Terms; where possible we provide aggregate usage rather than personal data.
• Our legal counsel, and law enforcement, where we reasonably believe our Terms, our intellectual property, or our data licenses have been breached, or where required by law.

We may also disclose data if required by law, subpoena, or court order; to protect the rights, safety, or property of QuantGPT, our users, or the public; to enforce our terms; or as part of a merger, acquisition, financing, or sale of assets, in which case this policy continues to apply to your data until it is changed with notice.

We have not sold personal information in the preceding 12 months. The ad measurement in Section 8 may count as "sharing" personal information for cross-context behavioral advertising as California law defines it; that is the only such sharing we do. It is on by default for United States visitors, and you can opt out at any time with the "Do Not Sell or Share My Personal Information" link at the foot of every page, with Global Privacy Control, or by email (Sections 8 and 11).

// 5. YOUR AI PROVIDER AND THE PLUG-IN

The plug-in lets an AI assistant you operate, such as Claude or ChatGPT, call our Service with a key you issue. Your prompts, conversations, and anything you type go to your AI provider, under its terms and privacy policy, not to us. We receive only the structured tool calls the assistant makes to our endpoint (for example "run this backtest with these parameters"), plus your key hash, call counts, and the technical information in Section 7. We return computed results. We keep each of those calls, with the settings it sent and a copy of the result we returned, in your usage record for 180 days (Sections 2 and 8). We do not receive your conversation history from the provider.

Where the Service itself uses an AI model to parse a request you type into the terminal into a structured study, we send only that request text to the model provider Anthropic under a contract that prohibits training on it, and we do not send your identity with it.

The house model is different by design. A paid member can ask the house model without a key of their own: those conversations pass through our server to Anthropic on our key, under a contract that prohibits training on them, and we keep only the token counts and dollars, never the text. Each plan carries a monthly allowance; past it, the panel returns to your own key or your own connected AI.

Whichever model the AI panel uses, the tools it runs for you are recorded in your usage record like any other tool call.

// 6. BROKERAGE DATA

Linking is optional and off by default. If you link a brokerage account:

• Authorization happens on your broker's site or app. We never see or store your broker credentials.
• Access is read-only by construction. Our software cannot place, change, or cancel orders or move money.
• We read what is needed to render performance: balances, positions, orders, and activity. We store daily snapshots of equity, cash, and positions so that statements and history can be shown for past periods, because most brokers report only current holdings.
• Brokerage data is shown to you. It is shown to others only if you choose to publish a performance card or list a system in a directory, and then only the figures you choose to publish.
• You can disconnect at any time in your account settings or by revoking access at your broker. When you disconnect, we stop reading and delete the connection. Historical snapshots are deleted within 30 days unless you ask us to keep them, or we are required to retain them.

// 6A. PORTFOLIOS YOU IMPORT

Importing a portfolio is optional. You can paste your positions, upload a file from your broker (a CSV, a spreadsheet, or a statement PDF), have your AI send them, or type them in. Importing is not linking: we do not connect to your broker, and a portfolio does not update on its own. You see every row before anything is saved.

• What we keep. The portfolio's name and cash balance. For each holding: the ticker, the number of shares, the cost basis and the date acquired if you give them, the short description it was imported with, its kind (a stock, a fund, an option and so on), whether we found it in our data, and, for something we do not price, its value and the date of that value as imported. We also keep when the portfolio was made and last changed, the kind of file it came from, and a short code computed from the rows so the same import is not saved twice. If the import shows an account number, we keep at most its last 4 characters, so you can tell your accounts apart.
• What we never keep. The file you upload or the text you paste: we read it to find the positions and do not save it. A full account number: we cut any account number to its last 4 characters. Anything shaped like a Social Security number, a tax id, or a date of birth: we remove it from every name and description before anything is saved.
• What we use it for. Only to show your portfolios to you and to work out your own figures from them: the summary (value, gains against the cost basis you gave, allocation, dividends, upcoming earnings, and similar figures) and, when you or your AI pass your holdings to them, the portfolio checkup and our other analysis tools. Your holdings are read against our own market data. We do not sell your portfolios, share them with anyone, or use them for advertising.
• Who sees it. You. Other members never see your portfolios, and they are not on the leaderboard. An AI sees a portfolio only through your own key or sign-in, when it calls one of the portfolio tools for you, or in the terminal's AI panel; what the tool returns then goes to that AI's provider, as Section 5 describes. No other account's key can read it.
• Your usage record. For a portfolio tool, your usage record (Section 8) keeps the shape of the call: which tool, how many rows or characters it carried, its other settings (such as the portfolio it named or the sections it asked for), and whether it worked, with any error message. It does not keep the holdings, the text you pasted, or what the tool returned.
• Deleting. Delete a portfolio on the Portfolio page in the terminal (its Holdings tab), or ask your AI to (its delete_portfolio tool asks you to confirm first), and the portfolio and every holding in it are removed from the Service at once. You can also remove one holding at a time. Deleting your account erases every portfolio you keep. The data export on your account page includes them.
• Retention. We keep a portfolio until you delete it or your account; it does not expire on its own. Our backups hold copies for a while longer: the continuous backup copy of the portfolio database keeps 30 days of history, our server's own nightly copy is kept 14 days, and the nightly full copies stored away from our servers are kept for up to 12 months. So a deleted portfolio can remain in a backup for up to 12 months. We do not edit backups; it is gone as each copy reaches the end of its period.

// 7. SECURITY AND ENFORCEMENT LOGS

We say this plainly because it matters to how the Service is protected. Every request to the Service is logged with the IP address it came from, characteristics of the device and browser that made it, the time and pattern of requests, and, for accounts, the key or session used. We use these records to:

• rate-limit, block brute-force attempts, and detect automated traffic;
• detect scraping, bulk extraction, redistribution, and use of the Service to build competing products, all of which our Terms prohibit;
• identify accounts that are operated by the same person or organization, including accounts opened to evade a limit, block, or termination, and accounts opened under a false name;
• identify the person or organization responsible for a breach, preserve evidence, and support legal claims, including by combining these records with payment, account, and export records; and
• meet our obligations to the data providers whose data we license.

These records are kept for 12 months, and longer where they relate to an active investigation, a suspected breach, or a legal claim, for as long as that matter remains open. They are not used for advertising or profiling for marketing, and they are not sold. Exports and share cards may carry identifiers tied to your account for the same purpose, as described in Section 15.3 of the Terms.

// 8. COOKIES AND TELEMETRY

We use functional cookies: a session cookie so the terminal knows you are logged in, a gate cookie for password-protected areas, cookies set by Stripe during checkout, and a Cloudflare bot-protection cookie. On quantgpt.co we use a cookieless analytics service from our hosting provider, which counts page views without identifying you, and Google Analytics, which sets _ga cookies and receives the pages you view, your IP address, and browser details, only for United States visitors without Global Privacy Control or Do Not Track who have not opted out. Its advertising features are off. The same opt-out as the advertising pixel turns it off. The Cookie Policy lists every cookie and local storage key by name.

Advertising pixel (marketing site)

quantgpt.co carries an advertising partner's pixel so we can see whether our ads work. It loads only on quantgpt.co itself, never inside the terminal, and only when all of these hold: your browser does not send the Global Privacy Control or Do Not Track signal, our server's country lookup (made from the request, nothing stored) says you are in the United States, and you have not opted out in this browser. For those visitors it is on by default: it loads with the page, and a short notice on your first visit says so and links to the opt-out. When it loads, the partner's script records a page visit on each page, and a "Lead" event when you join the waitlist. The partner's script also collects what a browser sends with any request, such as your IP address, user agent, and the page address, and sets the _rdt_uuid cookie on quantgpt.co. It may also read an email address or phone number you type into a form on quantgpt.co and send it to the partner in hashed (one-way coded) form. When you give us your email address on one of our forms on quantgpt.co (such as the waitlist), our site codes it the same way in your browser with SHA-256, keeps only that code in local storage as qg_rdt_em, and gives it to the partner's script on your later page visits, so the partner can match those visits to its own users; the partner cannot read your address from the code. For each page visit the pixel records, our own server also sends the partner's Conversions API a copy of that visit: the visit's id (so the partner counts the visit once), the click id if your browser holds one, the value of the _rdt_uuid cookie, and the IP address and user agent of your browser's request. The copy carries no email address and no account id. It is sent only from a page where the pixel itself ran, so every condition above applies to it, and our server checks again that your browser sends neither Global Privacy Control nor Do Not Track, that you have not opted out, and that the request comes from the United States.

Advertising click id and conversion reports

When you arrive from one of our ads, the advertising partner adds a click id (rdt_cid) to the link. Under the same conditions as the pixel, our site keeps it in your browser's local storage as qg_rdt_cid, with any advertising campaign code and the date of that visit in qg_rdt_first, for 28 days from that first visit (a later ad click does not replace it), and adds them to the terminal sign-in link; if the conditions do not hold, they are discarded and cleared. Under the same conditions, and also when you did not arrive from an ad, our site adds the value of the partner's _rdt_uuid cookie to that link. The terminal keeps these values in its qg_attr cookie and stores them with an account you create. When you create an account, start a trial, or make your first payment, our server sends the partner's Conversions API one report per event, whether or not you arrived from one of our ads, so the partner can measure its ads; if you arrived from one of our ads, it also reports when you start a checkout. Each report contains: the event (checkout started, sign-up, trial started, or first purchase) and when it happened; the click id, if there is one; the partner's own cookie id (the _rdt_uuid value), if we hold one; a SHA-256 hash of your lowercased email address, which the partner uses to match the report to its own users (the hash is one-way: the partner cannot read your address from it); a SHA-256 hash of your account id; the IP address and user agent of the request that caused the event or, for a report made when our payment processor notifies us, those of your sign-up request; for a checkout, a trial, and a purchase, the plan you chose; and, for a checkout and a purchase, the plan's monthly price. Each event is reported once. These reports are made only for an account whose sign-up request our server's country lookup placed in the United States, whose browser sent neither Global Privacy Control nor Do Not Track, and whose owner has not opted out; an account created before this version took effect is reported only if it arrived from one of our ads, as the earlier version said. A second advertising partner adds its own click id (twclid) to its ads' links; under the same conditions our site keeps it as qg_twclid and adds it to the terminal sign-in link, and an account created from that visit stores it. We send that partner no report and no click id. Google adds its own click id (gclid, or on some Apple devices gbraid or wbraid) to the links of its ads, and Meta adds one (fbclid) to links people follow from Facebook and Instagram, its ads included; under the same conditions our site keeps them as qg_gclid, qg_gbraid, qg_wbraid, and qg_fbclid and adds them to the terminal sign-in link, and an account created from that visit stores them; if the conditions do not hold, they are discarded and cleared. We use them only to tell Google or Meta that one of its ads led to a sign-up or a purchase, with the click id, the event and when it happened, and for a purchase the plan's monthly price. We send no study, workspace, brokerage, or payment data to any advertising partner.

Your choices

The partner learns which of our pages you visit, which some state laws may treat as "sharing" personal information or as targeted advertising. To opt out, use the "Do Not Sell or Share My Personal Information" link at the foot of every page on quantgpt.co, which opens the buttons on the Cookie Policy, or turn on Global Privacy Control (or Do Not Track) in your browser, which we honor as an opt-out on every visit. After you opt out none of the above runs in that browser: the pixel stops on the page you are on and does not load again, the click ids, the partner's cookie id and the hashed email code are not stored or forwarded, and the partner's cookies and that code are deleted from quantgpt.co. Your choice is also passed to the terminal, so our server sends the partner no page-visit copies from that browser and no reports about an account you sign in to there. Opt back in with the button beside it. The choice is kept in your browser, so make it again on each browser or device. You can also clear the cookie and local storage for quantgpt.co at any time, or email desk@quantgpt.co and we will stop reporting your account to any advertising partner. Each partner's handling of the data is governed by its own privacy policy, and you can limit how an ad platform uses activity from other sites for ads in your account settings with that platform.

Beyond these we use no cross-site advertising trackers, and we do not sell personal data.

Your usage record

We keep a usage record for each account, described in Section 2: what happened on your account, the pages you open, each run and tool call with its settings and a copy of the result we returned, and each call's timing and outcome. That includes the tool calls your AI makes to us and their results, kept per account for 180 days. We do not receive or keep your conversations with your AI.

We use it to run the Service and support you (when a run fails, the record shows us what was asked and what came back), to keep the Service secure and stop abuse, to find and fix errors, and to improve the product, for example by seeing which tools are used and where people get stuck.

Only the QuantGPT founders can view it, on founder pages that require two-factor sign-in. We do not sell it, give it to advertisers, or use it for ads. We may publish aggregate figures, such as the number of tool calls or active sessions on the public cluster page or in our posts, but never a member's own queries or results. The one place other members see figures from your own runs is the leaderboard, described below, on the terms you set there. The data export on your account page includes your events and your calls with the settings they sent.

Separately, the service counters behind the public cluster page count active sessions and keys from short anonymous hashes held in memory only, never written to disk and cleared when the service restarts; the page shows only totals and dataset health. Some things we count only as daily totals with no visitor id at all: visits to quantgpt.co and clicks on its main buttons (start a trial, start free, pick a plan, monthly or annual, the cookie choice), by page and by the campaign code or referring site that brought the visit, forum thread views, and clicks through to our Discord, and page views on quantgpt.co and in the terminal by kind of device (phone, tablet or computer: a class worked out from the screen size on quantgpt.co and from the browser's user agent in the terminal, which is read and not kept).

The leaderboard

The terminal has a leaderboard. Its contents are shown only to members who are signed in; it is not on the public site, and a signed-out visitor or a search engine gets no member data from it. It ranks members by use of the Service, never by returns. For windows from one day to all time, it shows other signed-in members how many backtests you ran, studies you journaled and forum posts you wrote, how many days you were active, and a score, a rank and a trend made from those counts. Beside them, as hypothetical backtests on past data, it shows the Sharpe ratio and CAGR of the highest-Sharpe backtest you included in the window and how many backtests you ran, and, when that run is in your journal, how it did on data that arrived after you journaled it (its journal grade). Members may also view the board ordered by the highest CAGR or Sharpe among the runs members include, and side panels list the highest CAGR, the highest Sharpe, the most backtests and the best graded journal entries. Backtests and days active are read from your usage record, which we keep for 180 days, so those counts reach back no further; studies and posts come from your journal and the forum. The board keeps no copy of its own.

Your forum name shows on the leaderboard by default. Turn off Show my forum name on the leaderboard, on your account page, to appear instead as "operator_" and four characters made from your account id with a keyed hash that cannot be reversed; an account without a forum name always shows that way. Your other settings, all on your account page: Share my best run (off by default; on, other members can open the run behind your figures read only, with its settings and every year of its results, and see the name of your best journal entry; off, they see the figures and not the run); Show that my paper bot is running (off by default; on, your row says that one of your QuantGPT Cloud bots is running on paper, which is never part of the score); New runs are included on the leaderboard (on by default; each backtest result and journal entry also has its own Include on leaderboard switch, and Include all and Exclude all apply to the runs you already have; only an included run can supply your Sharpe, CAGR and after-the-run figures or be opened by others, and a left-out run still counts as one backtest run); and Leave me off the leaderboard (off by default; on, no other member sees you on the board at all and no rank counts you, while you still see the board and your own place, marked for you alone). Founder and internal accounts are ranked like every member. These choices are kept with your account and erased with it; a per-run choice is erased with its journal entry.

// 9. HOW LONG WE KEEP IT

Backups may hold copies for up to 35 days beyond these periods, after which they are overwritten. Where you request deletion, we may retain the minimum needed to honor the request itself, to complete an open investigation or legal matter, or to meet a legal obligation.

// 10. SECURITY AND BREACH NOTICE

We protect data with measures appropriate to its sensitivity: encryption in transit everywhere; hashed passwords and hashed keys; read-only, scoped brokerage access; secrets kept out of code and logs; rate limiting and lockouts on authentication; and a policy of not storing what we do not need. No system is perfectly secure. If we learn of a breach affecting your personal data, we will notify you and any regulator as the law requires, including, for Florida residents, within the time required by the Florida Information Protection Act, section 501.171 of the Florida Statutes.

// 11. YOUR RIGHTS

Wherever you live, you can email desk@quantgpt.co to ask us to show you the data we hold about you, correct it, delete it, or stop using it for marketing. We will verify the request by matching it to your account email, and we will respond within 30 days, or within 45 days where California law allows, telling you if we need longer.

European Economic Area and United Kingdom

You have the right to access, rectify, erase, restrict, and port your personal data, to object to processing based on legitimate interest, and to withdraw consent at any time without affecting earlier processing. Where you object to processing we carry out for security or enforcement, we will stop unless we have compelling legitimate grounds that override your interests or the processing is needed to establish, exercise, or defend legal claims. You may complain to your local supervisory authority; in the UK that is the Information Commissioner's Office. QuantGPT LLC is a U.S. company and runs the Service from the United States. We do not market the Service in the European Union or the United Kingdom, and we have not appointed a representative there under Article 27 of the GDPR or the UK GDPR. If that changes, we will name our representative here.

California

Under the CCPA and CPRA you have the right to know what personal information we collect, use, and disclose; to delete it; to correct it; to opt out of sale or sharing (we do not sell; the ad measurement in Section 8 is the only sharing; it is on by default for United States visitors, and it is off after you opt out with the "Do Not Sell or Share My Personal Information" link at the foot of every page, whenever your browser sends Global Privacy Control, or on request by email); to limit use of sensitive personal information (we do not use it beyond providing the Service); and not to be discriminated against for exercising these rights. We honor Global Privacy Control signals as an opt-out of sale or sharing. You may designate an authorized agent by giving them written permission that we can verify.

Other U.S. states

Residents of states with comprehensive privacy laws (including Virginia, Colorado, Connecticut, Utah, Texas, Oregon, and others) have comparable rights to access, correct, delete, and port data and to opt out of targeted advertising and sale. We do not sell personal data. The ad measurement in Section 8 may count as targeted advertising in some states; it is on by default for United States visitors, and the "Do Not Sell or Share My Personal Information" link at the foot of every page, Global Privacy Control, Do Not Track, or an email to us opts you out. If we decline a request, you may appeal by replying to our response, and we will explain the outcome in writing.

// 12. INTERNATIONAL TRANSFERS

We are based in the United States and our providers are in the United States. If you use the Service from elsewhere, your data is transferred to and processed in the United States, where privacy laws may differ from yours. For transfers from the EEA, UK, or Switzerland we rely on standard contractual clauses with our providers and, where applicable, the EU-U.S. Data Privacy Framework participation of those providers. You may ask us for details of the safeguards in place.

// 13. CHILDREN

The Service is for adults. You must be 18 or older to create an account. We do not knowingly collect personal data from anyone under 18, and never from anyone under 13. If you believe a minor has given us data, contact us and we will delete it.

// 14. MOBILE APPS

Our iOS and Android apps collect the same categories described above and nothing beyond what the app's store listing discloses. The apps do not access your contacts, photos, microphone, camera, or precise location. Any data the app stores on your device is protected by the platform's encryption. Apple's App Privacy labels and Google Play's Data Safety section for our apps are kept consistent with this policy. In-app purchases made through the app stores are subject to the store's payment terms.

// 15. CHANGES

We will update this policy as the Service changes. Material changes will be announced by email or in the Service at least 14 days before they take effect. The date at the top shows the current version.

// 16. CONTACT

QuantGPT LLC
15350 N Florida Ave
Tampa, FL 33613
desk@quantgpt.co