Integration Terms

These Integration Terms form part of the ScreenJournal Business Terms of Service (the "Terms") and apply whenever a Member connects a Connected Tool to the Services. Capitalised terms not defined here have the meanings given in the Terms. If these Integration Terms conflict with the Terms on a matter they cover, these Integration Terms prevail.

1. What the integration feature is

1.1 The integration feature lets an AI assistant or other application that supports the Model Context Protocol (MCP) query the Services on a Member's behalf. Today it consists of our MCP server at mcp-beta.screenjournal.ai and the OAuth sign-in through which a Member authorises a Connected Tool. Any other programmatic access to the Services is available only if we agree it in writing, and these Integration Terms then apply to it as well.

1.2 The integration feature is a beta feature under section 7 of the Terms. It is provided as-is, may change or be withdrawn at any time, and has no service-level commitment.

2. How a connection works

2.1 Who can connect. Any Member of the Customer's organisation can connect a Connected Tool from the MCP page of the web app. Connecting opens our consent screen, where the Member signs in with their own account and approves the tool.

2.2 Read-only. A connection is granted only a read-only permission. A Connected Tool can read data; it cannot create, change or delete anything in the Services. Requests to change data made with a connection's token are refused.

2.3 Same view as the Member. A Connected Tool sees exactly what the connecting Member's role can see in the Services, and no more. A member sees their own data; a manager sees the people they manage; owners, administrators and viewers see the organisation. This can include timelines, descriptions, scores, rankings, presence, application usage, audio transcripts, review cases, alerts and the organisation's policy text.

2.4 Tokens. The Connected Tool receives a short-lived access token, valid for up to fifteen (15) minutes, and a refresh credential that keeps the connection alive for up to sixty (60) days unless it is revoked first.

3. The Customer directs the disclosure

3.1 When a Member connects a Connected Tool, data flows from the Services to that tool on the Customer's instruction. The provider of the Connected Tool is a recipient the Customer chooses. It is not our subprocessor, and we do not control it.

3.2 The Connected Tool's own terms and privacy policy govern what its provider does with the data, including where it processes the data, how long it keeps it and whether it uses it to train models. The Customer is responsible for reviewing those terms and for the lawfulness of each disclosure, including any notice to Monitored Users and any international-transfer requirement.

3.3 The Customer decides whether its Members may connect Connected Tools, and which ones. The Services do not currently provide an organisation-wide setting to turn the integration feature off; the Customer must set and enforce its own rules for its Members.

3.4 Data a Connected Tool has received is outside our systems. Our deletion obligations under the Terms and the Data Processing Agreement do not reach it.

4. Revocation

4.1 A Member can disconnect a Connected Tool at any time from the Connected tab of the MCP page. Disconnecting ends the refresh credential at once, but an access token already issued keeps working until it expires, so the tool can keep reading for up to fifteen (15) minutes after disconnection.

4.2 When a Member is deactivated or leaves the organisation, their Connected Tools can no longer renew their access, and existing access tokens expire within fifteen (15) minutes.

4.3 If the Customer needs a connection ended on behalf of a Member, it can deactivate the Member or ask us at support@screenjournal.ai for help.

5. Security obligations

The Customer must ensure that its Members:

1. connect only tools they trust, from the provider's genuine application or website;
2. do not share a connection, its tokens or a signed-in session with anyone else, and do not copy tokens out of the tool;
3. disconnect a tool they no longer use, and disconnect at once and tell us at support@screenjournal.ai if they suspect a token or the tool's account has been compromised; and
4. do not use a Connected Tool to show data to people who could not see it in the Services.

6. Limits

6.1 We apply rate limits to the integration feature to protect the Services. They are set well above normal use and may change. A Connected Tool that exceeds them is refused temporarily.

6.2 The Customer must not use the integration feature to extract data in bulk, overload the Services, or get around the read-only permission, the role limits or the rate limits. The Acceptable Use Policy applies.

7. Answers produced by Connected Tools

Answers a Connected Tool produces are generated by that tool, not by us. They can misread or misstate the data they receive. Section 13 of the Terms applies to the data the Services provide, and we are not responsible for anything a Connected Tool produces from it.

8. No warranty, liability

8.1 We make no commitment about the availability, performance or compatibility of the integration feature with any particular tool, and we do not support third-party tools.

8.2 We are not responsible for a Connected Tool, its provider, or what the provider does with data a Member chose to send it. The Customer's indemnity in section 19.1 of the Terms covers claims arising from a Connected Tool its Members connected.

8.3 Our liability arising from the integration feature is limited as section 7.2 of the Terms provides for beta features.

9. Suspension and termination of access

9.1 We may suspend or end a connection, a Member's use of the integration feature or the feature as a whole, at any time, including where we reasonably suspect misuse, a compromised token, a security threat, or a breach of these Integration Terms. Where practicable we tell the Customer first.

9.2 The Customer's right to use the integration feature ends when the Terms end, and any connections that remain are revoked when we delete the organisation's data under the Terms.

10. Changes

We list every change to these Integration Terms on the Legal page with its effective date and, where practicable, post material changes before they take effect.