Relex security and confidential legal context

Keep control of client identities. Verify local anonymisation, encrypted cloud storage and the data path of your chosen reading model.

Why should I trust you with client data?

Don’t take our word for it. Supported browser processing de-identifies documents locally and seals detected identity data before cloud storage. Relex stores ciphertext and encrypted key material for portability—not your PII password. Private-server and custom-endpoint reading have different data paths. Check the actual mode, file type and requests with the verification guide.

Discover, connect, then use

Public documentation and published Marketplace profiles can be read before sign-in. Access to private matters requires the user’s authorization. The hosted MCP endpoint is https://relex.legal/api/mcp. Use search to discover current operations and execute to call them. Read permitted matter context before work and conclude steering sessions so their results enter the continuing record. Never request plaintext client identities through chat.

What this does not promise

Relex is not a law firm. A connected model may still be wrong; professional judgment and source checking remain necessary. Portability applies to context stored in Relex, not every private chat or a model’s internal memory. Marketplace publication, professional verification and use of agents are different facts. A listing is not a guarantee of availability or engagement.