MonitUp Security and Compliance

Last updated: 2026-03-26

Version: security_v2_2026_03_26

Identity and contact: MonitUp (brand and service name), [email protected].

1. Security Approach

MonitUp applies reasonable administrative, technical, and organizational measures designed to protect service data and reduce operational risk. Our practices may evolve over time as our infrastructure and product change.

2. Current Technical and Operational Controls

Based on the current implementation, MonitUp uses controls such as:

• encrypted transport for web traffic (HTTPS/TLS);
• account authentication and password requirements;
• internal logging and monitoring that support troubleshooting and operations;
• role-based and need-based access for support and service operations.

3. Infrastructure and Hosting

MonitUp relies on hosted infrastructure and service providers for parts of the platform. Physical security controls for underlying facilities are managed by the relevant hosting providers.

4. Incident Response

MonitUp maintains internal processes for identifying, evaluating, and responding to suspected security incidents.

Where notification is required by applicable law or contractual terms, MonitUp will provide notice in accordance with those obligations.

5. Backup and Recovery

MonitUp maintains backup and recovery practices intended to support service reliability and operational continuity. Backup scope, frequency, and retention may vary by environment and may change over time.

6. Development and Change Management

Code and configuration changes are generally reviewed and tested before release according to current engineering practices. The exact toolchain and release workflow may be updated as the platform evolves.

7. Support Access and Confidentiality

MonitUp limits internal access to data to personnel who need access for operations, support, or security-related work.

For on-premise deployments, the customer controls the environment and access model. MonitUp does not have standing access and support access is provided only when explicitly enabled and authorized by the customer.

8. Screenshot and Monitoring Data

Screenshots are an optional feature and are processed only if enabled by the customer. Data transmission between clients and service endpoints is intended to use encrypted channels.

9. Billing and Payment Data

MonitUp uses Stripe integrations for payment processing in the current platform. MonitUp does not intentionally store full payment card numbers or CVC values on MonitUp application servers.

10. Related Legal Documents

Terms of Service: /terms-and-conditions

Privacy Policy: /privacy-policy

Cookie Notice: /cookie-notice

Service Level Agreement: /service-level-agreement

11. Updates

MonitUp may update this page from time to time to reflect changes in product, operations, and legal requirements.