Your data and your AI
Last updated: September 4, 2026
The guides on this site ask you to hand a file to an AI app: a credit report, a statement, a card's terms. This page says what leaves your device when you do, what reaches Miles, and what never does. It is written for the reader who paused at that step. If you did not, nothing here changes the guides.
Two different AIs
Miles Chat is one. The AI app you connect to Miles is another: Claude, ChatGPT, Codex, or an agent you run yourself. They see different things.
- Miles Chat. What you type, and the wallet you keep with Miles, go to the model providers Miles uses, through OpenRouter. The privacy policy names them. Miles Chat never asks for a file, a login, or a statement; it has no field to put one in.
- Your AI app. Reads a file where you attached it: on your device, or in that app. Miles never receives the file. What the app sends Miles is a short series of tool calls, and each guide names what is in them.
What each guide sends to Miles
- Wallet from your credit reports. Card names, open and close dates, and whether you are the holder or an authorized user. Not the report, not balances, not account numbers.
- Credits and free nights from your statements. A status per credit per period: used, partly used, unused, or unknown. For a free night, whether the spend threshold was crossed. Not the transactions, not the merchants.
- A card at its annual fee. The retention offer's terms, the decision you made, and a review date.
- The Hilton Aspire and Surpass shuffle. Product-change dates, certificate statuses, and which credits you used.
- Miles with a local model. Whatever the guide you follow with it sends. The model itself sends nothing to anyone.
None of it includes a card number beyond the last four digits. Miles refuses to store more than four if an app hands it more.
Who reads the file
The AI app you chose, under its own terms. Miles is not in that conversation and cannot see it. Whether the app keeps the file, trains on it, or deletes it is that app's policy, so read the one you use: Anthropic for Claude and Claude Code, OpenAI for ChatGPT and Codex, Google for Gemini. Most offer a setting that keeps your conversations out of training; turn it on before the first upload.
Run a local model
Miles works with a model that runs entirely on your own computer. The connector is a standard MCP server over HTTP with an OAuth login, so any app that can run a local model and connect to a remote MCP server can connect to Miles. Your conversation, the file you attached, and every word the model reads or writes stay on your machine. The only traffic that leaves it is the tool calls in the list above, over the same connection every other app uses.
- LM Studio. Runs the model locally and connects to remote MCP servers with a browser login (version 0.4.10 or later). Add https://mcp.askmiles.ai/mcp as an MCP server, sign in when the browser opens, and choose what to allow. The step-by-step guide walks through it.
- Open WebUI. Add the same address as an MCP server of type Streamable HTTP with OAuth 2.1 (version 0.6.31 or later). It runs models through Ollama or any local server behind it.
- Ollama on its own. Ollama has no MCP support built in. Put an MCP client in front of it that uses it for the model: Goose, mcphost, or ollmcp are the common ones.
- An agent you run yourself. OpenClaw connects the same way, and its model is your choice.
Three things to know before you rely on it. Miles has not tested every client; the protocol is standard and the login is the same one Claude and ChatGPT use, so a client that can sign in to any OAuth-protected MCP server can sign in to this one, but if one refuses, say which. The model has to be one trained for tool calling, with a context window large enough for a few dozen tool definitions; an Apple silicon Mac with 8 GB of memory runs a suitable one, and the guide names some. And your wallet itself still lives with Miles, encrypted with a key that belongs to your account: what a local model buys you is that nothing you type, upload, or read ever leaves your machine, not that Miles holds nothing.
If you would rather keep the file local but do not mind the model running at a vendor, an agent such as Claude Code or Codex reads a file from a folder on your disk and sends Miles only the tool calls above.
What you can undo
- A connection. Settings, Connected AI Apps: pause every connection at once, or disconnect one app.
- Changes to your wallet. Off by default. An app can write to your wallet only if you turned on Also allow changes to your wallet on the approval screen, and you can turn it off there again.
- An import. A spreadsheet import can be undone for 30 days.
- Everything. Deleting your account destroys your encryption key, and the backups become unreadable with it. The security page covers how the key works and where its protection ends.