Encryption
Data is protected in transit using TLS/HTTPS and encrypted at rest.
PlaybookOps combines technical safeguards, organization-scoped access, transparent AI data practices, and documented operational controls to protect the knowledge customers place in the platform.
Last reviewed August 18, 2026Data is protected in transit using TLS/HTTPS and encrypted at rest.
Customer data is logically separated using organization-level controls and restricted to authenticated users in the same organization.
Administrative and member permissions limit access based on each user’s responsibilities.
Access logging, vulnerability monitoring, and documented incident-response procedures support ongoing platform protection.
Stripe processes payments. PlaybookOps does not store full credit-card numbers.
Customers retain ownership of their uploaded content and can request access, correction, export, or deletion.
PlaybookOps uses third-party AI services, including OpenAI, Anthropic, and Google, for capabilities such as document generation, chat assistance, embeddings, transcription, and media creation.
PlaybookOps does not use customer-authored content to train, fine-tune, or improve AI models. Relevant content is transmitted to providers for real-time processing subject to their applicable data-processing terms.
PlaybookOps is not currently designed for regulated sensitive data such as protected health information, Social Security numbers, financial account numbers, or payroll records. Multi-factor authentication and SOC 2 compliance are on the security roadmap and should not be represented as completed certifications.
Organizations with regulated-data requirements should contact PlaybookOps before uploading that information or beginning implementation.
Request additional information about privacy, subprocessors, data handling, or organizational requirements.
Contact PlaybookOps ↗Read the full Privacy Policy →