Security overview
Play encrypts stored data with AES-256 and data in transit with TLS 1.3. Access controls determine who can use shared resources and connected accounts.
| Area | Protection or control |
|---|---|
| Stored data | AES-256 encryption at rest |
| Data in transit | TLS 1.3 encryption |
| Shared resources | Permissions for people and teams |
| Connected services | Account access governed by authorized integration permissions |
| Enterprise identity and governance | SSO, SCIM provisioning, and audit logs |
Before sharing work, review the resource’s members and inherited access. Permissions and roles explains the access model; Data handling and privacy covers connected information and the Privacy Policy.
Review organization requirements
For an enterprise security review, identify the requirements you need confirmed:
- Identity provider and provisioning requirements.
- The resources and connected accounts users need to access.
- Audit-log, retention, and deployment requirements.
- Any specific compliance evidence or contractual terms your organization requires.
Enterprise security lists the verified offering. Do not treat a general security feature description as evidence of a particular certification or a deployment commitment.
Still stuck? Email support@play.fast