Trust

Security and data

For security reviewers and admins: what an assistant can reach through Nylon, what we record, where data goes, and how access ends.

What an assistant can access

The two tools are read-only. They search and read Nylon’s library of published legislation, cases and guidance.

An assistant can

Search Nylon’s library of cases, legislation and commentary
Read the full text of a document in the library

An assistant can't

See your Nylon chat history, folders or saved work
Change account, billing or team settings
Upload, edit or delete anything in the library

The library is published law and guidance. The tools never read your firm’s documents or client records.

Each person connects with their own Nylon account, and the assistant acts for that person only while their seat allows it. Every connected user sees the same library.

OAuth 2.1 with PKCE (S256 only); public clients, no shared API keys.
Access tokens last 1 hour and are bound to the MCP server’s audience (RFC 8707). The MCP server verifies the signature, issuer, audience and expiry on every request.
Refresh tokens last 30 days and rotate on every use, and reuse revokes the whole token family.
Nylon stores only SHA-256 hashes of refresh tokens and authorisation codes, never the raw values.
Nylon checks the user’s seat and their organisation’s settings every time it issues or refreshes a token. The check fails closed.
The MCP endpoint and Nylon’s sign-in accept TLS 1.2 or later only.

Details are in Authentication.

What we log

For each tool call, the MCP server records:

which tool ran, the outcome (success, error or invalid arguments) and how long it took;
which assistant made the call, and the user and account;
a hashed session reference;
the shape of the request, not its content: how many searches, which search types, which jurisdiction, practice-area and content-type filters, whether date, section or paging options were used, and how many results came back;
for a read, the read mode and the document ID.

These usage records have no field for query text or search-within phrases. The MCP server redacts bearer tokens and cookies from its logs.

Connecting an assistant also records that the connection was made and when tokens were issued, with the assistant’s client ID.

Data flows

Where	What	Retention
AWS Sydney (Australia): the MCP server	Query text and tool results, in memory while it answers. Server access logs: method, path, status and timing.	Access logs: 90 days
AWS Sydney (Australia): Nylon’s library	Query text, to run the search. Results are published law, not your firm’s data.	Not stated here
AWS Sydney (Australia): Nylon’s app database	The usage records listed above.	Not stated here
Datadog (US): logs from Nylon’s sign-in	Sign-in and token requests: user and account IDs, the assistant’s client ID and IP addresses. No query text.	Per our sub-processor terms
Your AI assistant’s vendor	Your prompts, and the tool results Nylon returns.	Under that vendor’s own terms

The MCP server itself calls no AI model. Your AI assistant (Claude, ChatGPT, Copilot or another) processes your prompts and Nylon’s results under its vendor’s terms, not Nylon’s.

Citations

Every result carries a link to Nylon’s source viewer at docs.usenylon.com. The assistant is told to cite only these links and never to invent case-law URLs. Opening a link needs a Nylon sign-in, so a reader without a Nylon account can’t follow it.

Disconnect

There’s no token revocation endpoint today. Access ends in these ways:

Who	Action	Effect
The user	Remove Nylon from the assistant’s connectors	The assistant discards its tokens.
An admin	Turn off Allow AI tool connections in Organisation Settings → Connections	Nylon refuses new tokens and refreshes for everyone in the organisation.
An admin	Remove the user, or move them to a Starter seat	Nylon refuses new tokens and refreshes for that user.

Certifications and policies

Nylon holds SOC 2 Type II, ISO 27001 and ISO 42001 (AI management). Reports and policies are in the Nylon Trust Centre, and our certifications are listed at usenylon.com/security.

For security questions or to report a vulnerability, email support@usenylon.com.