Temidy MCP Privacy Policy

This policy explains the data flow for the Temidy connector for ChatGPT, Claude and other Model Context Protocol (MCP) clients. It applies to https://mcp.temidy.ai/mcp and the Temidy sign-in and OAuth pages used to connect it. It supplements our general privacy policy, which covers your Temidy account and other platform features. Effective date: 13 November 2026.

Before connecting: your assistant sends selected tool inputs to Temidy; Temidy returns matching legal-source content or a fee calculation to that assistant's provider. Court-source text can contain personal information already present in the source. Connecting does not give the assistant access to your Temidy private documents, account profile or conversation history.

1. Who is responsible and how to contact us

The controller is UAB “Temidy group”, company code 306933664, J. Savickio St. 4-7, LT-01108 Vilnius, Lithuania. For privacy requests, deletion, source corrections or questions, contact [email protected] or +37061849141. Please identify the connection or source concerned; do not email passwords or access tokens.

2. What is received when you connect

• Sign-in and account access: Temidy processes the account identifier and authentication information you provide on its own sign-in page, an authenticated session, and your internal account ID and subscription eligibility. Necessary session and anti-forgery cookies support sign-in and OAuth consent. These are not MCP tool inputs. A password entered on Temidy is verified by Temidy; it is not returned to the assistant.
• Connection and authorization: client name and ID, registered redirect URLs and optional client URL, the read-only legal:read scope, PKCE challenge, authorization state and consent, linked account ID, and creation, expiry, use and revocation times. We store hashes of authorization codes, access/refresh tokens and client secrets rather than usable plaintext copies in the OAuth database. The connecting client receives its issued tokens so it can make authorized requests.
• Network and request information: our infrastructure processes the requesting IP address, HTTP headers such as user agent, route, request time and status to deliver and secure the service. For server-to-server MCP calls this may be the assistant provider's address rather than your device's address. The MCP audit table stores a keyed hash of the IP address.

3. Current tool inputs and outputs

The client chooses what to include in a tool call. Temidy receives the named tool and its explicit arguments, not an automatic copy of the full chat. Free-text search terms can contain personal information if you or the assistant include it. The following ten tools are available:

Results can also contain a success/error message, result count and pagination needed to interpret the answer. Explicit output-field allowlists exclude unrelated account/profile information, internal telemetry and private exception details. These tools do not retrieve subscriber lists, private files, messages or stored conversations, and do not write documents or change subscriptions.

4. Personal information in legal sources and requests

The corpus contains legislation, draft legal acts from the e-Seimas legislative register and court decisions obtained from legal sources. Depending on the original publication, returned titles, paragraphs and excerpts may include names of judges, representatives or parties, organizations, case references and facts about legal proceedings. Some decisions concern criminal proceedings or sensitive personal circumstances. Court paragraph and excerpt strings retain the source wording and existing source redactions; Temidy does not apply additional NER or regex anonymization to those strings for MCP. Draft texts can name the officials or members of the Seimas who submitted or signed them; in draft text, e-mail addresses and Lithuanian personal codes, phone numbers and bank account numbers are replaced with [redacted]. We do not represent that every legal-source result is anonymous. We do not add Temidy account details to the legal text.

Use only task-specific legal search criteria. Do not submit passwords, authentication codes, payment-card data, government identifiers, private health records or confidential client documents through tool arguments. These tools have no document-upload or full-chat-history input. Review the assistant's proposed tool inputs when the client offers that control. A query can itself reveal a legal matter even when it contains no person's name.

5. Purposes and uses

• Authenticate you, check access eligibility, obtain and maintain the connection, retrieve the requested sources or calculate a fee, and let you disconnect: provision of the requested service and contract performance (GDPR Article 6(1)(b)).
• Enforce call/read/response-volume limits, prevent bulk extraction and misuse, investigate failures, provide support and maintain reliability: our legitimate interests (Article 6(1)(f)). This uses the limited audit and diagnostic data described below, not a hidden copy of your chat.
• Maintain and correct the legal-source database and provide verifiable legal research: legitimate interests, subject to applicable rules for the particular source and personal-data category. Public availability alone does not remove data-protection obligations. Contact us to raise a source-specific concern.
• Comply with legal duties and establish, exercise or defend legal claims where necessary (Article 6(1)(c), or Article 6(1)(f) for legal claims).

The MCP feature does not use tool inputs or outputs for advertising, sale of personal data, behavioral profiling or training Temidy AI models. It performs source retrieval and calculations rather than running a separate Temidy conversational model over your chat. The chosen assistant provider's own model processing and training settings are separate, as explained below. MCP does not make decisions on your eligibility for legal services or other decisions with legal or similarly significant effects.

6. Audit records and diagnostics

The MCP audit table records an internal request ID, account and client IDs, tool name, request time, a SHA-256 hash and byte size of the arguments, result byte size and count, duration, status, error code and a keyed IP hash. These hashes and linked identifiers are pseudonymous data, not a claim of irreversible anonymization. The MCP audit table does not store raw search terms, raw tool arguments, returned source text or the full conversation.

