Agent and Integration Schedule

This Agent Schedule governs software agents, background responsibilities and connected accounts within the Service. Definitions in the Platform Agreement apply. An Authorized Task is a User instruction identifying the objective and sufficient matter, resource and permission scope for the operation. An Ongoing Responsibility is an Authorized Task separately enabled to repeat on the selected schedule. A Consequential Action is an external communication, publication, submission, filing, signature, payment, purchase, settlement communication, permission change or destructive external operation. An authorization is permission to perform the specified technical operation, not a general power of attorney, authority to practice law or an instruction to exercise a client's professional judgment.

At public-beta launch, Talden may perform authorized internal planning, reading, research, drafting, checking and saving to the User's Talden workspace. Microsoft 365 access is read-only. All external-write functionality remains disabled, including creating a draft in another system, adding a calendar event, saving to external storage or creating a task. Downloading a document for Customer's own use is not authority for Talden to send it elsewhere. No standing permission or screen description overrides the disabled state. A future enabled action is governed by sections 5 and 6, the specific approval, and any required Feature Activation Rider.

The User must identify the appropriate matter, selected files, connected accounts, objective and permitted operations. Talden may choose intermediate software steps within that scope without repeated plan approval. Access to a connector does not authorize unrestricted use of every item accessible through its token. Separate authorization is required to expand to another account, client, matter, shared mailbox, site, repository or materially different destination. Talden must pause a task when materially ambiguous authority cannot be resolved safely.

Webpages, messages, attachments and retrieved content are task data, not a source of authority to change permissions, send information, incur charges or override instructions. Talden must not treat a third party's embedded command as Customer's authorization. A broadly phrased objective does not authorize a legal commitment, access-control change or unbounded spending. Customer is responsible for the authority it actually gives; Talden is responsible for staying within the approved technical scope and its express safeguards.

An Ongoing Responsibility may run every 15 minutes, hourly or daily, only as selected and recorded. The activation record identifies its objective, resources, matter, permitted read and internal-draft operations, frequency, start, expiry or continuation condition, run cap, credit budget and stop method. It may read selected Outlook messages, including message bodies and attachments, calendar or OneDrive material, or rerun public research. It may prepare and save work inside Talden while the User is away. It may not send, publish or write to connected services at launch.

Scheduling is best effort, not a docketing, emergency alert or guaranteed deadline service. Access restrictions, revoked grants, service outages, run caps, exhausted credits or failed subscription payment may delay, skip or stop runs. Talden will present actual status rather than report a failed or partial job as complete. The User must monitor the responsibility's continuing appropriateness and independently maintain critical deadlines. Each run consumes credits under Document 02; a run has no authority to buy credits without the separate auto-refill authorization.

The User may pause or revoke a responsibility at any time. Revocation stops unstarted runs and further operations as soon as received and applied; Talden will make reasonable efforts to halt in-flight processing but cannot undo a transfer already completed within valid scope. Material expansion, reactivation after loss of authority, or a change from read to write requires renewed approval. A responsibility ends when its authorization expires, the account closes, active subscription access ends, the relevant connector is disconnected, or Talden disables it for a valid reason. Mere retention of a task record does not renew its authority.

The optional Microsoft connection can read the authorized Outlook mail, attachments, calendar, contacts and OneDrive files. Shared mailboxes and SharePoint resources require explicit selection and any necessary organization-admin consent. Talden may import selected material, transmit the necessary content to approved AI and infrastructure providers, produce analyses and drafts, and retain resulting work under the Data Addendum. Outlook material may include third-party communications and confidential client data. Talden must obtain the distinct, express AI-processing permission in Document 10, section 6 before using email for AI analysis; Microsoft's OAuth permission screen alone does not replace that disclosure.

Talden will request only scopes necessary for activated read functions. A User must not authorize another person's mailbox or organization resource without sufficient authority. Background mailbox monitoring requires the separate Ongoing Responsibility activation, not merely connecting the account. Talden will not use Microsoft API data or its derivatives for advertising, marketing audiences or an unrelated shared corpus.

Disconnecting in Talden removes its stored tokens and stops future access. It does not necessarily remove the Microsoft-side consent grant or imported copies. Users should also revoke the grant through Microsoft personal-account permissions or Microsoft work/school applications, as applicable, and contact the organization's administrator where needed. A separate deletion request covers imported copies, subject to the Data Addendum and Microsoft's applicable source-data correction, restriction, deletion and abandonment requirements. Talden will not characterize an outstanding Microsoft-side grant as revoked merely because its local token was deleted.

