getraxx.com DifferentiationSection — Securities + Advertising Copy Review

Status: research-only. This document does NOT constitute legal or tax advice. Before acting on any item below, consult a securities attorney licensed in Pennsylvania (and any state where Raxx markets to customers), an FTC advertising-law attorney, and — for any RIA-classification question — an Advisers Act specialist. Last updated: 2026-06-04. Primary-source citations as of that date — verify freshness.

TL;DR

The differentiation section copy is deliberately and carefully architected to avoid advisory-like language. Most of the risk it carries is not from being mistaken for an RIA — Raxx almost certainly does not meet the three-pronged investment-adviser definition — but from two narrower issues: (1) the D2 backtest card reads adjacent to a performance advertisement and would need a disclaimer cluster whether or not Raxx is an RIA, because the FTC substantiation standard applies to all advertisers and because state fraud statutes cover misleading financial claims broadly; and (2) the phrase "qualification record" in D3 carries a false-regulatory-certification connotation that an attorney should confirm is harmless or rewrite. Everything else is LOW-to-MED and addressable with a footer disclaimer block rather than copy surgery.

1. Regulatory Map — What Applies to Raxx

1.1 Is Raxx an Investment Adviser?

The Investment Advisers Act of 1940, §202(a)(11), defines an investment adviser as any person who, for compensation, engages in the business of advising others about the value of securities or the advisability of buying or selling them (SEC Release IA-1092, Oct. 8, 1987 — the controlling three-prong test).

Applying the three prongs to Raxx as currently described:

Conclusion (research-only): Based on publicly available guidance, Raxx's described functionality — user-defined parameters + backtested history + paper qualification + live enforcement against user's own broker account — does not appear to satisfy the "advice" prong of IA-1092. The platform is architecturally analogous to a rules-execution engine, not a portfolio manager. However, this conclusion is fact-specific and must be validated by a securities attorney before the product launches with live-trading features. The line between "enforces your rule" and "takes discretion on your behalf" can be narrow in practice.

Key risk factor: The "enforces them" language in D1 (examined in §2.1 below) is the phrase most likely to attract scrutiny on this prong. An attorney should confirm the factual architecture matches the copy claim — specifically that Raxx never independently decides to enter, modify, or exit a position.

Source: SEC Release IA-1092 landing page

1.2 Does the SEC Marketing Rule (Rule 206(4)-1) Apply?

SEC Rule 206(4)-1, the 2020 Marketing Rule (effective Nov. 4, 2022), governs performance advertising by investment advisers registered or required to be registered with the SEC. If Raxx is not an investment adviser (§1.1 above), Rule 206(4)-1 does not apply directly.

However: The Titan Global Capital enforcement action (SEC, Aug. 21, 2023) makes clear that the SEC will act against fintech platforms that are investment advisers and post misleading backtested performance to a general public website. Raxx must be confident it is not an investment adviser before relying on Rule 206(4)-1 non-applicability as a defense.

The important secondary point: Even if Rule 206(4)-1 does not apply, the FTC Act §5 substantiation standard does. Any performance-adjacent claim on a public website — including a backtest description — must be (a) truthful, (b) not misleading, and (c) substantiated. The same disclaimer logic the SEC requires of RIAs reflects what a prudent advertiser should carry anyway.

Sources: - SEC Rule 206(4)-1 Final Rule - SEC Marketing Rule FAQ - SEC v. Titan Global Capital, Press Release 2023-153

1.3 Does FINRA Rule 2210 Apply?

FINRA Rule 2210 applies to FINRA member firms (registered broker-dealers and their associated persons). Raxx is not a broker-dealer and is not a FINRA member. Rule 2210 does not apply directly.

The indirect relevance: FINRA 2210(d)(1)(F) prohibits predictions or projections of performance and the implication that past performance will recur. This reflects a widely-held standard for what a reasonable financial-services advertiser should not do. The phrase "See what the structure returned" (D2 heading) and "historical record of what these exact rules produced" (D2 body) do not predict or project — they describe historical results — which is the safer side of this line.

