i18n Launch Language Research — Raxx

Status: research-only. This document does NOT constitute legal or tax advice. Before filing, acting, or making launch decisions based on this research, consult a business/securities attorney licensed in each relevant jurisdiction, a Quebec-registered language-compliance counsel, and a CPA familiar with international SaaS tax obligations. Last updated: 2026-05-09 UTC. Sources as of that date — verify freshness before counsel meeting. Related issue: https://github.com/raxx-app/TradeMasterAPI/issues/1463

TL;DR (3 sentences)

English-only is defensible and sufficient for a US-first v1 launch on 2026-05-23 UTC, but any Canadian customer intake — including passively accepting Canadian signups — triggers a Quebec French obligation that carries fines up to CAD $30,000/day and was enforceable as of June 1, 2025. EU markets (Germany, France, Spain, Netherlands) each require local-language risk disclosures and ToS for retail investment clients, with MiFID II overlay adding prescribed investor-warning obligations in local language. The operator should not make a final tier-1 launch language decision without a 30-minute call with a securities-and-language-compliance attorney: the Quebec question alone could force a French sprint before any Canadian marketing begins.

Section 1 — Target Markets: Jurisdiction × Language Matrix

Evaluation Key

• Day-1: Launch at v1 (2026-05-23 UTC). Regulatory path is clear or English-only is tolerated.
• Soon-after: Launch within 60–90 days post-v1. Regulatory obligations are manageable but require prep.
• Defer: Significant regulatory licensing, local-language translation, or country-specific legal counsel requirements make near-term launch inadvisable.

1.1 United States

Notes: Raxx is NOT a registered investment adviser at this writing (status pending; final determination for licensed securities counsel per docs/legal/research/ai-strategy-execution-risks-2026-04-29.md). The SEC staff position (Reg BI FAQ, sec.gov) permits simultaneous foreign-language plus English delivery; English-only is not prohibited. California has Spanish-language disclosure requirements for certain consumer financial products (California Financing Law, DFPI) but those apply primarily to lending and financing transactions, not investment-advisory SaaS. Confirm applicability with CA-licensed securities counsel.

Sources: - SEC Marketing Rule FAQ: https://www.sec.gov/rules-regulations/staff-guidance/division-investment-management-frequently-asked-questions/marketing-compliance-frequently-asked-questions - SEC Reg BI FAQ on foreign-language delivery: https://www.sec.gov/rules-regulations/staff-guidance/trading-markets-frequently-asked-questions/faq-regulation-best - CA DFPI state-licensed investment adviser: https://dfpi.ca.gov/regulated-industries/broker-dealers-and-investment-advisers/state-licensed-investment-adviser/

1.2 Canada (English-speaking provinces)

Notes: Any Canadian signup from a Quebec-resident user triggers Quebec Charter obligations (Law 14, Charter of the French Language, RSQ c C-11). If Raxx geo-accepts Canadian users without restricting Quebec, the French obligation is live on signup acceptance.

1.3 Canada — Quebec (deep dive in Section 3)

1.4 United Kingdom

Notes: Post-Brexit, MiFID II EU passporting does not extend to UK. A US company marketing to UK retail investors must either obtain FCA authorization or qualify under a specific exemption (e.g., "reverse solicitation"). This is NOT a language question — it is a licensing question that is independently disqualifying without prior FCA registration. Flag for securities attorney.

Sources: - FCA COBS 4 handbook: https://handbook.fca.org.uk/handbook/cobs4 - FCA Consumer Duty: https://www.skadden.com/insights/publications/2023/02/uk-adopts-a-new-consumer-duty

1.5 Australia / New Zealand

Notes: ASIC's Regulatory Guide 221 (digital financial services disclosure) applies to digital platforms. AFSL is required to provide "financial product advice" to retail clients — question for AU-licensed securities attorney on whether Raxx's signal layer constitutes "advice."

Sources: - ASIC financial product advice: https://www.asic.gov.au/regulatory-resources/financial-services/giving-financial-product-advice/ - ASIC financial product disclosure: https://www.asic.gov.au/regulatory-resources/financial-services/financial-product-disclosure/

1.6 Singapore

