Encryption practices, access controls, authentication paths, monitoring, recovery planning, and vendor oversight.
Security & ComplianceProtection that follows the work.
Security in Workroomly is not a badge beside the product. It is the discipline around access, infrastructure, integrations, recovery, and the customer information moving through every workflow.
Trust is stronger when buyers can see what exists today.
This page separates current controls from the work still maturing, then connects those practices to platform security, integrations, subprocessors, the DPA, and a direct security contact.
Identity, infrastructure, data handling, product changes, connected services, and customer-facing operations.
A candid view of the compliance roadmap, supporting documentation, subprocessor information, and contact paths.
Current Security Controls
Encryption
We protect customer data with encryption in transit and encryption at rest across the core platform and supporting infrastructure where applicable.
Access Controls
We apply role-based permissions, account protections, and controlled administrative access to reduce unnecessary exposure to customer data.
Authentication Security
We support stronger account protection through secure authentication flows and evolving account security controls, including MFA-oriented protection paths.
Monitoring & Logging
We maintain platform monitoring, alerting, and operational visibility to help detect issues, investigate incidents, and improve platform resilience.
Backup & Recovery
We plan for continuity through backup, recovery, and infrastructure resilience practices designed to reduce operational risk and support service restoration.
Vendor Oversight
We rely on established service providers for key infrastructure and enabled integrations, and we maintain visibility into how they support the platform.
Security is not a single feature
For Workroomly, security covers the full system: data storage, communication flows, account access, infrastructure, integrations, internal administration, and the handling of customer-facing workflows.
Platform Security Areas
These are the main areas we actively think about as we strengthen the Workroomly platform.
Identity & Access Management
Controlled access, workspace permissions, administrative safeguards, and least-privilege thinking across internal and customer-facing surfaces.
Change Management
We continue to improve how code, infrastructure, and configuration changes are reviewed, shipped, and tracked over time.
Infrastructure Resilience
We build on managed infrastructure and operational practices designed to improve service continuity, reliability, and controlled scaling.
Data Handling
We consider retention, deletion, export, access, visibility, and the operational flow of customer data across the platform.
Operational Visibility
Logs, alerts, and monitoring support platform operations, issue investigation, and better incident response readiness.
Incident Readiness
We are building toward stronger internal response discipline, escalation procedures, and clearer security operations maturity.
Connected Integrations and Data Responsibility
Workroomly may connect with third-party services for login, inboxes, calendars, advertising workflows, and communication channels. These integrations are part of the trust surface too.
OAuth and Connected Accounts
Customers can authorize integrations such as Google, Microsoft, and Meta-connected workflows. We treat the handling of connected-account data as a privacy and security responsibility, not just a product feature.
- Authorized account connection handling
- Feature-linked access scope expectations
- Integration-aware privacy disclosure
- Customer-controlled enablement
Messaging and Customer Channels
Where customers enable messaging or telephony-related workflows, the platform may handle communication data and metadata in support of customer operations use cases.
- Customer-enabled channel workflows
- Message and communication metadata handling
- Customer responsibility for lawful outreach
- Integration-specific operational controls
Lead Capture and API Intake
Workroomly may receive customer data through widgets, forms, embedded lead capture, and API endpoints. This means security and transparency must cover inbound data collection flows too.
- Structured lead ingestion
- CRM lifecycle data handling
- Embeds and endpoint-based intake
- Customer responsibility for notice and consent where required
Privacy-Aware Product Direction
We design the platform with privacy, access control, customer data responsibility, and future contractual processor obligations in mind.
- Privacy Policy and Terms separation
- DPA availability for customer processor relationships
- Subprocessor transparency
- More formal enterprise trust documentation over time
Customer responsibility still matters
Customers remain responsible for using Workroomly lawfully, especially when enabling outreach, messaging, telephony, ad-connected workflows, lead capture, or other customer data collection and communication features.
Compliance Roadmap
Our compliance approach is to first build real security and privacy discipline, then improve procurement readiness, and then pursue more formal audit and certification milestones as the company matures.
Current Focus
- Security-focused product and infrastructure design
- Clearer legal and privacy documentation
- Access control and internal process maturity
- Operational monitoring and evidence discipline
Next Maturity Layer
- Enterprise-friendly trust documentation
- Published DPA and clearer processor posture
- Better vendor and subprocessor transparency
- Improved audit readiness processes
Future Audit Direction
- SOC 2 readiness over time
- More formal control evidence collection
- Stronger internal security governance
- More structured operational review cadence
What we do not claim
- We do not claim SOC 2 certification on this page
- We do not claim ISO 27001 certification on this page
- We do not claim HIPAA compliance on this page
Subprocessors
The providers below support core Workroomly infrastructure and enabled integrations. Some are only used when customers turn on specific features.
| Provider | Purpose | Typical Data Involved | When Used |
|---|---|---|---|
| Amazon Web Services (AWS) | Core cloud hosting, storage, infrastructure, and platform operations | Application data, files, metadata, logs, backups, and operational platform data | Core platform infrastructure |
| Google login and Google-connected integrations such as Gmail, Calendar, and related workflows where enabled | Identity data, authorized integration data, mailbox/calendar connection metadata | Only when enabled by customer or user | |
| Microsoft | Microsoft login and Microsoft-connected integrations such as Outlook and calendar-related workflows where enabled | Identity data, authorized integration data, mailbox/calendar connection metadata | Only when enabled by customer or user |
| Meta / Facebook | Meta login and Meta-connected advertising workflows where enabled | Authorized account connection data and relevant ad integration metadata | Only when enabled by customer or user |
| Twilio | Messaging, WhatsApp, SMS, voice, or related communication workflows where enabled | Phone numbers, message metadata, communication data, related workflow metadata | Only when relevant communication features are enabled |
We may update this list over time as our infrastructure and integrations evolve.
Data Processing Addendum (DPA)
If your team handles personal data through Workroomly, our DPA defines exactly how we protect it — including who controls what, how we secure it, and what happens when you need data deleted or exported.
What's covered
- Your role as controller, ours as processor
- What data we process and why
- Our security commitments to you
- How we manage subprocessors
- Data deletion, export, and return
- Support for your privacy obligations
You'll want this if
- Your procurement team requires it
- You operate in regulated industries
- You handle personal data at scale
- You need formal controller-processor terms
Ready to review
Our DPA is available as a standalone document. Review it alongside our Privacy Policy and Terms of Service.
Related Trust Documents
We keep our public trust materials separate so each document does one job clearly.
Privacy Policy
Explains how personal data is collected, used, stored, shared, and handled across the platform.
View Privacy PolicyTerms of Service
Explains the legal terms for using Workroomly, including integrations, AI features, messaging, and customer responsibilities.
View Terms of ServiceDPA
Defines controller-processor terms where Workroomly processes customer personal data on behalf of customers.
View DPASecurity and Compliance Contact
If you have procurement, privacy, legal, or security questions about Workroomly, reach out and we will point you to the right documentation or respond directly.