Commercial Redistribution Terms

1. Relationship to other terms

These Commercial Redistribution Terms supplement the FXMacroData Terms of Service, Privacy Policy, and any order form, invoice, written Enterprise agreement, or signed amendment between you and FXMacroData. If there is a direct conflict, the signed written agreement controls, followed by these Commercial Redistribution Terms, then the general Terms of Service.

The Commercial Redistribution add-on is a display license. It is not a wholesale data-vendor license, marketplace listing license, bulk data license, feed license, or right to build a substitute for the FXMacroData API or datasets.

2. Definitions

• Customer means the business, organization, or individual that holds an active Commercial Redistribution add-on.
• Registered Surface means any customer-facing website, web app, Telegram channel, email newsletter, Discord or Slack community, mobile app, private community, report, or other display channel saved by the Customer in API Management.
• Registered Website means a website Registered Surface measured automatically by the FXMacroData redistribution pixel.
• Self-Reported Surface means a non-web Registered Surface whose additional deduplicated audience is reported by the Customer in API Management.
• Authorized Product means the Customer's customer-facing product or publication across one or more Registered Surfaces.
• FXMD Data means FXMacroData API responses, datasets, indicators, calendars, market data, COT data, metadata, documentation-derived data, and any substantially similar machine-readable output obtained from FXMacroData.
• Displayed Output means charts, tables, calendars, indicators, written commentary, alerts, and other human-facing product views that incorporate FXMD Data without exposing the underlying raw feed.
• Derived Data means any transformed, normalized, aggregated, enriched, combined, calculated, or reformatted data produced from FXMD Data.
• End User means a visitor, customer, subscriber, employee, client, or other person who can access the Authorized Product.

4. Registered distribution surfaces

The Customer must register every customer-facing distribution surface that displays FXMD Data or Derived Data in API Management. A Customer may register any number of website domains, Telegram channels, email newsletters, chat communities, mobile apps, private communities, and other display surfaces under one Commercial Redistribution account.

• All Registered Surfaces share one account-level billing meter. The combined unique audience, not the number or type of surfaces, determines the add-on quantity.
• Website domains use automatic pixel measurement. Non-web surfaces use the Customer's self-reported additional unique audience.
• Branded portals, embedded displays, client portals, newsletters, chat channels, and mobile apps are included when they present human-readable Displayed Output and do not expose a raw data feed or substitute API.
• Adding or removing a Registered Surface does not add a separate licence fee and does not enter a review queue.
• The Customer must not spoof, obscure, proxy, strip, falsify, or manipulate domain, origin, referrer, pixel, attribution, or telemetry signals used to verify compliance.

Self-service Commercial Redistribution covers customer-facing display through websites, web apps, Telegram, email newsletters, Discord, Slack, mobile apps, private communities, and other registered display channels on the same transparent per-user pricing.

5. API key security

Commercial Redistribution API keys are server-side secrets. The Customer must keep each API key confidential and must call FXMacroData from backend systems under the Customer's control.

The Customer must notify FXMacroData promptly if a key is exposed or suspected to be exposed, rotate the affected key, remove the exposure, and cooperate with any remediation required to protect FXMacroData systems and data.

6. Allowed uses

Commercial Redistribution allows the Customer to show FXMD Data as Displayed Output inside the Authorized Product, provided the output is not a substitute data product and cannot reasonably be used to reconstruct a bulk dataset or API feed.

• Customer-facing charts, tables, dashboards, market calendars, indicator panels, widgets, and alert views.
• Customer-facing Telegram posts, email newsletters, Discord or Slack messages, mobile-app views, private-community posts, and downloadable human-readable reports.
• Written market commentary, research summaries, tooltips, and explanatory text generated from FXMD Data.
• Customer-facing AI-generated summaries, automatic translations, and derived analytical scores or probabilities, provided they remain human-readable Displayed Output, include required attribution, and cannot be used to reconstruct FXMD Data.
• Server-side caching required for reasonable performance, subject to the caching limits below.
• Limited screenshots or website reports where the FXMacroData attribution remains visible and the data is presented for human reading rather than machine redistribution.

7. Prohibited uses

The Customer must not use Commercial Redistribution to resell, mirror, proxy, syndicate, or republish FXMD Data as a data source. The Customer must not:

