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 plan 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 subscribes to Commercial Redistribution.
• Approved Domain means the website domain saved and accepted in API Management for the Customer's commercial redistribution use.
• Authorized Product means the Customer website, app, dashboard, portal, report, or product surface operated on an Approved Domain and using FXMacroData under these terms.
• 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. Approved Domain requirement

The Approved Domain is the unique identifier for Commercial Redistribution setup and metering. The Customer must register the production domain in API Management before using the redistribution API key in a customer-facing product.

• Use is limited to the Approved Domain and the Authorized Product associated with that domain.
• A separate root domain, product, client portal, tenant domain, white-label deployment, embedded third-party site, broker portal, or materially different product experience requires prior written approval from FXMacroData.
• The Customer must not spoof, obscure, proxy, strip, falsify, or manipulate domain, origin, referrer, pixel, attribution, or telemetry signals used to verify compliance.

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.
• Written market commentary, research summaries, tooltips, and explanatory text generated from FXMD Data.
• Server-side caching required for reasonable performance, subject to the caching limits below.
• Limited screenshots, reports, or pages 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. Without prior written approval from FXMacroData, 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 pass-through access, sublicensing, reseller access, broker platform feeds, client-specific portals, or tenant-specific redistribution outside the Approved Domain.
• 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, security testing without approval, scraping, excessive polling, or attempted circumvention of rate limits or access controls.

9. Pixel, attribution, and billing meter

The Customer must install the FXMacroData redistribution pixel on the Approved Domain and maintain visible FXMacroData attribution wherever FXMD Data is displayed. API access may remain disabled, paused, or throttled until FXMacroData detects valid pixel events and visible attribution.

• Billing is based on measured monthly unique non-bot website users, not page views.
• 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 the pixel or attribution is missing, blocked, manipulated, or removed, FXMacroData may pause the API key, estimate usage from available telemetry, invoice under the applicable plan, or require remediation before restoring access.

10. Usage limits and request caps

Unless a written order form or Enterprise agreement states otherwise, Commercial Redistribution includes a monthly API request allowance that scales with the same 1,000-user blocks used for billing. The first 1,000 measured monthly users include 100,000 API requests per month. Each additional 1,000 measured-user block adds 50,000 API requests per month, up to a 500,000 request/month self-serve cap.

Each additional 1,000 measured-user block adds 50,000 API requests per month. Commercial Redistribution also has fixed operational guards of 300 requests/minute, 5,000 requests/hour, and 20 concurrent in-flight requests. Higher usage, multiple domains, client portals, raw feeds, warehouse shares, or broader redistribution require Enterprise terms.

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 unless FXMacroData approves a longer period in writing.
• 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 require separate written Enterprise terms.
• 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 a signed agreement or applicable law requires a different retention period.

12. Audit, monitoring, and enforcement

FXMacroData may monitor API usage, pixel events, attribution status, domain activity, error patterns, request volume, and other service telemetry to verify compliance. FXMacroData may also crawl or review the Approved Domain and request reasonable compliance information, including architecture descriptions, screenshots, sample product URLs, 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.