Privacy Policy

Last updated: October 3, 2026

1. Introduction

Welcome to Solo. We respect your privacy and are committed to protecting your personal data. This privacy policy explains how we collect, use, disclose, and safeguard your information when you use our service.

2. Information We Collect

2.1 Information You Provide

  • Account information (name, email address, password)
  • Profile information (display name, avatar)
  • Phone number(s) you provide for SMS and voice communication features
  • Email content you send, receive, or process through Solo
  • Chat messages, live chat transcripts, and in-app communications
  • Voice call recordings and transcripts (when applicable and with your consent)
  • SMS and text message content sent or received through Solo
  • Agent configurations and workflows you create
  • Payment information (processed securely through Stripe)
  • Communications with our support team (including via email, chat, SMS, or phone)

2.2 Automatically Collected Information

  • Usage data (features used, actions taken, time spent)
  • Device information (browser type, operating system, IP address)
  • Log data (access times, pages viewed, errors encountered)
  • Call and messaging history, including identity and agent association, direction, timestamps, duration, delivery or completion status, and provider reference identifiers
  • Usage and accounting records, including token or duration measurements, saved rate versions, credit reservations, finalized credit charges, provider costs, and reconciliation evidence
  • Cookies and similar tracking technologies

2.3 Information from Third Parties

  • Authentication providers (Google, GitHub, etc.)
  • Email service providers (Mailgun)
  • Communications providers (Twilio — for SMS, voice calls, and phone number services)
  • Analytics services
  • Integration partners (Supabase)

3. How We Use Your Information

We use your information to:

  • Provide, maintain, and improve our services
  • Process your email, chat, SMS, and voice communications through AI-powered agents
  • Orchestrate agent workflows that analyze, route, and respond to your communications
  • Personalize your experience and agent behaviors
  • Deliver SMS notifications, alerts, and agent-initiated messages to your phone number
  • Facilitate voice calls and phone-based interactions through our platform
  • Process payments and manage subscriptions
  • Send service notifications and updates
  • Respond to support requests
  • Detect and prevent fraud or abuse
  • Comply with legal obligations
  • Analyze usage patterns to improve our service

3A. Agent Orchestration & Communications Data

Solo operates an AI-powered agent orchestration system. When you interact with Solo — whether by email, chat, SMS, or phone call — your communication data is processed by our agent system to understand, route, and respond to your messages. This means:

  • Email Data: Emails sent to or processed through Solo are analyzed by AI agents to categorize, draft responses, extract action items, and automate workflows on your behalf.
  • Chat & Messaging Data: Messages you send through Solo's chat interface or in-app messaging features are processed by AI agents to provide real-time assistance and automate tasks. Chat transcripts are stored to maintain conversation context and improve service quality.
  • SMS & Text Message Data: When you opt in to SMS communications, messages sent and received are processed through Twilio's messaging platform. Message content, phone numbers, timestamps, and delivery status are collected and stored.
  • Voice & Phone Call Data: When you use voice features, call metadata (phone numbers, duration, timestamps) is collected. With your consent, calls may be recorded or transcribed to enable AI agent processing and improve service quality.
  • Agent Processing: All communication data processed through our agent orchestration system is used solely to provide the services you have requested. We do not use your communication content to train general-purpose AI models, and we do not share your communication content with third parties for their marketing purposes.

3B. Your Work Data and AI Models

Your professional intelligence belongs to you. Solo does not use your business knowledge, messages, files, or other work content to train or fine-tune general-purpose AI models. Giving an agent context helps it perform your work; it does not turn that context into a model-training dataset.

We use business AI APIs under no-training terms and policies. We do not authorize optional sharing of your work content for provider model training. The providers used depend on the features and models in your workspace:

  • OpenAI: API inputs and outputs are excluded from model training by default, unless an API customer explicitly opts in. Solo does not opt your work content into that training. OpenAI API data controls.
  • OpenRouter: Our agent and draft-generation requests explicitly deny routing to providers that collect data for training. OpenRouter documents prompt retention as opt-in and provides separate controls for downstream providers. OpenRouter data policy and provider routing controls.
  • TypeSafe: When enabled, Jev processes limited context to help agents make decisions. TypeSafe states that it does not train or fine-tune models on prompts and other inputs. TypeSafe privacy policy.
  • xAI: Where used for voice, its API policy excludes training on inputs and outputs without explicit permission. Solo does not grant that permission for your work content. xAI API security policy.

