Tejma LLC logo
DispatcherEmail SummariesLead IntakeHow We WorkTrustBook a Consultation
Tejma LLC logo
DispatcherEmail SummariesLead IntakeHow We WorkTrustBook a Consultation

Tejma Dispatcher

Data Processing Agreement

This Data Processing Agreement ("DPA") forms part of the Terms of Service between Tejma LLC ("Tejma", the "Processor") and the customer organization using Tejma Dispatcher (the "Customer", the "Controller"). It applies whenever Tejma processes personal data contained in Customer Content on the Customer's behalf and is subject to data protection law such as the GDPR, the UK GDPR, or the California Consumer Privacy Act. It is incorporated into the Terms of Service; no signature is required, though Tejma will countersign a copy on request.

Effective October 30, 2026 · Last updated October 30, 2026 · Reno, Nevada

On this page

  1. 1. Roles and Scope
  2. 2. Details of the Processing
  3. 3. Processing on Documented Instructions
  4. 4. Confidentiality and Personnel
  5. 5. Security Measures
  6. 6. Subprocessors
  7. 7. Assistance to the Controller
  8. 8. Personal Data Breach
  9. 9. Deletion and Return
  10. 10. International Transfers
  11. 11. Audits and Information

Related documents

  • Tejma Dispatcher Terms of Service
  • Tejma Dispatcher Privacy Policy

1. Roles and Scope

Customer is the controller; Tejma is the processor. The Customer decides which channels to connect, which agents to run, which connectors to grant its members, and what those agents do; Tejma processes the resulting Customer Content only to provide the service. Where the CCPA applies, Tejma is the Customer's "service provider" and does not sell or share personal information, retain it except to provide the service, or combine it across customers. Tejma's own connector services that the Customer's members use (for example Tejma Books) are separate Tejma services; their processing is governed by their own terms and, where applicable, their own data processing terms.

Precedence. For personal data processing, this DPA prevails over any conflicting term of the Terms of Service. Everything else — including the limitation of liability, which applies to this DPA in aggregate with the Terms — remains governed by the Terms of Service.

2. Details of the Processing

Subject matter and nature. Ingestion, storage, task extraction, task routing, evaluation of the Customer's approval workflows (including runs of the Customer's judge agents), AI-assisted task execution with the connectors the Customer wires to its agents, metering of the resulting AI usage, confirmation to Tejma's connector services of which members are entitled to use them, and Customer-directed outbound messaging — including completion reports — to recipients the Customer's configuration determines, who may be outside the Customer's organization, of communications flowing through channels the Customer connects (email mailboxes, including the earlier messages of a thread, Slack channels, Discord channels) and content submitted through the Customer's MCP clients, dashboard, and API calls.

Duration. The term of the Customer's subscription, plus the period until Customer Content is deleted on the Customer's instruction under Section 9.

Categories of data subjects. The Customer's personnel (organization members and invitees), and the people who correspond with the Customer through connected channels — email senders and recipients, chat-workspace participants, recipients of messages the Customer's agents send, and persons referenced in messages, attachments, and tasks.

Categories of personal data. Names, email addresses, and chat handles; message and thread content and any personal data those messages, attachments, and files happen to contain (which the Customer, not Tejma, determines); task content derived from them and the text of messages agents send; organization-member account, role and connector-grant, consent, and billing data, including invitees' email addresses and members' authorization tokens for connectors; AI usage records (token counts and amounts per call, never content); and operational logs that may contain email addresses, attachment names, judge reasons, and request paths. The service is not designed for, and the Customer agrees not to direct to it, special-category data or data subject to sector rules (such as HIPAA or PCI card data) absent a separate written agreement.

3. Processing on Documented Instructions

Tejma processes Customer Content only on the Customer's documented instructions: this DPA, the Terms of Service, the Customer's configuration of the service (connected channels, agents, skills, connectors and grants, approvals, outbound links), and the Customer's use of its API — unless processing is required by law, in which case Tejma will inform the Customer before processing where the law allows. Tejma will inform the Customer if, in its opinion, an instruction infringes data protection law.

4. Confidentiality and Personnel

Persons Tejma authorizes to process Customer Content are bound by confidentiality obligations and access Customer Content only as needed to operate, secure, and support the service. Tejma's operator controls do not display message content; personnel with infrastructure access can reach stored content, which the application does not encrypt, and a maintenance tool allows operators to re-read a connected mailbox's messages from the email provider to recover mail a notification missed.

5. Security Measures

