Privacy policy

This is a translation for convenience. If it differs from the Spanish version, the Spanish version prevails.

Óptimo MCP is a Model Context Protocol server that lets AI assistants (for example Claude) query and operate ServiceNow instances that the user registers and controls. This policy describes what data the service processes, for what purpose, for how long and with whom it is shared.

1. Controller and contact

The service is operated by the owner of https://mcp.optimotech.co. For any question or request for access, correction or deletion of data, write to [email protected].

2. Data collected

Category	Data	Source
Panel account	Email address, password (only an irreversible fingerprint, never the password itself), role, creation date, last access.	The user, when signing up by invitation.
Profile	Display name and photo.	The user, from My profile.
Account security	Verification method, authenticator app secret (encrypted), passkeys (only their public part and their counter), backup codes (as a hash) and the remembered-browser mark for the configured hours.	The user, when setting up two-step verification.
ServiceNow instances	Alias, URL, technical user and credential (password, token or OAuth secret).	The user, when registering each instance.
OAuth authorization	Dynamically registered clients, codes, access and refresh tokens, scopes, source IP.	The connection flow from the MCP client.
Audit	Tool name, instance, user, date, result and a summary of what was requested, without credentials.	Each tool execution.
Account history	History of sign-ins and account changes (audit, 90 days).	Each sign-in and each account change.
Working memory	Observations and preferences that the user or the assistant save explicitly (for example, when the person asks Claude to remember something).	Explicit user actions.
Cache	Table metadata and public ServiceNow documentation, with expiration.	Queries to the instance and to docs.servicenow.com.
Allowed IPs	IP addresses or ranges allowed to connect, with an expiration date.	An administrator from the panel, or the person when asking Claude to allow their current IP.
Optimo Chat (chat inside ServiceNow)	Conversations and their messages (the person's and the assistant's text, steps, lists and sources with record numbers and descriptions), confirmed or cancelled actions (the action fields and the resulting record number), usage per person and day, and each person's ServiceNow user name and sys_id.	The instance's people who use the chat and their instance's responses.

With the MCP connector, the service does not store the content of conversations with the assistant: ServiceNow records returned by a tool are sent to the MCP client and are not kept, unless the user saves them as an observation. Optimo Chat, the chat installed inside ServiceNow, does store its conversations in this service to show each person their history, for the retention period stated below.

3. How it is used

• To authenticate the user and their MCP client (OAuth 2.0 with PKCE).
• To run, on the user's behalf, the operations they request on their ServiceNow instances.
• To keep a record of operations (audit) and detect abuse.
• To provide continuity across sessions through the working memory that the user chooses to save.

Data is not used for advertising, profiling or model training.

4. Storage and security

• Data is stored in a PostgreSQL database under the control of the service operator.
• Instance credentials are encrypted at rest with Fernet (AES-128-CBC with HMAC) using a master key that is not stored in the database. They are never shown in the panel or in tool responses.
• Account passwords are not stored: only an irreversible fingerprint that lets us check them, but not recover them.
• All traffic uses HTTPS. The MCP endpoint requires an OAuth token and, if the operator enables it, an IP allowlist.
• The panel applies CSP, HSTS, X-Frame-Options and CSRF protection.

5. Third parties

• The user's ServiceNow instances. The service sends each instance only the requests the user asks for, authenticated with the credential the user registered. ServiceNow processes that data under the user's contract with ServiceNow.
• MCP client (for example Claude). It receives the tool responses. Any further processing is governed by the assistant provider's policy.
• Infrastructure. The operator's hosting and HTTPS proxy. Data is not sold or transferred to third parties for their own purposes.
• The panel does not load third-party fonts or scripts: everything is served from this server. The HTTPS proxy adds the Cloudflare Web Analytics visit counter.

6. Retention

• Account, instances and working memory: while the account is active. The user can delete their instances from the panel, in My instances (Mis instancias). Saved preferences are deleted by asking Claude (for example, “forget my preferred update set”), which uses the snow_forget tool; memory observations are deleted from Memory (Memoria) if you administer the panel, or by asking for it by email.
• Unused instances: invalidated after 30 days of inactivity and must be revalidated in the panel.
• OAuth tokens: they expire with their lifetime; to revoke them earlier, go to My profile › Connected clients (Mi perfil › Clientes conectados) and press “Revoke” (Revocar).
• Audit: kept for traceability and can be purged at the request of the account owner.
• Cache: expires automatically and can be cleared from the panel.
• Optimo Chat: conversations without activity are deleted, with their messages and actions, after 90 days (a period the operator can configure); daily usage is kept for the status page. Uninstalling the chat does not delete what was stored earlier: it is deleted when that period ends, or sooner at the account owner's request.

7. User rights

You can revoke an MCP client's authorization in My profile › Connected clients. You can request access to, correction or deletion of your data and delete your account by writing to [email protected]. Requests are handled within 30 days at most.

8. Changes

Relevant changes to this policy are published on this same page with the update date. Continued use of the service after a change implies its acceptance.