This Acceptable Use Policy explains how customers and users must use MomentumOS responsibly so the platform remains secure, reliable and trusted for all workspaces.
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.
Overview
MomentumOS is designed for legitimate business use: executive intelligence, revenue momentum analysis, assessments, benchmarking, reporting, investigations, integrations readiness and governed recommendations.
Prohibited use
Users must not attempt to disrupt, overload, scan, reverse engineer, scrape or bypass MomentumOS systems, authentication, rate limits, access controls or workspace boundaries.
Users must not use MomentumOS to submit unlawful, harmful, deceptive, infringing, abusive or malicious content, or to interfere with other customers or users.
Users must not use MomentumOS to generate or distribute spam, malware, credential harvesting, social engineering, fraudulent communications or other harmful activity.
Credential and integration misuse
Credentials, OAuth authorisations, service-account materials, certificates, private keys and webhook secrets must only be submitted through approved secure exchange flows.
Users must not paste secrets into ordinary workspace fields, reports, support messages, comments, feedback, prompts or uploaded files unless the field is explicitly designated for secure credential handoff.
Users must not use integrations to access systems, records or data that they are not authorised to access.
Users must not share API credentials, perform origin spoofing, spoof allowed origins, abuse webhook endpoints, perform token replay, replay tokens, bypass approval controls, trigger unauthorised write-back, abuse embedded sessions or attempt cross-customer access.
Users must not attempt to extract confidential platform data, customer data, source-system data, credentials, tokens, prompts, private keys, webhook signing secrets or hidden configuration from MomentumOS.
Data and workspace responsibilities
Customers are responsible for ensuring that data submitted to MomentumOS is accurate, authorised and appropriate for the intended workspace.
Customers must manage user access, roles and permissions so users only access workspaces and information they are authorised to view.
Customers must review AI-assisted recommendations, action plans, briefings and reports before relying on them for business decisions.
Platform protection
MomentumOS may restrict, suspend or investigate activity that appears to create security risk, platform abuse, credential exposure, workspace boundary issues, integration misuse or harm to other customers.
