Skip to content
eben.
← Back to Eben

VERSION 2026-10-16-MCP-1

AI connection terms.

These additional terms apply when a company administrator approves a customer-directed external AI connection.

This addendum supplements the customer's existing agreement with Pixelbrink Software Limited. An authorised customer administrator chooses which external AI service and categories of information may be connected. Each user must then authorise their own connection. Approval is a documented instruction to disclose information requested through that connection, within the user's current Eben permissions and the approved categories.

Research can include company, officer, property and planning information. Documents can include extracted passages and tables, filenames and source references. Deals can include briefs, borrower and guarantor information, financial and credit information, findings and saved review material. Monitoring can include watchlists and alerts. These may contain personal or confidential information. The integration reads existing information; it does not change records, launch Ask Eben, create reports or process new documents.

The customer selects and contracts with its external AI service separately. The customer must authorise the account or workspace used, establish that sharing is lawful and permitted, and check appropriate contractual coverage, retention, training settings, processing locations and any required international-transfer safeguards. An employee's personal subscription alone is not company approval. The selected AI service's own terms govern its use of information after receipt; it is not appointed as Pixelbrink's subprocessor merely because the customer connects it.

Pixelbrink remains responsible for its own processing, secure transmission, tenant isolation, enforcing current permissions and assisting under the existing data-processing agreement. Pixelbrink will flag instructions it considers unlawful. This addendum does not transfer those duties to the customer or promise zero retention, no training or UK-only processing by the chosen AI service.

Administrators may disable a service or revoke connections in Settings. Users may revoke their own connections. Revocation stops future requests; it cannot recall information already sent or delete conversations or copies held by the external service. The customer should use that service's deletion and retention controls where needed. Changes to approval require reconnection. Connections expire after 30 days and must be authorised again.

Eben retains the administrator's approval, scope and terms version as evidence of instructions under the agreement. Connection records contain user, provider, scopes and connection timestamps. Operational usage logs contain action, outcome and timing for up to 90 days, without queries, document contents or tool responses. Credentials are protected and are never included in ordinary diagnostics. AI answers can be incomplete or wrong: check original sources before making lending decisions.

Eben applies shared company request, tool-call and data-volume limits, shown in AI connections settings. These limits may block further reads; reconnecting does not reset them. Aggregate counts and fixed security-alert types are kept for up to 90 days. Company and Pixelbrink administrators may receive content-free alerts about high usage, limits and repeated rejections. Limits reduce bulk extraction but do not prevent an authorised recipient retaining information already returned.

Contact andre@pixelbrink.co.uk for assistance, export or deletion requests. All other provisions of the customer's existing agreement remain in force.

LET’S LOOK AT A REAL CASE

Bring a question.
See what Eben can find.

Tell us about your team and the work you want to make easier. We’ll walk through the platform and discuss access that fits.

Book a demo Speak to PIXELBRINKWe’ll contact you to arrange a convenient time.