Privacy
Effective October 11, 2026
What the app handles
MOMUS PM shows account identity, Project membership, assigned work, notifications, comments, planning fields, and report facts that an administrator has authorized the signed-in employee to access.
Credentials and device data
A rotating refresh credential is kept in protected device storage. A push token may be stored with the revocable server-side device session. Passwords, access tokens, refresh tokens, GitHub credentials, MCP credentials, and push tokens are not placed in analytics or support logs.
Offline data
The app may retain bounded, account-scoped copies of previously opened non-secret read models for up to seven days. It labels cached and stale data explicitly. Signing out removes that account's cache and revokes the current device session.
Notifications
Lock-screen push messages are generic and contain no issue title, comment, repository, person, date, or Project detail. Opening a notification retrieves the current access-scoped Inbox record before protected content is shown. Revoked devices are excluded from API and push delivery.
Diagnostics and tracking
MOMUS PM records bounded request identifiers, operation outcomes, status classes, and redacted server errors for support. It does not include issue or comment bodies, credentials, cookies, notification text, or push tokens. The mobile app includes no advertising SDK, third-party crash-reporting SDK, or cross-app tracking.
Deletion and retention
Employees can sign out to revoke the current device. Administrators can revoke individual devices or delete an account. Account deletion revokes browser, agent, MCP, and mobile sessions and removes external notification eligibility. Server audit, notification, and calibration records follow the administrator-visible retention settings.