Data and privacy

Use synthetic test data only. Never send real patient records, names, dates, record numbers or any other identifier. Orinyx does not connect to any electronic health record. There is no business associate agreement (BAA) for this service.

What is sent

• Your agent host (for example Claude Code) sends each order, as the agent passes it, to the Orinyx MCP service at orinyx-mcp.fly.dev. If the agent passes a tool name and version, those go too. The host keeps its own copy of the conversation under its own terms.
• The MCP service relays the request to the Orinyx API with your own sign-in. The MCP service has no database of its own.
• If you run the local server or the orinyx CLI, it sends your requests to the Orinyx API with your own API key.

What is stored

The API stores an audit record for each check, under your account. It holds:

• the order or claim text exactly as your agent sent it;
• the result for each claim;
• the tool name and version, if your agent passes them;
• any context label you give;
• the email address of the account that ran the check.

Later actions on that check, such as an export, are added to the same record. The API also writes an access-log entry for each request, including the time, the route, the status, your account and the IP address the request came from.

Audit records are not deleted

Audit records cannot be deleted. Access-log entries are not deleted either. This is why you must send synthetic data only.

The identifier screen is a backstop

The API refuses an order that looks like it holds an identifier: a phone number, Social Security number, date, long number or record number. A refused order is not checked or stored. The screen is a backstop, not permission. It looks for identifier-shaped text only. It does not catch names, addresses or other details written in words.

On the hosted service, orders are split and identifiers are screened by fixed patterns. No language model is enabled there, and no model decides a verdict. orinyx observe runs the same identifier screen on your machine before it sends anything.

Reports

Never include real patient data, credentials or keys in an issue or a vulnerability report. Replace any key with a placeholder. GitHub's own privacy terms apply to what you post there.