Version: 2026-08-08 v2.0
Momentum Digital Labs Ltd may process account, contact, tenant, billing, transaction, security, fraud-prevention, authentication, device/session, support, analytics and legal-acceptance information where necessary to provide, secure and administer the Services, comply with law and protect users and Momentum.
Legal-acceptance records may include user and tenant identifiers, timestamp, document version, cryptographic document hash, authentication path, device/session metadata where lawful, and related evidence of consent or acknowledgement.
Where Momentum processes personal data on behalf of a business Customer, the Momentum Data Processing Addendum applies.
Momentum may use service providers and subprocessors for hosting, infrastructure, communications, payments, support, security, analytics and AI/provider connectivity. Their processing is governed by applicable contracts and law.
Personal data may be transferred internationally using lawful safeguards where required.
Momentum retains personal data only for as long as reasonably necessary for the applicable purpose, contract, security, fraud prevention, billing, dispute handling, legal obligations and establishment or defence of legal claims.
Subject to applicable law, individuals may have rights of access, correction, deletion, restriction, objection, portability and complaint to a supervisory authority.
Momentum does not use Customer Data to train general-purpose or foundation AI models unless Customer separately and expressly agrees.
Security measures are designed to protect personal data, but no system can guarantee absolute security.
Customer-specific workflow discovery information is processed to configure and provide the Customer's Julia workspace.
Cross-customer product learning from Founder feedback is opt-in. Where the Customer chooses to participate, Momentum may create anonymised and generalised workflow patterns after excluding credentials, secrets, personal data and Customer-identifying confidential information.
Momentum may process task classifications, prompt-template identifiers, model selections, latency, token usage, estimated provider cost and quality signals to operate and improve Julia's orchestration and cost-routing functions.
API keys, passwords and provider secrets are not stored in the Prompt Vault.
Where enabled by the Customer, Julia may process Customer-authorised business contacts and lawful business information to suggest potential referral candidates. The Customer controls whether an invitation is sent.