MLflow on Databricks (BYOK) — Privacy Policy

Effective 16 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What MLflow on Databricks (BYOK) is. MLflow on Databricks (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own MLflow on Databricks data: Read the MLflow experiments, runs, metric history, artifacts and model registry of your AWS Databricks workspace with your own personal access token. You bring your own MLflow on Databricks Databricks personal access token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one MLflow on Databricks call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to *.cloud.databricks.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If MLflow on Databricks rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What MLflow on Databricks receives. The request we make on your behalf, including the key and the arguments, under MLflow on Databricks's own terms and privacy policy (https://www.databricks.com/legal/mcsa). MLflow on Databricks acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer MLflow on Databricks gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your MLflow on Databricks data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. MLflow on Databricks (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at MLflow on Databricks at any time to end all access.

Children. MLflow on Databricks (BYOK) is a general-audience service operated by the adult using the assistant, under MLflow on Databricks's own age rules.

Changes. We will post changes here with a new effective date.