Source: FINRA Rule 2210 full text

1.4 CFTC / Commodity Trading Advisor (CTA) Exposure

A commodity trading adviser is any person who, for compensation, advises others about commodity interests (futures contracts, commodity options, swaps). Equity options are not commodity interests for CTA purposes — they are securities regulated by the SEC. Index futures and broad-based index options straddle this line, but Raxx's described product (IC builder, options on equities) falls under SEC, not CFTC, jurisdiction.

Caveat: If Raxx adds features involving futures contracts, forex, or commodity ETFs, CTA analysis would need to be re-run.

Source: CFTC CTA Intermediaries page; NFA CTA registration

1.5 State Securities Laws (Blue Sky)

Blue sky laws govern the offer and sale of securities and the registration of investment advisers and broker-dealers within each state. Raxx is not selling securities and (per §1.1) does not appear to be an investment adviser. Most state blue sky advertising rules that would restrict financial-performance claims apply to securities offerings and registered investment advisers, not SaaS tools.

The relevant state-level risk for Raxx is narrower: state consumer-protection and anti-fraud statutes, which apply to all commercial advertising and prohibit materially misleading claims regardless of whether the advertiser is a registered financial entity.

Pennsylvania: The PA Securities Act of 1972 (70 P.S. §1-101 et seq.) is administered by the PA Department of Banking and Securities. Its advertising restrictions target securities offerings and IA/BD conduct; they do not appear to create additional obligations for a non-registrant SaaS platform's homepage. However, the state's consumer-protection statute (UTPCPL, 73 P.S. §201-1 et seq.) covers unfair or deceptive trade practices broadly and would capture materially misleading performance claims.

New York (Martin Act): The NY Martin Act (N.Y. Gen. Bus. Law Art. 23-A) is one of the broadest state securities statutes and empowers the NY AG to prosecute fraud in connection with any security. The AG has brought actions against entities that are not formally registered as investment advisers. The Martin Act risk for Raxx is low as long as D2's backtest language is accurate and properly qualified — but non-trivial enough to warrant attorney confirmation.

California: The CA Corporate Securities Law (Corp. Code §25000 et seq.) and the CA Department of Financial Protection and Innovation (DFPI) regulate investment advisers and securities. The DFPI has jurisdiction over IA conduct for California-based customers. If Raxx accepts CA customers, it should confirm its non-IA status with California counsel.

Massachusetts + Texas: Both have aggressive securities enforcement. Massachusetts was the first state to bring an action against a robo-adviser (Robinhood, 2020). Texas has active merit-review and anti-fraud enforcement. The risk profile for Raxx in both states follows the same logic as California — confirm non-IA status before launch.

Sources: - PA Department of Banking and Securities — Laws & Regulations - NY Martin Act overview — LII - Blue Sky Laws by state — Acquisition Stars

2. Element-by-Element Redline

The eight copy elements are the section headline, sub-headline, and four cards (each with a heading + body). Each element is assessed for severity, the rule or doctrine it touches, and a suggested rewrite that preserves marketing intent.

Severity key: - LOW — Defensible as-is; no immediate rewrite required; consider tightening. - MED — Should be rewritten or disclaimed before flag flip; risk of misleading interpretation is plausible. - HIGH — Strong candidate for rewrite before any public exposure; potential enforcement or litigation hook.

Element 1 — Section Headline

Copy: "Not another trading tool."

Severity: LOW

Analysis: This is a product-category positioning statement. It is comparative in direction ("Not another...") but does not name competitors, does not make an objective measurable claim, and does not imply performance. Under FTC comparative-advertising standards (FTC Statement of Policy Regarding Comparative Advertising), the claim must be truthful and substantiated when it makes an objective comparison. "Not another trading tool" is a category claim, arguably puffery (non-measurable superiority claim). It does not require head-to-head substantiation.

Lanham Act note: The Lanham Act §43(a) private right of action requires a claimant to show the statement was false or misleading and likely to cause competitive injury. A category-positioning statement without specific competitor identification is very low risk.

