Ethics & Compliance

Official statistical agencies, central banks, exchanges, market-data providers, news providers, and other upstream publishers remain the source of record for their own releases. Macro by Mark may summarize, route, normalize, cache, visualize, or contextualize data, but users should verify important figures against the original source and release documentation.

Where practical, indicator and data surfaces should preserve source labels, provider names, release timing, units, frequencies, revisions, geography, transformations, and status signals that materially affect interpretation.

Referencing a data provider, agency, central bank, company, publication, school of thought, or external source does not mean that the provider sponsors, endorses, certifies, approves, or is affiliated with Macro by Mark. Provider marks and names belong to their respective owners.

If a sponsored placement, affiliate relationship, academic collaboration, paid review, or material connection is introduced, the relationship should be disclosed clearly where the user encounters the affected content.

Structural models, DSGE tools, empirical labs, theoretical graphs, simulations, nowcasts, and forecasts are analytical aids. They should make assumptions inspectable, communicate uncertainty, and avoid presenting preliminary or experimental outputs as settled conclusions.

Where a route is incomplete, beta, synthetic, toy-level, stale, or dependent on fragile source coverage, the product should say so rather than imply full production readiness.

Marco is intended to support navigation, explanation, and product understanding. It should not invent source data, represent itself as a licensed adviser, provide personalized investment guidance, or replace primary-source review.

Specific current values, release dates, news items, forecasts, dashboards, and watchlists require source context available to the server for that request. If that context is missing, Marco should say what is missing and avoid stating the fact as verified. For releases, this includes actual, prior, consensus, and surprise fields.

Marco may use limited account preference context, such as locale, timezone, country, experience level, and focus areas, to set language, formatting, explanation depth, and examples. That context is not evidence for source claims and does not replace the source context requirement for live data, releases, forecasts, or saved work.

Users should treat assistant responses as draft help. High-stakes academic, financial, legal, policy, investment, or professional decisions require independent verification and qualified judgment.

If Macro by Mark receives compensation, free access, credits, sponsorship, affiliate benefits, or other material consideration that could affect a product mention, recommendation, placement, review, or comparison, the relationship should be disclosed clearly and close to the affected content.

Testimonials, endorsements, or user quotes should not be edited in a way that materially changes meaning, and should not imply typical results where that would be misleading.

Account-backed features should scope reads and writes to the signed-in user, keep sensitive service credentials server-side, avoid exposing Supabase tokens to browser JavaScript, and retain only the operational state needed to run account features, billing, analytics, support, security, and compliance.

Administrative routes and grant tools should require explicit admin authorization. Development bypasses and test fixtures should not grant production access.

Paywalls, subscription plans, academic lifetime access, beta access, admin access, and promotional grants should be represented accurately. Users should not be misled about what is free, paid, experimental, time-limited, or manually granted.

Academic lifetime access is intended as a discretionary, no-subscription grant for selected professors, colleagues, and trusted reviewers. It should not be described as provider-sponsored or institutionally endorsed unless that is separately true and documented.

If a source link, route, chart, label, assistant response pattern, forecast, summary, attribution, legal page, or product-controlled interpretation is materially inaccurate, Macro by Mark may correct, clarify, annotate, or remove it. Corrections should prioritize user clarity over protecting old product copy.

For material corrections, the product should preserve enough context for a reasonable user to understand what changed and why, without exposing private user data or security-sensitive details.

Macro by Mark may be useful in classrooms, research discussions, and policy or market monitoring workflows, but it is not a substitute for course requirements, instructor guidance, primary-source review, formal research methods, or institution-specific compliance rules.

Users should cite original data providers when relying on underlying public datasets, and cite Macro by Mark separately only when relying on product-specific framing, visualization, or commentary.

Concerns about source handling, misleading content, privacy, accessibility, sponsorship disclosure, assistant behavior, billing representation, data integrity, or account access can be sent to privacy@macrobymark.com.