GDELT Cloud provides API and agent-native access to structured global event intelligence. This page summarises how we approach security, privacy, subprocessors, availability, and methodology so commercial buyers, security reviewers, and developers can evaluate the platform.
We operate GDELT Cloud on managed cloud infrastructure with restricted administrative access, multi-factor authentication where supported, separated development and production environments, and routine error and availability monitoring.
Code changes ship through version-controlled deployments. Secrets are stored outside the codebase. We monitor application errors and service health and respond to incidents that affect customer data or availability.
GDELT Cloud collects what it needs to operate accounts, billing, API access, MCP workflows, product analytics, and support. We do not sell customer data.
We do not use customer API queries, prompts, uploaded content, or private workspace activity to train third-party foundation models. Some subprocessors process limited customer data only to provide infrastructure, payment, email, observability, or support services on our behalf.
GDELT Cloud relies on established cloud providers for hosting, application data, analytical storage, MCP infrastructure, agent observability, payments, and email. Each provider runs its own security and compliance programme.
We publish a current list of subprocessors, the purpose each serves, and the data each processes. Commercial customers can request advance notice of material subprocessor changes as part of their agreement.
GDELT Cloud transforms public GDELT and Global Energy Monitor data into structured event intelligence: clustered stories, ACLED-coded conflict events, CAMEO+ multi-domain events, and enriched entities.
The methodology page documents source coverage, update cadence, taxonomy, story clustering rules, and known limitations such as historical coverage gaps before March 2026 and same-day-only story clustering. We treat GDELT Cloud as analytical signal, not ground truth.
We publish two distinct views of service health. The status page tracks uptime and incidents for the web app, API, MCP endpoint, authentication, and core data pipeline. The data status page reports live ingestion freshness for GDELT Events, GKG, GEG, and the GDELT Cloud product pipeline.
GDELT Cloud currently targets 99.5% monthly availability for paid API access, excluding scheduled maintenance, upstream provider outages, customer-side issues, and beta or experimental features.
We publish a changelog of product-meaningful changes: new endpoints, schema or taxonomy updates, methodology refinements, and reliability improvements. Material schema or classifier changes are documented there so integrators can plan around them.
GDELT Cloud has not yet completed SOC 2 attestation. We are implementing operational controls aligned with SOC 2 Security, Availability, and Confidentiality criteria and will pursue formal attestation as customer demand and production deployments justify it.
For commercial evaluations we can share our security overview, subprocessors list, data retention practices, and answers to reasonable vendor security questions. Email security@gdeltcloud.com to start a review.
Commercial and self-serve use of GDELT Cloud is covered by our Terms of Service and Acceptable Use policy. These cover allowed uses, rate limits, prohibited activity, attribution, and the boundary between internal use and redistribution.
