Skip to content

Data and privacy

When you connect your assistant as yourself (scope openid graphql:role:user), it sees what you see in the emely app, never more. It runs with the app’s own user role and your own token, so it can reach exactly the data the app shows you, and nothing the app hides from you. Each tool answers only the fields named for it in MCP tools. Today that is your workspaces, the society catalogue and your own society memberships.

The assistant works in one workspace you chose (see The workspace switch). Every answer says which workspace it is about, and your society memberships follow it: with a workspace chosen the assistant lists your own and that workspace’s, never another workspace’s.

Some data stays in the app, and the assistant never reads or edits it: the private person records behind artists (name, contact, address, date of birth), your label and company contacts, payments and plans, sign-in, and connected apps. For these it answers with a link to the right app screen (link_to_app).

Staff connections stay narrow. A staff member who connects with their own sign-in gets a plain user connection, with no staff rights. The staff tools on the api roles reach only what is described below.

The api roles (scripts, society and import tools) can reach two things only: the shared society catalogue, and the caller’s own society memberships. Other people’s data is never reachable on them. This covers people, names, contact data, IPI name numbers and member numbers.

Access is enforced by roles, not by filtering in the application. Every token is restricted to one role: either the app’s user role alone, or the api roles. There is no admin access in the MCP server.

  • api_operator maintains the catalogue. It has permission on the society catalogue and the reference vocabularies it needs, and nothing else. A query for a person fails at the database.
  • user is your own sign-in: the same rows as the app, including the society catalogue and your own memberships, which the assistant can read. It cannot change memberships yet, so use the app for that. The MCP never sees more than you see in the app.
  • api_user reads and writes the caller’s own memberships and reads the catalogue. It has no permission on anyone else’s rows.

Membership identifiers are write-only. A member number, an IPI base number, an IPN or a name’s IPI/CAE number can be sent on a write but is never returned. Flags such as hasMemberNumber say whether one is on file.

Two more layers sit on top:

  • The API and the MCP server map every response through fixed field lists. A field that is not named in the response schema is never returned.
  • Neither service logs request or response bodies.

The apps you have signed in to through OAuth are listed under Account settings, Connected apps in the emely app, and you can revoke an app there. Revocation stops new tokens for that app; an access token the app already holds keeps working for up to 15 minutes.

Data is hosted in the EU.