TRMNLYPricing

Privacy

Effective November 1, 2026

TRMNLY is a terminal for macOS with an iOS companion app, an account at trmnly.dev, and an optional cloud workspace. It is made by AW3 Technology, Inc., a Delaware corporation (“we”). This page says what each of those pieces sends off your device, who else handles it, and how to have it removed. If something here is unclear, write to will.schulz@aw3.tech.

The short version: your terminal, your files and your agent conversations stay on your machine unless you use a feature that sends them somewhere, and this page names every one. The apps contain no analytics or advertising SDKs. We do not sell personal information, share it for advertising, or use it to train AI models.

What stays on your Mac

The Mac app keeps its working data locally: terminal sessions and scrollback, projects, notes, agent conversations and memory, command history, browser data, and settings. API keys, access keys and saved browser passwords are stored in the macOS Keychain and are not synced to iCloud. None of this is uploaded to us unless you use one of the features below that does so, such as pushing keys to your cloud workspace or handing work off to it.

Crash dump files are written to ~/.local/state/ghostty/crash/ and stay there; the error reports described below may include a summary of a crash. The tool-call counter in the app (how often each agent tool succeeds or fails) is stored only on your Mac.

What the Mac app sends to trmnly.dev

  • Signing in and pairing. When you connect the app to your trmnly.dev account, we store a record of that device: the name you give it, its platform, the app version, when it was paired and last seen, and a device token. We keep only a hash of the token. You can revoke a device from your account page or by unpairing in the app.
  • Access check. Release builds check with trmnly.dev that your account is approved to use the app. The check sends the app version and a one-way hash of your Mac's hardware identifier, so an access pass works only on that Mac. If you ask for access, we email the operator your name, email address and app version.
  • Updates. The app fetches its update feed from trmnly.dev and downloads updates from Vercel's file storage. It does not send a system profile.
  • Error reports. While the app is signed in, it reports failures to trmnly.dev so they can be fixed. A report contains which part of the app failed, a short error type and the error message, with API keys, tokens, your home-folder path and identifiers removed. Depending on the failure it can also contain: the model provider, model name, status code and the error response the provider returned; the name of an agent tool that failed and the first line of what it printed, up to 300 characters, which can come from your own files or commands; and, after a crash or a hang, the signal, exception codes and the app's own stack frames. Every report carries the app version, build type, platform, operating system version and a random ID that changes each launch. Reports never include your prompts or the model's replies. They are on by default; turn them off with Send error reports to trmnly.dev in the app's tool telemetry settings. A Mac that is not signed in sends none.
  • App usage. A signed-in Mac or iPhone checks in with trmnly.dev as part of normal use (the Mac confirms its access at launch and every 15 minutes). For each day a device checks in, we record the device, its account, the app version, and when it was first and last seen that day, so we know how many people use the apps and which versions they run. Nothing about what you do in the app is included.
  • Feedback you send. If you file a bug report or feature request (from the Help menu, the agent's feedback tool, the trmnly feedback command or the website), we store its title, text and type, and the name of the agent that filed it if one did. Unless you untick it, it also carries diagnostics: operating system and version, CPU architecture, build type and app version. On the Mac you can also tick “Include the current agent conversation”, which is off unless you tick it. Only then does the report carry the chat from that window's Agent sidebar: its title, your messages and the agent's replies, and the tools it ran with their inputs and results, as text (images and files in the chat are not sent). Before it leaves your Mac, anything that looks like a key, token or password is replaced with a placeholder, and it is capped at 2 MB by leaving out the oldest messages. The form shows its title, message count and size before you send. We store it encrypted with a key specific to your account. A bug report from the Mac app also carries recent logs unless you untick “Include recent logs”: TRMNLY's own error log (the errors and freezes the app recorded, not what you typed or what ran in your terminals), a summary of where the app was stuck in its latest freeze, and its error messages from the last 30 minutes. Keys, tokens, passwords, email addresses and your home folder name are replaced before it leaves your Mac, it is capped at 512 KB, and it is stored encrypted the same way. Only TRMNLY administrators can read either attachment.
  • Remote control. If you turn on remote access so your phone can reach your Mac, the Mac tells trmnly.dev how to reach it: the tunnel's address (through Cloudflare or Tailscale), whether it is up and why not if it is down, its address on your local network with a port and certificate fingerprint, and, so your phone can wake it, the Mac's network hardware (MAC) address. Traffic between your phone and your Mac passes through the tunnel you chose. Only devices signed in to your account are let through.
  • Notifications to your phone. When a phone is paired, the Mac sends trmnly.dev what the notification should say, and we forward it to Apple's push notification service. For an approval request that is the Mac's name, the tool name, the safety level, the reason given and a preview of the tool's arguments (cut to 600 characters). For events — a pane you asked to watch going quiet or finishing a command, or, while you are away from the Mac, a pane raising a flag or a long agent turn ending — it is the Mac's name and a short description: a pane's title, the start of a command with its exit code and duration, the flag's reason, or a short summary of the agent's turn. We do not keep notification text after it is sent.
  • Your cloud workspace. When you use the cloud workspace from the Mac, what you send it goes through trmnly.dev: agent prompts and tool calls, files you hand off (including uncommitted work and a Claude Code conversation you continue there), and access keys you choose to push to it.
  • Shared chat. If you share a chat room, its threads and messages are uploaded to trmnly.dev, including the ones already in it, and agents in the room can post to it for you. See Shared chat below.
  • Credits. The Account pane fetches your credit balance and plans from trmnly.dev and opens checkout in your browser.

AI models and agents

When you use the agent in the Mac app, what it works with — your prompt, the conversation so far, and any file contents, terminal output or web pages it reads — is sent to the model provider you picked (Anthropic, OpenAI, Google Gemini or OpenRouter) using the API key you supplied, straight from your Mac; it does not pass through trmnly.dev. If you choose to run a model on TRMNLY credits instead of your own key, the same content is sent through trmnly.dev to the provider (Anthropic or OpenAI) on our key, so the turn can be paid from your balance; we forward it and count the tokens, and do not store the conversation. A local model, for example through Ollama, keeps that traffic on your machine. Command-line agents you run in a terminal, such as Claude Code, Codex or Gemini CLI, talk to their own services under their own terms. If you use a Claude subscription, the app reads Claude Code's sign-in on your Mac to show your usage limits from Anthropic.

The cloud workspace's agent is different: it runs on our servers, so your prompts and attachments reach it through trmnly.dev, and it calls the model provider from there using the key or Claude sign-in you stored for it.

The assistant in the signed-in web app runs on our servers with our own Anthropic key. What you type to it, the account details it looks up for you (credit balance, licence, devices, workspace time) and any docs or workspace files it reads are sent to Anthropic to write the reply, and each reply is paid from your credits.

Images, PDFs and text files you attach to the assistant are uploaded to Anthropic (its Files API) so the model can read them. We don't keep a copy of the file itself. Anthropic stores each file for up to 30 days and then deletes it. Until then it is listed under Files in the assistant, on any device you sign in on, so you can use it again; for that we keep its name, size, type, upload and expiry dates, which account it belongs to, and for an image a small preview. Deleting it from Files, or removing it before you send it, deletes it at Anthropic straight away; deleting a chat leaves its files under Files. Deleting your account deletes them all.

Your chat history with the assistant is stored only in your browser (on this device, in this browser's site storage), not on our servers. Clearing your browser's site data deletes it, and so does signing out; a chat started on one device doesn't appear on another.

The provider's own privacy policy governs what it does with that data. Running an agent on your own key does not use TRMNLY credits.

Features that send data elsewhere

These features talk to services other than trmnly.dev. Except where noted, each is off until you set it up.

  • Web search. On by default for the agent. Its search queries go to the search service you have a key for (Brave, Tavily, Exa, Serper or Perplexity); with none, to DuckDuckGo; or, for Anthropic models, to Anthropic's own search. You can turn web search off.
  • Voice. Dictation and voice input use Apple's speech recognition, which on the Mac may send audio to Apple to transcribe. The optional Whisper mode sends audio to OpenAI or the endpoint you set. The optional ElevenLabs voice sends the agent's replies to ElevenLabs to be read aloud.
  • Telegram. If you add a Telegram bot, messages between you and the agent, including summaries of its tool calls, pass through Telegram.
  • VibeHub. If you turn on VibeHub sync, agent conversations (messages, tool calls and shortened tool results) and terminal command records (the command, its folder, exit code and duration) are uploaded to vibehub.co, or a server you name, after secrets are removed.
  • Sharing a session. Share Session uploads the terminal's scrollback, with secrets removed, as a secret GitHub gist using your own GitHub sign-in.
  • Integrations with your tokens. Figma, Linear and GitHub are called with tokens you provide, when you or the agent use them.
  • The in-app browser. Pages you visit see your requests as in any browser. In Chrome mode, Chrome runs with its own Google services as usual.
  • Plugins you install can make network requests within the permissions you grant them.
  • Downloads. Some features fetch components when you first use them: the Cloudflare tunnel tool and the container engine's kernel from GitHub, and the diagram renderer from the jsDelivr CDN. Those hosts see your IP address.

The iOS app

The iOS app is a remote control for your Mac and your cloud workspace. To pair it, it registers with trmnly.dev as a device, the same way the Mac does (name, platform, app version, a hashed token); the token itself is kept in the iPhone's Keychain. If you allow notifications, we store the phone's Apple push token so we can send it notifications. Signing in with GitHub goes through trmnly.dev to github.com.

When it controls your Mac, it talks to the Mac through the tunnel or local network described above. When it uses your cloud workspace, its prompts, model choice and attachments go through trmnly.dev. Voice input on the iPhone is transcribed on the device. It contains no analytics or advertising SDKs.

While signed in, the iOS app sends error reports the same way the Mac app does, which can include the start of an error the cloud agent returned. Feedback from the iPhone also carries its model, how many Macs it is paired with and the state of your cloud workspace.

Your trmnly.dev account

  • Account details. Name, email address and profile picture, and whether and when your account was approved. If you sign up with a password, we store only a bcrypt hash of it.
  • GitHub and 1Profile sign-in. Signing in with GitHub gives us your GitHub user ID, username, name, avatar and email address, plus the tokens GitHub issues for the sign-in. Signing in with 1Profile gives us your 1Profile ID, name, email address, picture and whether the email is verified. Either is linked to an existing account with the same email address.
  • Repository access. Installing the TRMNLY GitHub App is a separate step from signing in. When you do, we store the installation's account name, the permissions granted and the names of the repositories you selected.
  • Connected agents. When you let an outside agent (such as Claude Code or Codex) connect to your cloud workspace, we store its access as a device on your account, under the name the agent gives. You can revoke it like any device.
  • Usage events on the website. We record a few events tied to your account: opening the dashboard or the credits page, starting a checkout, and joining the waitlist. Each records the event, time, browser type and a per-tab session ID. We count active accounts from these events and from error reports.
  • Error reports from the website. When a page on trmnly.dev fails in your browser while you are signed in, the page reports it, tied to your account: a short error type and message with web addresses cut to their path and tokens, keys and email addresses removed, where in our code it failed, the page path with IDs removed, the site version, browser type and a per-tab session ID. Errors on our servers are recorded the same way without being tied to an account. Reports never include what you typed, page contents, or request and response bodies.
  • Page analytics on the website. trmnly.dev counts its own page views and Mac downloads, with no third-party script. It sets no cookie and stores no IP address: for each view it records the page, the site that linked to it, any campaign tags in the link you arrived by (utm_source, utm_medium, utm_campaign), the country and whether the device is a desktop, phone or tablet, plus a visitor code made by hashing your IP address and browser together with the date. That code changes every day, so it can tell how many people visited today but can't recognise you tomorrow.
  • Waitlist. If you join the waitlist, we store your email address and browser user agent, plus the campaign tags and referring site of the visit you joined from, and the operator gets an email telling them you joined. A sign-up attempt with an address that is not yet approved joins the waitlist the same way. We record when and by whom the address was approved, and email you at that address when it is.
  • Academy learner pass. If you ask for a learner pass on /academy, we email you a one-time link and add your address to the waitlist as above, marked as coming from the Academy. A pass does not create an account or approve your address.
  • Newsletter. If you subscribe to the AW3 Technology newsletter, your email address is kept as a contact in Resend so we can send it to you, and the operator gets an email telling them you subscribed. Every issue has an unsubscribe link.
  • Contact form. A message sent from the contact page is emailed to the operator with the name, email address, company and browser user agent you send it with. It isn't stored on our servers.
  • Rate limiting and logs. Your IP address is used as a short-lived counter key to limit how often some actions can be called; the counter expires on its own. Our host keeps standard request logs, including IP addresses, for a limited time.

Support chat on the website

The trmnly.dev home page has a support chat provided by AngelSend. It loads only when you click Chat with us: until then no request goes to AngelSend and nothing of theirs is stored in your browser. If you use it, your messages, and any name or email address you give, go to AngelSend, which stores them and answers with an AI assistant. It keeps a random visitor ID, and your name and email if you gave them, in your browser's local storage, and sees your browser type. Do not put passwords or keys in it. Ask us at will.schulz@aw3.tech to have a chat deleted.

Cookies and browser storage

trmnly.dev uses no advertising or tracking cookies. It sets:

  • Sign-in cookies that keep you signed in and protect forms. Needed for the site to work.
  • trmnly_plan, for 30 days, after you enter the password for a password-protected page.
  • trmnly.theme, which remembers light or dark mode.
  • trmnly_learner, for a year, after you open a learner pass link: it unlocks the Academy lessons in that browser and holds the address the link was sent to.

It also keeps some things in your browser's own storage, never sent to us unless noted: the remote-control credential and terminal history on /remote, your cloud agent conversations and layout preferences, a per-tab session ID used in the usage events and error reports above, an offline cache for the remote page, and the support chat's keys, and the campaign tags and referring site of the first page you opened in the tab, kept for that tab only and sent with a waitlist request. Clearing your browser's site data removes all of them.

The cloud workspace

A cloud workspace is a Linux machine run for you on Vercel Sandbox. Whatever you put on it — files, repositories, terminal sessions, agent conversations — lives on that machine while it runs.

  • Saved files. When you press Save, your workspace folder is packed into an archive, encrypted with AES-256-GCM under a key derived for your account, and stored in Vercel Blob storage. It is restored onto your next workspace.
  • Conversation archive. If you choose “On this Mac and on trmnly.dev” in the Mac app's Conversation archive setting, the app uploads its Agent chats and the Claude Code, Codex and Gemini CLI transcripts it finds on your Mac. They include everything that passed through those sessions. Each is stored encrypted the same way, with its name, source, project folder, first prompt, size and dates kept so the list can show them. You can download or delete any of them at /app/conversations; deleting your account deletes them all. Nothing is uploaded in the other two modes.
  • Terminal history. If you choose “On this Mac and on trmnly.dev” in the Mac app's Terminal history setting, the app uploads the text its terminal panes printed, one file per pane per day, once the pane has been quiet for ten minutes. A file holds whatever the pane showed, including anything a command echoed, and opens with the project, tab and pane names, folders and your Mac's name. It is stored, listed and deleted exactly like the conversation archive above and counts toward the same limit. Nothing is uploaded in the other two modes.
  • Keys and tokens. API keys you add to the workspace's key vault, and the Claude and GitHub tokens the workspace's agent and scheduled jobs use, are stored encrypted the same way and placed on the workspace when it needs them. Only their names are shown back to you.
  • Projects and jobs. We store your cloud projects (name and folder) and scheduled jobs (their prompt or command, repository, schedule and settings), with a record of each run: timing, status, a summary, its log, its model cost, the Claude conversation it used, and a link to its result. If notifications are on, we email you when a job finishes.
  • Metering. We record when each workspace session started, when a client was last attached, and how many minutes have been charged.

Shared chat

Chat rooms you create or join on trmnly.dev are stored on our servers: the room, its members (display name and handle), its threads and every message, including threads you had locally before sharing the room. Agents that are members can read and post in it. If you invite someone by email, we store their address and send them the invitation.

Purchases, credits and plans

The desktop app is bought per seat, with 12 months of updates; renewing updates for another year is a separate, optional purchase, and we record the date your updates run to. Credits pay for cloud workspace time, and the Pro plan is a monthly subscription that adds credits each month. Balances, plans and purchases are handled by cred.diy, a billing service also used by other AW3 Technology apps: when you create an account we send it your account ID, email address and name, and it records your balance, purchases and how credits were used. Payments go through cred.diy's hosted checkout and Stripe; we never see your card number. If you use the same email address with another AW3 app, cred.diy may recognise you there.

Who else handles your data

These services process data for us to run TRMNLY:

  • Vercel hosts trmnly.dev, runs cloud workspaces, stores encrypted workspace archives and app updates, and keeps request logs.
  • Neon hosts the database behind trmnly.dev.
  • Upstash holds short-lived rate-limit counters.
  • Resend sends email: job results, chat invitations, the newsletter, contact-form messages and notices to the operator. It also keeps the newsletter's subscriber list.
  • cred.diy and Stripe handle credits, plans and payments.
  • GitHub and 1Profile provide sign-in; GitHub also provides repository access.
  • Cloudflare and Tailscale carry remote-control traffic when you choose them.
  • Apple delivers push notifications and distributes the iOS app through TestFlight.
  • AngelSend runs the website's support chat.
  • Anthropic writes the web app assistant's replies, from what you send it (including files you attach, which it stores for up to 30 days) and what it reads for you.
  • ElevenLabs reads our learning lessons aloud. It receives only the lesson text, nothing about you.

The model providers and other services you choose to use (see above) receive what you send them directly, under their own terms. We may also disclose information if the law requires it, to protect people or the service from harm, or as part of a merger or sale of the business, in which case this policy would continue to apply to it.

Who can see it

TRMNLY's administrators can see account records, paired devices, the waitlist, feedback, error reports and activity counts through an admin page. We look at them to run the service, fix bugs, prevent abuse and answer you, and for nothing else. We do not read your workspace files, saved archives or chat rooms unless you ask us to, for example to help with a problem. An agent conversation you attach to a bug report is that kind of request: administrators can open it from the report to work out what went wrong, and no one else can.

Why we use it

We use your information to provide the service you signed up for (our contract with you), to keep it secure and fix what breaks (our legitimate interest in running a reliable service), to bill you, and to meet legal obligations. Where a feature depends on your consent, such as notifications or the optional integrations above, you can withdraw it by turning the feature off.

Your choices and rights

You can see and correct your account details on your account page, revoke devices, turn off error reports and optional integrations, and delete your account (below). Depending on where you live, including the EU, the UK and California, you may also have the right to a copy of your information, to have it corrected or deleted, to object to or restrict how we use it, and to complain to a data protection authority. To use any of these, email will.schulz@aw3.tech from the address on your account; we will answer within 30 days and will not treat you differently for asking. We do not sell or share personal information as California law defines those terms.

TRMNLY is run from the United States, and the services above store data in the United States and elsewhere. By using it you understand your information will be processed there.

Keeping and deleting data

We keep account data for as long as your account exists. TRMNLY is in beta and does not yet delete old records on a schedule. You can delete your account yourself, from the Account tab of the iOS app or your account page on trmnly.dev, and it takes effect immediately. It cancels your Pro plan straight away, so you are not charged again, and permanently deletes your cloud workspace and saved archive, keys, projects and jobs, devices, sign-ins, chat rooms you own, feedback (including any agent conversations you attached to it), error reports and usage events. An attached conversation is otherwise kept with its report until then; to have one deleted sooner, email will.schulz@aw3.tech with the report's reference. If you can't do either, email will.schulz@aw3.tech from the address on the account and we will do it for you.

A few things are kept after deletion:

  • Messages you posted in other people's chat rooms stay as a placeholder that says the author deleted their account; what you wrote is removed.
  • Records of GitHub App installations are disconnected from you; to end access, uninstall the app on GitHub.
  • Your cred.diy record, balance and payment history are kept, because they may be shared with other AW3 apps and payment records must be kept by law. Email will.schulz@aw3.tech to have the cred.diy record deleted too.
  • Support chats with AngelSend, server errors not tied to an account, and our host's request logs, which expire on their own.

Security

Device tokens and passwords are stored as hashes. Workspace archives, keys and job tokens are encrypted before they are stored, and traffic to trmnly.dev is encrypted in transit. No system is perfectly secure, and TRMNLY is beta software. Please tell us at will.schulz@aw3.tech if you find a problem; if we learn of a breach that affects your information, we will tell you as the law requires.

Children

TRMNLY is a developer tool and is not meant for children under 13, or under 16 in the EU and UK. We do not knowingly collect their data, and will delete it if we learn we have.

Changes

If this policy changes, we will update this page and its effective date. For significant changes we will tell account holders by email or in the app before they take effect. The terms cover the rest of how TRMNLY works.

Contact

AW3 Technology, Inc., attention Will Schulz, CEO: will.schulz@aw3.tech.