Suggested rewrite: No change needed. Consider adding a period or em-dash for rhythm, but the copy is legally clean.

Element 2 — Sub-Headline

Copy: "Most platforms track what you made. Raxx tracks whether you stayed inside the structure you decided on before the trade was open."

Severity: MED

Analysis: "Most platforms" is a comparative claim. Under FTC substantiation standards, "most" is an objective quantitative assertion (not puffery) when it is verifiable. The FTC requires a "reasonable basis" before dissemination of objective comparative claims. (FTC Policy Statement on Advertising Substantiation)

The claim "most platforms track what you made" is directionally accurate — P&L tracking is indeed a primary feature of major retail brokerage and trading apps — but Raxx has not conducted a market survey to confirm it. Without substantiation on file, "most" creates a Lanham Act vulnerability if a competitor were to contest it.

The second half of the sentence — "Raxx tracks whether you stayed inside the structure you decided on before the trade was open" — is a product-description claim and is internally consistent with D1-D4 and with Raxx's architecture. No issue here.

Suggested rewrite (preserves intent, reduces substantiation risk):

"Traditional platforms track what you made. Raxx tracks whether you stayed inside the structure you decided on before the trade was open."

"Traditional" is a descriptive category term that does not make a quantitative comparative claim requiring substantiation. Alternatively, "P&L dashboards track what you made" further narrows the comparison to a feature rather than a class of competitor.

Element 3 — D1 Heading

Copy: "You chose the structure. Raxx makes sure you stay in it."

Severity: LOW

Analysis: This is a product-description claim about enforcement behavior. "Makes sure you stay in it" implies Raxx will actively intervene. The intervening mechanism should be technically accurate — if Raxx sends alerts or blocks order submission outside parameters, that is defensible. If Raxx's enforcement is advisory-only (alerts that the user can ignore), then "makes sure" slightly overstates the enforcement and could be challenged as misleading by a dissatisfied user.