No training does not mean no storage

Solo stores business records and context to operate your workspace. API providers may retain content for service operation, security, abuse monitoring, or legal obligations. For example, OpenAI documents default abuse-monitoring retention of up to 30 days, with exceptions. We do not promise universal zero retention. Feature-specific storage and deletion rules still apply.

Apps, websites, and services you choose to connect or send information to have their own policies. Your agents share information with those services only as part of the work you authorize. Business context is separate from your personal AI account; you decide what information to bring into Solo. To ask about providers, export, or deletion, contact privacy@solomail.co.

3C. Google Calendar Data

Connecting Google Calendar lets Solo identify your connected Google account, list calendars, check availability, and read calendar events. With write access, Solo can create, update, and delete events as part of the scheduling work you authorize. Calendar access does not grant access to your Gmail inbox or Google Drive.

Calendar data can include calendar identifiers, event titles and descriptions, dates, times, locations, attendees, meeting links, and event status. Solo stores synchronized event records and connection information to display your calendar, keep it synchronized, and perform your scheduling workflows. OAuth credentials are encrypted in storage. Calendar information used by an agent may be included in the context processed by the AI providers described above and in the resulting workspace records. The work-data and no-training terms in section 3B apply to this data.

You can remove Solo's Google access in your Google Account's third-party connections settings. Revoking access prevents further authorized access to Google; it does not automatically delete calendar data already stored in Solo, conversation records, or events in Google Calendar. To request deletion of stored Calendar data, contact privacy@solomail.co. Retention of related workspace records and backups is subject to the storage and deletion provisions of this policy.

3D. Connected Gmail Mailboxes

A Gmail mailbox you connect is separate from your Solo identity inbox. Connecting Gmail does not automatically synchronize its messages into Solo or treat incoming Gmail messages as instructions from the identity owner. An owner must explicitly enable the connection for an agent. Read access supports bounded searches and message retrieval requested through an authenticated owner conversation.

Retrieved data can include message and thread identifiers, sender and recipient display headers, subjects, dates, snippets, bounded plain-text message content, and attachment names and types. The message-reading feature does not retrieve attachment contents. Solo uses this data to answer the authorized request; email content itself does not authorize further actions. Read-only permission does not allow Solo to send messages or change your mailbox. Any separately available write feature requires the corresponding Google permission and additional owner authorization.

Solo stores connection information and encrypted OAuth credentials. Retrieved information may be processed by the AI service providers described in section 3B and retained in conversation, execution, and resulting workspace records needed to perform and explain your requested work. The no-training and provider-retention disclosures in that section apply to Gmail data too. Connecting a mailbox does not create a continuously synchronized copy of it.

Disable an agent's Gmail switch to stop that agent from using the connection. You can also revoke Solo's access in your Google Account's third-party connections settings. Revocation stops future authorized Google access; it does not automatically erase information already included in Solo records or delete messages in Gmail. Contact privacy@solomail.co to request deletion of stored Gmail-derived data. Related records and backups remain subject to this policy's storage and deletion provisions.

4. Data Storage and Security

We implement industry-standard security measures to protect your data:

  • Encryption in transit (TLS/SSL) and at rest
  • Secure database hosting with regular backups
  • Access controls and authentication systems
  • Regular security audits and updates
  • Secure third-party service providers (Supabase, Redis, PostgreSQL)

Your communications — including emails, chat messages, SMS messages, and voice call data — are processed by AI agents and stored as necessary to provide our services. Communication data is retained for the duration of your account and for a reasonable period thereafter, or as required by law. You may request deletion of your communication data at any time by contacting us at privacy@solomail.co.

5. Data Sharing and Disclosure

