Privacy Policy

This Privacy Policy is issued by FXMacroData, a registered business name in Australia (ABN 97 837 657 289). FXMacroData is responsible for the personal information described below. Privacy questions can be sent to info@fxmacrodata.com.

This policy covers the FXMacroData website, accounts, API, MCP service and integrations you choose to use. An integration's permissions and data flows depend on its features and configuration. Your employer, the platform hosting an integration and any service you connect may also process information under their own policies.

Integration details: ChatGPT and MCP, Google Sheets, Google Workspace, Excel, Microsoft 365, Notion, messaging and webhooks, data and automation clients, browser extension and voice assistants. See also retention and your privacy choices.

1. Information We Collect

We receive information when you create or use an account, subscribe, contact us, use the website or API, authorize a connection, or run an integration. We also receive relevant account, payment, authorization and delivery information from providers. This includes:

• Contact Information: Name, email address, account and organization identifiers, communication preferences, support correspondence, and account or billing details supplied by you or our providers.
• Usage Data: Requested datasets and tool inputs, API and website activity, integration settings, request metadata, network addresses and credential identifiers. Some research tools process portfolio or scenario inputs. The sections below explain which content, authorization records and outputs each integration processes.
• Cookies and analytics: We use sign-in, language and pricing-display cookies, and browser storage for campaign, referral, landing-page, checkout and advertising-choice information. Google Analytics, Google Ads and Microsoft Advertising can also process browser and conversion information as described below. Integrations may separately save credentials and settings in browser, Office or Google storage. Blocking browser tracking does not itself stop server-side conversion or operational records, and blocking necessary sign-in cookies can prevent login.

2. How We Use Your Information

Your information is used to:

• Process your subscription and provide API access.
• Monitor and ensure the security and performance of the Service.
• Answer support requests, send service and billing messages, deliver requested alerts and manage optional product or newsletter communications.
• Measure usage, personalize relevant product features, understand acquisition and communication outcomes, and improve the service, as described below.

3. Data Sharing and Disclosure

We do not sell or rent your personal information. We disclose information to the providers, authorized recipients and integration destinations described in this policy, including:

• Service Providers: Google Cloud and Firebase for service operation and authentication, Stripe for billing, Google and Microsoft for the analytics or advertising described below, Cloudflare for delivery and security, Mailgun for email, and the AI and integration providers explained in the feature sections. Requested outputs also go to the platforms and recipients you choose.
• Legal Requirements: If required by law or to protect our rights or property.

4. Security

We use access controls, authenticated connections and HTTPS to help protect information. Protection and credential storage also depend on the integration and hosting platform; some client-side stores are not encrypted by the integration. Keep credentials out of shared files and messages, control workspace permissions and revoke credentials you no longer need. No method of transmission or storage is completely secure.

Accounts, API access and organizations

Google Firebase Authentication processes sign-in credentials and account identity. We keep account and contact details, authentication identifiers, API-key records, access permissions, subscription status, preferences and communication choices. Stripe processes checkout and payment details and supplies customer, subscription, invoice and payment records so we can provide access, handle billing and support, and prevent duplicate trials or abuse. Payment-card information is handled by Stripe rather than collected through integration tool inputs.

API, streaming, dashboard and MCP usage can be associated with your account, email, organization, seat, service account or partner identifier. Records include requested endpoint or tool, currency or indicator, request time, success or error status, usage volume, credential hashes or fingerprints, and network information. Account details and credential identifiers can also be copied into our analytics systems to relate usage to account access. We use these records for access limits, security, troubleshooting, customer support and product analysis. Website activity and saved preferences may also be used to identify currencies, pairs, indicators and articles of interest to you. Organization administrators may manage membership, roles, credentials and access within their organization.

FXMacroData Android and iPhone apps

The mobile apps use your existing FXMacroData account. Firebase Authentication processes your sign-in details, and the app reads your account's active API key to access data. Your key is kept in encrypted device storage on Android or the iOS Keychain on iPhone and sent over HTTPS. Signing out clears the locally stored key. Account and API usage records are handled as described above.

