Terms of Use
The usage rules, no-advice framing, intellectual-property boundaries, and service protections for the site.
Legal
How this site uses local browser storage, optional synced watchlists, public-data providers, and basic operational logs
Effective March 30, 2026. This policy applies to the public Macro by Mark website and the local-first dashboard and watchlist workflows available on it.
This page covers what information the site handles, which third parties are involved, and what choices you have. It covers the public site as it stands today: browser-local dashboards and watchlists, indicator pages, the calendar and news pages, and the contact link.
Depending on how you use the site, it may handle: saved dashboards, local watchlists, bookmarks, notes, projects, and saved model runs stored in your browser; technical request and device information used to serve the site; public-data queries sent to third-party economic or market-data providers; and any contact information you send through external contact links. If optional synced account features are enabled and you sign in, the site may also handle the account identifier and the synced workspace records needed to keep those items available across devices through Supabase.
Saved dashboards, local watchlists, bookmarks, notes, projects, saved model runs, recent indicator history, and some site preferences are stored locally in your browser. That storage keeps the site working between visits on the same device. It is not used to create an advertising profile.
Like most hosted web products, the site may generate basic operational data such as request timestamps, IP-derived network information, browser or device metadata, response status, and performance or error logs through the hosting stack. The codebase also includes a lightweight internal events endpoint for product telemetry. If enabled, it’s used for reliability monitoring, not advertising.
Macro by Mark may request public macroeconomic data from third-party providers such as FRED, BEA, BLS, Census, Treasury, EIA, IMF, the World Bank, and selected market-data services such as Polygon. Those providers control their own endpoints, revision behavior, uptime, and metadata. The site may also rely on third-party hosting or infrastructure providers to serve the application itself.
This site does not intentionally run ad-tech trackers or build cross-site behavioral advertising profiles. Browser-local storage is used for product state. The site does not currently change its behavior in response to browser Do Not Track signals, because it is not built around a separate ad-tech tracking stack to toggle on or off.
The product now includes live account authentication and synced workspace wiring for account-backed features. When configured, authentication and stored watchlists, dashboards, notes, projects, or saved-run records may be handled through Supabase. Sign-in can use password, magic-link email, or third-party identity providers such as Google so the same signed-in account can see the same workspace on more than one device. Local-first remains the default for routine browsing, and public visitors who do not create an account can still use large parts of the site without sending account credentials.
Browser-local dashboard and watchlist data stays on your device until you clear it or overwrite it. Public economic and market data may be cached temporarily for performance, but primary providers remain the source of record. Revisions and corrections can flow through from those providers without separate notice. If you report an error in public-facing content controlled directly by this site, it may be corrected or clarified without preserving older wording on the page.
You can clear browser-local dashboard and watchlist data by clearing site storage in your browser. You can also control cookies or site data through your browser settings, avoid optional external contact submissions, and contact the site operator to report a privacy concern, request a correction to public-facing content, or ask a question about data handling.
This policy may change as the product evolves. When it does, the effective date on this page will be updated and the revised policy will apply from that date forward.
For questions about this policy, use Get in Touch.
The privacy page is one part of the trust stack. Terms, ethics, and accessibility stay grouped with it so the product’s legal posture is easy to inspect.
Terms of Use
The usage rules, no-advice framing, intellectual-property boundaries, and service protections for the site.
Ethics & Compliance
Source transparency, no-endorsement posture, model restraint, and research-integrity guardrails.
Accessibility Statement
The accessibility posture, current limitations, and how to report a barrier or request an accommodation.