Privacy Policy

Overview

SeaSalt ("we," "us," or "our") makes SeaSalt for Mac, which runs AI agents on your Mac, and the SeaSalt iPhone app, which lets you follow those agents and reach your Mac remotely. This policy explains what we collect, where it goes, and how long we keep it.

SeaSalt handles two kinds of data differently:

• Agent and work-session data is stored on our servers. Conversations, prompts, results, and code changes sync through SeaSalt so they are available on all of your devices. This data is encrypted in transit and at rest, but it is not end-to-end encrypted, and our systems can read it.
• Remote access is end-to-end encrypted. Terminal, remote desktop, file, and Browse traffic between your iPhone and Mac is encrypted on your devices. We cannot decrypt it and do not store it.

Information We Collect

Account information

Your email address and sign-in details (email and password, or Sign in with Apple), which our authentication provider handles. We also store your plan, trial dates, and subscription status.

Device information

For each device you register: the device name, platform, app and operating system versions, a hardware identifier for your Mac, public encryption keys, when it was last active, and push notification tokens for your iPhone. If you connect ChatGPT, your Mac also reports that account's email, plan type, and usage limits so the apps can show them.

Agent and work-session content

To sync agents across your devices, we store on our servers:

• Agent and Captain conversations, including attachments
• Agent names and instructions, and project names, summaries, and local folder paths
• Work-session prompts, progress updates (including command output, reasoning summaries, and web search queries), results, and errors
• Code changes made during work sessions, including file paths and diffs
• Approval requests, such as a command or file change an agent asks you to allow
• Tasks, schedules, skills, and your preferences
• Context sources you add, including the text of documents you attach. When you add a web page, our servers fetch it and store its text.
• Notification text, which can include up to 200 characters of an agent's reply or result

Remote session metadata

For terminal and desktop sessions we store the session title, working directory, launch command, and lifecycle events (created, attached, detached, ended). We do not store terminal input or output, screen contents, or file contents from remote sessions.

Diagnostics

Our apps send crash reports, errors, and a trail of recent app events and log lines to our error reporting provider, Sentry, tagged with your account and device IDs. Log lines can include your email address, the text of a session assistant question, and the first 50 characters of text sent into a terminal session. This reporting is always on. If you send diagnostics from the iPhone app, we also receive the logs you submit with your device model and OS version.

Billing information

Payments are processed by Stripe. We store your Stripe customer and subscription IDs and your subscription status, not your card details.

Connection information

Our servers and network providers process IP addresses and connection timing to route traffic. Server-side error reports can include your IP address.

End-to-End Encrypted Remote Access

Terminal, remote desktop, file, and Browse sessions between your paired iPhone and Mac are encrypted with AES-256-GCM using keys derived through Curve25519 (X25519) key agreement. Private keys are generated on your devices and stored in their Keychains. Our relay forwards these encrypted frames without storing them and cannot decrypt them.

Some data is not covered by this encryption:

• Agent and work-session content, described above.
• Messages that coordinate sessions, such as session titles, working directories, and the conversation used to start a work session. These pass through our relay encrypted in transit but are readable by our servers. Credentials for an MCP integration also pass through the relay this way when you connect one from your iPhone. On your Mac, MCP credentials are stored in the Keychain.
• The session assistant. When you ask it a question from your iPhone, your Mac sends your question, recent conversation with the assistant, session titles, and the last 50 lines of output from your active terminal sessions to our servers, which send them to xAI to generate the answer. Answers return through our relay without end-to-end encryption.
• App diagnostics sent to Sentry, described above.

AI Model Providers

Agents run on your Mac using the provider account you connect, such as Claude Code, ChatGPT through Codex, or Devin. Prompts, code, and files an agent works with are sent from your Mac directly to that provider under your account and its privacy terms, not through SeaSalt. With a local model through Ollama or LM Studio, inference stays on your Mac (Ollama's cloud models run on Ollama's servers).

How We Use Information

We use the information we collect to:

• Provide SeaSalt, including syncing agents and work sessions across your devices
• Authenticate you and manage your devices and pairings
• Route encrypted remote-access traffic between your devices
• Send notifications you have enabled
• Process subscriptions and enforce plan limits
• Diagnose errors and improve reliability
• Send essential service communications

We do not sell or rent your personal information, and we do not share it with third parties for their marketing. We do not use your agent content to train AI models.

Data Security

• TLS for all connections between your devices and our servers
• Database encryption at rest, with no public network access to the database
• End-to-end encryption for remote-access sessions, as described above
• Outbound-only connections from your Mac and iPhone; no ports are opened on your network
• Device pairing with a verification code shown on both devices and confirmed on your Mac
• Device revocation that takes effect immediately

Authorized SeaSalt staff can access account and service data when needed to operate and support the service.

Data Retention and Deletion

We keep account, device, and agent data while your account is active. Agent content stays on our servers until you delete it (for example, by clearing a conversation or deleting a project or work session) or your account is deleted; it does not expire automatically. Server logs and submitted diagnostics are kept for 30 days. Database backups are kept for 7 days.

To delete your account and its data, email privacy@seasalt.app from the address on your account. Deleting your account removes your agent, work-session, device, and session data from our database; backups are overwritten as they expire. Stripe keeps billing records it is required to retain.

Your Rights

Depending on where you live, you may have the right to access, correct, delete, or export your personal data. To exercise these rights, contact us at privacy@seasalt.app.

Third-Party Services

We use these providers to operate SeaSalt. Each has its own privacy policy.

• Clerk: Account sign-in. Processes your email address and sign-in credentials.
• Amazon Web Services: Hosts our API, relay, database, logs, and app downloads.
• Cloudflare: Network and security services in front of our API. Handles connection data such as IP addresses.
• Stripe: Subscription payments and billing.
• Sentry: Crash and error reporting from our apps and servers, as described under Diagnostics. Server reports can include request details such as IP addresses.
• Apple Push Notification service: Delivers notifications to your iPhone, including their text.
• xAI: Generates session assistant answers from the terminal output you ask about.
• Google: Our apps load plugin logos from Google's favicon service, which receives the plugin's web domain and your IP address.
• Google Analytics and PostHog: Website analytics, described below.

Website Cookies and Analytics

Our website shows a consent banner on your first visit. PostHog collects nothing until you accept; after you accept it records page views, interactions, and session replays (form inputs are masked). Google Analytics runs in consent mode: before you accept, it sets no cookies but can send Google basic, cookieless signals such as page views; after you accept, it uses analytics cookies. You can decline, and the site works the same either way.

Changes to This Policy

We may update this policy. We will notify you of significant changes by email or in the app. Continuing to use SeaSalt after a change means you accept the updated policy.

Contact

Questions about this policy? Contact us at privacy@seasalt.app.