Security & Data Protection Overview

ServiceOS safeguards

• TLS/HTTPS for supported production web traffic.
• Role-based and account-based access controls within the application.
• Password hashing and session security controls.
• CSRF and application-layer request protections for browser actions.
• Operational logging, audit records, monitoring, and health checks.
• Database backup and restore-verification procedures.
• Payment handling that relies on a specialized payment processor rather than storing full card numbers in ordinary ServiceOS application fields.
• Security maintenance and incident-response procedures appropriate to the Service.

Shared responsibility

• Use unique passwords and protect administrator accounts.
• Give each user only the access needed for their job.
• Remove access promptly when staff leave or change roles.
• Keep devices, browsers, email accounts, and connected integrations secure.
• Do not place full payment-card numbers, account passwords, or unnecessary sensitive data in notes or support requests.
• Review audit, billing, and security notifications and report suspicious activity promptly.

Regulated or highly sensitive data

Unless ServiceOS has expressly agreed in writing to additional requirements, do not assume the Service is certified for specialized regulated data regimes. Contact ServiceOS Support before using ServiceOS for data subject to contractual or sector-specific security requirements.

Report a security issue

Report suspected vulnerabilities, unauthorized access, or security incidents promptly through ServiceOS Support. Do not publicly disclose exploitable details before ServiceOS has had a reasonable opportunity to investigate and remediate.