5.1 Activation rule. The modules in this section are contract terms for a specifically activated future feature, not representations of current availability. No module becomes operational or authorizes a data transfer merely because Customer accepts this schedule. Before activation, Talden must approve provider eligibility and terms, complete required verification, identify recipients and regions, supply any necessary processing terms, and present the specific permissions and data notice. The User must then affirmatively activate the feature. Scope changes require incremental permission.

5.2 Google Workspace. Authorized reads may include selected Gmail messages and attachments, Drive files, Calendar entries and Contacts. Only the least necessary scopes for the enabled feature may be requested. Talden's use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy, including its Limited Use requirements. Restricted-scope data and derived information may be used only for approved, prominent user-facing functions, not advertising or shared-model training. Human access requires specific approval for identified material, a permitted security investigation, binding law, or another narrowly applicable Limited Use exception; the Agreement does not expand those exceptions.

Transfers for an approved function require the User's informed permission. A merger or asset-transfer provision does not replace explicit prior consent where Google's policy requires it. Talden must complete applicable verification and any required security assessment before public access, and may not request dormant write scopes to future-proof the product. Disconnect in Talden and revoke at Google third-party connections; imported copies and deletion remain governed by the Data Addendum and applicable source rules. Gmail sends, external drafts, Drive writes or Calendar creation require the separate write activation and approval below.

5.3 Clio Manage and Grow. An activated Clio connection is limited to the approved Clio account, product and region, which must be stated before authorization. Supported regions or APIs in code do not constitute approval to transfer client data internationally. Authorized reads may cover selected matters, contacts, communications and documents. Creating tasks, notes, calendar entries, documents or Grow intake leads is an external write, requiring separate activation and scope. No Clio module may be enabled until Talden's eligibility under Clio developer terms, including any applicable competitive-service restriction, is resolved and required permissions are documented. Customer's Clio subscription alone does not supply Talden's developer license.

5.4 Messaging channels. Slack, Teams, WhatsApp, Twilio SMS, Google Chat, Signal and iMessage are not launch channels. Any later channel requires channel-specific eligibility, verification, consent, retention and transmission approval before it is offered. Incoming messages are untrusted context and cannot themselves authorize external acts. Outgoing legal or client communications require the consequential-action controls below and any legally required recipient permission or AI disclosure. This module does not license bulk solicitation, message recording, or a channel that its provider does not authorize. The applicable channel, provider, recipient class and opt-out mechanism must be identified in the activation record.

Every Consequential Action requires a User's approval immediately before submission, after the Service displays the actual sending account, recipient or destination, final content, attachments, amount if any, and practical consequence. Approval of a draft is not approval to send; approval to send one version is not approval to send a materially changed version. A changed recipient, attachment, material term, payment amount or permission scope requires renewed approval. The User must possess the relevant authority and complete the professional review required by the Platform Agreement. Talden does not supply a lawyer's signature or become counsel to a recipient.

A bounded standing authorization may cover lower-risk external operations, such as saving drafts to a specified folder or creating identified internal tasks, only if a separately activated feature expressly permits it and the record identifies the resources, operation, maximum frequency, duration, spending limit, logs and revocation method. Standing authorization may not bypass the per-action gate for external communications, publication, filings, signing, settlement communications, purchases, payments, access-control changes or irreversible deletion. No external email batch may exceed the enabled recipient limit, which may not exceed 50 under this beta architecture; every recipient, including copy and blind-copy recipients, must be visible in the approval record.

Talden must use idempotency or equivalent duplicate-prevention controls where available, avoid automatic retries of an uncertain consequential submission until actual status is checked, show partial completion accurately, and notify the User of a material execution error. A stop instruction prevents future attempts; it cannot guarantee recovery of a message delivered, filing accepted, payment completed or other irreversible act. The Agreement's limitations apply, but there is no blanket deeming of every unauthorized agent act as Customer's act.

Research may use public government and legal-publisher sources, tax or financial regulators, other permitted public sites and a User-supplied source list. Public availability is not a representation of a license to scrape, retain or redistribute an entire work. Talden may retain necessary excerpts and source links for the authorized task within applicable rights and access rules. A source-storage character limit is a technical maximum, not a copyright safe harbor. Customer must preserve required source attribution and may not use a Talden feature to circumvent a paywall or subscription restriction. Talden remains responsible for its own access permissions and extraction design.

Task records identify scope, approvals, timestamps, relevant source or destination identifiers, execution result and stop events to the extent supported by the enabled feature. Content-bearing records remain Customer Content and follow the Data Addendum; auditability is not an unlimited-retention license. Talden will supply the available export, not a certification that the record establishes legal authority, evidentiary admissibility or correctness of the work.