Explore demo ↗
IMPACT DATA GOVERNANCE

Know where every claim
came from.

ImpactGround separates organisation data, product suggestions and approved decisions—and keeps the source and review state attached.

WHAT BUYERS NEED TO KNOW
WHAT IS RECORDED?

Context, initiatives, evidence, decisions and approvals.

WHO CAN ACT?

Production roles separate submission, review, approval, viewing and administration.

WHAT DOES IMPACTGROUND SUGGEST?

It may structure supplied context, surface gaps and draft material. It does not create evidence or approve decisions.

CAN WE EXPORT OR DELETE IT?

Production contracts define export, retention and deletion controls.

PLANNED PRODUCTION ARCHITECTURE

Regional hosting for impact data.

Region, transfer rules, inference location and retention are agreed before customer data are accepted.

REGIONAL DATA CELLSaudi, UK, EU or another contracted region holds the organisation’s content without pooling it globally.
Application dataFilesSearch indexesBackupsAudit logsApproved inference
REGION LOCKNo unannounced cross-region replication.
TENANT ISOLATIONEach organisation is logically isolated.
IN-REGION PROCESSINGWhere required, document processing and inference stay in-region.
TRANSFER GATEPermitted transfers require purpose, legal basis and minimisation.
PLANNED CONTROLS

Controls around every impact claim.

Production requirements—not a claim that this public prototype has passed a security or compliance audit.

SOURCE TRACESource, period, method, owner and review state remain attached.
HUMAN APPROVALSuggestions stay separate from organisation data and approved decisions.
ROLE + AUDIT CONTROLAttributable permissions, changes, reviews and approvals.
EXPORT + RETENTIONContracted export, deletion and retention rules.
IMPACTGROUND + AI

Assistance without invented evidence.

IMPACTGROUND MAY

Structure supplied context, clarify statements, surface gaps and draft questions or reports.

IMPACTGROUND MUST NOT

Invent outcomes, turn a forecast into evidence, hide uncertainty or approve its own recommendation.

A PERSON APPROVES

Definitions, sources, interpretations, decisions and external reporting.

SAUDI DEPLOYMENT NOTES

Residency and sector requirements are designed into deployment.

PERSONAL DATA

PDPL conditions and safeguards govern permitted transfers outside the Kingdom.

SDAIA PDPL ↗
CLOUD + DATA CONTROLS

NCA classification, risk, protection and localisation controls shape hosting design.

NCA controls ↗
FINANCIAL INSTITUTIONS

SAMA-regulated organisations have additional cloud, outsourcing and approval requirements.

SAMA requirements ↗
No production residency or compliance certification is claimed today. Qualified specialists must confirm each deployment.
BEFORE DEPLOYMENT

Request a production security review.

Review architecture, data flow, subprocessors, access, retention and implementation status.

Request the trust pack →