Privacy

What stays on your Mac

Conversations, session history, workspace registrations, preferences, and every file the agent reads or writes live in application data on your Mac. None of it is uploaded to Submergent.

Your Submergent account

Submergent is a paid application and requires a Submergent account. That account exists to license the app and handle billing; it is separate from the provider accounts you connect, and it is not where your sessions or files live.

The account holds licensing, billing, and Team reporting data:

• Your email address, and your name if you give us one
• Which plan you are on, when it renews, and whether it is in trial
• Which Macs your licence is activated on, identified by an opaque installation id
• Billing records held by Polar, our merchant of record — we do not store card numbers
• On Team and Enterprise, your membership of an organisation and your role in it

It does not hold your sessions, prompts, transcripts, file contents, workspace names or paths, or the credentials for any provider you connect. Eligible Team usage uploads the daily counters described below, rather than conversation content.

Application data is not encrypted at rest by Submergent. It is protected by macOS file permissions. Turning on FileVault is the recommended way to encrypt it. Credentials are the exception: provider API keys are stored in the macOS Keychain.

Team usage reporting

While you are signed in with eligible Team access, Submergent records provider-reported token consumption on your Mac and sends changed daily totals to your team in background batches. The totals identify the account, team membership, provider integration, actual model when available, and reporting source. Missing measurements remain unavailable. Prompts, transcripts, message content, workspace paths, and provider credentials are excluded from these reports.

Current Owners and Admins with Team subscription access can read usage for all team members; Members can read only their own. Leaving a team removes report access. Ending Team subscription access locks reports until eligible paid access resumes, while preserving their history.

Your reporting name, email, and uploaded usage remain with the team for its lifetime, including after membership removal or account deletion. Permanently dissolving the team deletes its cloud reporting history and retained reporting identities. Deleting a chat does not delete its usage accounting.

Ordinary sign-out preserves upload-only authorization for earlier eligible work. A pending window may finish after sign-out; later uploads pause until a user signs in again. Revoke a Mac from the Account page to stop that account's reporting authorization. Account deletion permanently stops that identity's reporting on every Mac. Reporting credentials are protected with macOS Keychain encryption and cannot read team reports or manage an account.

What goes to your provider

When you send a message, its content — your text, the files the agent reads, and command output it needs — goes from your Mac directly to the provider you selected for that session, under that provider's terms and privacy policy. Submergent does not proxy these requests through a service of ours, and does not keep a copy. Choosing Ollama keeps everything on your Mac, since Ollama runs locally.

Diagnostics

Crash and error reporting is on by default. You can turn it off anytime in Settings → Share Diagnostics. While it is on, reports carry operational fields only: app version, release channel, macOS major and minor version, architecture, provider adapter and version, error class and code, sanitized component and state identifiers, and bounded timing measurements.

Reports never carry:

• Prompts, assistant responses, or any conversation content
• File names, file contents, or diffs
• Workspace or repository names and paths, or your local username
• Terminal commands or their output
• Credentials, API keys, or tokens
• Browser URLs, including their paths and query strings

A report that cannot be shown to be free of these is dropped rather than sent partially.

Email updates

If you enter your address in the “Get notified” form on this site, we store that address, which page you submitted it from, and the time you submitted it, in a hosted Postgres database run by Neon. Nothing else is recorded — not your IP address, not your browser, not where you came from.

That address is used only to tell you about Submergent releases. It is not sold, shared, or used to build a profile, and it has nothing to do with the app on your Mac. Every email includes an unsubscribe link, and you can ask for the address to be deleted at any time at the contact below.

Local logs

Submergent keeps sanitized local logs, bounded in size and count, readable only by your macOS user. You can reveal or delete them from Settings.

Deleting your data

Deleting your account from the Account page immediately ends Product Access and starts removal of your hosted sign-in account data from Submergent, Clerk, and Polar. Previously uploaded Team usage and its reporting name and email are retained as described above. Prompts, workspaces, transcripts, and other local application data remain on each Mac until you remove them there. Deleting a session also keeps any git worktree and branch that session created — Submergent discloses the location when you delete it, and removing those is a git operation you perform yourself.

Contact

Privacy questions and deletion requests: support@submergent.ai.