• Create a public or customer-facing API, GraphQL endpoint, webhook, SDK, query tool, database connector, MCP server, or feed that exposes FXMD Data or Derived Data.
• Offer raw JSON, CSV, XLSX, Parquet, database, warehouse, FTP, SFTP, bucket, ZIP, archive, or bulk download access to FXMD Data or Derived Data.
• Build or operate a service that is a substitute for FXMacroData, including by changing endpoint names, formats, schemas, branding, table names, or delivery mechanisms.
• Populate, maintain, or sell a permanent database, warehouse, historical archive, benchmark, index, signal library, or dataset derived from FXMD Data.
• Provide white-label raw-data pass-through access, sublicensing, reseller data feeds, or tenant-specific APIs that expose FXMD Data or Derived Data as a data source. Human-readable presentation inside branded or client-facing products remains allowed.
• Remove required attribution, hide attribution, block the redistribution pixel, manipulate measured users, under-report exposure, or otherwise interfere with billing and compliance controls.
• Use FXMD Data to train, fine-tune, publish, benchmark, or distribute a machine learning model, dataset, embedding set, retrieval corpus, or AI product that can reproduce, extract, or redistribute the underlying data.
• Use FXMD Data for illegal activity, abuse, service disruption, unauthorized security testing, scraping, excessive polling, or attempted circumvention of rate limits or access controls.

9. Pixel, attribution, and billing meter

Registering any distribution surface enables self-service access immediately. The Customer must then install the FXMacroData redistribution pixel on every website page or application module that displays FXMD Data or Derived Data and maintain visible FXMacroData attribution wherever that output is displayed. The pixel is not required on unrelated pages or on non-web Registered Surfaces. Pixel verification is an automatic measurement and compliance check, not an approval step or launch gate.

• Billing is based on the combined unique audience across all Registered Surfaces in each billing period, not page views, domain count, channel count, registered accounts, or seats.
• Website audience is measured automatically as unique non-bot users. In API Management, the Customer reports the additional unique people reached through all non-web surfaces after excluding anyone already counted by the website pixel.
• The Customer may update the self-reported additional audience at any time. The latest report for the billing period is used for the non-web part of the combined audience total.
• Single-page applications may use exposure metering for sections that actually display FXMD Data, but the Customer must not under-meter product areas where FXMD Data is visible.
• If measurement, self-reporting, or attribution is missing, blocked, manipulated, or removed, FXMacroData may estimate usage from available telemetry, invoice under the applicable plan, or pause access for a material breach.

10. Usage limits and request caps

Commercial Redistribution does not carry its own API request allowance and does not change the limits of the plan it is added to. The Customer's Individual or Enterprise subscription sets the request budget; the add-on sets where FXMD Data may be displayed and how the audience is billed.

The allowance is deliberately independent of audience size. Section 11 requires the Customer to call FXMacroData from its own server-side systems and to cache responses, so a compliant Authorized Product makes calls in proportion to the data it displays and how often that data is refreshed — not in proportion to the number of End Users who view it. A product whose request volume rises with its audience is passing FXMD Data through to End Users, which is outside the licence granted in section 3.

The applicable subscription limits, including the fixed operational guards of 300 requests/minute, 5,000 requests/hour, and 20 concurrent in-flight requests, are published in the rate-limit guide. Client portals, newsletters, chat channels, apps, reports, and other Registered Surfaces draw on that same allowance. The number or type of Registered Surfaces does not change the request allowance or licence fee.

FXMacroData may also apply endpoint-specific limits, response-size limits, historical lookback limits, row limits, anti-abuse controls, and throttling where necessary to prevent API mirroring, excessive polling, service degradation, or usage outside the licensed scope.

11. Caching, storage, and deletion

The Customer may cache FXMD Data only as reasonably necessary to operate the Authorized Product efficiently and reliably. Caching must not become a substitute dataset, permanent warehouse, replicated database, or independent data product.

• Raw API responses may be cached for up to 24 hours.
• Displayed Output and aggregated or derived product views may be cached for up to 30 days if they cannot be used to reconstruct a raw dataset or machine-readable feed.
• Full-catalog replication, historical backfilling for resale, warehouse loading, database sharing, and retained archives of raw FXMD Data are not permitted under Commercial Redistribution.
• On termination or expiration of the license, the Customer must stop using FXMD Data and delete raw API responses, caches, exports, replicas, and stored FXMD Data within 30 days, except where applicable law requires a different retention period.

12. Audit, monitoring, and enforcement

FXMacroData may monitor API usage, pixel events, attribution status, Registered Surface activity, self-reported audience totals, error patterns, request volume, and other service telemetry to verify compliance. FXMacroData may also review publicly accessible Registered Surfaces and request reasonable compliance information, including screenshots, sample product URLs, sample messages, sample logs with secrets removed, and confirmation that API keys are kept server-side.

If FXMacroData reasonably believes the Customer is exceeding the license scope, exposing a key, creating a substitute product, distributing through a marketplace, under-metering, or otherwise violating these terms, FXMacroData may throttle requests, disable the redistribution API key, suspend access, require remediation, invoice for unmetered use, or terminate the license.

13. Suspension and termination

FXMacroData may suspend or terminate Commercial Redistribution immediately for non-payment, suspected key exposure, security risk, API abuse, missing pixel or attribution, marketplace redistribution, raw data resale, public API mirroring, white-label pass-through, or any other material breach of these terms.

Termination does not relieve the Customer of payment obligations incurred before termination, confidentiality obligations, deletion obligations, audit cooperation, or restrictions on further use and redistribution of FXMD Data.