End User Terms

composerID connects the decision your organisation makes about a piece of work to the systems that carry it out: your vendor management, recruiting, HR, finance, contract and service-desk systems. These terms explain, in plain language, what composerID does when your request passes through it, and what we and you can and cannot do. They apply to you as an individual using composerID inside your organisation’s Triage deployment. Your organisation’s own agreement with Deployed governs the deployment as a whole.

Who is involved

There are four parties. You are a person at a customer organisation: a requester asking for work, a hiring manager, an approver, or someone in procurement or HR. Your Organisation is the Deployed customer whose Triage deployment you are using. A Destination is one of your Organisation’s systems of record that a decision is published into, such as SAP Fieldglass, Beeline, Workday, Coupa or ServiceNow. Deployed is the company that makes Triage and composerID; composerID is the technology in the middle.

What composerID does with your request

Triage asks you the diagnostic questions, where you work (a web page, Microsoft Teams, Slack, Google Chat or ServiceNow), and reaches a decision about the right channel for the work. composerID takes that decision, gives it one Intent ID, checks it against each Destination’s own required fields, and publishes a valid record into each Destination your Organisation has connected. If a Destination needs a field you have not supplied, composerID asks you for it before publishing rather than creating an incomplete record. Every step is written to an append-only timeline under the Intent ID, so your Organisation can show later what was decided, when, and what was sent where.

Two things are always true. A Destination receives only a valid request plus the Intent ID: your diagnostic answers, the score and the Compliance File never leave composerID. And composerID never creates duplicates: publishing the same decision twice returns the same record.

What you cannot do

Do not use composerID to do anything dishonest or unlawful, to publish into a system you are not authorised to use, to try to break, probe or bypass its security, or to copy how it works in order to build a competing service. Do not enter information about other people that you are not permitted to share.

Responsibilities on both sides

Deployed’s job is to keep composerID working as documented and to keep your data secure, under the terms we have agreed with your Organisation. Your job is to use it lawfully and as intended: answer the questions honestly, follow your Organisation’s own policies for requesting work, and make sure you have the right to share the information you enter.

Stopping

You can stop using composerID at any time by not submitting requests through it; your Organisation controls whether it remains connected to each Destination. If your Organisation ends its agreement with Deployed, composerID stops publishing for it and its data is returned or deleted as that agreement provides. If you break these terms, Deployed will tell your Organisation, and access may be withdrawn.

Who owns what

Deployed owns composerID. Your Organisation owns the requests, decisions and records that pass through it, and the records created inside each Destination belong to whoever owns that system. While a request is being processed, your Organisation has given Deployed permission to process it on its behalf.

Your privacy

Your Organisation is the controller of the personal data in your requests, and its privacy notice explains what it collects and why. Deployed processes that data only on your Organisation’s instructions, under our Data Processing Agreement. If you want to exercise a data protection right, contact your Organisation first; Deployed will help it respond. Our own Privacy Policy covers the composer.id website and developer portal.

No guarantees to you personally

composerID is provided to your Organisation under its agreement with Deployed. To you as an individual it is provided as it is: Deployed does not promise that it will always be available, error-free or suited to every need, and any commitments about service levels are made to your Organisation, not to you.

Changes

We may change these terms. If we do, the date at the top moves, material changes are noted in the changelog, and changes take effect 30 days after posting. Continuing to use composerID after that means you accept them.

Contact

Questions about these terms: jamie.gannaway@deployed.co. These terms are governed by the laws of England and Wales.