Release notifications are optional. If you enable them, Firebase Cloud Messaging processes an installation identifier and notification token, and we store the token, device platform and currency preferences with your account to deliver alerts. On iPhone, notification delivery also uses Apple's Push Notification service. You can change your currency choices in the app or turn off notifications in your device settings.

App analytics collection is disabled. Crash reporting is off by default. If you enable Share Crash Reports in Settings, Firebase Crashlytics processes crash reports, diagnostic information and installation identifiers to help us investigate failures. You can turn crash reporting off again in Settings.

To request deletion of your FXMacroData account and associated personal data, use Request Account Deletion in the app or email info@fxmacrodata.com from your account email address. This request concerns the shared FXMacroData account used on the website and in the app. We may verify your identity before processing it and will explain any records retained for legal, billing, dispute or security obligations. Uninstalling the app or cancelling a subscription does not itself delete the account.

Data, analytics, developer and automation integrations

This includes SDKs and command-line clients; Power BI, Tableau, Looker Studio, Grafana and other reporting tools; database, warehouse and streaming connectors; trading-platform extensions; and workflow services such as n8n, Make, Zapier, Pipedream and similar platforms.

• Requests and outputs: these integrations send selected datasets, currencies, indicators, time windows, filters and other request parameters to FXMacroData. Authenticated requests also use your API key or authorized connection. We return data and operational responses to the integration. General account, usage, network and retention practices in this policy apply.
• Where information is kept: credentials, configuration, workflow execution records, imported data, caches and checkpoints may be stored on your device, in your database or workspace, or by the platform you choose. Looker Studio saves its API key in Google Apps Script user properties. Platform administrators and collaborators may be able to access saved connection settings, workflow runs or imported results under that platform's permissions. FXMacroData does not gain general access to your databases, files or workflow history simply because a client requests our data.
• AI applications: when you ask a third-party AI application to analyze results, it may receive those results and any context you provide. Its provider controls that processing. Remote MCP connections are described in the dedicated section above.
• Credentials and controls: storage and credential transport vary by integration and version. Some clients send keys in HTTPS URL parameters rather than headers; URLs can be retained in browser, proxy or hosting logs. Do not share authenticated URLs. Remove saved credentials using the client's controls and revoke the key in API management if it should no longer authorize access. Uninstalling a client or removing a workflow does not necessarily erase its saved secrets, execution history, exported tables or backups. Manage those copies with the platform or its administrator.

ChatGPT plugin and MCP connections

This section applies when you connect FXMacroData to ChatGPT, Codex or another AI application through our Model Context Protocol (MCP) service. It supplements the rest of this policy. The application you connect is referred to below as your AI application.

