How Unity keeps secrets a secret, no matter which tool the team is in.

The challenge

One universal tool for secrets, whatever platform the work happens in.

Unity’s DevOps and Customer Support teams routinely exchange sensitive credentials, API keys, and proprietary files — both internally and with external contributors or customers. Their existing tools, including email, Slack, Zendesk and Jira, aren’t designed for the level of secure data handling Unity required.

Audit compliance with SOX, SOC 2 and GDPR required strict control over how data is stored, shared, and retained, regardless of the platform used. Unity needed to prevent secrets from living in third-party systems while still supporting external collaboration.

The solution

Two use cases, one secure store

Unity adopted SendSafely to securely transmit and store sensitive data inside and outside the organization. Two key use cases emerged across the customer engagement and technical teams.

1. Use case 01
   External Collaboration

   The Customer Engagement Team uses Workspaces to collect and store sensitive customer data during support. A Workspace is associated with a specific ticket, folder names are generated from the corresponding bug, and support engineers are provisioned access automatically.

2. Use case 02
   Internal Collaboration

   Each technical team maintains its own secrets store of passwords, API keys, and configuration files. When temporary credentials must be shared beyond a team — with another group or a contractor — SendSafely is the standard tool.

3. Use case 03
   Controls

   Key features include automatic expiration and deletion, access limits controlling how many times a package can be opened, and detailed tracking of views and accesses.