Tejma implements technical and organizational measures appropriate to the risk, including:

  • Tenant isolation. Every message, task, document, connector, and channel record belongs to exactly one user; requests for another tenant's identifiers behave as if the record does not exist, and stored files are keyed per user.
  • Encryption. TLS for data in transit; AES-256-GCM encryption by the application for stored secrets (channel and connector authorization tokens, the Customer's own Anthropic API keys where supplied, and Tejma's managed Anthropic API keys), which are write-only and decrypted solely at the moment of use; encryption at rest of the database, stored files, and backups by the hosting and storage providers.
  • Authenticated ingress. OAuth 2.0 bearer tokens verified as JWTs (signature and issuer) against the identity provider on every API and MCP request; cryptographic signature verification on every inbound webhook (Nylas, Slack, Stripe) before any processing; a shared secret per Tejma connector for entitlement checks, which return identifiers and roles only.
  • Access control. Role-gated administration within the Customer's organization: billing, credit, and credential changes require the billing role; member, invitation, grant, and role changes require the users role; starting AI work requires the usage role. Tejma's operator controls (plans and prices, organizations' billing standing and ledgers, usage counters, credit adjustments, cross-organization usage records, the managed key pool, templates, member lookup, member deletion, and role changes) sit behind a separate, dedicated identity tenant.
  • Payment isolation. Card data is entered only on Stripe's hosted pages and never reaches Tejma's systems.
  • Operational integrity. Idempotent, at-least-once ingestion with verified redelivery; billing events journaled in append-only ledgers within the same transaction as the balance they change; recorded evaluations for every automated approval decision.

6. Subprocessors

General authorization. The Customer authorizes the subprocessors below. Tejma will inform the Customer's administrators before adding or replacing a subprocessor; the Customer may object on reasonable data-protection grounds, and if the objection cannot be resolved, may terminate the affected service.

Current subprocessors— each engaged under a written agreement imposing data-protection obligations no less protective than this DPA

  • WorkOS, Inc. (US) — authentication, sessions, organization and member management, invitation emails.
  • Anthropic, PBC (US) — AI processing of message and task content, and server-side execution of the agents' connector tool calls. Under managed AI billing (the default), calls are made with Tejma's own Anthropic API keys under Tejma's commercial agreement with Anthropic, and Anthropic acts as Tejma's subprocessor; where the Customer supplies its own Anthropic API key, calls are made under that key and Anthropic also acts under its direct commercial terms with the Customer.
  • Nylas, Inc. (US; EU region available) — email mailbox connectivity, message sync, thread listing, attachment retrieval, and sending.
  • Slack Technologies / Salesforce, Inc. (US) — receiving and sending messages in connected Slack channels.
  • Discord Inc. (US) — receiving and sending messages in connected Discord channels.
  • Stripe, Inc. (US) — payment processing and recurring subscription billing.
  • Railway Corp. (US) — cloud hosting: compute, the Postgres database holding messages, tasks, and account data, and server logs.
  • Cloudflare, Inc. (US) — R2 object storage holding message documents and attachments, and the network tunnel delivering inbound webhooks.

Connector servers the Customer registers by URL, and the channels' own providers in their capacity as the Customer's communication services, are engaged by the Customer directly and are not Tejma subprocessors. Tejma's own connector services are Tejma processing under their own terms, not subprocessors of this service.

Tejma remains responsible to the Customer for its subprocessors' performance under this DPA.

7. Assistance to the Controller

Data subject requests. Taking into account the nature of the processing, Tejma will assist the Customer with data subject requests (access, rectification, erasure, restriction, portability, objection). The service's built-in controls cover reading content, deleting individual documents, hiding tasks, disconnecting channels, and deleting a member's whole seat; requests narrower than a seat — the erasure of particular messages or of one correspondent's data, or a copy of particular records — are carried out by Tejma on the Customer's written instruction without undue delay. Requests Tejma receives directly from data subjects about Customer Content will be forwarded to the Customer without undue delay.

DPIAs and consultations. Tejma will provide reasonable assistance with data protection impact assessments and prior consultations with supervisory authorities, insofar as they concern processing by the service.

8. Personal Data Breach

Tejma will notify the Customer's administrators without undue delay after becoming aware of a personal data breach affecting Customer Content, and in any event within 72 hours, providing what is known at the time — the nature of the breach, categories and approximate volumes affected, likely consequences, and measures taken — and supplementing as facts develop. Tejma will not characterize the Customer's own notification obligations; notification is not an admission of fault.

9. Deletion and Return

During the term, the Customer deletes documents and whole seats directly through the service (deletion of a document removes its stored bytes before its record), and instructs Tejma in writing for anything narrower. The service applies no time-based deletion of its own, and cancelling the subscription deletes nothing. At the end of the processing, on the Customer's written instruction, Tejma deletes Customer Content by deleting each of the organization's seats — including stored documents and the encrypted credentials held with them — and, on request made before that deletion, provides the Customer a copy of its Customer Content. Exceptions: records the law requires Tejma to retain (billing and tax records, for their statutory periods, and consent records), database backups and server logs held by Tejma's hosting providers until they age out on those providers' schedules and protected until then, and authorizations the Customer's members granted to connectors, which remain valid at the accounts that issued them until the Customer revokes them there.

10. International Transfers

Tejma processes Customer Content in the United States. Where personal data protected by the GDPR or UK GDPR is transferred to Tejma or its subprocessors outside the EEA or UK, the parties rely on the EU Standard Contractual Clauses (Module 2, controller-to-processor), which are incorporated by reference with the Customer as data exporter and Tejma as data importer, supplemented by the UK International Data Transfer Addendum where the UK GDPR applies, and on the subprocessors' own transfer safeguards. The processing details in Section 2 complete the Clauses' annexes.

11. Audits and Information

Tejma will make available the information reasonably necessary to demonstrate compliance with this DPA — security documentation, subprocessor agreements' data-protection terms, and answers to reasonable security questionnaires — and will allow audits required of the Customer by a supervisory authority, on at least 30 days' notice, at most annually absent a breach, during business hours, under confidentiality, and at the Customer's expense.

Contact. Privacy and data protection matters: Tejma LLC · Reno, Nevada · ai.assistants@tejmallc.com · tejmallc.com

Matej Meciar · Tejma LLC

925-963-4257 · ai.assistants@tejmallc.com · tejmallc.com

Tejma LLC · Reno, Nevada · Practical workflow automation for business teams. · 925-963-4257 · ai.assistants@tejmallc.com

Tejma Dispatcher: Terms of Service · Privacy Policy · Data Processing Agreement

Tejma Books: Terms of Service · Privacy Policy

Tejma Work Order Scheduling: Terms of Service · Privacy Policy