• Information received from your AI application: we receive the tool name and arguments it sends to us. Depending on the tool, these include currencies, currency pairs, indicators, date ranges, filters, chart labels, a task-specific natural-language question, scenario assumptions, or portfolio positions such as direction and notional size. Information from your conversation is received if your AI application includes it in those arguments. Connecting does not give us general access to your chat history, files or other connected applications. Do not put passwords, API keys, payment-card details, health information or government identifiers in tool inputs.
• Account and authorization information: when you sign in to FXMacroData to authorize a connection, we use your FXMacroData account identifier, email, plan, access permissions and, where applicable, organization or seat identifiers. We store authorization records linking the client application to your account and credentials that allow authorized access. API-key connections use the supplied key for authentication. Credentials belong in the connection's authentication settings, never in a chat message or research input.
• Technical and usage information: we process network and request information, including IP addresses, client information, timestamps, tool names, request identifiers, success or error status, response time and usage counts. Account-linked usage records can include your email, account and organization identifiers, plan, client identifier, a credential hash or fingerprint, and requested currency or indicator. Our network-identifier attribution is described under Analytics, advertising and how you found us.
• Research inputs and results in logs: some portfolio, trade-setup and backtest tools record their submitted research inputs, including portfolio positions and scenario settings, together with result summaries for service analysis and troubleshooting. Standard tool-execution records contain operational metadata rather than the full conversation. Enterprise privacy handling suppresses research inputs, prompt fields and credential-correlation context from these research logs, and currency and indicator dimensions from MCP usage records; operational counts, status and duration can still be recorded.
• Purposes: we use this information to authenticate the connection, enforce access and usage limits, retrieve requested economic and market data, calculate research results, render charts, provide support, diagnose failures, prevent abuse, measure service usage and improve reliability and product features. A portfolio or scenario is used to calculate the analysis you request. These tools do not place trades or transfer funds.
• Outputs and recipients: we return requested data, source references, calculations, research summaries, charts and errors to your AI application. Outputs can include your submitted labels, question, assumptions or portfolio details, so they may become part of its conversation or displayed chart. OpenAI receives these outputs when you use ChatGPT or Codex; another application's provider receives them when you use that application. Google Cloud processes authentication, storage and operational logs on our behalf, and Cloudflare processes network traffic, security and the attribution information described below. Authorized FXMacroData personnel can access records for the purposes above. Account billing is handled separately by Stripe where applicable; connecting MCP does not itself send your portfolio inputs to Stripe. We do not sell or rent your personal information. Disclosure required by law is covered above.
• Retention: MCP application and account-linked usage logs are retained in our operational logging service for 30 days. Separately, exported HTTP request logs are stored in a Google Cloud analytics archive with no automatic deletion period; these can contain network addresses and request metadata. You can request deletion of personal information in these records by contacting us below, subject to security, dispute and legal needs. The pseudonymous network-attribution records described below are kept for up to three months. Authorization codes expire after five minutes, access tokens after one hour, and refresh-token authorization after up to 30 days; token expiry stops authorization and is not a promise that every stored authorization record is deleted at that moment. Account, permission and client-registration records have no automatic deletion period and remain until removed through account administration or a privacy request, subject to records needed for security, disputes or legal obligations. Disconnecting does not erase earlier logs. Copies of inputs and outputs held by your AI application follow that provider's retention rules.
• Your controls: choose what you include in a request and omit personal or confidential portfolio details that are not needed. You can disconnect FXMacroData in your AI application's connection settings to stop using the integration. For API-key connections, you can revoke the key in API management. To request revocation of an OAuth connection, access to your personal information, correction, deletion, or to raise a privacy complaint, email info@fxmacrodata.com. We may need to verify your identity. Removing a connection does not cancel your subscription or delete your FXMacroData account. To remove conversations or control their use by OpenAI or another AI provider, use that provider's privacy and account controls.
• Provider policies and international processing: our providers and your AI application's provider may process information outside Australia. OpenAI's processing of your conversations and tool outputs is governed by its Privacy Policy and your applicable account or workspace settings. This MCP connection is separate from the on-site Ask FXMacroData assistant described below.

FXMacroData for Google Sheets

The FXMacroData Google Sheets add-on uses Google Apps Script to import requested data, insert and refresh custom functions, and create charts in your current spreadsheet.

• Spreadsheet access: the add-on reads the selected output range to check for occupied cells, reads formulas on the active sheet when you request a refresh, and reads imported date and value columns when creating a chart. It writes requested data, formulas, formatting, source captions and optional charts. Imports can replace existing cell contents when you enable overwrite.
• Requests to FXMacroData: the add-on sends your selected dataset, currency or currency pair, indicator, dates and pagination settings to the FXMacroData API over HTTPS, with your API key in a request header for authenticated requests. Cell values used as formula arguments become part of these request inputs. Other spreadsheet contents, sheet names and workbook files are not sent to FXMacroData. API requests create the authentication, usage and security records described in this policy.
• API-key storage: when you save a key, the add-on stores it in Google Apps Script user properties for your Google account and this script project, and keeps a copy in the sidebar's browser local storage for imports. These copies contain the full key; the sidebar displays a masked version. A key pasted for an import is also held in memory during that request. Protect your Google account and browser profile, and keep keys out of shared cells and screenshots.
• Use and sharing: Google hosts the spreadsheet, runs Apps Script and stores the saved script properties. FXMacroData receives the API request inputs to supply data and operate API access. Spreadsheet contents read by the add-on are used for the spreadsheet features above; they are not sold, used for advertising, or used to train AI models. People who can access your spreadsheet can see the imported data and formulas under your Google sharing settings.
• Retention and clearing keys: saved keys have no automatic expiry in the add-on. Clear saved key attempts to remove the browser copy in that browser and requests deletion of the Apps Script user-property copy. If browser storage blocks removal, the sidebar shows a warning; retry clearing the key or clear the sidebar site's browser data. If Google blocks that deletion, the sidebar shows a warning; restore authorization and clear the key again. Other browser copies must be cleared in those browsers. Clearing a saved key does not revoke the key at FXMacroData; manage or revoke it through API management.
• Removing access and data: you can remove the add-on's Google permissions through Google Account connections. Imported tables, formulas and charts remain in your spreadsheet until you delete them in Sheets. Clear saved keys before removing access. For questions about API request records, or to request access, correction or deletion of personal information held by FXMacroData, email info@fxmacrodata.com.