Not an RIA trigger: This does not imply Raxx is making independent discretionary decisions. The structure was chosen by the user; Raxx is enforcing user-set parameters. This is analogous to a conditional order at a brokerage (a limit order "makes sure" you don't pay more than X). Courts and regulators have not treated conditional-order mechanics as RIA-equivalent discretion.

Suggested rewrite: Acceptable as-is. If "makes sure" overstates the enforcement in practice (it is actually alert-based rather than order-blocking), consider: "You chose the structure. Raxx holds you to it." or "...Raxx enforces it."

Element 4 — D1 Body

Copy: "Raxx does not suggest what to trade, recommend entries, or flag opportunities. It takes the entry, credit, and exit parameters you already decided on and enforces them when you are looking at the chart with a position open."

Severity: LOW — with one note

Analysis: The explicit disclaimer in the first sentence ("does not suggest what to trade, recommend entries, or flag opportunities") is the strongest available statement that Raxx is not providing investment advice. This is well-constructed and should be preserved verbatim. It is the key factual predicate for the non-IA argument.

The word "enforces": "Enforces them" raises the factual question of what enforcement mechanism exists. If enforcement means Raxx sends a visual/audio alert or prevents order submission outside parameters via the broker API, that is accurate. If enforcement means Raxx submits, modifies, or cancels orders autonomously without a user affirmative step, then "enforces" could be read as discretionary trading authority — which is the line where RIA analysis begins to apply. This is the most important factual/architectural checkpoint in this entire review. The copy is only defensible if the architecture matches: user sees alert / block, user takes action, broker executes.

Suggested rewrite: No change unless the product architecture is discretionary. If an attorney review is pending on the discretionary question, add "(You take action — Raxx provides the constraint)" as a parenthetical until the architecture is confirmed to be non-discretionary.

Element 5 — D2 Heading

Copy: "See what the structure returned before a dollar moves."

Severity: MED-HIGH

Analysis: "See what the structure returned" frames a backtest result as a definitive historical fact about returns. The word "returned" carries financial-performance connotation. Under FTC substantiation standards and industry norms for financial advertising, a performance claim — even a historical one — requires context about its limitations.

Key risk: The SEC has specifically flagged public-website performance advertising as a high-risk area. The Titan Global enforcement action (2023) found violations where a fintech RIA advertised performance results on a public website without adequate qualification. While Raxx is not an RIA, the same principle applies: a user reading "see what the structure returned" may reasonably interpret this as a claim about what their strategy will return. This is the closest the page comes to an implied performance promise.

Mitigating factors in the copy: The body text corrects this with "The result is the historical record... Not a projection." This corrective language is important and should be preserved. However, the heading sets the expectation before the user reads the corrective body text.

Suggested rewrite (preserves intent, reduces performance-promise read):

"See the structure's historical record before a dollar moves."

or

"Run your structure against history before it runs live."

The second option removes "returned" (financial-performance word) and reframes as "run against history" — an analytical tool rather than a profit claim.

Element 6 — D2 Body

Copy: "Before a structure runs live, Raxx runs it against 10+ years of real bars. The result is the historical record of what these exact rules produced — in your own parameters, on real market data. Not a projection."

Severity: MED

Analysis: This body text is well-constructed for the purpose. "Historical record" and "Not a projection" are the key corrective phrases that distinguish backtest from forecast. The phrase "what these exact rules produced" is accurate — it describes what the rules would have done historically, not what they will do in the future.

Two specific issues:

1. "10+ years of real bars" — This is a factual claim about data coverage. It must be substantiated: what data source, what instruments, what time period, is data survivorship-bias-adjusted? If the data has gaps, if certain instruments have shorter histories, or if survivorship bias inflates the results, "10+ years of real bars" becomes a misleading claim. The FTC requires pre-dissemination substantiation of factual claims. A footnote or disclaimer page documenting the data source and methodology should exist.

2. "Real market data" — This implies the data is not synthetic or adjusted. Confirm this is accurate (e.g., sourced from a licensed OHLCV provider, not adjusted close approximations that exclude dividends or splits in ways that would inflate backtest results).

Suggested disclaimer addition (on-page or linked): "Backtest results are based on historical data and do not represent live trading. Historical results have inherent limitations and do not guarantee future performance. Results vary by parameter settings, time period selected, and instrument."

Suggested copy tweak: Add "within the selected historical window" after "what these exact rules produced" to make the time-boundedness explicit.

Element 7 — D3 Heading

Copy: "Promote a structure when it earns it."

Severity: LOW

Analysis: "Earns it" is a product-UX framing. "Promote" is used in the product-workflow sense (paper → live). Neither phrase implies a regulatory gate or certification. The risk here is low.

Element 8 — D3 Body

Copy: "Every structure runs paper before it runs live. The paper ledger is not a sandbox — it is the qualification record. You flip to live when the structure has demonstrated what it does in conditions that resemble live."

Severity: MED

Analysis: "Qualification record" is the phrase that warrants attention. In regulatory and professional-certification contexts, a "qualification record" connotes a formal determination by a credentialing body that a person or system meets defined standards. A user encountering "qualification record" in a financial-platform context might interpret it as: - A record that qualifies the user to trade with Raxx approval, or - A Raxx-certified determination that the strategy is approved for live trading.

Neither interpretation is accurate. The paper ledger is a user-controlled performance history, not a regulatory or platform certification. If a regulator or plaintiffs' attorney were constructing a misleading-claim argument, "qualification record" is the phrase most likely to be characterized as implying a certification Raxx does not hold.

Secondary issue: "Conditions that resemble live" — paper trading does not fully replicate live conditions (no slippage, no partial fills, no market impact). This qualification should be acknowledged somewhere, though not necessarily in the marketing copy.

Suggested rewrite (preserves the architectural distinction, removes regulatory-certification connotation):

"Every structure runs paper before it runs live. The paper ledger is not a sandbox — it is the performance record that shows what the structure actually did under live market conditions. You flip to live when you have seen what it does."

Or more compactly:

"Every structure runs paper before it runs live. The paper ledger is your performance record — not a sandbox. You flip to live when the structure has earned it."

(This version loops back to D3 heading's language and avoids "qualification record" entirely.)

Element 9 — D4 Heading

Copy: "Raxx holds the structure. Your broker holds the money."

Severity: LOW

Analysis: This is a clean, accurate product-architecture description. It draws a clear distinction between Raxx's role (rule/parameter custody) and broker's role (asset custody). No advisory connotation, no performance claim, no custodial assertion for Raxx's benefit.

Element 10 — D4 Body

Copy: "Raxx connects to the broker you already use. Your account, your holdings, your P&L stay where they are. Raxx enforces the structure against that account — it does not move, custody, or hold any assets."

Severity: LOW — with one verification note

Analysis: "Does not move, custody, or hold any assets" is a factual claim about Raxx's architecture. This is accurate as described and is the correct disclaimer framing. However, it creates a fact-in-advertising obligation: Raxx must actually not have any mechanism — even transient — by which assets pass through Raxx-controlled infrastructure (e.g., a Raxx-controlled broker sub-account, a margin-call buffer, or a cash-management feature). If any such feature exists or is planned, "does not move, custody, or hold any assets" would become false advertising.

Disclaimer gap: The copy says what Raxx doesn't do (custody) but doesn't say what Raxx is. A footer disclaimer "Raxx is not a broker-dealer, custodian, or registered investment adviser" closes the loop and answers the implicit question a sophisticated user would ask.

Suggested copy: Acceptable as-is. The footer disclaimer handles the rest (see §3 below).

3. Required Disclaimers Punchlist

These disclaimers should appear on the getraxx.com page — either in the differentiation section itself, in a site-wide footer, or on a dedicated legal-disclosures page linked from the footer. Items marked (A) should be visible without a click. Items marked (B) may be linked.

Note on D-1: This is industry-standard language carried by all platforms that are not registered financial entities. Carrying it proactively pre-empts the most common regulatory inquiry and the most common user misconception. It should be a permanent footer element.

Note on D-2 through D-3: These are the minimum equivalent of what the SEC expects of a registered adviser publishing backtested performance. A non-RIA publishing backtest claims on a public website should carry at minimum the same substantive disclosures, even though not legally required to do so under Rule 206(4)-1, because (a) the FTC substantiation standard requires they be truthful and not misleading, and (b) state consumer-protection statutes in NY, MA, CA, and TX would treat a materially misleading financial performance claim as a deceptive practice regardless of RIA status.

4. Jurisdiction Flags

5. Timing / Deadlines

6. AI Framing Question

The copy does not reference AI. Per project_strategic_position and feedback_deterministic_execution_ai_augments, this is the correct posture for v1 — execution is deterministic, AI is opt-in and retrospective.

Research finding: There is no federal obligation for a non-RIA SaaS platform to disclose AI involvement on a marketing homepage. The EU AI Act (Articles 13-14, transparency obligations) does not apply because EU users are geo-blocked. GDPR Art. 22 (automated individual decision-making) would apply only if Raxx's AI features produce decisions with legal or similarly significant effects on an individual — which the described retrospective, analytical AI features do not.

One edge case to flag for attorney: If and when Raxx's AI features move from retrospective analysis to prospective alert generation (e.g., "your structure would have triggered here based on current conditions"), that crosses into the kind of individualized guidance that warrants reanalysis of the IA question and a disclosure review of the AI component.

For now: Not disclosing AI on the homepage is consistent with both the product positioning and the regulatory posture. No change recommended.

7. Questions for Your Securities Attorney

(Deliver this list to the attorney at engagement; these are the specific factual and legal questions this research cannot resolve.)

1. Non-IA confirmation: Does Raxx's architecture — user-defined parameters, backtest engine, paper qualification, live enforcement via broker API — satisfy all three conditions for non-investment-adviser status under IA-1092? Specifically: does any part of the "enforces them" functionality (D1) involve Raxx independently determining when to send an order signal without a concurrent affirmative user action?

2. Discretionary trading line: At what point in the product roadmap does Raxx's enforcement mechanism cross from "conditional alert" or "order-block" into "discretionary trading authority" that would trigger RIA or CTA registration? Where is that line technically and legally?

3. Martin Act (NY) exposure: Given that Raxx will have New York customers, does the D2 backtest copy as revised (with disclaimer block) adequately insulate the company from Martin Act exposure on performance advertising? Does the NY AG historically pursue non-registered entities for backtested performance claims?

4. D3 "qualification record" rewrite: Confirm whether the rewritten "performance record" language (proposed in §2, Element 8 above) eliminates any false-certification connotation. Any residual risk?

5. D4 factual accuracy: The copy states Raxx "does not move, custody, or hold any assets." Confirm this is architecturally accurate for all planned broker integrations, including any OAuth token flows, sub-account structures, or order-routing intermediaries. Any path through which Raxx transiently touches customer funds?

6. State-specific RIA confirmation: Pennsylvania, New York, California — does the federal non-IA analysis flow through to state registration exemption in each of these states, or does each state's definition of "investment adviser" require separate analysis?

7. Publisher's exclusion applicability: Does the §202(a)(11)(D) publisher's exclusion apply to Raxx's backtest-result display? (This is an alternative theory of non-IA status that could provide an additional layer of protection, but its scope is narrow and fact-specific.)

8. Timing of legal engagement: Given the live-trading feature is in the product roadmap, what is the earliest point at which a securities attorney must review the architecture before any broker API connection is established?

8. Questions for Your FTC/Advertising Attorney

1. "Most platforms" substantiation: What level of market research would be required to substantiate the claim "most platforms track what you made"? Is a competitive feature survey of the top 10-15 retail trading platforms sufficient, or does this require a consumer perception study?

2. Backtest substantiation file: What should be in the internal documentation supporting the D2 factual claims ("10+ years of real bars," "real market data") to satisfy FTC reasonable-basis standards? Is a data-provider agreement + methodology description sufficient?

3. Footnote vs. footer placement: For D-2 and D-5 (disclaimer language), is footer placement sufficient for FTC purposes, or must performance-related disclaimers be proximate to the performance claim (i.e., adjacent to the D2 card)?

9. Summary Redline Table

Sources

• SEC Investment Advisers Act of 1940 — govinfo.gov
• SEC Release IA-1092 (1987) — three-prong test
• SEC Rule 206(4)-1 Marketing Rule — Final Rule 2020
• SEC Marketing Rule FAQ — sec.gov
• SEC v. Titan Global Capital Management — Press Release 2023-153
• FINRA Rule 2210 — Communications with the Public
• FINRA Regulatory Notice 20-21 — performance advertising
• CFTC CTA registration — cftc.gov
• NFA CTA registration requirements
• FTC Policy Statement on Advertising Substantiation
• FTC Statement of Policy Regarding Comparative Advertising
• 17 CFR §230.156 — SEC Rule 156 (Investment Company Sales Literature)
• PA Department of Banking and Securities — Laws & Regulations
• PA Securities Act of 1972 — FindLaw
• NY Martin Act — LII Wex
• Blue Sky Laws — AcquisitionStars
• SEC Internet Adviser Exemption 2024 Final Rule
• Hypothetical Performance Compliance — Databento
• Troutman Pepper — SEC Marketing Rule: Hypothetical Performance
• Kitces — SEC Marketing Rule performance advertising
• Quebec Bill 96 website impact — Globallinkweb
• GDPR Art. 22 Automated Decision-Making — gdpr-info.eu
• Mayer Brown — First SEC Marketing Rule Enforcement Action

Before acting on any item in this document, consult a securities attorney licensed in Pennsylvania (and in any state where Raxx accepts customers), and an FTC advertising-law attorney. This document is research preparation material, not legal advice.