1. Who We Are and What This Covers
Tejma LLC is a Nevada limited liability company based in Reno, Nevada. This policy covers the Tejma Work Order Scheduling service — its MCP endpoint, REST API, dashboard, and the database behind them. It does not cover the WorkOS sign-in pages; the MCP clients and AI providers you connect; the email, calendar, and portal accounts your assistant reads and writes through connectors of its own; or Tejma Dispatcher, which has its own Privacy Policy; each handles your information under its own terms.
Our role. The organization whose workspace it is is the controller of the content in it — the details of the customers its portals send it to included; Tejma processes that content on the organization's behalf as described here. A data processing agreement is available to business customers on request.
2. Information We Collect
Account information. Sign-in is handled by WorkOS AuthKit, under the single WorkOS application every Tejma service shares. On each request we receive a signed token carrying your WorkOS user identifier and, depending on how you signed in, your email address, a session identifier, and an organization identifier. We store your user identifier — as the actor on every change you make, as the member who accepted or declined a work order, and on your acceptance record — and nothing else about you: the service keeps no table of users, members, or profiles, and learns which organization you act for, and which roles you hold, from Tejma Dispatcher on every request rather than storing it. We do not store your password; authentication credentials live with WorkOS.
Terms acceptance records. When you accept the Terms of Service and this policy for yourself, we record the versions accepted, the time, the network (IP) address and client software (user agent) of the request, and your user identifier. Acceptance is personal: nothing is accepted on an organization's behalf, and no organization-level record exists. The record is append-only and is kept as evidence of consent after you leave an organization or your account is deleted.
Your organization's workspace. Everything your members, or the assistants and clients they connect, record:
- portals — for each network you receive work orders from (a home-warranty company, a property manager, a facilities platform): its name and short name, a color, its website, the ordered steps its process expects of you, a hint for recognising its emails, notes, and whether it is active;
- work orders — one record per work order received: the portal and the portal's own number for it; the job in a few words and the relevant text of the portal's message; the trade; the service address and city; the customer's name and phone number; the fee or not-to-exceed amount as the portal stated it; the link to the job in the portal; the requested date and window, or the words the portal used for a flexible request; the job's estimated length; the response deadline; when it was received and by what route (email, the portal, a phone call, or by hand); the identifier of the email it came from; its status; who accepted or declined it, when, and any note they left; the booked slot and the identifier of the calendar event it became; which of the portal's steps have been completed; when it was completed; and notes;
- calendar blocks — the busy time the calendar check books around: for each event your assistant syncs from your organization's calendar, the event's identifier, its calendar, its title, its start and end, whether it is all-day, and a note; and the same for blocks entered by hand. The service connects to no calendar and holds no calendar credentials — what it holds is what your assistant passed to it;
- availability and settings — the working hours of each weekday, the default job length, the travel buffer, the workspace's name and time zone, and when email and the calendar were last synced.
Audit trail. Every insertion, change, and deletion of a work order, portal, calendar block, or working-hours row is recorded with the table and record, the action, the user identifier of the member who made it, the record's values before and after, and the time.
Entitlement checks. On each request we ask Tejma Dispatcher whether the seat of your user identifier is entitled to the service and which roles it holds, and keep the answer in memory briefly — at most five minutes for a positive answer, thirty seconds for a refusal.
Logs and diagnostics. Standard server logs — request metadata, timestamps, and error traces — used to keep the service reliable.
What we do not collect. No mail: the service reads no mailbox and stores no email; what it holds of a work-order email is the fields your assistant extracted from it and the message's identifier. No calendar access: it connects to no calendar and holds no calendar credentials. No portal access: it never signs in to a portal, holds no portal credentials, and never acts in one. No files: a work order may carry a link to the job in the portal, which is never retrieved. No AI provider keys: the service makes no AI calls. No payment data: the service is free.
3. How We Use Information
We use the information above to run the service you configured: to store your work orders, calendar blocks, portals, and availability and keep them isolated to your organization; to check on every request that the caller is signed in, entitled, has accepted the current policies, and holds the role the action needs; to run the calendar check — whether a requested window fits inside your working hours, clear of booked time and its buffer — and suggest open slots; to refuse a duplicate work order and a double booking; to attribute each decision and change to the member who made it and keep the audit trail; to compute the portal statistics you ask for; to secure the service and prevent abuse; to keep the consent records the law expects; and to provide support.
We do not sell your data, use it for advertising, or use your work orders to train AI models.
The content of your workspace is processed only to provide the service to you, by us and by the service providers listed below.
4. AI Clients and MCP Access
Tejma Work Order Scheduling makes no AI calls. Nothing in your workspace is sent to Anthropic or any other AI provider by the service itself. It is a store of records with tools to read and change them, and a calendar check that is plain arithmetic on your working hours, booked time, and buffer; it does not read, interpret, or summarize anything with a model.
The assistant brings the content in. The service is built to be run by an MCP client — an AI assistant such as Claude, an agent configured in Tejma Dispatcher, or any other MCP-compatible software — that reads your mailbox and your calendar through connectors of its own, which you authorize separately and which the service never touches. That client extracts each work order from the portal's email and records it here; lists your calendar's events and syncs them here as busy time; and, after you decide, creates the calendar event and stores its identifier on the order. What ends up in your workspace is therefore what the client chose to pass: it may include text from the portal's email and the titles of your calendar events, events unrelated to work orders among them.
What a connected client sees. That client, and the AI model behind it, receives whatever the tools return for the roles the member holds: the work orders it lists or fetches — customer names, phone numbers, and addresses included — the calendar blocks, the calendar check's verdicts and reasons, the portal statistics, the change trail, and the tool descriptions. The model's provider receives that content under its own terms, not ours — for an assistant you run yourself, under your agreement with its provider; for a Tejma Dispatcher agent, as described in the Tejma Dispatcher Privacy Policy, including whose Anthropic account the processing runs under. Choose and configure clients with that in mind, and grant them only the role they need.
Attribution. Every change a connected client makes is recorded in the audit trail, and every decision it records is attributed, to the member whose sign-in authorized it, exactly as a change made by hand.
Before access is granted. A caller who has not accepted the current policies, whose organization's workspace has not been set up, or who lacks the role a tool needs can still list the tools — their names and descriptions — but every call is refused with a message naming the step to take, and nothing from the workspace is returned.
5. Service Providers and Recipients
We share information only with the providers needed to run the service, each bound to use it solely to provide their service to us and to you:
- WorkOS — authentication and sign-in: issues the signed tokens we verify (identity data).
- Railway — cloud hosting: runs our servers and the Postgres database that holds your workspace, the audit trail, and the acceptance records.
- Cloudflare — network edge in front of the service: DNS, TLS, and request routing.
Tejma Dispatcher is our own service, not a third party. On every request, Tejma Work Order Scheduling sends it your user identifier, asks whether your seat is entitled to this connector and which roles it carries, and learns from the answer which organization you act for; your token and your work orders never travel to it. What Dispatcher holds about you is described in its own Privacy Policy. The MCP clients and AI providers you connect, and the email, calendar, and portal accounts they read and write on your behalf, are recipients you choose, as described in the previous section.
Beyond these, we disclose information only if required by law or legal process (we will notify an organization administrator unless legally barred), to protect the rights, safety, or security of Tejma, our customers, or the public, or as part of a merger or acquisition — in which case this policy continues to apply until you are notified otherwise.
6. Data Retention and Deletion
Records are kept until you delete them. Work orders, calendar blocks, portals, and settings remain until a member removes them or the organization's workspace is closed; nothing expires on its own. A declined, completed, or cancelled work order stays on file as part of your history and of the portal statistics.
Removal keeps history. Deleting a work order flags it as deleted and hides it from the inbox, the lists, and the calendar check but keeps the row, so what the portal sent and what was decided can be shown later. Calendar blocks are removed outright — though a block synced from your calendar returns on the next sync unless the event is deleted in the calendar too — and a portal can be removed outright only while no work order refers to it; otherwise it is archived and keeps its history. In every case, like every other change, the previous values remain in the audit trail.
Full erasure is a request to us. Because of this, erasing a record completely, including its audit history, or erasing an organization's workspace, is done by Tejma on request from an organization administrator at the address below. We will complete it within 30 days unless a law requires us to keep particular records, in which case we will tell you what we keep and why. A request from someone whose details appear in a customer's workspace — a homeowner or tenant the portal sent the customer to, say — is referred to that customer, who controls the workspace.
What outlives the workspace. Terms acceptance records are kept as evidence of consent. Server logs age out on a fixed schedule.
After closure. When an organization ends its use of the service, we honor export requests for 30 days and then delete the organization's workspace and audit trail in the ordinary course of operations. Backups age out on a fixed schedule.
7. Security
We protect information with measures matched to what the service holds:
- TLS in transit, and a bearer token verified on every request against the signing keys WorkOS publishes — a missing, expired, or unverifiable token is refused before anything else happens;
- entitlement confirmed with Tejma Dispatcher on every request, failing closed: when Dispatcher cannot be reached, the service refuses rather than guesses;
- strict per-organization isolation: every table in the workspace carries the organization, every query is scoped to it, the audit mechanism is organization-aware, and an automated test suite checks that one organization's identifiers are invisible to another;
- your own acceptance of the current policies checked before anything else — before your organization is even looked up, so nothing is created for a user who has not consented — and the role gate checked before every change;
- append-only consent records and audit trail, enforced by the database itself: rows can be added but not changed or removed through the service;
- only web addresses accepted as the link to a job, so that a link extracted from an email and shown in the dashboard can never carry a script;
- no stored secrets of yours: the service holds no mailbox, calendar, portal, or AI provider credentials, and the only credential it keeps is its own, for the entitlement check with Tejma Dispatcher.
The names, phone numbers, and addresses of the customers your portals send you to are stored on their work orders like every other field, under the protections above, and are visible to every member of your organization who holds the reader role and to every client such a member connects. Record what the job needs, and grant the reader role accordingly.
No service can promise perfect security. If a breach affects your personal data, we will notify affected organization administrators without undue delay and as the law requires.
8. Your Rights and Choices
Access, correction, deletion, portability. Every record in your workspace can be read through the dashboard, the API, and the tools, and corrected or removed by a member with the writer role. For anything else — a complete export, full erasure including history, or correction of something you cannot change yourself — email us at the address below and we will respond within the time the applicable law sets. If your personal data reached us through a customer's workspace (for example, a portal sent one of our customers to your home), we will refer your request to that customer, who controls that workspace, and assist them in honoring it.
Roles are a choice. Your organization's administrators decide, in Tejma Dispatcher, who may read the workspace and who may change it, and may revoke either at any time with immediate effect.
What the assistant brings in is a choice. Which mailbox and which calendars your assistant reads, and how far back, is configured in the assistant and its connectors, not here; a calendar block it synced can be removed from the workspace at any time by a member with the writer role, and stays away once the event is gone from the calendar.
Region-specific rights. Depending on where you live, you may have statutory rights — under the GDPR or UK GDPR (access, rectification, erasure, restriction, portability, objection, and complaint to a supervisory authority) or the California Consumer Privacy Act (to know, delete, correct, and not be discriminated against; we do not sell or share personal information as the CCPA defines those terms). We honor these rights regardless of which law applies.
Communications. Service notices — about these documents and about the availability of the service — are part of running it. We do not send marketing communications through the service's data.
9. Children, International Transfers, and Changes
Children. The service is a business tool and is not directed to children under 16; we do not knowingly collect their data.
International transfers. We operate from the United States and our providers process data in the United States. Where the GDPR applies to transfers, we rely on appropriate safeguards such as Standard Contractual Clauses, set out in the data processing agreement available on request.
Changes to this policy. We will post updates here and change the date at the top. When we publish a new version, the service asks you to accept it again for yourself before you continue — every member of every organization, since acceptance is personal; material changes will also be announced to organization administrators through the service or by email before they take effect.
Contact. Tejma LLC · Reno, Nevada · ai.assistants@tejmallc.com · tejmallc.com
Matej Meciar · Tejma LLC
