Financial data privacy and security

Where does my financial data go?

Request: your AI app sends a tool request to the hosted connector. The connector checks your sign-in and associated connection, retrieves the token from Nango, and requests the allowed records from Lunch Money.

Response: Lunch Money returns records to the connector. The adapter selects supported fields, then the connector returns the result to your AI app. Your app may pass those records to its model provider to generate an answer. This is a hosted service, not an entirely local workflow.

Where is my Lunch Money token stored?

Enter your token only in Nango's browser connection flow, never in chat or an MCP configuration file. Nango stores the credential. The connector retrieves it into server memory to authenticate requests to Lunch Money; it does not store the token in its identity database or return it as a tool result.

Nango documents encryption of stored credentials in its security documentation. That is a provider-described control, not an independent audit of this deployment. This review does not verify provider dashboard settings, backup deletion, or retention periods.

What does read-only access protect?

The connector exposes tools for reading accounts, transactions, categories, tags, recurring items, and budget summaries. Its adapter permits only GET requests to a fixed Lunch Money API origin and an allowlist of read endpoints. It cannot edit financial records or move money through these tools. Connection tools can still create or delete the saved connection.

This restriction belongs to the connector, not necessarily to your Lunch Money token. A token used elsewhere may have broader permissions. Read-only access does not stop sensitive records from being read, included in an AI answer, retained by a provider, or shared from your conversation. Review which tools and records you authorize your AI app to use.

What can my AI app and model provider receive?

Depending on the requested tool, results can include account names and balances; transaction dates, payees, amounts, currencies and category or tag identifiers; category and tag names; recurring items; and budget summaries. Transaction notes and undeclared fields are removed by the adapter, but the returned records remain sensitive and are not anonymous.

Your AI app decides how to use tool results and which conversation context to send to its model provider. The connector cannot enforce that provider's storage, training, sharing, or deletion settings. Check the policies and data controls for your specific app, account plan, and model before connecting. Disconnecting later does not recall records already returned.

What does the connector retain?

• Account and connection records: internal user ID, authentication issuer and subject, connection identifiers, status, environment, and timestamps are stored in Cloudflare D1 to associate your connection with your account.
• Financial results: requested records pass through the connector to your AI app. The connector does not persist financial responses in its database. Your AI app and its model provider may retain those results in conversations under their own settings and policies.
• Operational counts: allowlisted event labels, tool names, and HTTP status codes help measure reliability. Connector telemetry excludes user identifiers, tool arguments, tokens, connection links, request bodies, and financial results. Infrastructure providers may keep separate security and network logs.
• Website usage: PostHog receives page-view, Connect-click, and successful setup-copy events with a fresh random identifier for each event. We do not send financial data, credentials, chat content, page URLs, referrers, or user identities in those events. The website uses no analytics cookies or session recording. PostHog still receives network information, including your IP address, when your browser connects.

Website usage counts are enabled by default. You can disable them; Global Privacy Control and Do Not Track also prevent collection. An explicit preference is stored locally for 180 days.

Services involved

These providers handle different parts of the connection. Their policies explain their own processing and retention.

• Auth0 (Okta): account sign-in at auth.n3wth.com and authentication information. Privacy policy.
• Nango: browser connection setup and storage of your Lunch Money API token. Privacy policy.
• Cloudflare: connector execution, identity and connection records in D1, and operational telemetry. Privacy policy.
• Vercel: website hosting and routing requests to the connector. Privacy notice.
• PostHog US Cloud: website usage events described above. Privacy policy.
• Lunch Money: your original financial records and API requests authenticated with your token. Privacy policy.

Your chosen AI app also receives the requested financial results. Review its privacy policy and data controls before connecting: OpenAI (ChatGPT and Codex), Anthropic (Claude), Cursor, or xAI (Grok). Listing a provider here does not mean its integration is available or verified.

How is disconnecting different from revoking my token?

Disconnect the saved connection: ask your AI to run lunchmoney_disconnect. The server requests deletion of the Nango connection, then marks its connection record deleted after success. If deletion fails, access may remain active; retry and confirm success.

Revoke the original token: open Lunch Money's Developers page and revoke that token. This invalidates the credential for future API requests, including uses outside this connector. Lunch Money describes this control in its API getting-started guide. Disconnecting does not revoke the token, and uninstalling the plugin performs neither action.

Identity and connection lifecycle records remain after disconnect to preserve ownership and prevent replay or reconnection races. They do not currently have an automatic expiry. Provider logs and backups follow their respective retention settings. This integration does not configure automatic deletion of PostHog events.

Disconnecting does not delete your AI chat history. Manage that through your AI provider. For removal of retained connector records, contact oliver@newth.ai.

Report a security issue

Email oliver@newth.ai with a description and steps to reproduce. Do not include API tokens or financial records. You can also inspect the source code.