Notes: MAS Financial Advisers Act 2001 (FAA) requires a Financial Adviser's Licence for those providing financial advisory services. Exempt categories exist. This is a licensing question for SG-licensed securities counsel, not a language question.

Sources: - MAS FAA: https://www.mas.gov.sg/regulation/acts/financial-advisers-act - MAS Financial Advisers Licence: https://www.mas.gov.sg/regulation/capital-markets/apply-for-licensing-or-registration-of-capital-market-entities/financial-advisers

1.7 Germany

Notes: A non-EU firm actively targeting German retail clients typically needs a German license (BaFin authorization) or an authorized third-party distributor. The licensing process is 6–18 months. German is mandatory for retail client-facing disclosures. Verify with BaFin-licensed counsel.

Sources: - BaFin license requirement for non-EU firms: https://www.kronsteyn.law/en/non-eu-firms-german-bafin-licence - Cross-border marketing Germany: https://www.aosphere.com/products/cross-border-distribution/rulefinder-marketing-restrictions-asset-management/marketing-restrictions-germany/

1.8 France

Notes: Loi Toubon (1994) is France's language law; it pre-dates and supplements MiFID II. Commercial contracts and advertising in France must be in French. AMF has specific requirements for investment service providers. A US firm needs AMF approval or EU-passported authorization. Open question for French-licensed securities counsel.

Sources: - AMF home: https://www.amf-france.org/en (unsourced via web search — confirm with counsel) - Loi Toubon reference: Law 94-665 of August 4, 1994 (French Republic legislative record — verify freshness with French counsel)

1.9 Spain

Notes: Foreign investment firms must either obtain CNMV authorization or passport in from an EU member state. Post-Brexit, US firms cannot use UK passporting. Spanish language required for client-facing disclosures.

Sources: - CNMV guide for investment firm authorisation: https://www.cnmv.es/docportal/welcome/Guide_for_authorisation_BD_SB_PMC.docx - Baker McKenzie Spain authorization overview: https://resourcehub.bakermckenzie.com/en/resources/global-financial-services-regulatory-guide/europe-middle-east-and-africa/spain/topics/what-are-the-requirements-to-obtain-authorization-in-your-jurisdiction

1.10 Netherlands

Notes: Dutch-language privacy notice is effectively mandatory based on AP enforcement precedent even though GDPR Article 12 doesn't specify language explicitly.

Sources: - AFM sector investment page: https://www.afm.nl/en/sector/beleggingsondernemingen/vergunningen-en-meldingen - Dutch privacy notice enforcement (unsourced exact cite — confirm AP decision number with NL-licensed counsel): reference in IAPP article https://iapp.org/news/a/gdpr-lost-in-translation

1.11 Switzerland

Notes: Switzerland is not an EU member and does not have MiFID II obligations, but has a domestically equivalent regime (FinSA/FinIA). FINMA licensing is required; the Switzerland path is potentially accessible sooner than EU markets because of the client-consent-to-English mechanism.

Sources: - FINMA requirements: https://www.finma.ch/en/supervision/banks-and-securities-firms/requirements/ - Swiss FinSA overview: https://iclg.com/practice-areas/fintech-laws-and-regulations/switzerland/ (verify FinSA Article references with CH-licensed counsel)

1.12 Mexico

Notes: Mexican financial law (Ley del Mercado de Valores) prohibits foreign financial institutions from soliciting Mexican clients or offering offshore investments to the public in Mexico. This is a structural market-access barrier, not a language preference.

Sources: - Baker McKenzie Mexico authorization: https://resourcehub.bakermckenzie.com/en/resources/global-financial-services-regulatory-guide/north-america/mexico/topics/what-are-the-requirements-to-obtain-authorization-in-your-jurisdiction - Banxico FinTech regulation: https://www.banxico.org.mx/regulations-and-supervision/d/%7BBCED7618-FED0-6513-EB07-28D9B60CE0FC%7D.pdf

1.13 Brazil

Notes: LGPD applies to any platform that processes data of Brazilian residents regardless of where the platform is headquartered. The DPO must communicate with ANPD in Portuguese. Brazilian registered documents must be in Portuguese or accompanied by certified Portuguese translation.

