Status: General personal-use notice for self-hosted deployments Effective date: 2026-08-31 Controller: Each deployment’s controller, if any, is the person running that deployment; this repository appoints none. Contact: This repository publishes no deployment contact address.
This notice describes the personal-data processing that may occur when a person runs a local installation of Enable Banking MCP. It is not the privacy policy of Enable Banking, a bank, an ASPSP, an MCP client, an AI host, or the repository maintainer. It does not identify, appoint, or make the repository maintainer responsible for any deployment or user’s actions.
Enable Banking MCP runs on the computer where the individual operator installs it. It is used only for the operator’s own personal, noncommercial account-information access:
This deployment is not a hosted service and is not intended for another person’s data, business accounts, professional use, payment initiation, or commercial use.
The person running each deployment determines the purposes and means of that deployment’s local processing. This repository does not operate deployments, receive their tool results, or assume responsibility for their users. Enable Banking and each participating bank or ASPSP process data under their own terms and privacy notices and may have their own controller or processor role:
Depending on the functions used, the local deployment may handle:
The deployment does not intentionally add advertising identifiers, analytics, profiling, or a central database.
Data comes from the individual operator, the Enable Banking Control Panel, the operator’s selected bank or ASPSP, the local operating system, and the MCP client or AI host.
The operator uses it to:
The applicable legal basis depends on the operator’s jurisdiction and facts, and may include the operator’s consent or a contract with the relevant provider. This notice does not claim a legal basis for Enable Banking or a bank.
The deployment sends or exposes data as follows:
The repository maintainer does not receive tool results from a self-hosted deployment.
The current macOS implementation stores the following in macOS Keychain:
New credential values are written as a single native Keychain item through
@napi-rs/keyring, under a separate service name from the older records.
Existing raw and chunked credential records remain readable until a successful
replacement, then are removed; /usr/bin/security is used only to read or
remove those legacy records, never to pass newly written secret values.
Previously written large credential records may occupy multiple related
Keychain records. The private key is generated or supplied by the operator and
is used to sign API requests. The certificate is registered with Enable
Banking and may be trusted locally for the HTTPS loopback callback. API
responses and callback codes are held in process memory while used; the MCP
does not intentionally persist banking responses.
The retention schedule for this personal deployment is:
| Data | Retention |
|---|---|
| Control Panel authentication | Until explicit logout, clear_local_credentials, or replacement; expiry alone does not clear the record |
| Application private key and certificate | Until clear_local_credentials, replacement, or manual teardown |
| Current session ID | Until delete_session, clear_local_credentials, replacement, or manual teardown; no local expiry metadata is stored |
| API responses and callback data | Process memory only unless the MCP client, AI host, logs, or backups retain them |
| Operational logs and diagnostics | Only as retained by the operator’s operating system and tools |
The Control Panel record includes the sign-in email and authentication tokens. An expired Control Panel record may remain in Keychain until explicit cleanup or replacement. The local session store retains an opaque provider session ID and does not know when the provider considers it expired.
clear_local_credentials clears local Keychain records and attempts to remove
the locally trusted certificate. It does not delete provider-side records,
revoke bank consent, erase environment variables, erase MCP-client or AI-host
history, or erase backups. The operator must use the relevant provider controls
and delete_session where appropriate.
The deployment uses HTTPS for remote API requests and the bank-consent callback, binds callback responses to a one-time state value, restricts callbacks to an explicit loopback host and port, and avoids returning credentials in status tools. The Control Panel email-link callback uses a separate loopback HTTP listener with a state-bound one-time sign-in code; it is not exposed as a public endpoint.
The person running a deployment controls the macOS account and Keychain, environment variables, certificate trust, browser, MCP client, AI host, network, backups, logs, and access to the computer. This repository does not control those systems. Private keys, tokens, authorization codes, session IDs, account data, and transactions should not be placed in source control, prompts, public issues, or untrusted tools.
If data or credentials may have been exposed, the person running the affected deployment should stop use, clear or rotate local credentials, delete or revoke the relevant provider session or consent, and contact Enable Banking or the bank as appropriate.
Subject to applicable law, data subjects may have rights of access, correction, deletion, restriction, portability, objection, and withdrawal of consent. Requests about a deployment should be sent to the controller or operator of that deployment, or to the relevant provider. This repository does not operate the deployment and does not provide a data-subject contact channel.
Do not send passwords, private keys, tokens, full account numbers, or unnecessary transaction data with a request. Enable Banking and a bank may independently control their data, so a request may also need to be directed to the relevant provider. A complaint may be made to the applicable supervisory authority.
The person running a deployment does not control the locations, subprocessors, or transfer mechanisms used by Enable Banking, banks, MCP clients, AI hosts, operating systems, or infrastructure. Their current terms and privacy notices govern those services. The person running a deployment should review those materials and applicable law.
This deployment is intended for the individual operator’s own personal financial information and is not designed for children’s data.
This notice is reference information for personal self-hosted use. The person running a deployment must publish and maintain any deployment-specific notice, contact channel, retention schedule, and legal information required for that deployment.
This repository publishes no personal or corporate contact address.
This notice is not legal advice. It does not replace the separate notices and terms of Enable Banking or any bank.