We may share your information with:

  • Service Providers: Stripe (payments), Mailgun (email delivery), Clerk (authentication), Supabase (storage), Twilio (SMS, voice, and phone number services)
  • AI Processing: Your email, chat, SMS, and voice content may be processed by AI models to power agent functionality
  • Communications Providers: Twilio processes your phone number, SMS messages, and voice call data on our behalf to facilitate messaging and calling features. Twilio's use of your data is governed by Twilio's Privacy Policy.
  • Legal Requirements: When required by law, court order, or government request
  • Business Transfers: In connection with a merger, acquisition, or sale of assets
  • With Your Consent: When you explicitly authorize us to share your information

We do not sell, rent, or share your personal information with third parties for their marketing purposes. Your communication data (emails, chats, SMS messages, call recordings) is never shared with third parties for advertising or marketing. Information is only shared with the service providers listed above to the extent necessary to deliver our services to you.

No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with any third parties.

6. Your Privacy Rights

You have the right to:

  • Access: Request a copy of your personal data
  • Correction: Update or correct inaccurate information
  • Deletion: Request deletion of your account and data
  • Export: Download your data in a portable format
  • Opt-out: Unsubscribe from marketing communications
  • Object: Object to certain processing of your data

To exercise these rights, contact us at privacy@solomail.co.

6.1 Voice, SMS, and Accounting Records

We use communication metadata and usage records to display history, calculate credits, reconcile provider costs, investigate errors, prevent abuse, and resolve billing disputes. Call-history access is restricted to the authorized identity owner. The history view does not include raw recordings, transcripts, authentication codes, or provider credentials.

Voice media and message content are processed by the communications and AI providers needed to deliver the features you use. Live audio processing, transcription, and storage of an audio recording are distinct activities; using voice does not mean every call is stored as an audio file. Required notices and consents apply to the selected features and participants. You are responsible for obtaining required permissions when communicating with others through your identity.

Mobile opt-in information and consent records are not sold or shared with third parties for their marketing or promotional purposes. Service providers may process this information only as needed to operate messaging, honor preferences, and meet applicable obligations.

We retain communication and consent records as needed to provide the service, honor opt-outs, address security issues, and satisfy legal obligations. Limited accounting and settlement records may be retained after communication content is deleted to support billing, audit, and dispute resolution. Contact privacy@solomail.co to request access, correction, or deletion, subject to applicable retention requirements.

7. Analytics, personalization, and advertising

On solomail.io and solowork.app, optional analytics, personalization, and advertising measurement are off until you choose. Accept all enables all three. Accept essential and Reject all disable all optional collection; authentication, security, billing, and storage needed to deliver requested features still work. Customize choices lets you change each purpose independently. Privacy choices is available in the footer and in the guest experience, or under Account → Privacy in your workspace.

What analytics collect

With analytics enabled, PostHog receives public page views and generalized product screen names, business-category selections, calls to action, chats started and messages sent (counts, not their contents), agents added, model choices, onboarding steps, owner responses submitted, integration connections, work completion or failure, and completed checkout amounts. Events include time, website, production or development environment, browser and device metadata, random browser and session identifiers, and a broad acquisition category such as direct, Google, or LinkedIn. We do not send raw referral URLs, URL queries, or fragments.

When you sign in and enable analytics, activity is associated with your internal account ID. Profile fields are limited to your plan, signup date, onboarding status, and number of business identities. Optional onboarding answers describe your business category, stage, and primary goal; with analytics consent we use these structured categories to understand which customers Solo serves. Business activity may include an internal business identity ID, allowing us to distinguish multiple businesses owned by one account. PostHog can connect earlier consented anonymous events to your account. We use this information to understand acquisition, onboarding, feature adoption, retention, work reliability, and conversion.

We do not send names, email addresses, chat or message text, documents, contacts, passwords, payment credentials, or free-form input. Automatic interaction capture, session replay, and automatic advertising form matching are disabled. With analytics consent, PostHog uses the connecting IP address to estimate country, region, and city, then discards the IP before storing the event. This is approximate network location, not GPS, and may reflect a VPN. We do not infer age, income, employer, or other personal demographics. Business answers also help your agents understand your priorities independently of analytics permission.

Advertising measurement

