1. What this agreement is
This End User License Agreement (the “Agreement”) is the license that governs every way you use World Monitor. It is made between you — and, where you use World Monitor for an organization, that organization — and World Monitor, based in the United Arab Emirates (“World Monitor”, “we”, “us”). It applies whichever surface you use:- the web dashboard at
worldmonitor.appand its variant subdomains (tech, finance, commodity, energy, happy); - the desktop applications for macOS, Windows, and Linux;
- the REST API and the MCP server;
- the SDKs and CLI (npm, Python, Ruby, Go);
- embeds and widgets, including the live map embed;
- alerts, webhooks, digests, and email;
- exports, downloads, reports, and briefings produced by any of the above.
2. How this fits with our other documents
The warranty disclaimer, limitation of liability, indemnity, and governing-law terms in the Terms of Service apply to this Agreement and are incorporated into it by reference.
Enterprise terms are negotiable. The governing law, venue, liability cap, and any service-level commitment stated in the Terms are our standing self-serve terms. A signed order form may state different ones — a different governing law and venue, a negotiated cap, or an SLA — and where it does, the order form controls.
The source-code license is not affected by this Agreement. World Monitor’s source code is licensed under AGPL-3.0-only, and the official thin client packages under MIT. Nothing in this Agreement removes, narrows, or adds conditions to any right the AGPL or MIT licenses grant you in that code. This Agreement licenses the hosted Service and its Outputs — the data, the analysis, and the servers we operate. Those are two separate things, and where they meet — a desktop build that calls our cloud, a self-hosted deployment that uses our API — section 6.2 says exactly which one applies.
Order of precedence. If these conflict, the one higher in this list controls: (1) a signed order form or enterprise agreement; (2) this Agreement; (3) the Terms of Service; (4) plan descriptions, pricing pages, and documentation.
3. Definitions
- Licensed User — one named individual authorized under your plan. A seat is not a role, a shift, or a shared login.
- Your Organization — for organization plans, the single legal entity that subscribes, including its employees and contractors acting for it.
- Credentials — account logins, sessions, API keys, license keys, MCP tokens, and OAuth grants.
- Derived Facts — quantities we compute: resilience and risk scores, forecast probabilities, indices, event counts, aggregates, and rankings.
- Structured Events — normalized event records: what, where, when, type, severity, entities, and a link to the source, without the source’s own text.
- Source Content — text, images, and other expression created by a third-party source: headlines, article bodies, feed items, and quotations.
- Term — the period during which you hold an active plan or an active order form.
4. License grant
Subject to your payment of the applicable fees and your compliance with this Agreement, we grant you a limited, non-exclusive, non-transferable, non-sublicensable, revocable, worldwide license for the Term to access the Service and to use the Outputs within the scope of the plan you purchased. Every plan grants only the rights we are able to grant. Third-party data stays subject to its provider’s own license and terms, which may be narrower than your plan.4.1 Plan license scopes
The right plan depends on who uses the Service and who receives its Outputs — not on how much you use it.
Examples:
- an individual using Pro to research their own portfolio is covered by the Personal license;
- a consultant using Pro Business to prepare a client report is covered by the Pro Business commercial license;
- a company feeding API data into a private employee risk dashboard needs API Starter;
- a software company showing API data inside a customer-facing product needs API Business;
- a standalone data feed, bulk resale, white-label product, or custom deployment requires an Enterprise agreement or our written approval.
4.2 Rules that apply to every plan
- A seat belongs to one named user. Credentials may not be sold, transferred, published, or shared outside the people and systems your plan authorizes.
- An agent, script, or MCP client acting for you consumes your license, at your plan’s scope. Automating access does not widen what you are licensed to do, and does not let a personal seat serve an organization.
- Customer redistribution under API Business must be part of a product or service with material value beyond providing a copy of World Monitor data.
- Attribution to World Monitor is optional for reports, presentations, and derived analysis permitted by your plan. If you choose to credit us, “Source: World Monitor” or “via World Monitor” is sufficient. You must still preserve any source-specific citation, attribution, timestamp, license notice, or usage restriction supplied with an Output.
- No plan transfers ownership of the Service or the underlying data, grants trademark or branding rights, or permits you to imply that World Monitor endorses your product.
5. What you may do with the Outputs
Outputs are not one thing, and they do not carry one set of rights. What you may keep, cache, and pass on depends on which class an Output falls into, and then on your plan.
Default rule. For any source whose provider terms we have not individually cleared, its Source Content is R4, while facts derived from it are R1 and R2. Facts are not owned; the sentence a wire service wrote is. We license you the first freely and the second not at all.
Retention and caching are granted, not merely tolerated. Within the classes above you may store, cache, index, and re-query R1 and R2 Outputs for as long as you like, including after your subscription ends, for records, audit, and back-testing. What you may not do after the Term ends is fetch, refresh, or operate integrations that require an active entitlement (section 10).
Attribution travels with the Output. Where an Output arrives with a source-specific citation, timestamp, license notice, or usage restriction, that notice must survive every copy you make and every screen you show it on.
R3 rights are available per source on request — ask us and we will tell you which sources are cleared for it.
6. Terms for each surface
6.1 Web dashboard, embeds, and widgets
The dashboard is licensed per Licensed User. Embeds and widgets may be placed only on properties your plan covers: internal properties for API Starter, customer-facing properties for API Business and Enterprise. Do not remove, obscure, or restyle attribution or source notices carried inside an embed.6.2 Desktop applications
The desktop applications are built from World Monitor’s AGPL-3.0-only source. The application binary is licensed to you under AGPL-3.0-only, not under this Agreement — you may run it, study it, modify it, and redistribute it under the AGPL’s terms, and nothing here changes that. What this Agreement governs is the World Monitor services the application reaches: the cloud fallback that serves a request when a local handler is missing, entitlement and license-key checks, update checks, and any hosted data the app fetches. Using those is using the Service, at your plan’s scope. It follows that:- Running a desktop build entirely against your own API keys and your own local sources, with no calls to World Monitor’s servers, is governed by the AGPL alone. You need no plan from us for that.
- The moment the app fetches World Monitor data — through cloud fallback, entitlements, or our API — that fetch is under this Agreement.
- Modified builds must follow the Trademark Policy: distinct branding, no presenting a modified build as the official World Monitor application.
- Desktop and web are the same license, not two. A Pro seat is one person, whether that person is at a browser or in the desktop app, and using both does not consume two seats.
6.3 API and MCP server
- API keys and MCP credentials are issued to a subscriber and are confidential. You are responsible for all usage attributed to them. Do not publish them, embed them in client-side code you distribute, or hand them to another organization.
- You may hold separate keys per environment or service within the licensed organization. You may not use one organization’s key to serve another.
- Published rate limits, daily quotas, and plan allowances are part of the license, not merely a technical ceiling. Circumventing them — key rotation to reset quotas, distributed request pools, scraping the front end to avoid metered endpoints — is a breach of this Agreement, not just of a limit.
- We may throttle, suspend, or revoke access to protect the Service or to stop abuse, and will tell you why when we do.
- MCP and agent access is licensed exactly like human access. See section 4.2.
6.4 SDKs and CLI
The official npm CLI and the Python, Ruby, and Go SDKs are MIT-licensed and may be embedded in any application, including proprietary ones. The code is MIT; the data it fetches is not. Everything those clients retrieve from the Service remains subject to this Agreement.6.5 Alerts, webhooks, digests, and exports
Alerts and webhook deliveries may be routed into systems your plan covers — your own tooling for Personal and Pro, Your Organization’s systems for API Starter, and customer-facing destinations only under API Business or Enterprise. Re-broadcasting alert streams beyond your licensed scope, including to a public channel, requires written permission.7. Your content
You keep everything you bring: declared site coordinates, alert rules, saved views, queries, uploads, and prompts (“Your Content”). You grant us only the license we need to operate the Service for you — to store Your Content, process it, and transmit it to the subprocessors named in the Privacy Policy. The Service’s core monitoring is built to run on customer-declared static coordinates and configuration — it does not require names, locations, itineraries, or contact details of individuals. Do not submit personal data you do not need to submit, and do not put sensitive personal data into AI prompts. If you send us feedback or feature suggestions, we may use them without obligation to you.8. Restrictions
Across every surface and every plan, you may not:- Share or transfer Credentials beyond the users and systems your plan authorizes, or sell, sublicense, or resell access to the Service.
- Circumvent quotas, rate limits, entitlement checks, authentication, paywalls, or access controls — by any means, including scraping a rendered page to avoid a metered endpoint.
- Bulk-extract the Service, or any substantial part of it, in a way that substitutes for a subscription or reconstitutes our data as a standalone database or a substantially similar feed.
- Redistribute beyond your class and plan — in particular, redistribute R4 Source Content, or strip attribution from R3 Outputs.
- Train on the Outputs. Do not use Outputs to train, fine-tune, distill, evaluate, or benchmark a machine-learning model, or to build a dataset, that competes with the Service, without our written permission. Using Outputs inside your own AI workflows — as context, retrieval, or analysis for your licensed use — is expressly allowed. Model-training and dataset rights are licensable: if you want to train on World Monitor Outputs, that is an Enterprise order form, not a prohibition — ask us.
- Remove or alter notices — copyright, license, attribution, source citations, timestamps, or provenance markers.
- Misrepresent affiliation with, endorsement by, or certification from World Monitor.
- Reverse-engineer the hosted Service — its models, ranking, scoring, or infrastructure — to build a competing service. This does not apply to the source code, which the AGPL expressly permits you to study and modify.
- Use the Service unlawfully or against a person — to harm, harass, surveil, profile, or endanger any individual, or to make decisions about an individual that affect their rights.
- Rely on the Service where errors cause harm. Outputs are aggregated from third-party sources with automated and AI analysis layered on top. They may be delayed, incomplete, wrong, or misattributed, and AI-generated briefings and forecasts can be confidently wrong. Do not use the Service as the sole basis for trading, travel, security, medical, or life-safety decisions without independent verification. The full disclaimer is in the Terms of Service.
- Breach sanctions or export controls. You may not use the Service, or make it available, where doing so would breach applicable sanctions or export-control law, or in favor of a restricted party under it.
9. Ownership
We own the Service: the platform, the data pipeline, the models and scoring methods, our compilations and databases, the Derived Facts we compute, and all associated intellectual property, subject to the source-code licenses in License. Third-party data belongs to its sources. You own Your Content and the reports, presentations, and analysis you create within your plan’s scope. Nothing here transfers ownership. Everything not expressly granted is reserved.10. Term, suspension, and termination
This Agreement runs for as long as you use the Service or hold an active plan. We may suspend or terminate access for non-payment, for a breach of this Agreement, or to protect the Service or its sources. You may stop at any time by cancelling; cancellation ends future renewals at the close of the current billing period. When your plan ends:- you may keep and continue to use reports, analysis, and R1/R2 Outputs lawfully created or retrieved during the Term, under the same class rules;
- you must stop fetching, refreshing, distributing to new recipients, and operating integrations that depend on an active entitlement;
- you must stop distributing R3 Outputs, and delete cached R3 Source Content once its 30-day window closes;
- Credentials are revoked.