Google Workspace and Looker Studio

In addition to the Sheets add-on described above, Google Workspace integrations can provide document and slide creation, Drive exports, calendar entries, Gmail context, Chat commands and Forms workflows. Google runs the Apps Script code and presents the permissions requested by the particular integration.

• Gmail: when you open the contextual add-on, it can read the current message's subject and plain-text body to identify a currency or indicator. This processing takes place within Google Apps Script. The detected currency or indicator becomes part of the data request to FXMacroData; the contextual feature does not send the message's full subject or body to our data API. The combined Workspace add-on uses message context to select a currency. This differs from emailing our support team, which is covered below.
• Docs, Slides and Drive: the integrations insert requested macroeconomic tables or text in a document or presentation, or create documents, presentations and CSV exports in Drive. The standalone Docs and Slides add-ons act on the current file; the combined Workspace and Drive export tools request broader file permissions to create their outputs. Requested dataset parameters go to FXMacroData. These export features do not upload the rest of your document, presentation or Drive contents to our data API.
• Calendar, Chat and Forms: calendar synchronization checks for matching events and creates requested release-calendar entries. Chat processes the command text and returns the requested data to the chat space. Forms workflows create a watchlist form, whose responses and sharing are managed in Google Forms. These features do not need to send unrelated calendar events, other chat history or form responses to FXMacroData's data API.
• Credentials, retention and recipients: Apps Script integrations that offer a saved API key keep it in your Google user properties until you clear it; some also keep browser storage as explained for Sheets. Looker Studio report configuration and returned data are handled by Google and anyone you share the report with. Requests create FXMacroData's account and usage records. Files, forms, calendar entries and reports remain in Google until you or an authorized administrator removes them, even after uninstalling an integration.
• Use limits and controls: our use and transfer of information received from Google Workspace APIs adheres to the Google Workspace user data and developer policy, including its Limited Use requirements. Workspace content accessed for these features is not sold, used for advertising or used to train generalized AI models. Clear saved keys before revoking authorization at Google Account connections; separately remove generated content and revoke FXMacroData keys if required. For personal information held by FXMacroData, use the privacy contact below.

Analytics, advertising and how you found us

We measure how people find and use FXMacroData so we can improve the product and understand which channels bring us customers. We do not sell this information.

