Data Processing Agreement
Work Intelligence Inc. | Last Updated: November 20th, 2026
This Data Processing Addendum (“DPA”) is between Work Intelligence Inc., a Delaware corporation at 251 Little Falls
Drive, Wilmington, DE 19808, USA (“WorkLLM”), and the business customer (“Customer”) identified in the applicable
order form, subscription agreement, WorkLLM Terms of Service or Execution and Customer Details Schedule
(“Execution Schedule”). The applicable agreement for the services is the “Agreement.” This DPA is available at
https://workllm.io/dpa/ and forms part of the Agreement when incorporated, including through the WorkLLM Terms
of Service at https://workllm.io/terms/, or when the parties separately execute the Execution Schedule, which
identifies the applicable Agreement. This DPA takes effect on the date agreed in the Execution Schedule or, for
incorporation by reference, on the date it becomes binding under the Agreement.
1. Scope and roles
“Applicable Data Protection Law” means privacy and data protection law applicable to the processing under this
DPA. “Customer Personal Data” means personal data that WorkLLM processes on Customer’s behalf to provide the
contracted services. WorkLLM acts as processor or subprocessor, and Customer acts as controller or processor on
behalf of a controller. A Customer acting as processor confirms its authority to instruct and engage WorkLLM on the
controller’s behalf. Schedule 1 describes the processing. WorkLLM’s independent processing for its own account
administration, billing and legal compliance is governed by its Privacy Policy and applicable law.
2. Instructions and permitted use
WorkLLM will process Customer Personal Data only on Customer’s documented instructions, including for transfers,
unless applicable law requires otherwise. Where permitted, WorkLLM will inform Customer of that legal
requirement before processing. The Agreement, this DPA, and authorized service configurations and actions are
documented instructions. WorkLLM will immediately inform Customer if, in its opinion, an instruction infringes
Applicable Data Protection Law and may suspend the affected processing pending resolution. Customer is
responsible for the lawfulness of its instructions and for providing required notices and obtaining any required
permissions.
WorkLLM will limit processing to Schedule 1 purposes, bind authorized personnel to confidentiality and grant access
only as needed. WorkLLM will not sell Customer Personal Data, use it for targeted advertising, or use it to train, fine-
tune or improve foundation models.
WorkLLM-managed inference and embeddings. For inference routed through OpenRouter, WorkLLM configures Zero
Data Retention (“ZDR”)-only routing under applicable OpenRouter and provider terms, disables prompt and chat
logging, and excludes Safety Retention and training endpoints. Provider eligibility reflects applicable provider policies
and OpenRouter’s terms, including limited exceptions in those terms. WorkLLM sends embedding requests directly
to Google Cloud (Vertex AI) outside OpenRouter, currently in U.S. regions, under Google’s Cloud Data Processing
Addendum and applicable no-training commitments. Inference ZDR does not apply to those embedding calls. Alibaba
Cloud inference is subject to Schedule 3.
Customer-supplied keys. The ZDR commitment applies to WorkLLM-managed inference. Where Customer
independently contracts with a provider and supplies its own API key or credentials (BYOK) and directs processing
under that agreement, the provider is a Customer-selected service for that processing. Customer’s provider
agreement and applicable retention and training settings govern that processing. WorkLLM remains responsible for
its own processing under this DPA and for any subprocessor it engages, including any intermediary it uses for BYOK.
WORKLLM / 13. Security and breach notification
WorkLLM will implement and maintain appropriate technical and organizational measures under Applicable Data
Protection Law, including the measures in Schedule 2. WorkLLM may update these measures without materially
reducing the overall protection of Customer Personal Data.
WorkLLM will notify Customer without undue delay after becoming aware of a breach affecting Customer Personal
Data, including accidental or unlawful destruction, loss, alteration, unauthorized disclosure of or access to that data.
WorkLLM will provide available details about the nature and scope of the breach, affected data and individuals, likely
consequences, mitigation measures and a contact for follow-up. WorkLLM may provide information in phases and
will investigate, take reasonable steps to contain and mitigate the breach, and assist Customer with required
notifications. WorkLLM will use Customer’s designated incident contact or, if none is designated, its account contact.
4. Subprocessors and integrations
Customer provides general written authorization for WorkLLM to use the subprocessors identified in Schedule 3 or
the subprocessor list made available to Customer before acceptance, including identified providers scheduled for
activation, subject to the change process below. WorkLLM will require each subprocessor by written contract to
protect Customer Personal Data under substantially equivalent obligations, including applicable transfer restrictions,
and will remain responsible to Customer for its subprocessors’ performance of those obligations.
WorkLLM will give Customer at least 30 days’ prior notice of additions or replacements of core subprocessors by
email or another agreed account channel, with enough information to assess the change. Core subprocessors include
AWS, OpenRouter, Google Cloud (Vertex AI), Qdrant Cloud, Mem0, Ably, Tavily, Composio and Alibaba Cloud, as
applicable. Customer may object on reasonable data protection grounds during the notice period. The parties will
work in good faith to resolve objections. While an objection remains unresolved, WorkLLM will, where technically
feasible, block the proposed subprocessor for the objecting Customer. If it cannot isolate that Customer’s traffic,
WorkLLM will suspend or disable the affected route or service feature to prevent that subprocessor from receiving
the Customer’s Personal Data. If unresolved, either party may terminate the affected service without penalty and
WorkLLM will refund unused prepaid fees.
OpenRouter catalog. Customer and its authorized users select models per request or AI agent. OpenRouter routes
across a dynamic catalog of more than 200 models and may select among eligible providers for a model. WorkLLM
limits managed requests to eligible ZDR endpoints. Customers may request the current eligible provider list at
hello@workllm.io. A model or endpoint update that leaves the agreed subprocessor list unchanged does not trigger
the 30-day procedure. OpenRouter does not commit to 30 days’ advance notice of downstream model-provider
changes.
Downstream changes. WorkLLM will maintain a record of authorized downstream subprocessors and review changes
to the eligible provider list. If Clause 9(a), Option 2 applies under Schedule 4, WorkLLM will send written notice
identifying each intended addition or replacement, with enough information for Customer to assess it, at least 30
days before that entity receives Customer Personal Data. Customer may object during that period, and the objection
safeguards above apply. For other changes subject to applicable law or mandatory transfer terms, WorkLLM will give
the required advance notice and opportunity to object. Newly eligible entities will stay blocked for affected traffic
until the applicable notice and objection process is complete. If WorkLLM cannot reliably enforce this at provider
level, it will suspend the affected route or feature for affected traffic.
Enterprise controls. Eligible customers may request workspace-level model or provider allowlists, exclusions
(including Alibaba Cloud) or regional processing restrictions. Controls apply once documented in an agreed Order
Form or Execution Schedule and implemented for the specified workspace, workloads and routes.
A third-party app that Customer independently contracts with and directs WorkLLM to connect may process data
under its own terms. A connector or other vendor engaged by WorkLLM to process on Customer’s behalf remains
subject to this section, including when an integration is initiated by Customer.
WORKLLM / 25. Assistance and audit
Taking account of the nature of processing and information available, WorkLLM will reasonably assist Customer with
requests from individuals, security duties, breach reporting, impact assessments and consultations with regulators,
and other responsibilities required by Applicable Data Protection Law. WorkLLM will promptly forward requests it
receives relating to Customer Personal Data and respond only on Customer’s instructions or as required by law.
WorkLLM will make available information reasonably necessary to demonstrate compliance and will allow and
contribute to audits and inspections by Customer or its independent auditor. WorkLLM may first provide relevant
records or assessments. Routine audits are at Customer’s sole expense, during normal business hours, at most once
a year and on at least 30 days’ written notice, subject to confidentiality and reasonable safeguards for other
customers’ data. These limits do not restrict an urgent audit following a confirmed personal data breach, an audit
required by a competent supervisory authority, or rights under applicable law or mandatory transfer terms.
WorkLLM will cooperate with competent authorities as required.
6. Return and deletion
At the end of the services involving processing, WorkLLM will, at Customer’s choice, return or delete Customer
Personal Data and delete remaining copies unless law requires retention. For deleted accounts, active data remains
available for recovery for up to 30 calendar days in the same hosting environment. Customer may request return or
earlier deletion at hello@workllm.io. Upon expiry of the recovery window without reactivation, or sooner upon a
verified deletion request, WorkLLM will permanently delete active data from its systems and initiate deletion of
active tenant data in its applicable subprocessor workspaces. WorkLLM’s own AWS backups expire on a rolling cycle
within 30 calendar days after permanent deletion from active systems.
Subprocessor-held backups and logs. WorkLLM requires deletion of remaining processor-held copies under each
applicable subprocessor DPA and retention schedule, subject to applicable law and mandatory transfer terms.
Provider timelines may differ from WorkLLM’s AWS backup cycle. Retained copies remain protected, access-
restricted and unavailable for ordinary service use until deleted. WorkLLM’s own backups remain encrypted and
isolated and may be accessed only for controlled recovery or deletion. Any data required by law to be retained
remains protected and limited to that purpose. WorkLLM will confirm its deletion and provide available information
about downstream deletion on reasonable request.
7. Order of precedence and contact
Schedule 4 applies as relevant to international transfers and regional law. Mandatory transfer terms prevail over any
conflict with this DPA or the Agreement. This DPA prevails over the Agreement on processing of Customer Personal
Data. The Agreement otherwise governs, including its liability provisions to the extent permitted by law and
applicable transfer terms. The DPA continues for as long as WorkLLM or its subprocessors retain Customer Personal
Data. Contact WorkLLM at hello@workllm.io for DPA requests, privacy matters and transfer or subprocessor
information.
WORKLLM / 3Schedule 1 | Description of processing
Subject and purposes. Host and operate the WorkLLM subscription service. Enable authorized collaboration, AI chat
and inference, document and knowledge retrieval, organization memory, and customer-enabled agents and
integrations. Provide security, support, troubleshooting and service administration on Customer’s behalf.
Operations and frequency. Ongoing as needed during the subscription, including collection from authorized users
and connections, hosting, retrieval, indexing and embedding, transmission to authorized providers, AI processing,
support access, export and deletion.
Individuals. Customer and its affiliates’ authorized users, personnel, contractors, customers, prospects, suppliers and
other individuals whose data Customer or its users submit, upload, connect or otherwise make available to the
service.
Data categories. Workspace user names, business contact information and identifiers. Workspace content may
include conversations, prompts, outputs, documents, knowledge-base records, embeddings and memory, connected
email, calendar events, files and associated metadata, and access and usage records processed on Customer’s
behalf. Content and categories depend on the features and inputs Customer elects to use.
Sensitive data. Sensitive data is outside the standard processing scope. For any authorized exception, the parties will
document the categories, permitted purposes and safeguards in writing before processing or transfer.
Duration. For the Agreement term and as needed to return or delete data under Section 6. Subprocessors process
data for the purposes and duration required for their functions, subject to Section 6 and the applicable transfer
terms.
Workspace hosting. Standard workspaces currently use shared AWS infrastructure in the EU with logical tenant
isolation. WorkLLM may change or expand standard hosting without advance notice solely for a storage-region
change, subject to applicable law, Schedule 4, the Agreement and Section 4 where a subprocessor changes.
Enterprise deployments may use a custom storage region and dedicated single-tenant AWS infrastructure with
dedicated RDS, compute instances and private S3 storage if specified in an Order Form or the Execution Schedule.
Storage location alone does not restrict inference, embeddings or integrations. Any agreed regional processing
restriction must be specified in an Order Form or the Execution Schedule.
Schedule 2 | Technical and organizational measures
Access and confidentiality. Scope access by workspace roles and permissions. Restrict administrative access to
authorized personnel. Limit integration access through customer authorization and scoped credentials.
Isolation. Apply logical tenant isolation and scoped access and retrieval for shared workspaces. Where agreed
for Enterprise, use dedicated single-tenant AWS infrastructure with dedicated RDS, compute instances and
private S3 storage. Check authorization for integration actions and require confirmation for designated high-
impact actions.
Encryption and credentials. Encrypt data in transit using TLS and encrypt hosted workspace data at rest. Protect
credentials and secrets with restricted access and encryption.
Operations and recovery. Maintain backups and recovery processes designed to support timely restoration
where appropriate. Limit access to backups and apply controlled deletion.
Monitoring and maintenance. Use logging and monitoring, maintain procedures for security event escalation
and incident response, and use vulnerability management and controlled software deployment practices.
Review and disposal. Review security controls periodically and after material changes. Limit data access during
recovery and apply deletion under Section 6.
WORKLLM / 4Schedule 3 | Providers and service functions
This schedule identifies core providers and applicable processing functions. WorkLLM maintains current
subprocessor information, including the identity of eligible OpenRouter downstream providers and available location
and transfer details. Customers may request it at hello@workllm.io. WorkLLM will provide advance change notices
under Section 4 using the agreed account channel.
Provider or service Function and data
Amazon Web Services (AWS) Cloud infrastructure, workspace hosting, storage and backups. Workspace data and
associated operational data.
OpenRouter and ZDR-configured
downstream inference model
providers
Model routing and inference using ZDR-eligible endpoints, excluding Safety Retention
and training endpoints. Prompts, relevant context, outputs and request metadata.
Request the current list at hello@workllm.io.
Google Cloud (Vertex AI) Direct embedding generation outside OpenRouter, currently in U.S. regions. Text
inputs and vector outputs. Google Cloud Data Processing Addendum applies.
Mem0 Memory functions. User preferences, memories and related conversation context.
Qdrant Cloud Managed vector database APIs for storage and search of embeddings and associated
metadata.
Ably Realtime service events and associated thread event metadata.
Tavily Optional web search and the search queries submitted when enabled.
Composio and WorkLLM-managed
integration connectors
Orchestration for 105+ supported integrations. Scoped credentials and authorized
integration data as required for enabled actions.
Alibaba Cloud Contracted inference provider awaiting activation. U.S. and EU endpoints only. May
process prompts, relevant context, outputs and request metadata.
Alibaba Cloud activation. WorkLLM has contracted for Alibaba Cloud model APIs. It may use only U.S. and EU
endpoints after verifying the contracting entity, signed data protection and transfer terms, remote-access limits, and
zero-retention and no-training controls. Customers whose existing authorization does not cover Alibaba Cloud
receive the applicable Section 4 process before activation. Enterprise customers may exclude Alibaba Cloud in an
Order Form or the Execution Schedule.
Customer-Authorized Integrations and Independent Services (Not WorkLLM Subprocessors)
Customer-authorized third-party applications include Google Workspace, Microsoft 365, Slack and Notion among
105+ supported connections. When Customer contracts independently with an application provider and connects it,
Customer controls access via scoped OAuth permissions and the provider acts under Customer’s own terms.
WorkLLM-managed connectors remain covered by Section 4.
Stripe processes billing and payment information for WorkLLM’s own billing activities under Section 1. Stripe does
not process Customer workspace content as a WorkLLM subprocessor.
WORKLLM / 5Schedule 4 | Regional and transfer terms
A. International transfers
WorkLLM will carry out and permit restricted transfers only where a valid mechanism is in place under Applicable
Data Protection Law. Before routing Customer Personal Data to a subprocessor in a third country, WorkLLM will
verify the required mechanism and downstream protections, document any required transfer assessment, and
implement supplementary safeguards where necessary. WorkLLM will suspend the affected transfer if it cannot
maintain the required protection. This section also applies to onward transfers and remote access where covered by
applicable law.
OpenRouter onward transfers. WorkLLM may use a documented assessment of OpenRouter’s applicable DPA, role
coverage, transfer terms and written downstream protections across providers and routes that share the same
relevant safeguards. WorkLLM will document the recipients and routes covered, including relevant processing and
remote-access locations, the applicable transfer mechanism and any supplementary measures. A separate
assessment of each request is unnecessary. WorkLLM will review material differences and changes, including a new
recipient or country, a change in remote access, or different contractual terms or technical safeguards, before relying
on the affected route. Registry listing and ZDR alone do not establish coverage. WorkLLM will restrict routes for
which applicable terms or safeguards cannot be verified.
B. EEA transfers
Where an EEA transfer from Customer to WorkLLM requires safeguards, and the clauses are available for the
transfer in question, the standard contractual clauses in the Annex to Commission Implementing Decision (EU)
2021/914 of 4 June 2021 (“EU SCCs”) are incorporated as set out below. Module Two applies where Customer is a
controller and Module Three where Customer is a processor. The parties will complete and execute any additional
information or formalities needed before the restricted transfer. If these clauses are unavailable for a particular
transfer, the parties will establish another valid mechanism before that transfer.
Clause 7 applies. In Clause 9(a), Option 2 applies with the 30-day notice period in Section 4. The optional wording in
Clause 11 does not apply. In Clause 17, Option 1 applies and Irish law governs. In Clause 18, the courts of Ireland are
selected.
Annex I.A. Customer is the exporter. Its identity, address, representative and contact appear in the Execution
Schedule or the Agreement and associated acceptance records. Work Intelligence Inc., 251 Little Falls Drive,
Wilmington, DE 19808, USA, hello@workllm.io, is the importer and processor or subprocessor. Activities and roles
are described in Section 1 and Schedule 1. Signature of the Execution Schedule or valid electronic acceptance of this
DPA under the Agreement also evidences acceptance of the selected EU SCCs and incorporated transfer terms, to
the extent permitted.
Annexes I.B, I.C and II. Schedule 1 describes transfers, including downstream processing and its duration. The
competent authority for Annex I.C is determined under Clause 13. Schedule 2 supplies the measures for Annex II,
including measures that support access restrictions, deletion and assistance. WorkLLM will document any transfer-
specific details or additional measures required before the relevant transfer.
WORKLLM / 6C. UK transfers
For a restricted UK transfer requiring this safeguard, the ICO’s Approved International Data Transfer Addendum to
the EU SCCs is incorporated. Table 1 uses the exporter and importer information in Schedule 4.B and the effective
date of this DPA. Table 2 uses the EU SCCs and applicable module, clauses and options selected in Schedule 4.B.
Table 3 uses Schedule 4.B and Schedules 1 and 2 for Annexes I.A, I.B and II, respectively. For Table 3 and the Annex III
reference, the authorized subprocessor information is in Schedule 3 and the current eligible ZDR provider list
available on request. This information is supplied for transparency under general written authorization and does not
select specific authorization or amend the approved clauses. For Table 4, neither party may end the Addendum
under Section 19. Part 2 consists of the ICO’s Mandatory Clauses of the Approved Addendum B1.0, as revised under
Section 18 of those clauses. The Addendum governs in the event of conflict for UK transfers.
D. Swiss transfers
For a restricted transfer subject to the Swiss Federal Act on Data Protection (“FADP”) requiring contractual
safeguards, the applicable EU SCC module in Schedule 4.B applies with references to the GDPR read as references to
the FADP to the extent of Swiss coverage. References to Member States are read to include Switzerland for that
purpose. The Swiss Federal Data Protection and Information Commissioner (“FDPIC”) is the competent authority for
the FADP, without displacing an EU authority where the GDPR also applies. For transfers governed solely by the
FADP, Swiss law and Swiss courts apply under Clauses 17 and 18. Where the GDPR also applies, the EU governing law
and forum selections remain effective for EU purposes. Individuals in Switzerland may bring claims in the courts of
their habitual residence.
E. United States
Where U.S. state privacy laws apply, WorkLLM acts as a processor, service provider or contractor as applicable. The
limited business purposes are the contracted hosting, inference, collaboration, security, integration and support
operations in Schedule 1. WorkLLM will provide the same level of privacy protection required of Customer for the
processing under applicable law and comply with its applicable duties, including the CCPA where applicable.
WorkLLM will not sell or share personal information as defined by the CCPA, process it for targeted advertising, use
or disclose it beyond the specified purposes or outside the direct business relationship, or combine it with data from
other customers or its own interactions with individuals, except as permitted by applicable law. WorkLLM will
promptly notify Customer if it determines it can no longer meet its obligations. Customer may take reasonable steps
to verify compliant use under Section 5 and to stop and remediate unauthorized use. WorkLLM will assist with
consumer rights and required assessments, provide relevant information, and notify and bind subcontractors by
written contract as required by law. To the extent treated as a contractor under the CCPA, WorkLLM certifies that it
understands and will comply with these restrictions.
F. Canada and other jurisdictions
Where Canadian privacy law applies, WorkLLM will use contractual and operational measures to provide a
comparable level of protection for Customer Personal Data, including when it uses providers outside Canada.
WorkLLM will support Customer’s required transparency, access and breach obligations. Where Québec law applies,
WorkLLM will process only to perform its mandate, keep the information confidential, restrict use during the
mandate, refrain from keeping it after expiry except as required by law or as otherwise lawfully instructed by
Customer, notify Customer without delay of an actual or attempted violation of confidentiality, and permit Customer
to verify compliance. WorkLLM will assist Customer with any legally required cross-border assessment and agreed
safeguards. Where another jurisdiction requires additional terms or a specific transfer mechanism, the parties will
document and implement those requirements before undertaking the affected processing or transfer.
WORKLLM / 7Execution and Customer Details Schedule
Complete for standalone execution. By signing, the parties accept this DPA and the applicable transfer terms in
Schedule 4. The Agreement and agreed Enterprise terms identified below apply to this DPA.
Customer legal entity name ______________________________________________
______________________________________________
Registered address ______________________________________________
Privacy or incident contact email Competent supervisory authority ______________________________________________
Default authority is determined under EU SCCs Clause 13, or is the UK ICO or Swiss FDPIC as applicable.
Order form or agreement reference ______________________________________________
Effective date ______________________________________________
Enterprise options
Leave unchecked for Standard plans. Specify agreed restrictions and affected workspaces in the Order Form or
below. Agreed options control the applicable service configuration, subject to Schedule 4.
Dedicated single-tenant AWS infrastructure as specified in the Order Form ☐
Custom workspace storage region __________________________________ ☐
Standard storage is shared AWS infrastructure in the EU as described in Schedule 1.
Regional AI processing restriction _________________________________ ☐
Standard routing uses global ZDR inference and U.S. Vertex AI embeddings. Specify affected workloads and regions,
including any limits on embeddings or fallback routes. Availability is subject to supported routes.
Model or provider allowlist or exclusions ____________________________ ☐
Specify the provider or model names and any exclusions, such as Alibaba Cloud.