Practitioner licence

This licence applies to you if you subscribe to the Practitioner plan, if you hold a Facets credential, or if you are named as the facilitator on a team in a workspace that is not your own employer’s. It is between you and GasBuggy Media LLC and it forms part of the terms of service.

You do not sign it and you do not need to ask for it. Subscribing, or claiming a credential, has the same effect as signing, in the same way clause 1 of the data processing agreement works. We will counter-sign a copy for anyone whose own client procurement needs one. Where this document and the general terms disagree, this one wins on the point of disagreement, and the data processing agreement still wins over both on anything it covers.

A client can have a workspace of its own. On the Practitioner plan you can create one for a client, or register one you already work in as an admin, from the clients page in the product. The client’s owner accepts your engagement there; from then on the workspace is the client’s, you work in it as an admin, and either of you can end the engagement. You move between your own workspace and your clients’ with one sign-in. Clause 3 says who is the controller in each.

Your practice’s name and logo can be shown beside ours. On the Practitioner plan they appear beside Facets on the surveys, mails and reports of the teams and 360s you facilitate, and our attribution stays on every page and printed report. Clause 4 below tells you what you may and may not do about it.

If something the product does not do yet blocks an engagement, tell us at legal@facets.team — it moves up the list, and it is better evidence than a testimonial.

In a workspace you own, you are the controller and we are the processor. A client’s team you run there is, to us, people you added, and the data processing agreement already settles what follows: between you and us, you are the controller and we are the processor, for your client’s people exactly as for your own. We act on your instructions and we do not have a relationship with your client.

So, in a workspace you own, you must have your client’s written authority before you invite anyone who works for them. Authority to collect their employees’ names and work email addresses, to run the instrument on that team, and to be named as facilitator with the access clause 5 describes. You warrant that you have it. You do not have to send it to us and we will not ask for it routinely.

In a client’s workspace, the client is the controller, and you act on its grant. A client’s workspace belongs to the client’s organization, whoever created it. Its owner accepted your engagement in the product, and from then on the client is the controller of what the workspace holds and we are its processor under the data processing agreement. You work in it as an admin, on the client’s instructions, with an admin’s access and, on the teams and reviews that name you, a facilitator’s. The written authority this clause asks for is that grant, as the product records it: who accepted it, when, and the version of these documents in force when they did. The client can end the engagement at any time, and your access ends with it.

Either way, how you and your client divide the controller role between yourselves is yours to settle, and you should settle it in writing. An employer normally remains a controller of its own employees’ data whatever it asks a consultant to do, so in most engagements there are two controllers and a written arrangement between them is what the law expects. We are not a party to that arrangement and we cannot write it for you.

Every obligation in clause 4 of the terms — tell people first, do not make participation a condition of anything, have a lawful basis, keep the roster accurate, consult employee representatives where you have to — applies to every person you invite, including everyone who works for a client rather than for you. Being an outside facilitator makes those obligations harder to discharge, not lighter: the people answering have never heard of you, and the person who can actually tell them what is happening is your client.

You may set up a Leadership 360 for someone else, and it runs only if they accept it. Where you may start a review, you may set one up for a named person by their address, with you as its facilitator. They are asked to accept it on a page that tells them, before they do, that you will read who was asked and who has answered, anything written in the confidential box, and their brief before they do. Nothing is sent to anyone until they accept, they may decline, and an invitation nobody accepts expires. Setting one up for someone who works for your client needs the same authority as inviting them.

The Slack workspace or Microsoft Teams tenant connected to a client’s workspace is the client’s own, connected by the client’s own owner or admin. In a client’s workspace you cannot connect Slack or a Teams flow, and the product tells you so. Once the client has connected its own, the invitations and reminders you send there may go through it as direct messages, as they would for the client.

In a workspace you own, connect only your own Slack workspace or Teams tenant, and invite a client’s people by email. When you invite people who work for a client from a workspace you own, choose email: do not send their invitations or reminders through your own Slack or Teams, which your client’s people did not choose and whose administrators are yours.

Nothing in the product can tell whose Slack or Teams a connection is, so beyond the refusal in a client’s workspace this clause is the rule.

Charge for your work. That is the point of this tier. You may present, quote and debrief from the reports, build a paid engagement around them, and keep every dollar of it. We take nothing from what you bill and we do not need to be told about it. Clause 6B of the terms says the same thing and this clause is the longer version of it.

What you may not do, and none of it should be a surprise:

Do not remove or obscure our attribution from a report, an export or a slide you rebuilt from one. Presenting our output as your own instrument, or as another brand’s, is the line.

Co-branding beside our attribution is available on the Practitioner plan. Your practice’s name and logo can be shown beside ours on the surveys, mails and reports of the teams and 360s you facilitate. Our attribution stays on every page and printed report, and co-branding is not a way around the rule above.

A white-label option — our attribution replaced with yours rather than merely removed — is not available today. We would like to offer one and intend to. Until it exists and this licence says so, nothing here grants it, and the attribution rule above is the rule. Terms clause 6B says the same thing in the same words, deliberately.

Do not sell a report on to anyone who was not its subject. The team it is about, and the client who engaged you for that team, are the audience. A report is not a dataset to license onward, and an aggregate you build across several clients’ teams is not yours to publish or sell either.

Do not build a competing questionnaire out of our items. The instrument is published for inspection — every item, its keying, and how the scoring works — and publishing it is not a licence to reuse it. If a Creative Commons licence is ever attached to the items on that page, that licence governs them on its own terms and is the narrower permission that wins over this clause.

You may say publicly that you use Facets with client teams, name it in a proposal, and put our name in a list of the tools you work with. You may not describe yourself as a partner, reseller, distributor or agent of ours, because you are none of those and we have no such program.