• Google Analytics: we use Google Analytics 4 to record pages viewed, how you arrived (the referring site, search engine or campaign tags in the link you followed), your browser, device and approximate location, and actions such as creating an account, starting a subscription or creating an API key. Google Analytics sets first-party cookies (_ga and _ga_*). Our GA4 event-data retention setting is 14 months. Retention for a user identifier resets when that user has new activity, so an active identifier may be kept longer. This setting does not limit Google's standard aggregated reports.
• Signed-in accounts: when you are signed in, we link your analytics activity to an internal account ID (never your email address in readable form) and to your account status, such as free, trial, paying or cancelled, so we can see which channels lead to subscriptions. A SHA-256 hash of your normalized email may also be sent to Google for account and conversion matching; a hash is a pseudonymous identifier, not anonymous information. If your browser blocks Google Analytics, creating an account, starting checkout or creating an API key may instead be reported to Google Analytics from our servers. Blocking browser scripts does not itself stop server-side reporting.
• Google Ads: we advertise with Google Ads. Our site uses the Google Ads tag to measure which ads lead to sign-ups and subscriptions, and to show our ads to people who have previously visited fxmacrodata.com. To match conversions, a one-way hashed (SHA-256) copy of your email address may be shared with Google; it is not sent in readable form. If you arrived through one of our ads, we also report your subscription's first payment to Google Ads together with the ad click identifier from that visit. In the European Economic Area, the United Kingdom and Switzerland, advertising cookies and ad personalisation stay off unless you accept them in the cookie notice.
• Microsoft Advertising: we use Microsoft's Universal Event Tracking (UET) tag to measure page visits and attribute a completed paid subscription to a Microsoft ad click. Microsoft may receive page and referrer details, browser/device signals and its ad-click and UET identifiers. The purchase event contains only a commerce category and subscription label; we do not send Microsoft your email, transaction ID or payment amount through this event. In the European Economic Area, the United Kingdom and Switzerland, UET advertising storage stays off unless you accept it in the cookie notice. See Microsoft's Privacy Statement.
• How you first found us: the first page you landed on and how you arrived (referring site and campaign tags) are kept in your browser's local storage and saved with your account when you sign up or subscribe. After you subscribe we may also ask you, optionally, how you heard about FXMacroData; your answer is stored with your account and your billing record.
• Network identifier: our content delivery provider, Cloudflare, derives a pseudonymous identifier from your network address using a secret key and a one-way hash. We never store your IP address itself for this purpose. The identifier is recorded with page views, with requests to our API and MCP server made without an API key, and with your account when you sign in, so we can tell whether a new account first found us through the website, the API or the MCP server. These records are kept for up to three months.
• Your choices: use the advertising choice in the cookie notice where it is shown, block or delete cookies and site storage in your browser, turn off personalised ads at Google Ad Settings, or install the Google Analytics opt-out add-on. The cookie notice's advertising choice does not switch off all analytics, necessary authentication or operational usage records. Clearing site storage removes the saved advertising choice and may cause the notice to appear again. Blocking necessary sign-in cookies can prevent login. To ask about server-side reporting, object where applicable, or request access, correction or deletion, email info@fxmacrodata.com.

FXMacroData Excel add-in

The FXMacroData Excel add-in requests data using the currency, indicator, date range and other arguments supplied to its worksheet functions. These requests are sent to FXMacroData. The add-in does not read or upload the rest of your workbook.

• API key: if you save a key, the add-in keeps it in Microsoft Office runtime storage and sends it in an authentication header with data requests. This storage persists between sessions, is not encrypted, and can be shared by add-ins on the same domain within your Office environment. The add-in does not write your key into workbook cells or formulas. Use Clear Key in the task pane to remove the saved key.
• Usage and controls: authenticated requests are associated with your API account and are subject to our normal API usage and security records. The task pane does not include advertising or analytics tags. Clearing the saved key does not revoke it at FXMacroData; revoke it in API management if it should no longer authorize requests. Saved keys have no automatic expiry in the add-in. Removing the add-in does not remove data already imported into workbooks.
• Workbook sharing: data returned into cells can be saved and shared with the workbook. Sharing a workbook does not grant its recipients access to your API account; their own credentials may be required to recalculate protected functions.
• Microsoft: the add-in loads Microsoft's Office JavaScript library to work within Excel. Microsoft's handling of Office and browser data is described in the Microsoft Privacy Statement.

Microsoft 365, Word, PowerPoint, Outlook and SharePoint

Word and PowerPoint add-ins insert requested macroeconomic text or tables into your document or presentation. The Outlook add-in inserts requested content into the current email; inserting content does not itself send that email. These features send the selected dataset parameters to FXMacroData and do not upload the rest of the document, presentation or email body to our data API.

