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

Tejma Books

Privacy Policy

This Privacy Policy explains what information Tejma LLC ("Tejma", "we", "us") collects when you use Tejma Books — our bookkeeping service for sole proprietorships — how we use it, who we share it with, how long we keep it, and the choices you have. Tejma Books exists to hold your organization's financial records, so please read the "Information We Collect" section carefully: the books are shared with every member of your organization who holds the reader role, every change is attributed to the member who made it, and entries are kept with their history because they may underlie a tax return. The service itself sends nothing to any AI provider; the "AI Clients and MCP Access" section explains what a client you connect can see.

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

On this page

  1. 1. Who We Are and What This Covers
  2. 2. Information We Collect
  3. 3. How We Use Information
  4. 4. AI Clients and MCP Access
  5. 5. Service Providers and Recipients
  6. 6. Data Retention and Deletion
  7. 7. Security
  8. 8. Your Rights and Choices
  9. 9. Children, International Transfers, and Changes

Related documents

  • Tejma Books Terms of Service

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 Books 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, or Tejma Dispatcher, which has its own Privacy Policy; each handles your information under its own terms.

Our role. The organization whose books are kept is the controller of the content in them; 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 and on your acceptance records — and nothing else about you: the service keeps no table of users, members, or profiles, and reads who belongs to an organization, and with which roles, 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. When a member accepts them on the organization's behalf, we record the same together with the organization. Both records are append-only and are kept as evidence of consent after you leave an organization or your account is deleted.

Your organization's books. Everything your members, or the clients they connect, enter:

  • expenses — date, amount, category, description, vendor, business purpose, payment method, receipt note, a link to the receipt, deductible percentage, and foreign-currency details where given;
  • vendors — name, address, default category, 1099 status, and the taxpayer identification number (EIN or SSN) entered for 1099 filing;
  • clients — name, email address, postal address, and payment terms;
  • invoices and payments — invoice numbers, dates, amounts, status, descriptions, notes, a link to the document, and each payment received against an invoice;
  • vehicles, mileage trips, and mileage rates — vehicle details and odometer readings; each trip's date, miles, start and end locations, purpose, and notes;
  • bank accounts and transactions — account names, types, and opening balances; each statement line's date, amount, description, and reference, and the book record it was reconciled to. The service connects to no bank and holds no bank credentials: transactions are entered by you or the clients you connect;
  • fixed assets — description, cost, the dates placed in service and disposed, business-use percentage, depreciation method, and a link to the document;
  • ledger entries — owner draws and contributions, transfers, sales tax, and other income and expense, with dates, amounts, and descriptions;
  • period locks, per-year tax settings such as the home-office deduction, expense categories, and the books' own name and time zone.

Audit trail. Every insertion, change, and deletion of an expense, invoice, payment, vendor, client, mileage trip, bank transaction, fixed asset, ledger entry, period lock, account, or tax setting 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 files: receipts, statements, and invoices are referenced by link and never retrieved or stored. No bank or card credentials: the service connects to no financial institution and processes no payments. No AI provider keys: the service makes no AI calls.

3. How We Use Information

We use the information above to run the service you configured: to store the books 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 enforce period locks and the other rules of the books; to attribute each change to the member who made it and keep the audit trail; to compute the reports 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 books to train AI models.

The content of the books 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 Books makes no AI calls. Nothing in your books is sent to Anthropic or any other AI provider by Tejma Books itself. The service is a store of records with tools to read and change them; it does not interpret, summarize, or analyze your books with a model.

What a connected client sees. When you or a member connects an MCP client to the service — an AI assistant such as Claude, an agent configured in Tejma Dispatcher, or any other MCP-compatible software — that client, and the AI model behind it, receives whatever the tools return for the roles the member holds: the records it lists or fetches, the reports it runs, 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 against 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, or whose organization has not, 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 books 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 the books, 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 Books sends it your user identifier and asks whether your seat is entitled to the Tejma Books connector and which roles it carries; your token and your books never travel to it. What Dispatcher holds about you is described in its own Privacy Policy. The MCP clients and AI providers you connect 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

The books are kept until you delete them. Entries remain until a member removes them or the organization's books are closed; nothing expires on its own.

Removal keeps history. Deleting an expense, mileage trip, bank transaction, fixed asset, or ledger entry flags it as deleted and hides it from lists and reports but keeps the row, so a filed year can be defended later; reversing an invoice payment flags it the same way. Vendors, clients, categories, and invoices are removed outright, but — like every other change — their previous values remain in the audit trail. A locked period refuses deletion altogether until it is unlocked.

Full erasure is a request to us. Because of this, erasing a record completely, including its audit history, or erasing an organization's books, 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 books — a vendor or client, say — is referred to that customer, who controls the books.

What outlives the books. 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 books 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 books carries the organization, every query is scoped to it, the period-lock and audit mechanisms are organization-aware, and an automated test suite checks that one organization's identifiers are invisible to another;
  • the role gate checked before every change, and the organization's policy acceptance before any tool runs;
  • append-only consent records and audit trail, enforced by the database itself: rows can be added but not changed or removed through the service;
  • no stored secrets of yours: the service holds no bank, card, or AI provider credentials, and the only credential it keeps is its own, for the entitlement check with Tejma Dispatcher.

Taxpayer identification numbers you enter for vendors are stored in the books like every other entry, under the protections above, and are visible to every member of your organization who holds the reader role. Enter them only where 1099 filing requires, 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 books 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 books (for example, you are a vendor or client of one of our customers), we will refer your request to that customer, who controls those books, and assist them in honoring it.

Roles are a choice. Your organization's administrators decide, in Tejma Dispatcher, who may read the books and who may change them, and may revoke either at any time with immediate effect.

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, and once more on your organization's behalf — before you continue; 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

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