This clause sets out what a facilitator can see and what that obliges you to do.

When you are named as the facilitator on a team, the product hands you three things nobody else can open unless they hold the same role — not the team lead, not a workspace owner or admin who is not the facilitator, a manager by that role alone, or us. An owner or admin names the facilitator, a manager or an admin can be named, and a facilitator cannot also be a member of the team:

Every member’s individual note, before and after it is released, for as long as you hold the role, with the check results and the reason anything was flagged, and the decision to release, hold or regenerate. Your access does not end when a note is released, and it covers the team’s past and future runs. It ends when an owner or admin names someone else or clears the role. Without a named facilitator those notes go out automatically; with one, none of them do.

A view of how the raters rated, which names raters beside patterns in how they rated: who showed no variance, who is systematically generous or harsh, and pairs whose ratings of each other are unusual once both tendencies are accounted for. It never shows ratings or comments as written. If you were named before anyone agreed to take part, and the run summarizes comments, it also includes a paraphrase of each written comment, without the writer’s name. Participants never see it.

On leadership reviews, a channel that goes to you and to nobody else, for the thing a rater will not put in a survey answer. It never enters the leader’s brief in any form.

You hold all three for the people who answered, not for the person who pays you. You must not relay an individual note, an individual rating, a rater-behavior observation, or anything from the confidential channel to your client’s management, to HR, or to anyone outside the team it came from — not in a debrief, not in a written summary, not verbally, and not in the form of a remark precise enough that the person can be worked out. You must not attribute a note to a rater, or confirm or deny a guess about who wrote one. You must not export, copy or retain any of it beyond what the engagement needs, and you must destroy your own copies when the engagement ends.

The release gate is a judgment you exercise for the team. You will sometimes be asked by whoever engaged you to hold something back, or to pass something on, because it is inconvenient. Neither is a decision they get to make through you. If holding to that costs you an engagement, we would rather you told us at legal@facets.team than quietly resolved it the other way.

Clause 2A of the terms applies to you in full and with an added edge: feedback-survey results must not be used in decisions about hiring, promotion, compensation, discipline, performance ratings or termination, and you must not produce, for a client, any document that lets them be. Being an outside consultant does not make you the route around a restriction the employer is subject to directly.

Breach of this clause is the one thing we act on first and explain afterwards, on the same footing as clause 4 of the terms: we may withhold reports, close the facilitator view, suspend a run, or restrict access to results while we look into it. We would tell you why and give you the chance to answer, and we would still act first.

Nothing in the product is or will be locked behind the credential. We say that on the certification page and we mean it here too: this clause governs what you may claim and how we may withdraw it, and it does not turn the credential into a gate on anything you can otherwise buy.

An earned credential is personal to you. It does not transfer with a job, cannot be shared with colleagues, and does not extend to a firm you work for. Where a purchase was made by an organization, the purchase is the organization’s and the credential is the individual’s — those are different objects and only one of them moves.

What you may say: that you are a certified Facets practitioner, with the version of the instrument your credential names, linking to your verification page. That page is the claim: anyone can check it, and a revoked credential renders as revoked rather than disappearing. Your directory listing, if you choose to have one, is opt-in, written entirely by you, and removable by you at any time.

What you may not say: that you are accredited, licensed, endorsed, employed by or in partnership with us; that Facets recommends you or your other services; that the credential carries continuing-education credit from any professional body, or a number of hours toward one, unless we have told you in writing that it does. We will write a letter describing what you completed, on request, for you to submit yourself.

We may revoke a credential for breach of clause 5, for misrepresenting what it is, for a practicum that turns out not to have met its conditions, or where the purchase behind it was refunded. We keep an evidence record of what each credential was awarded for, which is what makes a later review possible at all. Revocation removes the directory listing, ends the certified-practitioner rate, and marks the verification page. We would tell you first and hear your answer, except where clause 5 has us acting first.

You may use our name to say truthfully what you do with the product. You may not use our mark as your own logo, put it in your logo, use it as the dominant element on a page about your services, or use it in a way that suggests we produced or endorsed your material.

Do not register a company name, trading name, domain, handle or trademark that includes our name or is confusably close to it, and do not bid on it in a way that presents your service as ours. If you registered something before reading this, tell us and we will almost certainly say it is fine — asking afterwards is cheaper for both of us than a demand letter.

Either of us can end this by ending the underlying arrangement: you by cancelling the subscription, us by closing an account for breach. A credential is not ended by cancelling a subscription — it is personal and it does not expire — and cancelling does not revoke one.

Reports already delivered to you or to a client stay with them. Nothing here expires a report someone already holds. What ends is your right to run new cycles, to be named facilitator, and to make the claims in clause 6 if a credential has been revoked.

Your workspace and the data in it are governed by clauses 7 and 8 of the terms, including the ninety-day deletion of raw answers and the seven days of backup on top of it. If your client wants its people’s data out of a workspace you own when your engagement ends, that is a request you make to us and not one they can make directly, because to us they are people you added, as the workspace’s owner — which is clause 3 arriving where it always ends up. In a client’s own workspace it is the other way round: the workspace and what it holds stay with its owner when the engagement ends, and your access ends with the engagement.

Clauses 4, 5, 6 and 7 survive. The confidentiality duty in clause 5 in particular does not end when the engagement does, and it does not end when your subscription does.

We may change this document. Where a change materially reduces what you may do, we will tell subscribers by email before it takes effect and you may cancel rather than accept it. Re-dating this page does not re-date the general terms, and the reverse is also true.

Questions, a counter-signature request, or anything in clause 5 you would rather raise before it becomes a problem: legal@facets.team.