Sources: - Brazil LGPD overview: https://termly.io/resources/articles/brazils-general-data-protection-law/ - LGPD international companies: https://markdmartin.com/lgpd-in-brazil-international-companies-compliance/ - Brazil investment rules (DLA Piper): https://www.dlapiperintelligence.com/investmentrules/countries/handbook.pdf?c=BR

1.14 Japan

Notes: JFSA FIBO registration is a multi-year process for retail market access. FMEO exists for wholesale/institutional entry, not retail. Japanese-language client materials are not optional for retail clients.

Sources: - JFSA guidebook for investment management registration: https://www.fsa.go.jp/en/policy/marketentry/guidebook/03.html - JFSA Financial Market Entry Office: https://www.fsa.go.jp/en/policy/marketentry/index.html - AMT Law FIBO registration June 2024: https://www.amt-law.com/asset/pdf/bulletins2_pdf/240627.pdf

1.15 South Korea

Sources: - Kim & Chang FSC English disclosure measures: https://www.kimchang.com/en/insights/detail.kc?sch_section=4&idx=26719 - Financial Services Regulation 2025 Korea: https://practiceguides.chambers.com/practice-guides/financial-services-regulation-2025/south-korea

Section 2 — Mandatory Translation Requirements by Market

All entries are research findings only. "Required" means the research suggests a mandatory obligation; "verify with local counsel" is always implied.

Section 3 — Quebec Deep Dive

Verify with Quebec-admitted attorney (Barreau du Québec member) before any Canadian marketing.

3.1 The Legal Foundation

Quebec's Charter of the French Language (RSQ c C-11, commonly called "Law 101") was modernized by Bill 96 / Law 14, which received assent June 1, 2022, with the bulk of digital/commercial provisions entering force June 1, 2025.

Primary source: Gouvernement du Québec — Modernization of the Charter of the French Language: https://www.quebec.ca/en/government/policies-orientations/french-language/modernization-charter-french-language

3.2 What Is Required

