Data and retention

Conservatory tenants include controls for how member data is isolated, kept, and removed. These exist to support institutional requirements such as FERPA and your own records policy.

Tenant isolation

Your tenant’s data is isolated from every other tenant and from the public Ember commons. Accounts in your tenant cannot sign in elsewhere, and no other tenant can see your members or their work. Isolation is enforced in the application layer on every request, not left to client behavior.

Set a retention policy

In the Admin area, under Privacy, set your retention window. The policy governs how long member practice data is kept and what happens when a member leaves your tenant. Choose a window that matches your institution’s records requirements.

When a member leaves

When you remove a member, their tenant data is handled according to your retention policy rather than deleted on the spot, so you can meet record-keeping obligations. If your policy calls for removal after a period, Ember applies it automatically.

What is stored

Within a tenant, Ember stores the same kinds of practice data it stores for any player: profiles and instruments, routines and goals, practice history, and tone and range measurements. Much of this is produced on the player’s device as they practice. Audio is analyzed on the device; raw recordings are not uploaded.

Exports and requests

If your institution needs to export or remove a specific member’s data to satisfy a request, contact your Ember support representative. Because your tenant is isolated, these operations are scoped to your institution only.