Approach
SalesOps is a small, focused team operating a cloud-based B2B CRM. Our security program is proportionate to that context: we favour managed platforms with strong default controls, we minimize the personal information we collect, and we design privileged operations to require deliberate action.
Authentication and access
Email and password authentication for the SalesOps application
Current ControlGoogle single sign-on
Current ControlPassword reset with time-limited email tokens
Current ControlSession management with server-issued tokens
Current ControlRow-level authorization for workspace data
Every workspace read and write is scoped by the requesting user's workspace membership.
Current ControlRole-based access within a workspace (Admin / Manager / Rep)
Current ControlSAML / enterprise SSO
PlannedUser-configurable multi-factor authentication
Planned
Application security
TypeScript-strict application code
Current ControlServer-side authorization on every mutation
Current ControlServer functions run in a sandboxed edge runtime with least-privilege secrets
Current ControlInput validation with schema validators (Zod)
Current ControlAutomated dependency updates with review
Current ControlContinuous integration and code review before deploy
Current ControlStatic application security testing (SAST)
In DevelopmentFormal secure-SDLC documentation
Planned
Infrastructure
SalesOps runs on established cloud providers rather than self-managed servers. Our primary application database is hosted in the European Union (Germany). Web traffic is served through a global edge network operated by our hosting platform.
Managed Postgres database (primary region: Germany)
Current ControlManaged authentication service
Current ControlGlobal edge web hosting
Current ControlIsolated production and non-production environments
Current ControlDocumented disaster-recovery runbook
In Development
Encryption
All SalesOps web traffic uses HTTPS in transit. Our managed database provider encrypts data at rest using its standard managed-key mechanism. SalesOps does not currently offer customer-managed encryption keys.
TLS in transit (application and API)
Current ControlAt-rest encryption for the managed database (provider-managed keys)
Current ControlCustomer-managed encryption keys (BYOK / HYOK)
No
Monitoring and logging
Application error logging
Current ControlManaged database audit and query logs
Current ControlAdministrative-action activity trail inside the app
Current ControlCentralized SIEM with alerting
PlannedFormal on-call rotation
Planned
Vendor management
SalesOps engages a small, disclosed set of subprocessors. Each is chosen because it is a widely-used, security-mature platform. The current list is published at /legal/subprocessors and updated when new providers are engaged.
Vulnerability disclosure
Security researchers can report suspected vulnerabilities to info@salesops.ca. Please provide reproduction details and refrain from testing against production data belonging to other customers. We acknowledge good-faith reports and do not pursue legal action against researchers acting under this policy.
A machine-readable disclosure record is published at /.well-known/security.txt.
Roadmap
- Enterprise SSO (SAML) and user-configurable MFA.
- Formal secure-SDLC documentation and third-party penetration test.
- Consolidated audit logging with anomaly detection.
- Documented business-continuity and disaster-recovery testing.