Security Overview
Workplace.io is designed to help organizations understand culture and performance trends while protecting customer data
through encryption, access controls, monitoring, and secure development practices.
Last updated: December 16, 2025
At a glance
- Encryption: data is protected in transit (TLS) and protected at rest using encryption.
- Access controls: access is scoped by workspace membership and role-based permissions.
- Token security: OAuth tokens are protected and access-restricted to support integration sync.
- Monitoring & response: we monitor service health and security-relevant events and follow an incident response process.
Program summary
We operate a security program focused on confidentiality, integrity, and availability. We design controls to protect
customer data throughout its lifecycle—from ingestion through processing and storage—and we continuously improve our
practices as the product and customer needs evolve.
- Defense-in-depth: layered controls across identity, network, application, and data layers.
- Least privilege: access is scoped to role and business need.
- Secure by default: security controls are built into our workflows and deployments.
- Operational readiness: monitoring, alerting, and incident response processes support rapid remediation.
What data we handle
Workplace.io connects to collaboration platforms (currently Slack and Microsoft Teams) to generate culture and performance
insights. During processing, we may handle message content and related metadata. Message content is used only for analysis
and is retained for a short period; after processing, we retain primarily derived metadata and aggregated results needed to
operate reporting and trends.
Designed for organizational insight
Workplace.io is designed for team and organization-level insights. We support access controls and reporting structures that
reduce the risk of individual-level monitoring.
Infrastructure
Workplace.io runs on DigitalOcean infrastructure for application hosting and managed databases, with network and service
configuration designed for reliability and controlled access. Classification and culture inference workloads run on Amazon
Web Services (AWS) using Amazon SageMaker in secured, logically separated processing environments.
Encryption
We protect data in transit using TLS and protect stored data using encryption at rest. We also apply additional safeguards
for sensitive data, including limiting retention of message content and restricting access to secrets used for integrations.
- In transit: TLS for communication between clients, providers, and Workplace.io services.
- At rest: encrypted storage at the infrastructure layer.
- Secrets protection: credentials and tokens used for integrations are access-restricted.
Authentication
Users authenticate to Workplace.io using supported sign-in methods including single sign-on (SSO) and email/password.
Authentication is separate from data-source integrations: sign-in identifies the person, while integrations are managed
at the workspace level.
- SSO: Slack, Microsoft, and Google sign-in options.
- Password: optional email/password accounts for direct login.
- Session security: sessions use secure, HTTP-only cookies with CSRF protection on state-changing requests.
Access controls
Workplace.io uses workspace membership and role-based access control (RBAC) to determine who can view insights,
manage integrations, and administer workspace settings. Administrative actions are scoped to authorized roles.
Integrations and token handling
When a workspace connects Slack or Microsoft Teams, we store OAuth credentials needed to synchronize configured data.
Access is restricted and tokens are managed to support secure synchronization.
- Scope minimization: we request only permissions required for configured integration features.
- Access restriction: integration credentials are restricted to the services that require them.
- Revocation: disconnecting an integration stops future synchronization.
Webhooks
Where webhooks are used, requests are authenticated (signature verification and replay protection) and payload logging
is minimized to avoid exposing message content in logs.
Logging and monitoring
We collect operational telemetry and security-relevant logs to support reliability and incident investigation.
We minimize sensitive data in logs and avoid logging message content or credentials.
- Operational monitoring: service health, job processing, error rates, and performance signals.
- Auditability: administrative actions and key integration events support troubleshooting and review.
- Log hygiene: sensitive payload logging is minimized and redacted where appropriate.
Secure development
We apply secure development practices to reduce vulnerabilities and ensure changes are reviewed and deployed safely.
This includes peer review, dependency management, and controlled deployments.
Analytics and AI
Workplace.io uses a combination of deterministic rules and proprietary classification models to convert collaboration signals
into structured, research-informed metrics. We do not publicly disclose details of our model architecture, training data, or
internal signal taxonomy, but we design the system to be consistent, testable, and suitable for enterprise review.
Incident response
We maintain an incident response process to triage, contain, remediate, and communicate about security incidents.
When customer notification is required, we aim to provide timely, actionable information.
Compliance roadmap
We maintain a compliance roadmap aligned to customer expectations. Where third-party attestations are in progress,
we provide clear status updates and supporting security materials during reviews.