Separate operational logs and error reports may include request/connection metadata, queried source identifiers, diagnostic search terms or input fragments when a retrieval or calculation fails, and exception messages and traces. They are used for troubleshooting and security; they are not returned as tool output. Error monitoring uses Sentry. This distinction matters: absence of raw text from the MCP audit table does not mean it can never appear in a diagnostic record.

7. Recipients and international processing

• Your chosen assistant provider: OpenAI for ChatGPT, Anthropic for Claude, or the operator of another client you connect. It already handles the prompt/selected tool arguments on its side and receives the tool results from Temidy, including any source personal information in them. Connection tokens are used by that client; unrelated Temidy account profiles and subscription details are not included in tool results. The provider's subsequent storage, model use, training choices and transfers depend on its service, plan and your settings. See OpenAI's privacy policy and Anthropic's privacy policy. Check business-service agreements where applicable.
• Service providers working for Temidy: hosting/database/search and backup infrastructure, network delivery and security providers (including Cloudflare), and error monitoring (Sentry). They process the content or technical data necessary for their role under service and data-processing arrangements. Authorized Temidy personnel may access records for support, maintenance, security and privacy requests.
• Legal recipients: competent authorities, professional advisers or other recipients where legally required or necessary to protect legal rights. We do not disclose MCP records to advertisers or data brokers.

Temidy's application and legal-search infrastructure is hosted in the EU. Assistant providers and some infrastructure/support providers may process data outside the EEA. Where Temidy arranges such a transfer, applicable adequacy decisions or appropriate contractual safeguards, including EU standard contractual clauses where required, apply. Ask our privacy contact for information about the safeguards applicable to your request. Selecting an assistant does not mean that all copies of its results remain in the EU.

8. Retention and deletion

• Tool execution: raw arguments and returned text are processed to answer the request; MCP does not create a saved chat or per-call archive of those bodies. Request-local data ends with execution, apart from the diagnostic exceptions and the pre-existing source corpus described here.
• OAuth: authorization codes expire after 5 minutes; access tokens after 60 minutes; refresh tokens after 30 days. Daily cleanup removes expired authorization codes; access/refresh token records are removed once more than 7 days have passed after expiry, revocation or consumption as applicable. A rolling refresh creates a new expiry. Disconnect invalidates active access and refresh tokens immediately; invalidation is distinct from deletion of their hashed records.
• Connection metadata: retained while the registered connection is available. The daily cleanup removes client-registration records marked revoked more than 180 days ago. Disconnecting your tokens does not necessarily delete a reusable client registration; contact us to request deletion of your linked personal data.
• MCP audit: a 180-day rolling window, with older records removed by daily cleanup. Account/client identifiers remain linked during that period for quotas, abuse investigation and support.
• Diagnostics: application log files rotate after 14 days. Sentry's current error-event retention is 90 days; performance traces, when recorded, have a 30-day retention. Aggregated performance metrics may remain for up to 396 days. Exceptional preservation for a specific incident or legal obligation is limited to that purpose and the necessary period.
• Account, source and third-party copies: the main Temidy account is maintained for the account relationship, subject to deletion requests and statutory record-keeping described in the general privacy policy. Legal-source records are maintained for the research corpus and source corrections, independently of a tool call. Disconnecting does not erase the underlying court publication or a copy already received by an assistant provider. That provider's retention and deletion controls apply to its copies.

Erasure requests also cover any relevant diagnostic or backup copies subject to applicable legal exceptions. Backup restoration and rotation are operational processes, so deleting an active record is not a promise of instantaneous deletion from every disaster-recovery copy. We explain any remaining retention and applicable restrictions when responding to your request.

9. Controls, rights and complaints

You choose whether to connect and what to ask. To stop future access, sign in and open Temidy MCP connections, then revoke the relevant connection (or all connections). You can also remove the connector in your assistant's settings. For assurance that Temidy tokens are revoked, use the Temidy control. Reconnection requires authorization again. This stops future calls; it does not erase past results already in the assistant's history.

For access, correction, erasure, restriction, portability or an objection to legitimate-interest processing, write to [email protected]. You may request deletion of linked MCP/audit records or correction/removal review of a specific legal-source item; include its case reference or URL. We verify identity proportionately, assess applicable rights and legal exceptions, and normally respond within one month; a lawful extension will be explained. You may complain to the Lithuanian State Data Protection Inspectorate or your competent supervisory authority. Stopping the connector does not require closing your Temidy account. Necessary security/authorization processing cannot be selectively disabled while continuing to use MCP; you can disconnect and exercise your rights.

10. Security and changes

We use HTTPS, OAuth with PKCE, limited scopes and token lifetimes, hashed token storage, access checks, quotas and restricted operational access. Use the assistant provider's privacy/history/training controls for its copies. We update this policy when data flows or retention change, show the effective date here, and provide notice of material changes where required. The Lithuanian version is also available.