• Saved credentials: Word and PowerPoint use Office runtime storage with a browser local-storage fallback. Outlook uses Office roaming settings with a browser local-storage fallback. These stores can persist after the task pane closes and may synchronize under your Microsoft or browser account. Saved credentials have no automatic deletion period in these add-ins. Use their clear-key control, check other synchronized copies and revoke the FXMacroData key if necessary. Credential transport varies by version, as described under data clients.
• Teams and SharePoint: Teams tabs load FXMacroData website pages, so the website's sign-in, analytics and usage practices apply. SharePoint web parts keep connection settings, including a key if supplied, in the page or web-part configuration and load requested macroeconomic data. People with access to page configuration may be able to retrieve those settings; do not place a private key in a broadly shared page. Changing or removing a page does not revoke that key at FXMacroData.
• Microsoft Graph and Copilot: administrator-run connectors can publish an FXMacroData reference corpus into your Microsoft tenant's search index for retrieval in Microsoft services. Tenant authorization credentials and indexed content are handled in the environment running the connector and by Microsoft. Index access follows the connector's configured permissions. Administrators must separately remove the connection and indexed items when those copies are no longer wanted.
• Sharing and removal: inserted data stays in the document, slide, email, site or search index until you or its administrator removes it. Recipients may receive it when you share or send the item. Removing an add-in does not recall shared copies or delete the underlying account. Microsoft's processing follows the Microsoft Privacy Statement and your organization's settings.

Notion connections

When you authorize Notion, we receive authorization tokens and workspace details, and may receive the workspace owner's name, email and Notion identifier. We store the access and refresh tokens encrypted, together with your FXMacroData account, workspace identifiers and connection status. We read the identifiers, titles and URLs of pages shared with the connection to help you choose a destination, and create or update the release database you select.

Notion receives the economic data and source links written to the database. We retain the database and data-source identifiers, URLs and synchronization details so future updates reach the right place. Disconnecting through FXMacroData marks the connection inactive and clears its saved token fields; connection metadata remains without an automatic deletion period. You can also remove authorization in Notion. Database rows already written remain in Notion until you delete them there. Contact info@fxmacrodata.com to request deletion of personal connection metadata held by us. Notion's processing is covered by its Privacy Policy.

Webhooks, Slack, Discord, Telegram and other destinations

When you set up release alerts or an automation destination, we receive and store your selected filters, account identifier, destination URL and any destination credentials or signing secrets needed for delivery. Slack and Discord installation can also provide workspace or server identifiers, names, channel details and configuration links. These settings allow us to deliver requested releases and manage the connection.

• What is delivered: requested release data, source links and event metadata are sent to your chosen endpoint or platform, such as Slack, Discord, Telegram, Airtable or a workflow service. People with access to the destination can see the messages or records under its sharing settings. The destination provider may keep those copies after you remove the FXMacroData connection.
• Telegram channel verification: connecting a redistribution channel can involve your Telegram user identifier, channel identifier, title, username, administrator or bot membership status, subscriber counts and membership-event information. We use this to verify control, operate channel access and administer audience-based licensing. Connection and channel records may be linked to your FXMacroData or partner account.
• Retention and controls: delivery-history records and queued event records are scheduled for deletion after 90 days; provider cleanup may not happen at the exact expiry instant. Subscription, installation and channel-configuration records have no automatic deletion period. Disabling or deleting an alert stops future delivery but does not necessarily physically erase its configuration or earlier messages. Remove alerts in API management, disconnect the relevant channel or remove the app from its workspace, and separately revoke destination credentials where needed. Contact our privacy address to request deletion of retained personal records.

Browser extension

The FXMacroData browser extension requests macroeconomic data and calendars for the options you choose. Its storage permission is used to save an API key in the browser's synchronized extension storage, which may copy it to other signed-in browser profiles or devices. It does not require browsing-history access for its macroeconomic-data features. Requests use your selected dataset parameters and, when supplied, the key; some versions put the key in the HTTPS request URL.

The saved key has no automatic expiry in the extension. Use its clear-key control and your browser's extension-data settings to remove saved copies. Uninstalling it does not revoke the key at FXMacroData or guarantee that every synchronized copy and request log is removed. Revoke the key through API management if it should no longer work.

Voice assistants and personalized briefings

