This Data Processing Overview explains, in plain English, how customer information moves through MomentumOS to support executive intelligence, recommendations and reports.
Document control
Previous version: 1.2
Version: 1.3
Effective date: 11 July 2026
Last updated: 6 November 2026
Reviewed: 6 November 2026
Change summary: November 2026 cross-platform review: SourceMend data health, AI Connect MCP read-only access, tenant-gated Action Connect shadow proposals and approvals, independent ProProof execution boundary, updated UK privacy and cookies guidance, EU AI transparency, and clearer operational and commercial limitations.
Processing flow
Customer and authorised users provide account, workspace, organisation, assessment, report, integration and support information.
Customers may connect or upload data from approved business systems such as CRM, PRM, CSV files and other approved operational systems.
MomentumOS converts available data into executive intelligence, evidence snapshots, benchmark context, recommendations, action plans, scenarios, reports, briefings and customer handbooks.
Where approved, MomentumOS may process API request metadata, webhook event and delivery metadata, embed-session metadata and approved outbound-action metadata for security, audit and service operation.
Customers review the resulting intelligence, recommendations and reports and remain responsible for business decisions.
Data categories
MomentumOS may process operational data, assessment inputs, team assessment data, user and role data, workspace settings, integration metadata, connector configuration, mapping and validation metadata, evidence, benchmarks, recommendations, action plans, scenario assumptions, audit information, support requests and feedback.
MomentumOS may process generated reports, executive briefings, customer handbooks, secure document-sharing metadata, API usage metadata, webhook delivery records, embed-session records, allowed-origin configuration and outbound-action approval and execution metadata.
Where explicitly enabled and governed, MomentumOS may process approved transformed aggregate observations for privacy-preserving ecosystem intelligence, benchmark provenance, cohort metadata, scenario assumptions and shared pattern governance.
MomentumOS distinguishes operational configuration, sensitive credentials, evidence and derived intelligence, generated customer documents and audit metadata.
MomentumOS does not use ordinary onboarding or workspace tables to store raw credentials. Where the secure provider is configured, ordinary application records store credential references and lifecycle metadata rather than secret values.
Privacy-preserving ecosystem intelligence
Ecosystem intelligence participation is optional and separate from ordinary product acceptance. Existing acceptance is not treated as approval for participation.
Eligible shared intelligence is limited to approved transformed aggregate observations, bucketed distributions, cohort statistics, benchmark provenance and approved shared pattern summaries.
MomentumOS does not pool raw customer data, customer documents, transcripts, unrestricted assessment responses, raw CRM or PRM records, credentials, raw prompts or customer-specific embeddings into a shared memory.
Withdrawal stops new shared observations and triggers exclusion, recalculation and cache invalidation workflows where required. It does not promise removal from historic distributed PDFs or prior decisions.
Production contribution requires legal review records, DPIA approval, lawful-basis records, controller-role mapping, identification-risk assessment, privacy notice, terms/addendum, participation disclosure, threshold governance, withdrawal testing, security review and dual approval.
This disclosure is intended for legal review before production activation of contribution workflows and is not legal advice.
Connected systems
Customers may connect CRM, PRM, CSV and other approved business systems. MomentumOS primarily consumes read-only operational data unless a specific connector, customer agreement or approved workflow documents otherwise.
Data residency and hosting
MomentumOS's primary customer and workspace database is hosted through Supabase in West Europe, Ireland. Application delivery uses Vercel's Global Edge Network. Customers should review feature-specific subprocessors, AI processing, data flows and any contractual residency requirements before production rollout. MomentumOS does not currently claim that all processing remains exclusively within the EU or that customer-selected regional deployment is a standard self-service option.
Credentials and secure exchange
OAuth and Secure Credential Exchange are used where credentials are required. OAuth tokens, API keys, client secrets, service-account credentials, certificates, private keys, webhook signing secrets, API credentials and embed or service credentials should be stored separately from workspace information, managed through a secrets manager or approved credential provider, and not redisplayed after submission.
Audit and operational metadata
API, webhook, embed, outbound-action, secure sharing, support, incident and AI usage metadata may be logged for security, auditability, troubleshooting, service operation, entitlement enforcement and abuse prevention.
Customer control
Customers control the source data they provide, the users they authorise, the workspaces they configure and the recommendations they choose to act on.
