Privacy
Two ways to run it, two different answers.
On a hosted machine we receive what you write. On your own hardware we do not. This page says which is which, because one sentence covering both would be false about one of them.
Amelias Agent · last updated 31 August 2026
We sell neither data nor access to it. There is no advertising, no advertising identifier, no data broker, and no third-party tracking SDK in the app.
What stays on your device
- Server address and password. Stored in the iOS Keychain. Never transmitted anywhere except to the server you entered.
- Cached sessions. Conversations you have already loaded are kept on the device so they can be read offline. Deleting the app deletes them.
- Preferences. Theme, chosen model and similar settings, stored locally.
Hosted machines — what we receive
When you build on a machine we run for you, your request goes to our servers at
api.ameliasagent.com, operated by Houston IT Developers LLC. We receive and
process:
- What you write. The messages you type, and anything you dictate with the microphone.
- Your project files. The code and content the model reads and edits while it works.
- Voice recordings, when you dictate — sent to be turned into text, and not kept after that.
- Account and usage records. Your email, the model you chose, and what each turn cost, so the work can be billed and shown back to you.
We use this to run the build you asked for, to bill it, and to keep the service working. We do not use your prompts, your code or anything you build to train models.
The AI models, and who they belong to
Amelias Agent is an AI product: answering you means sending what you wrote to a language model, and those models run on other companies' computers. On a hosted machine the path is:
- Houston IT Developers LLC — our servers, which run the build and hold your project.
- OpenRouter, Inc. — routes the request to the model you picked.
- The model provider you choose — Anthropic, OpenAI, Google, Moonshot, MiniMax and others, depending on what is selected on the Models screen.
Each of these is bound by contract or by its own published policy to protect what it receives to a standard equal to this one, and none of them is permitted to sell it. Each provider's own privacy policy also governs what it does with what it is sent, and they differ — a model is a choice about privacy as well as about cost, which is why the app names the provider before you pick one.
The app asks before any of this happens. The first time you send a message, ask a question or dictate, Amelias Agent shows you what is sent and who receives it, and sends nothing unless you agree. You can withdraw that at any time under Profile → AI processing; the next send asks again, and until you agree nothing you write leaves the phone.
Your own hardware — what we do not receive
If you connect an agent running on a computer you control, your prompts, your code and your files stay between your device and that machine. We operate no server in that path and cannot read any of it. The agent on your machine then talks to whichever model provider you configure, or to a model running entirely on your own hardware, under your own account rather than ours.
If you connect through a relay, content is encrypted on your devices before it is sent and the relay stores only ciphertext. The keys never leave your devices.
Permissions the app asks for
- Microphone — only to dictate a message, when you tap to dictate. The recording is uploaded to be transcribed and is not kept afterwards.
- Camera and Photos — only to attach an image you pick.
None of this is uploaded until you attach it to a message or dictate, and then only to the machine your session is running on.
Keeping, and deleting
Projects and conversations on a hosted machine are kept while your account exists, so you can come back to them. Deleting your account — Profile → Delete my account in the app — removes them along with the account.
Three things outlive the deletion, and this page will not imply otherwise: billing records, which tax and accounting law requires us to keep for seven years; security and abuse logs, kept thirteen months so that deleting an account cannot be used to erase a trail; and last night’s backups, which are overwritten as the rotation turns over — about two weeks. Nothing you wrote or built is used to train AI models, before or after deletion. Delete your account sets out each of those in full, and it is the page to read if this one is the only page you read.
Usage measurement in the app
The app can report which screens get used and which errors happen, so we can see what to fix. It is off unless you turn it on, under Profile → Share anonymous usage, and it never includes your prompts, your code, or anything you build. Profile → Exactly what would be collected lists every field, generated from the code rather than written by hand.
Crash reports
When something breaks — the app closes on its own, the desktop connector stops, a page does nothing when you click it — a report is sent to Sentry, who process it on our behalf so we can fix it. This is separate from the usage measurement above and works differently: crash reports are on by default, because the person a crash happens to is usually left looking at a screen with no way to tell us about it.
A report contains what broke and where in our code: the error, the stack trace, the screen or page you were on, and which version you were running. It does not contain your prompts, your code, the contents of anything you are building, screenshots of your screen, your access tokens, or your IP address. On the phone, the desktop and a hosted machine, the paths of your own files are removed before the report leaves the device — what we receive never had them in it.
One exception, stated rather than glossed: when the failure happens on our servers, the report names the request that failed and the account it belonged to. That can include a project's name, because "is this one customer or everyone" is the first question worth answering about an outage. It still never includes what is inside the project.
You can turn crash reports off: in the app, Profile → Crash reports. On the desktop app,
create an empty file at ~/.amelia/no-crash-reports. A machine you host
yourself sends nothing at all, because the reporting is not compiled into it.
This website
ameliasagent.com (the website, not the app) uses Google Analytics to count visits and see which pages are useful. That measures pages viewed and general location — never your code, your conversations, or anything from the app. The site also reports its own JavaScript errors, as described under Crash reports above.
Children
Amelias Agent is rated 18+ and is not directed to children. Because the app builds whatever you ask it to, what a model produces cannot be guaranteed suitable for a younger audience, and the rating says so rather than leaving it to chance. We do not knowingly collect information from children.
Changes
If this policy changes, the date above changes with it. Material changes will be noted in the app's release notes.
Contact
Questions about privacy: support@ameliasagent.com
Houston IT Developers LLC, Texas, United States.
Run it where we cannot see it.
The desktop app and the self-hosted agent are the same Amelia on hardware you own, with your own keys. We charge nothing for it and we receive nothing from it.