A voice-assistant platform processes your spoken interaction under its own terms and sends structured requests to the connected integration. FXMacroData receives the data parameters and authentication information needed for those requests; the voice platform handles the microphone recording. Returned data and briefing text may be spoken or displayed by that platform.

Self-hosted briefing integrations can remember followed currencies, time zone, the last briefing time and the last release cursor. The briefing software stores these preferences under a credential fingerprint rather than the credential itself. Authenticated profiles have no automatic expiry; anonymous conversation preferences are held in memory. These records are controlled by the operator hosting that integration, which may be you. Contact that operator to remove persistent preferences, and use your voice platform's controls to manage voice history or remove the connection. Removing a voice connection does not delete FXMacroData account or request records.

Email, newsletters and support

We use contact details and preferences to send account and billing messages, requested alerts, support replies and product or newsletter communications. Mailgun processes outgoing mail and delivery information for us. Delivery, failure, complaint and unsubscribe events, and email opens and clicked links where tracking is enabled, may be stored with your email address, message identifiers, campaign information and account identifier to measure delivery and communication outcomes.

Messages sent to our support inbox can be stored with sender and recipient details, subject, message body and conversation identifiers. Our support team can read correspondence and related account or conversation records to investigate requests and reply. Please do not include passwords, API keys or other unnecessary confidential information in support messages.

Mail, support, communication-preference and imported delivery-event records have no automatic deletion period in our account systems. Newsletter unsubscribe links and account communication preferences let you stop optional marketing messages. We may keep a suppression record to respect your choice; unsubscribe does not erase prior correspondence or stop necessary account and billing messages. For access or deletion requests, use the privacy contact below.

Publishers, partners and referrals

If you apply for a publisher, affiliate or partner program, we may collect your name, email, website or channel, audience and promotion details, account identifier and payout contact information. Referral identifiers, click counts and qualifying billing events can be used to calculate commissions, reconcile refunds and prevent self-referral or fraud. These program and accounting records have no automatic deletion period. You can contact info@fxmacrodata.com about program participation, correction or deletion; accounting and fraud-prevention needs may limit what can be removed.

Ask FXMacroData assistant

You can ask the on-site assistant product questions without signing in, but must provide a contact email so our team can follow up. Answers are generated with Google's Gemini models. Your question, relevant earlier conversation turns, current page path and optional profile choices about your business and intended use are sent to Google to produce the answer. Data retrieved to answer a question may also be sent to the model.

• What we keep: we store questions, answers, contact email, subscription status and optional profile choices for support, follow-up and product improvement. Signed-in records are associated with your account; records without sign-in still contain the contact email you supply and are not anonymous. The conversation record does not itself contain an IP address, but separate network and request logs may do so. Conversation records have no automatic deletion period.
• Who sees it and your controls: a copy of the conversation, page context and contact details is emailed to the FXMacroData team through our email provider. Those mailbox copies are separate from the conversation record. You can stop using the assistant and request access, correction or deletion through info@fxmacrodata.com. Closing an account or disconnecting an integration does not automatically erase chat records, mailbox copies or provider records.
• Please do not include API keys, passwords or other personal information in your questions.

FXMacroData on WhatsApp

If you message FXMacroData on WhatsApp, Meta processes and delivers your messages. We use your WhatsApp number, message identifiers and message content to respond. Connecting an account also associates that number with your FXMacroData account so we can check subscription access.

When you ask the economic data assistant a question, your question, relevant recent questions and data needed for the answer are processed by our Google AI provider. Do not include passwords, API keys, payment card details or confidential personal information. Payments are handled through our existing Stripe checkout.

We clear delivered message content from our delivery records and schedule undelivered message records for deletion after one day. Recent question context expires after one hour; connection links expire after ten minutes and checkout links after one hour. Deletion is asynchronous, and provider records, security logs and backups may follow separate retention periods. The account connection remains until disconnected. WhatsApp chats are not automatically emailed to our team.

Send disconnect or stop in WhatsApp, or use WhatsApp connection settings, to unlink your account. This does not cancel your subscription or erase messages retained by WhatsApp, your device or our providers. Contact info@fxmacrodata.com for privacy requests. Meta and Google may process information outside your country under their applicable terms and privacy policies.

