Security & compliance
Built to protect your game project
A source control system holds your most valuable work. We take that seriously. Here's exactly how we protect it — and how you can verify the claims.
Purpose-built
How we keep your project safe
Encryption in transit
All transfers between the desktop app, web dashboard, and our servers use TLS 1.2+. Your files never traverse the internet in the clear.
SHA-256 integrity verification
Every file is hashed on upload and verified on download. Silent corruption — a file that looks correct but isn't — can't happen.
Role-based access control
Three clear roles (owner, admin, member) plus per-project membership. Contractors and freelancers get access to what they need, nothing more.
Complete audit logs
Every commit, sync, download, lock, and permission change is logged with actor, timestamp, and IP. Enterprise plans extend retention and include exports.
Open-source desktop app
Our desktop client is MIT licensed. Read the source, build it yourself, verify exactly how your data is handled. No black boxes.
Scoped API keys
API access uses per-project keys that can be regenerated instantly if compromised. No long-lived credentials, no broad org-wide tokens.
How access control works
Access is layered: • Organization-level roles determine what you can do across the org — owners handle billing, admins manage teams, members do the work. • Project membership determines which projects a member can see. A contractor added to one project has no visibility into the rest of your org. • API keys are scoped per project. A desktop app linked to one project can't access another — even if both belong to the same org. This layered model means you can bring on a freelance texture artist for two weeks, give them exactly the access they need, and remove it cleanly when the engagement ends.
Data handling and storage
Files are stored on Bunny CDN, which operates a global network of data centers with physical and logical security controls. Files are stored with content-addressable keys derived from SHA-256 hashes, which means: • Duplicate content is stored once, even across projects — reducing your effective storage footprint. • Tampering is detectable at the byte level. If even one byte of a stored file changes, the hash won't match and the system refuses to deliver it. Metadata (commit messages, lock state, project structure, membership) lives in PostgreSQL with standard database-level security controls.
Authentication
Web access uses Stytch B2B magic links — no passwords to leak, no password resets to compromise. Sessions are time-limited and device-bound. Desktop and CLI access uses per-project API keys prefixed with `usc_`. Keys are stored as SHA-256 hashes server-side, so even a complete database compromise wouldn't expose raw credentials. Keys can be rotated from the dashboard at any time. For Enterprise customers, SSO / SAML integration is available. Contact us to discuss.
Verifying our claims
Most of our security posture is observable: • The desktop app is open source (MIT, on GitHub). Read the code, check the hashes, build it yourself. • The API is documented and uses standard HTTPS. Inspect traffic yourself — no proprietary protocols, no obfuscation. • Audit logs are yours. Export and review at any time. For studios with formal compliance requirements (SOC 2 type 2, data residency, specific contract terms), Enterprise plans include appropriate documentation and controls. Contact us for your security review checklist.
FAQ
Common questions
Are files encrypted at rest?
Files are stored on encrypted volumes provided by our storage infrastructure. For customers requiring customer-managed encryption keys or specific crypto controls, Enterprise plans offer additional options — contact us to discuss.
Where is my data stored?
Files are distributed across a global CDN for delivery performance. Primary storage is in North American and European data centers. Customers with data residency requirements should talk to us about Enterprise deployment options.
What happens if an API key is compromised?
Regenerate the project's key from the dashboard — the old key is invalidated immediately. Check the audit log for any unauthorized activity. We can help trace it if needed.
Do you support SSO?
SSO / SAML integration is available on Enterprise plans. Contact us with your identity provider details.
Can I export my audit log?
Yes. Studio plans include dashboard access to logs; Enterprise plans extend retention and include programmatic export for integration with your security tooling.
What's your incident response process?
We maintain an incident response plan and notify affected customers promptly. Enterprise contracts include notification SLAs specific to your requirements.
Have you been audited?
SOC 2 type 2 certification is on the roadmap. Enterprise customers with immediate compliance needs should contact us to discuss current controls documentation.
Protect your project on solid foundations
Free for solo developers. Scale securely when you bring on your team.
Start for free