Personal data never goes to coding agents
We use AI coding agents under human review and automated tests, but no personal data is ever supplied to them. That boundary applies throughout development—not only after launch.
Unusual Assembly / Work with us / Data privacy
Privacy-first software for creative organizations.
Protect student, artist, staff and customer data with software designed around ownership, controlled access and private-by-default workflows.
UA_DATA
Your organization should control its data
Protecting data starts with clear ownership. Your organization owns its records, controls who can see them, and can export or delete them. Apps are published through your own Apple and Google developer accounts, so the relationship does not depend on being locked into ours.
Privacy by design
- Role-based access keeps each person limited to the information their role actually requires.
- Server-enforced permissions protect records at the source instead of relying only on what an app screen hides.
- Invitation-only access can keep private programs and communities closed to unapproved sign-ups.
- Private-by-default workflows keep portfolios, drafts and internal records out of public view until someone intentionally shares them.
- Data minimization means designing forms and workflows to collect what the product needs—not everything it could ask for.
- Export and deletion give your organization a practical way to retain control over its information.
Privacy for students and families
For programs serving minors, access rules are enforced on the server. Students, families, teachers and administrators each see only what their role allows, and families see only their own student's work.
A clean exit is part of ownership
Your organization can export or delete its data. We document account setup and ownership so the system can keep serving your team without creating artificial dependence on the studio.
Before you choose software
Questions worth asking every vendor
- Who owns the data, and can your organization export or delete it?
- Who can access each record, and are those rules enforced on the server?
- Is personal data used with AI systems during development, support or operation?
- Which accounts belong to your organization, and what happens when the contract ends?
- What is private by default, and what requires an intentional publishing action?
UA_HELLO
Tell us what needs protecting. We'll design around it.
We reply with questions first, including what data the product truly needs, who should see it, and what should remain private.