Embeddable widgets on third-party websites

Website owners can embed free FXMacroData widgets (economic calendars, release countdowns, latest macro prints, central-bank tables and FX charts). When you view a page that hosts one of these widgets, the widget loads from fxmacrodata.com inside that page and we record aggregate usage so we can operate the service and show publishers how their widgets perform.

• What we record: the address and title of the hosting page, the widget configuration, your country (derived from the request), browser and device characteristics (viewport, language, time zone, connection type), whether the widget was visible and for how long, and clicks on the widget. Raw widget-event records are scheduled for deletion after 90 days; provider cleanup can take additional time. Aggregated daily counts have no automatic deletion period.
• Identifiers: by default the widget uses a random identifier that lasts only for your browser session and is stored in the hosting site's session storage. A persistent identifier (stored in a first-party cookie named fxmd_partner_vid and in local storage for up to 13 months) is only set when the hosting website has told the widget that you consented, using its own consent mechanism.
• Publishers: website owners who register for widget statistics give us their email address and website domain, which we use to send them their publisher ID, their statistics link and occasional product information about FXMacroData.
• No fingerprinting: we do not attempt to identify you across websites, and we do not sell this data.

Retention, disconnection and copies

The feature sections above explain specific retention periods. Ordinary application and account-linked usage logs in our operational logging service are kept for 30 days. Exported HTTP request logs in our separate analytics archive have no automatic deletion period and can contain network addresses and request metadata. Account and billing records, stored connection metadata, support correspondence, chat records, communication preferences and some aggregate statistics also have no fixed automatic deletion period unless stated otherwise above. We retain these records for account administration, service operation, support, security, disputes and applicable legal obligations, until removed through administration or a privacy request where appropriate.

Credential expiry, revocation, disconnecting, uninstalling, unsubscribing, cancelling a subscription, closing an account and requesting erasure are different actions. Closing an account is an account and billing action: it does not automatically delete the sign-in identity, prior records or copies held by providers. A deletion request is assessed separately. Some records may need to be kept to meet legal obligations, resolve disputes, prevent fraud or preserve your communication choices. We will explain any applicable limits when responding to your request. Data already exported or shared, and copies held by integration platforms, recipients or their backups, must also be managed with those parties.

Service providers and international processing

Our service providers include Google Cloud and Firebase for hosting, authentication, storage and operational logs; Google for analytics, advertising and the AI features described above; Cloudflare for traffic delivery, security and attribution; Stripe for billing; and Mailgun for email. Integration platforms such as Microsoft, Google Workspace, Notion and your chosen AI, automation, database or messaging provider receive the information described in their feature sections.

FXMacroData operates in Australia. Information may be processed outside Australia, including in the United States, where some of our cloud storage and providers are located. Your chosen platform or organization may determine additional processing locations. Their privacy policies and your organization's contractual arrangements also apply to the information they receive. We do not promise that integration data remains exclusively in Australia or in your device's location.

Your rights, choices and privacy complaints

Email info@fxmacrodata.com to ask what personal information we hold, request access or correction, request deletion, object to a use of your information, or raise a privacy complaint. Tell us which account or integration is involved; do not include passwords or API keys. We may ask for information needed to verify your identity and understand your request. We will assess the request, investigate complaints and explain our response and any limits that apply.

Depending on applicable law, you may also have rights to restrict processing, receive a portable copy of information, withdraw consent where processing is based on consent, or complain to a privacy regulator. Processing needed to provide a requested service, meet legal obligations or protect the service may continue where permitted. Withdrawing consent does not undo earlier lawful processing. You can contact the Office of the Australian Information Commissioner or your relevant local regulator about an unresolved privacy concern, subject to its jurisdiction and complaint requirements.

Use the integration-specific controls above to disconnect services, remove local credentials, revoke keys or delete generated content. A privacy request to FXMacroData cannot directly delete an independent provider's conversation history, mailbox, database, shared document or backups. We may update this policy when our services or practices change; the date at the top identifies the current version.