Based on research (localizejs.com article, McCarthy Tétrault blog, CFIB summary, Cozen O'Connor alert):

1. Commercial digital presence (websites, apps): If accessible from Quebec AND the operator "sells products or services" to the Quebec public, French version required. Content, presentation, and functionality must match the English version. A French-language chat support = required if English chat exists.

2. Contracts of adhesion (Terms of Service): ToS presented to Quebec consumers must be in French. The Final Regulation (under Bill 96) specifically addresses contracts concluded online — French version must be provided, and the requirement entered force July 11, 2024 (earlier than the June 1, 2025 general deadline).

3. Marketing and advertising: All promotional copy directed at Quebec residents must be in French. Bilingual is permitted but French must be "equally prominent."

4. Customer support: Service to Quebec clients must be available in French.

3.3 Threshold for Applicability

The research reveals three layers:

• Passive accessibility: If your website is accessible from Quebec, the French obligation arguably applies — the law says "sells to the Quebec public," not "actively targets."
• Employee headcount: Francization registration with OQLF is triggered at 25+ employees in Quebec (Bill 96 lowered from 50). This is an internal francization program trigger, not the commercial-document trigger.
• E-commerce conversions from Quebec: If you are accepting signups or payments from Quebec IP addresses / billing addresses, the commercial-document obligations are active.
• Foreign companies: The law does not explicitly exempt non-Canadian companies. McCarthy Tétrault's analysis says Bill 96 "didn't materially change" the pre-existing website obligation — which predates Bill 96 and applies to commercial operators generally. The ambiguity on whether purely foreign websites with no physical Quebec presence must comply is unresolved in published enforcement decisions — this specific question must go to Quebec-licensed counsel.

3.4 Penalties

• First offense: CAD $3,000 minimum — up to CAD $30,000/day per violation
• Second violation: double the fines
• Subsequent violations: triple the fines
• OQLF may issue compliance notices; criminal penalties can target individual company directors

3.5 French-Only or French-and-English?

Both are legally acceptable. French-only is compliant. French-and-English (bilingual) is compliant if French is equally prominent. English-only to a Quebec consumer in a commercial context is non-compliant once the service threshold is triggered.

3.6 Raxx-Specific Risk Scenarios

Sources: - McCarthy Tétrault Bill 96 blog: https://www.mccarthy.ca/en/insights/blogs/consumer-markets-perspectives/french-language-requirements-bill-96-and-june-1-2025-common-misconceptions - LocalizeJS Bill 96 digital requirements: https://localizejs.com/articles/quebec-bill-96 - CFIB Law 14 summary: https://www.cfib-fcei.ca/en/site/qc-law-14-bill-96 - Cozen O'Connor Final Regulations alert: https://www.cozen.com/news-resources/publications/2024/qu-bec-publishes-final-regulations-under-qu-bec-s-charter-of-french-language - Gouvernement du Québec modernization page: https://www.quebec.ca/en/government/policies-orientations/french-language/modernization-charter-french-language - DLA Piper Bill 109 (emerging — discoverability): https://www.dlapiper.com/en/insights/publications/2025/07/quebec-proposes-french-language-legislation-targeting-digital-platforms

Section 4 — EU Language Considerations

Final determination requires counsel licensed in each target EU member state. This section is a research summary only.

4.1 GDPR and Language

GDPR Article 12 requires privacy information to be provided "in a concise, transparent, intelligible and easily accessible form, using clear and plain language." GDPR does not specify which language, but:

• The Dutch Data Protection Authority (Autoriteit Persoonsgegevens) fined TikTok €750,000 for an English-only privacy notice on the grounds that Dutch children could not understand it (GDPR transparency principle, Article 12).
• This sets a practical enforcement precedent: local-language privacy notice is required wherever a platform markets to or accepts consumers in that country.
• Practical rule of thumb (not legal advice): If you accept users in Germany, France, Spain, or Netherlands, provide a privacy notice in German, French, Spanish, and Dutch respectively.

Sources: - IAPP GDPR language analysis: https://iapp.org/news/a/gdpr-lost-in-translation - TermsFeed privacy policy language: https://www.termsfeed.com/blog/privacy-policy-language/ - Securiti privacy notice language: https://securiti.ai/blog/privacy-notice-in-users-language/

4.2 MiFID II Language Requirements

MiFID II (Directive 2014/65/EU, transposed into national law in each member state) establishes that:

1. Client communications must be "clear, fair and not misleading" (Article 24(3))
2. Member states retain discretion on language of implementation for retail clients
3. The practical standard (confirmed by ESMA guidance and national-law transpositions) is: retail client disclosures, Key Information Documents (KID/PRIIP), and pre-contractual information must be in the local official language of the member state where the retail client is located

Country-by-country status (all require national-language retail disclosures):

Source: ESMA MiFID II Article 24: https://www.esma.europa.eu/publications-and-data/interactive-single-rulebook/mifid-ii/article-24-general-principles-and

4.3 MiFID II Prescribed Investor Warnings

MiFID II Annex II and implementing regulation prescribe specific investor categorization and appropriateness disclosure formats. The exact wording is left to national competent authority guidance (not ESMA-uniform). Each of BaFin, AMF, CNMV, and AFM has published local-language investor warning templates. This research cannot reproduce the exact prescribed text — obtaining the BaFin, AMF, CNMV, and AFM template libraries requires counsel licensed in each jurisdiction.

Open item for counsel: Obtain the prescribed investor-warning text from BaFin (German), AMF (French), CNMV (Spanish), AFM (Dutch) for each disclosure type Raxx would need to present.

4.4 Post-Brexit US→EU Passporting

A US-headquartered platform cannot use UK FCA authorization to passport into EU member states. Post-Brexit (December 31, 2020), UK is a third country relative to EU. Separately, a US company cannot use any single EU member state license to automatically passport across the EU without individual national-competent-authority notification under MiFID II's third-country firm provisions (Article 46 MiFID II — third-country firm regime). This is a structural market-access question for EU-licensed securities counsel, not a language question, but it controls whether language work for EU markets is worth doing pre-authorization.

Source: Norton Rose Fulbright MiFID II third countries: https://www.nortonrosefulbright.com/en/knowledge/publications/689b2b17/mifid-ii-mifir-series

Section 5 — Recommended Launch + Post-Launch Language Sets

Tier 1 — Launch (v1, 2026-05-23 UTC)

Recommendation: English-only

Rationale: 1. US market is the home market and English-only is legally sufficient for a US-first launch. SEC Marketing Rule does not mandate non-English. No US federal statute mandates non-English investment advisory content. 2. UK, Australia, New Zealand, and Singapore — all English-language markets, but all have their own licensing/registration prerequisites that are not yet confirmed as cleared. Language is not the blocker — licensing is. Launching to these markets without confirmed regulatory clearance is the risk. 3. Canada (non-Quebec) — English is sufficient for English-speaking provinces. Do not accept Quebec residents at v1 unless French parity is ready — the June 1, 2025 deadline for Bill 96 commercial document obligations has already passed. 4. No EU markets, no LATAM markets, no APAC non-English markets — each requires local-language translation AND prior regulatory registration/authorization that is not confirmed as cleared.

Quebec decision before launch: Operator must decide before 2026-05-23 whether to (a) geo-block Quebec at signup, (b) ship French parity by launch, or (c) accept the regulatory risk of English-only to Quebec users. This is the single most time-sensitive decision in this document. 2026-05-23 is 14 days away.

Tier 1 language set: English (en-US)

Tier 2 — Post-launch within 60–90 days (by ~2026-08-15 UTC)

Priority order:

1. French (fr-CA) — Quebec parity — Non-negotiable if Canada signups are accepted. Start the translation sprint immediately. Legal documents (ToS, Privacy Policy) should use professional human translation. UI strings can use MT (DeepL) + human review. Timeline: 6–8 weeks from decision.

2. French (fr-FR) — France — Loi Toubon compliance + AMF registration prerequisite. Do not activate FR market until AMF registration path is confirmed; but begin French translation work alongside fr-CA since the language overlap is ~70%.

3. Spanish (es-ES or es-419) — Spain (CNMV path) and potential Latin America (Mexico = deferred; Colombia, Chile, Argentina = separate research needed). Begin Spanish translation once fr work is underway. Same caveat: regulatory registration precedes market activation.

4. German (de-DE) — Germany is a large market but BaFin licensing timeline is 6–18 months. German translation can begin earlier to reduce time-to-market once authorization is confirmed.

Tier 2 language set: fr-CA, fr-FR, es, de

Tier 3 — Indefinite defer

Section 6 — Translation Provider Landscape

Cost estimates are approximate (2026 market rates). Verify with vendors directly. No vendor endorsement implied.

6.1 Translation Management Systems (TMS) — for UI strings and ongoing content

Recommendation for Tier 1 launch: Crowdin (free plan sufficient for English-only sprint; upgrade as Tier 2 languages are added). GitHub integration aligns with existing Raxx development workflow.

Sources: - LocalizeJS platform comparison: https://localizejs.com/articles/localize-competitors - intlpull.com TMS comparison 2025: https://intlpull.com/blog/lokalise-vs-phrase-vs-crowdin-vs-intlpull-2025 - Crowdin vs Lokalise (Tekpon): https://tekpon.com/insights/productivity-tools/collaboration/crowdin-vs-lokalise/

6.2 Translation Marketplace — for legal document translation (one-off)

For ToS + Privacy Policy + Risk Disclosure translations: Engage a specialized legal translation firm with financial-services experience in the target jurisdiction. Budget estimate: USD $500–$2,000 per document per language for professional legal translation (unsourced rate estimate — verify with 3 vendor quotes).

6.3 Machine Translation (MT) — for non-legal copy

Rule of thumb: MT + professional human review is acceptable for UI strings, in-app notifications, and marketing copy. Legal documents (ToS, Privacy Policy, regulatory risk disclosures) require professional human translation with a reviewer who has securities-domain knowledge in the target jurisdiction.

6.4 Recommended Tier 1 Stack

• TMS: Crowdin (free tier, GitHub integration)
• Translation approach: English-only at launch; no MT or human translation spend needed for v1
• Pre-Tier 2 prep: Internationalize the codebase (i18n framework in Antlers; Flask-Babel or equivalent in Raptor) during the v1 sprint so translation strings are extracted and ready for Crowdin import when Tier 2 work begins

Section 7 — Open Questions for Licensed Counsel + CPA

7.1 Questions for Securities + Language-Compliance Attorney

Priority 1 — Must resolve before v1 launch (2026-05-23 UTC):

1. Quebec geo-block vs. French parity: Does Raxx's current Canadian user acquisition (if any) trigger the Bill 96 / Law 14 commercial document obligation? Is a geo-block on Quebec residents at signup sufficient to eliminate the obligation? What implementation is defensible?

2. US regulatory status: Has the "investment adviser" registration question been resolved? SEC and/or state securities registration may be required before any marketing of Raxx's signal/automation layer. If unregistered, what is the permissible scope of customer-facing claims about the product's capabilities?

Priority 2 — Must resolve before any non-US launch:

3. UK financial promotion: Does Raxx's current product description constitute a "financial promotion" under FSMA 2000 (UK)? If so, which FCA exemption applies to a US-headquartered operator marketing to UK retail investors? Is an authorized-person approval arrangement (FPR gateway) required?

4. EU third-country firm regime (MiFID II Article 46): What is the most cost-effective authorization pathway for Raxx to serve retail investors in Germany, France, Spain, and Netherlands? Is a single EU member state authorization + passporting feasible, or does each country require separate registration?

5. MiFID II prescribed investor warning text: Obtain the current BaFin (German), AMF (French), CNMV (Spanish), and AFM (Dutch) prescribed investor warning phrasings for algorithmic trading and investment advisory tools.

6. Australia AFSL question: Does Raxx's product constitute "financial product advice" under Corporations Act 2001 (Cth) s 766B? If so, AFSL is required before accepting Australian retail clients.

7. SEC Marketing Rule past-performance claims: Raxx's backtesting feature produces historical performance data. Confirm that presenting backtested strategy results to retail clients complies with Rule 206(4)-1 (IA Marketing Rule) — specifically the 1-/5-/10-year period requirement and the prohibition on backtested performance without specific disclosures (Rule 206(4)-1(d)(2)).

8. California Spanish disclosure question: Confirm whether California DFPI regulations require Spanish-language disclosures for any financial product category Raxx falls into.

Attorney type recommended: Securities attorney with US investment adviser expertise (primary); Quebec language-compliance specialist (for Q1); EU MiFID II specialist if EU expansion is in the 12-month roadmap.

7.2 Questions for CPA / International Tax Advisor

1. VAT / GST collection obligations: When Raxx collects subscription fees from UK (20% VAT), EU (local VAT rates 19–25%), Australia (10% GST), Canada (5% GST + provincial), what are the registration and remittance obligations? Does the SaaS revenue threshold for mandatory VAT registration apply immediately at first EU customer or at a per-country threshold?

2. Permanent establishment risk: Does accepting customers in UK, EU, Australia, Singapore create a taxable "permanent establishment" in those jurisdictions? Is a BYOB broker-connection model enough to trigger PE?

3. Transfer pricing: If Raxx creates a separate entity for international operations, what transfer pricing documentation is required?

4. Brazilian withholding tax: Brazilian law imposes withholding taxes on software license payments to foreign entities under certain structures. Confirm applicability to SaaS subscriptions.

5. Currency and payment rails: What payment processors support multi-currency collection for a US-domiciled SaaS? Stripe Atlas vs. local entity — tax implications? (Stripe supports local currency collection; tax treatment of FX conversion is CPA-territory.)

Section 8 — Decision Matrix for Operator

This table is the 60-second read. All supporting detail is in Sections 1–7 above.

Timing / Deadlines

Sources

Full URL list:

• https://www.quebec.ca/en/government/policies-orientations/french-language/modernization-charter-french-language
• https://localizejs.com/articles/quebec-bill-96
• https://www.mccarthy.ca/en/insights/blogs/consumer-markets-perspectives/french-language-requirements-bill-96-and-june-1-2025-common-misconceptions
• https://www.cfib-fcei.ca/en/site/qc-law-14-bill-96
• https://www.cozen.com/news-resources/publications/2024/qu-bec-publishes-final-regulations-under-qu-bec-s-charter-of-french-language
• https://www.dlapiper.com/en/insights/publications/2025/07/quebec-proposes-french-language-legislation-targeting-digital-platforms
• https://knowledge.dlapiper.com/dlapiperknowledge/globalemploymentlatestdevelopments/2025/Quebecs-language-laws-changed-this-week-Heres-what-you-need-to-know
• https://www.nimdzi.com/quebec-language-regulations/
• https://www.smartbiggar.ca/insights/publication/quebecs-french-language-requirements-for-commerce-and-business-reform-of-the-charter-of-the-french-language
• https://www.esma.europa.eu/publications-and-data/interactive-single-rulebook/mifid-ii/article-24-general-principles-and
• https://www.esma.europa.eu/publications-and-data/interactive-single-rulebook/mifid-ii/annex-ii
• https://www.adverbum.com/post/mifid-ii-disclosure-translation-ensuring-terminology-consistency-for-compliance-2026
• https://handbook.fca.org.uk/handbook/cobs4
• https://www.skadden.com/insights/publications/2023/02/uk-adopts-a-new-consumer-duty
• https://www.nortonrosefulbright.com/en/knowledge/publications/689b2b17/mifid-ii-mifir-series
• https://www.sec.gov/rules-regulations/staff-guidance/division-investment-management-frequently-asked-questions/marketing-compliance-frequently-asked-questions
• https://www.sec.gov/rules-regulations/staff-guidance/trading-markets-frequently-asked-questions/faq-regulation-best
• https://www.sec.gov/files/rules/final/2020/ia-5653.pdf
• https://www.sec.gov/resources-small-businesses/small-business-compliance-guides/investment-adviser-marketing
• https://dfpi.ca.gov/regulated-industries/broker-dealers-and-investment-advisers/state-licensed-investment-adviser/
• https://www.asic.gov.au/regulatory-resources/financial-services/giving-financial-product-advice/
• https://www.asic.gov.au/regulatory-resources/financial-services/financial-product-disclosure/
• https://www.mas.gov.sg/regulation/acts/financial-advisers-act
• https://www.mas.gov.sg/regulation/capital-markets/apply-for-licensing-or-registration-of-capital-market-entities/financial-advisers
• https://www.mas.gov.sg/-/media/mas-media-library/regulation/faqs/cmi/faqs-on-exempt-persons/sfa-and-faa-faqs-on-exempt-persons.pdf
• https://www.kronsteyn.law/en/non-eu-firms-german-bafin-licence
• https://www.aosphere.com/products/cross-border-distribution/rulefinder-marketing-restrictions-asset-management/marketing-restrictions-germany/
• https://www.cnmv.es/docportal/welcome/Guide_for_authorisation_BD_SB_PMC.docx
• https://resourcehub.bakermckenzie.com/en/resources/global-financial-services-regulatory-guide/europe-middle-east-and-africa/spain/topics/what-are-the-requirements-to-obtain-authorization-in-your-jurisdiction
• https://www.afm.nl/en/sector/beleggingsondernemingen/vergunningen-en-meldingen
• https://iapp.org/news/a/gdpr-lost-in-translation
• https://gdpr-info.eu/
• https://www.termsfeed.com/blog/privacy-policy-language/
• https://securiti.ai/blog/privacy-notice-in-users-language/
• https://resourcehub.bakermckenzie.com/en/resources/global-financial-services-regulatory-guide/north-america/mexico/topics/what-are-the-requirements-to-obtain-authorization-in-your-jurisdiction
• https://www.banxico.org.mx/regulations-and-supervision/d/%7BBCED7618-FED0-6513-EB07-28D9B60CE0FC%7D.pdf
• https://termly.io/resources/articles/brazils-general-data-protection-law/
• https://markdmartin.com/lgpd-in-brazil-international-companies-compliance/
• https://www.dlapiperintelligence.com/investmentrules/countries/handbook.pdf?c=BR
• https://www.fsa.go.jp/en/policy/marketentry/guidebook/03.html
• https://www.fsa.go.jp/en/policy/marketentry/index.html
• https://www.amt-law.com/asset/pdf/bulletins2_pdf/240627.pdf
• https://www.kimchang.com/en/insights/detail.kc?sch_section=4&idx=26719
• https://practiceguides.chambers.com/practice-guides/financial-services-regulation-2025/south-korea
• https://www.finma.ch/en/supervision/banks-and-securities-firms/requirements/
• https://iclg.com/practice-areas/fintech-laws-and-regulations/switzerland/
• https://intlpull.com/blog/lokalise-vs-phrase-vs-crowdin-vs-intlpull-2025
• https://localizejs.com/articles/localize-competitors
• https://tekpon.com/insights/productivity-tools/collaboration/crowdin-vs-lokalise/
• https://crowdin.com/lokalise-alternative