With Advertising measurement enabled, the X Pixel measures visits, successful guest activation, new account creation, and confirmed payments on solomail.io and solowork.app. X receives browser and device information, IP/network information, ad click identifiers, normalized page categories, conversion identifiers, and payment value and currency. Our server also sends verified account creation and payment events to X’s Conversions API with the same conversion identifier, the ad click ID when available, and a SHA-256 hash of your trimmed, lowercase email address for matching. We do not send the raw email, names, phone numbers, conversations, or documents, and automatic form matching stays off. X may associate these events with an X account under its own privacy policy.

Advertising measurement is separate from PostHog analytics. Prior analytics consent does not enable X tracking. Accept essential and Reject all disable analytics and advertising, including server-side advertising requests. Essential security and billing records remain necessary to operate your account. You can withdraw advertising consent in Privacy choices; this stops further pixel requests and clears our first-party advertising storage. Previously received events remain subject to X’s retention and privacy controls. We retain consented ad click and campaign identifiers in this browser and our server record for up to 30 days and carry them through our secure cross-domain handoff. Conversion matching data is removed within 30 days; minimal conversion identifiers and delivery status remain to prevent duplicate reporting. Withdrawal suppresses unsent conversions and removes matching data from our records. When you also allow analytics, campaign and creative labels appear in PostHog reports; the X click identifier is not sent to PostHog. See X’s privacy policy.

Personalized content

With personalization enabled, selected business categories and visits to our professional services, agencies, and home services pages tailor business examples, offers, and agent stories. An explicit selection takes priority. We remember the category and its source, not a browsing history, for up to 180 days. Without permission you can still select content for the current visit. We do not use private workspace content to personalize marketing.

Choices, storage, and withdrawal

Your choice is stored for up to 180 days. Analytics uses a separate first-party identifier cookie and tab storage. When you follow supported links between our two sites, a single-use transfer token carries your choice and, if analytics is enabled, a random anonymous identifier. It expires after two minutes. A newer choice at the destination takes priority; if transfer is unavailable, that site asks separately. We do not link unrelated sites or devices through fingerprinting.

For signed-in accounts, we also record analytics permission to govern background work and payment outcome events. A newer withdrawal takes priority over older choices. Withdrawing stops new optional collection and clears this browser’s analytics identifiers; disabling personalization removes its stored category. Already received events are not automatically deleted. Contact privacy@solomail.co for access or deletion. Browser Global Privacy Control or Do Not Track keeps optional browser collection off. Existing operational records needed to run the service are separate.

PostHog stores analytics in the United States, with retention of up to one year under our current plan. Read PostHog’s privacy policy and our cookie policy. Expanding these purposes requires a fresh choice; earlier public-site-only permission does not enable identified portal analytics.

8. Third-Party Services

Our service integrates with third-party services that have their own privacy policies:

  • Clerk: Authentication and user management
  • Stripe: Payment processing
  • Mailgun: Email delivery
  • Twilio: SMS messaging, voice calls, and phone number provisioning. When you use SMS or voice features, your phone number and communication data are transmitted to and processed by Twilio. See Twilio's Privacy Policy and Acceptable Use Policy.
  • Supabase: File storage

We encourage you to review the privacy policies of these third-party services. Each provider processes your data only as necessary to deliver the specific service functionality and is contractually prohibited from using your data for their own marketing purposes.

9. Children's Privacy

Our service is not intended for users under 13 years of age. We do not knowingly collect personal information from children under 13. If you believe we have collected information from a child under 13, please contact us immediately.

10. International Data Transfers

Your information may be transferred to and processed in countries other than your country of residence. These countries may have different data protection laws. We ensure appropriate safeguards are in place to protect your information.

11. Changes to This Policy

We may update this privacy policy from time to time. We will notify you of significant changes by posting the new policy on this page and updating the "Last updated" date. We encourage you to review this policy periodically.

12. Contact Us

If you have questions about this privacy policy or our privacy practices, please contact us:

  • Email: privacy@solomail.co
  • Support: Available through your dashboard

This privacy policy is effective as of the date listed above and applies to all users of Solo.