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 with storage and retention rights under section 11. It does not grant the right to resell or supply the underlying data to third parties as a dataset, API, feed, bulk download, or warehouse share.

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 or through the FXMacroData audience reporting endpoint.
• Public Feed Surface means a Registered Surface that publishes to an open audience through a public profile, channel, or broadcast — including social platforms, video platforms, public forums, and streaming or broadcast media — where no subscriber list or signed-in audience can be counted.
• Declared Reach means the follower, subscriber, or audience count the Customer declares for a Public Feed Surface.
• Authorized Product means the Customer's customer-facing product or publication across one or more Registered Surfaces.
• FXMD Data means FXMacroData API responses, datasets, and any substantially similar machine-readable output obtained from FXMacroData, in every endpoint family, including: official announcements and releases with their revisions, vintages, and timestamps; forecasts, consensus, and expectations (official forecaster surveys, central-bank and institutional projections, nowcasts, market-implied expectations, and FXMacroData's own forecasts); release calendars; FX reference rates; bond yields and curves; commodities; COT data; central-bank press releases; market-session data; metadata and data-quality fields; documentation-derived data; and values FXMacroData calculates from any of these, such as changes, differentials, and surprises.
• 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, client, an employee of the Customer's client or customer, or another external person who can access the Authorized Product. It does not include the Customer's own employees when they access FXMD Data solely for the Customer's internal operations.

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 contribute to one account-level add-on quantity. Websites, signed-in apps, bots, newsletters, private channels, and reports use blocks of up to 100 measured or reported users or recipients. Public Feed Surfaces use blocks of up to 1,000 declared followers. Registering more surfaces does not itself add a fee.
• Website domains use automatic pixel measurement. Surfaces with signed-in users, such as mobile apps and messaging bots, report one identity per unique end user from the Customer's own systems. Broadcast surfaces such as newsletters and channels report a subscriber count. Public Feed Surfaces declare a follower count.
• Distributing an application through a third-party directory, marketplace, or app store — for example a Slack app, a Telegram bot listing, a browser extension, or a custom GPT — is permitted as a Registered Surface. The restriction in section 8 applies to the listing exposing FXMD Data as a feed or dataset, not to the application being listed.
• A syndication feed such as RSS or Atom is a Registered Surface when it carries human-readable headlines and summaries. A feed that carries structured values, numeric fields, or machine-parsable records is a data feed and is not permitted under this licence.
• 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. Each channel uses the audience rule above and contributes blocks to the same account-level quantity.

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.
• Storage, caching, database replication, historical backfills, warehouses, backups, and audit records for internal use and operating the Authorized Product, subject to section 11.
• 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 resell or otherwise supply the underlying FXMD Data to third parties as an independent data source, whether paid or free. This restriction applies to all or part of a dataset, including reformatted or derived versions that expose or allow reconstruction of the underlying data. Storage for internal use and operating the Authorized Product is permitted under section 11. The Customer must not:

• Create a public or customer-facing API, GraphQL endpoint, webhook, SDK, query tool, database connector, MCP server, or feed that supplies the underlying FXMD Data as an independent data source. Backend endpoints used solely to deliver permitted Displayed Output within the Authorized Product are allowed.
• Offer third parties raw JSON, CSV, XLSX, Parquet, database, warehouse, FTP, SFTP, bucket, ZIP, archive, or bulk download access to the underlying FXMD Data, including derived versions that allow its reconstruction.
• Build or operate a service that is a substitute for FXMacroData, including by changing endpoint names, formats, schemas, branding, table names, or delivery mechanisms.
• Sell, license, share, or otherwise distribute a database, warehouse, historical archive, or dataset containing the underlying FXMD Data to third parties as a data product. Keeping such stores for internal use or to serve permitted Displayed Output is allowed.
• 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.
• Supply a machine learning model, dataset, embedding set, retrieval corpus, or AI product to third parties in a way that enables them to reproduce, extract, or redistribute the underlying FXMD Data as a data source.
• 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. Where FXMD Data names the publishing institution of a figure, the Customer should keep that institution's name with the figure, for example "Source: Bank of Canada, via FXMacroData". 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 audience blocks contributed by all Registered Surfaces in each billing period, not page views, domain count, channel count, registered accounts, or seats.
• After any applicable trial, the minimum monthly charge is one USD 10 audience block from 0 users. There is no free-user or 250-user allowance. The first paid block covers 0 to 100 measured or reported users or recipients, or 0 to 1,000 declared followers for a Public Feed Surface.
• 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.
• One USD 10 block covers up to 100 measured or reported users. For a Public Feed Surface, one USD 10 block covers up to 1,000 declared followers, because a public post reaches only a fraction of a following. Both convert into the same block quantity on one invoice line.
• Declared reach is summed across every Public Feed Surface without an overlap deduction. Audience overlap between separate public platforms is not measurable, and the Customer is not asked to estimate it.
• The Customer declares the follower or subscriber count for each Public Feed Surface at registration and keeps it current. FXMacroData may verify a declared figure against the public profile and may correct the billable quantity where the declared figure is materially understated.
• Audience size, including measured users, reported users or recipients, and Declared Reach, does not change the monthly API request allowance. The Customer's underlying Individual or Business plan sets that allowance.
• 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

Solo engineers and one-person commercial projects may use Individual as their base plan. Business is for incorporated businesses with two or more people; the Customer's app users, subscribers and other audience members are not Business seats. 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 Business 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. The Customer must keep API access server-side as required by section 5. Caching, persistent storage, and incremental refreshes are recommended to reduce repeated requests, but there is no mandatory cache duration. Request volume must remain within the underlying plan's limits; increasing audience size does not by itself establish prohibited data resale or pass-through.

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 of Registered Surfaces does not itself change the request allowance or licence fee; the audience blocks contributed by those surfaces set the add-on quantity.

FXMacroData may also apply endpoint-specific limits, response-size limits, historical lookback limits, row limits, anti-abuse controls, and throttling where necessary to prevent unauthorized third-party data feeds, excessive polling, service degradation, or usage outside the licensed scope. These controls do not impose a retention limit on data lawfully retrieved.

11. Storage and retention

The Customer may store and retain FXMD Data lawfully obtained while its subscription was active for internal use and to operate the Authorized Product. FXMacroData imposes no maximum retention period on raw responses, historical records, Derived Data, or Displayed Output. Applicable publisher conditions and legal requirements continue to apply.

• Permitted storage includes databases, replicas, private cloud warehouses, historical archives, backups, research and backtesting stores, and compliance or audit records. The Customer may retain event names, scheduled times, actual, forecast and previous values, and related alert records for multiple years or indefinitely. No separate retention addendum is required.
• The Customer may retrieve and store the full history and catalogue available under its plan, subject to the plan's access and request limits. Storage providers and contractors may process the data on the Customer's behalf under access controls and confidentiality obligations, without independent reuse or resale rights.
• Stored data may support customer-facing charts, calendars, alerts, reports, and analytical products while the applicable Commercial Redistribution license remains active. Registration, attribution, audience measurement, and the restrictions on supplying underlying data to third parties continue to apply.
• When cancellation, termination, or expiry of Commercial Redistribution takes effect, lawfully obtained data may be retained and used solely for the Customer's internal purposes, including research, backtesting, backups, compliance, and audits. FXMacroData does not require routine deletion or purge of those internal copies. Retention does not permit continued customer-facing use or redistribution of any stored copy, historical record, Derived Data, or Displayed Output. Section 13 requires external access and delivery to stop. New retrievals and updates require an active underlying subscription and do not restore redistribution rights.
• Reports and alert records lawfully delivered before the license ended may remain in the recipients' own internal or compliance records. This does not permit the Customer to keep hosting those records for external access, deliver them again, or otherwise continue redistribution after the license ends.
• Storage and retention do not authorize raw-data resale, substitute APIs or feeds, bulk data distribution, or warehouse sharing with third parties as a data product. The publisher conditions and source rights in section 3 continue to apply during and after the subscription.

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.

All redistribution rights under this agreement end when cancellation, termination, or expiry takes effect. The Customer must then stop supplying, displaying, publishing, or otherwise making FXMD Data, Derived Data, and Displayed Output available to End Users or other third parties, whether paid or free. This applies equally to data copied, downloaded, cached, archived, or stored before the license ended; the age of the data and the absence of new API calls do not extend the license.

The Customer must remove or disable external access to that output on its websites, apps, dashboards, embeds, hosted reports, and other distribution surfaces, and stop further alerts, messages, reports, and other deliveries containing it. Keeping the underlying subscription active, changing the format, or serving the data from the Customer's own database or warehouse does not permit continued redistribution without an active Commercial Redistribution license.

The Customer may retain lawfully obtained copies solely for internal use under section 11. Payment obligations incurred before termination, confidentiality obligations, audit cooperation, applicable publisher conditions, and restrictions on onward data resale and redistribution survive. The source rights preserved in section 3 remain unaffected.