Log inGet access
Log in
Get access

Privacy Policy

Version 1.2 · Last updated November 2026

Introduction

Sol Foundry, Inc. (“Sol,” “we,” “us,” or “our”) operates the Sol platform, including the web application at hellosol.app and its supporting services (the “Service”). This Privacy Policy explains how we collect, use, disclose, retain, and protect Personal Data when you use the Service or connect a third-party account to it.

Sol is designed to help users identify commitments and other work in connected accounts, prepare work for review, and take actions only when the user authorizes them. This Policy applies to our processing as a business for our own users. Where Sol processes Customer Data on behalf of an organization, the applicable Data Processing Agreement (“DPA”) governs to the extent it conflicts with this Policy.

At a glance

What mattersOur disclosure
Connected-account contentSol may process email and message threads, calendar details, file metadata and content, and chat messages from the accounts a user authorizes.
AI processingFor a request, Sol may send relevant thread/message content, text extracted from attachments, calendar details, and assistant conversation content to its AI providers. Original attachment files are not sent through the automatic processing pipeline.
Your approvalThe Service may prepare an action, but actions that send, post, share, delete, or invite others require a user’s confirmation in the Service.
DeletionDeletion is handled through a verified request. The in-app flow only submits the request, and we verify it with you by email before acting. Once verified, we remove synced content and derived data from Sol’s production systems. Some analytics and trace data is not automatically deleted and is removed through the same verified request process described below.
Where data is processedSol hosts Customer Data in AWS US East (N. Virginia), and its listed subprocessors process Customer Data in the United States.

1. Personal Data we collect

1.1 Information you provide and account information

CategoryExamplesWhy we use it
Identity and account dataName, email address, profile image, account identifiers, account settings and preferences.To create and secure your account, authenticate you, and provide the Service.
Assistant conversationsMessages you send to the assistant and information retained to personalize responses.To answer your requests and provide continuity in the Service.
Support and communicationsQuestions, feedback, and correspondence you send us.To respond to you, troubleshoot, and improve support.

1.2 Connected-account content

When you authorize a Connected Account, Sol processes the content needed to provide the Service. Depending on the connection and the action you ask the Service to perform, this may include:

  • Email messages and threads, including subject lines, message bodies, and participants;
  • Text extracted from attachments;
  • Calendar events;
  • File metadata and file content;
  • Chat messages from connected services; and
  • Names, email addresses, and publicly available professional information about individuals referenced in that content.

Sol does not intentionally collect special categories of Personal Data as a distinct category. Such information may be included in Connected Account content a user chooses to connect; when that occurs, Sol processes it with the protections described in this Policy and the DPA.

1.3 Content generated through use of the Service

CategoryExamplesWhy we use it
Work and contextLoops, topics, summaries, contact context, and daily briefs generated from connected-account content.To organize work and display the context behind it.
Generated contentDraft replies, research, documents, proposed times, and other work prepared for review.To perform the requested task and retain the user’s review history.
Search dataText embeddings of content used for search and retrieval.To allow users to find relevant work and context.

1.4 Usage, technical, and analytics data

We collect product usage events, account identifiers, session recordings of the web application with text and inputs masked, browser and device information, application and API logs, request and error logs, and performance metrics. These records support service delivery, security, troubleshooting, performance monitoring, and product analytics.

2. How we use Personal Data

We use Personal Data to:

  • Provide the Service, including connecting accounts a user authorizes, identifying work, preparing outputs, and carrying out user-confirmed actions.
  • Maintain, secure, monitor, troubleshoot, and support the Service.
  • Measure and improve the performance and quality of the Service.
  • Communicate with users about the Service, support requests, security matters, and other service-related information.
  • Comply with applicable law and enforce our agreements.

We do not sell Personal Data, use it for advertising, or use Customer Data to train AI models.

3. Connected accounts, permissions, and user controls

3.1 Google Workspace

Sol connects to Google through a single Google Workspace connection brokered by Composio, our integration provider. The Google consent screen describes the permissions requested. The current connection requests the following scopes:

AreaScope(s)Use
Identityuserinfo.email; userinfo.profileIdentify the account and confirm the connected mailbox matches the signed-in user.
Gmailgmail.readonly; gmail.modify; gmail.sendRead email threads and attachments; apply labels, save drafts, and move messages to trash; send, reply, or forward only after the user approves the action.
Contactscontacts.readonly; contacts.other.readonly; profile.emails.readResolve names and email addresses.
CalendarcalendarRead schedules and create or update events at a user’s request. Events that invite other people require approval.
DrivedriveFind and read referenced files, save files to a Sol folder, and make sharing changes only after approval.

These Google scopes are currently granted as one set. Drive is bundled with Gmail and Calendar and cannot be declined individually. If a user declines a requested scope, Sol does not complete the connection, removes the partial grant, and asks the user to reconnect. A user may revoke access in the Google Account settings or within Sol.

Limited Use of Google user data

Sol’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

  • We use Google user data only to provide and improve user-facing features of the Service that a user requests.
  • We do not transfer Google user data to others except to provide or improve those features, to comply with applicable law, or as part of a merger, acquisition, or sale of assets with notice to users. Subprocessors listed in Section 5 receive it only for these purposes.
  • We do not use Google user data for serving advertisements, including retargeting or interest-based advertising.
  • We do not allow humans to read Google user data unless we have the user’s affirmative consent for specific content, it is necessary for security purposes such as investigating abuse, it is necessary to comply with applicable law, or the data is aggregated and anonymized for internal operations. Any such access is role-based and recorded in an audit log.
  • We do not use Google user data to develop, improve, or train generalized AI models.

3.2 Slack

Slack is a separate, optional connection. A user can decline it without affecting Google-based functionality. If connected, Sol requests the following Slack permissions to provide user-requested functionality:

FunctionScope(s)
Channelschannels:history; channels:read; channels:write
Private channelsgroups:history; groups:read; groups:write
Direct messagesim:history; im:read; im:write
Group direct messagesmpim:history; mpim:read; mpim:write
Messagingchat:write
Filesfiles:read; files:write; remote_files:read; remote_files:share
Reactions, pins, and starsreactions:read; reactions:write; pins:read; pins:write; stars:read; stars:write
Callscalls:read; calls:write
Do Not Disturb and remindersdnd:read; dnd:write; reminders:read; reminders:write
Search and linkssearch:read; links:read; links:write
Users and groupsusers:read; users:read.email; users:write; users.profile:read; users.profile:write; team:read; usergroups:read; usergroups:write
Emojiemoji:read

3.3 Approval controls

Actions that reach other people, delete data, or change sharing require the signed-in account owner’s approval in the Service. This includes sending, replying to, or forwarding email; sharing files or changing Drive permissions; deleting messages or events; and sending calendar invitations. The Service stores the proposed recipient, content, file, or permission as a pending approval and executes it only as approved, including any edits the user makes. The Service does not permit the AI to approve or amend an action after the user approves it, and each approval executes at most once.

4. AI processing and content handling

4.1 How AI is used

Sol uses AI providers to identify work items, summarize threads, prepare drafts, generate the daily brief, and respond to user requests. For a particular request, the data sent may include relevant email and message thread content, text extracted from attachments, calendar details, and the user’s conversation with the assistant. Sol also generates text embeddings for search and retrieval.

4.2 What happens to attachments

Email and other connected-app attachments, including PDFs, documents, and images, are processed by an internal extraction service before content is sent to an AI provider. In the automatic processing pipeline, Sol sends extracted text and does not send the original attachment file to an AI provider.

There is one limited exception: when a user explicitly asks Sol in an interactive session to view an image (for example, a screenshot), Sol may send that image to a vision-capable model within applicable size and resolution limits. This exception requires the user’s request in that session and is not part of automatic email processing.

4.3 Training and provider retention

Sol does not use Customer Data to train AI models, and Sol’s AI subprocessors do not use Customer Data to train their models. Sol’s OpenAI account is configured for zero data retention, so OpenAI does not retain prompts or outputs after returning a response. Amazon Bedrock does not store or log prompts or outputs. In Sol’s work-item extraction pipeline, email addresses are replaced with placeholders before content is sent to the AI provider and restored within Sol’s environment.

4.4 Prompt injection and unauthorized instructions

Content from inbound email and web pages is treated as information, not as authorization to act. HTML email is converted to plain text and scripts and styles are removed before the AI sees it. The pipeline that reads inbound email to detect follow-ups can only read the thread and record what it finds; it cannot send, share, delete, or change connected accounts. User confirmation requirements continue to apply to actions in connected applications.

5. How we disclose Personal Data

We disclose Personal Data to service providers that help us provide, secure, support, monitor, and improve the Service. The following are our current subprocessors and the categories of Customer Data they may process:

SubprocessorPurposeCustomer Data processed
Amazon Web Services, Inc.Cloud hosting, databases, storage, queues, and AI model inference through Amazon Bedrock.All Customer Data.
Google LLC (Firebase Authentication)Customer sign-in.Name, email address, and authentication identifiers.
Composio, Inc.Connection to Connected Accounts and execution of API calls.Connected Account content in transit and OAuth tokens.
OpenAI, L.L.C.AI model inference.Thread and message content, text extracted from attachments, and assistant conversations.
Temporal Technologies, Inc. (Temporal Cloud)Background workflow orchestration.Workflow inputs and outputs, which can include account identifiers and content.
Voyage AIText embeddings for search.Text of synced messages and contacts.
Turbopuffer, Inc.Vector search database.Text embeddings and associated text.
LangChain, Inc. (LangSmith)AI request tracing for debugging and quality evaluation.AI prompts and responses, which may include Customer Data.
Snowflake Inc.Analytics data warehouse.Replicated Service data and usage events.
Exa Labs, Inc.Web and people search at a user’s request.Search queries, such as names and company names.
Browserbase, Inc.Hosted browser used at a user’s request.Web pages a user asks the assistant to visit.
Mixpanel, Inc.Product analytics.Usage events, account identifiers, and session recordings of the web application.
Mailgun Technologies, Inc.Delivery of Service email, including the daily brief.Recipient address and email content.
Resend, Inc.Delivery of transactional email.Recipient address and email content.
SigNoz, Inc.Application performance monitoring.Application traces, metrics, and logs, which may include account identifiers.
Functional Software, Inc. (Sentry)Error tracking.Error reports and stack traces.
HetrixToolsExternal uptime monitoring.Health check endpoint URL and response status only; no Customer Data.
Slack Technologies, LLCInternal routing of product feedback.Text of feedback submitted by users.

We require subprocessors to process Personal Data under data-protection terms consistent with our DPA. We do not sell, rent, or trade Personal Data. The current subprocessor list is maintained through the Sol Trust Center at https://trust.hellosol.app.

6. Retention and deletion

We retain Personal Data only for the periods described below, or longer where necessary to meet legal obligations, establish or defend legal claims, prevent fraud or abuse, or maintain security. Retention may differ by system because certain operational, analytics, and tracing systems serve distinct purposes.

System or data categoryRetentionAccount deletion treatment
Aurora PostgreSQL production database (AWS us-east-1)Life of the account for account data, synced content, and generated items. Automated backups expire within 30 days.Data is removed from active systems through the verified data-subject request process.
Snowflake analytics warehouseRetained for internal analytics; there is no automated purge today.Not removed automatically today. Removed on request through the verified data-subject request process.
LangSmith AI request tracing14 days in LangSmith. An exported copy is retained in Sol’s encrypted S3 for up to approximately 120 days.Traces expire automatically under the above schedule; they are not deleted immediately on account deletion.
Mixpanel product analytics2 years (approximately 730 days) in Mixpanel. An exported copy is retained in Sol’s S3 for up to 3 years.Not removed automatically today. Removed on request through the verified data-subject request process.
Short-term processing cacheUp to 30 days.Expires automatically.
Integration request logs60 days.Expires under the applicable retention period.
Application, API Gateway, load balancer, CDN, and VPC Flow Logs365 days.Expires under the applicable retention period.
Error reports90 days.Expires automatically.

6.1 Account deletion and connected-account disconnection

Account deletion is handled through a verified request. A user can submit a request from within the Service, which only raises the request, or by contacting us at the address below. We verify every request through correspondence with the user before acting on it. Once verified, account deletion removes synced content and derived data from Sol’s production systems, including work items, transcripts, contacts, drafts, assistant conversations and memory, search embeddings, attachments, integration connections held by Composio, and the account record and sign-in identity. The ancillary analytics and tracing records described above follow their stated retention or verified deletion process.

When a user disconnects a Connected Account, Sol revokes access and stops collecting new data from that account. Data already synced from the account is retained so the user can reconnect without re-syncing and is deleted on account deletion, subject to the separate retention practices described in this section.

7. Security

We use administrative, technical, and organizational safeguards designed to protect Personal Data. These include encryption at rest and in transit; role-based access controls; user-scoped data access; multi-factor authentication for administrative access; network segmentation; security logging and monitoring; vulnerability management; incident-response procedures; and resilience controls, including multi-AZ Aurora deployment, automated backups, and point-in-time recovery.

Access to customer account information and AI request traces is role-based, time-boxed where appropriate, and recorded in an audit log. We maintain documented incident-management, business-continuity, and disaster-recovery policies. If a Personal Data Breach affects Customer Data, we notify the relevant customer without undue delay and no later than 72 hours after becoming aware of the breach, as described in our DPA. Individual notifications are provided where required by applicable law.

8. International transfers

Customer Data is hosted in the United States in Amazon Web Services’ US East (N. Virginia) region. The subprocessors listed in this Policy process Customer Data in the United States. If you access the Service from outside the United States, your Personal Data may be transferred to and processed in the United States.

For transfers from the EEA or UK, Sol uses the EU Standard Contractual Clauses and the UK International Data Transfer Addendum where applicable. For onward transfers, Sol relies on a subprocessor’s EU–U.S. Data Privacy Framework certification (and UK extension) where applicable, or on Standard Contractual Clauses. For transfers from India and other jurisdictions, Sol applies the safeguards required by applicable law. You may request information about applicable transfer safeguards by contacting us.

9. Legal bases for EEA, UK, and Swiss users

Where the EU GDPR, UK GDPR, or similar laws apply, we process Personal Data on the following legal bases:

PurposeLegal basis
Providing the Service, including account management, integrations, and service communications.Performance of a contract.
Security monitoring, fraud prevention, and protecting the Service.Legitimate interests.
Service improvement and product analytics.Legitimate interests.
Meeting legal and regulatory requirements.Legal obligation.

Where we rely on legitimate interests, we seek to balance those interests against the rights and freedoms of affected individuals. You may object to processing based on legitimate interests by contacting us.

10. Cookies and product analytics

We use technologies required to authenticate users, maintain sessions, secure the Service, and remember preferences. We also use product analytics and session recordings as described in Sections 1.4 and 5. We do not sell Personal Data or use it for cross-context behavioral advertising. Where applicable law requires consent for non-essential cookies or similar technologies, we will provide the required notice and choice.

11. Your rights and choices

Depending on your location and applicable law, you may have the right to request access to, correction of, deletion of, restriction of, objection to, or portability of your Personal Data. You may also withdraw consent where processing is based on consent and lodge a complaint with a relevant supervisory authority.

To make a request, contact us at support@hellosol.app. We may need to verify your identity before acting on the request. We respond within the time required by applicable law. For information held in analytics or tracing systems that is not automatically removed on account deletion, please make a verified deletion request so we can process it through the applicable data-subject request workflow. Deletion requests raised in the Service are verified with you by email before we act on them.

California residents may have additional rights under the CCPA/CPRA, including rights to know, delete, correct, and limit certain uses of sensitive Personal Information. Sol does not sell Personal Information or share Personal Information for cross-context behavioral advertising.

12. Children's privacy

The Service is not directed to anyone under 18. We do not knowingly collect Personal Data from children. If we learn that we have collected Personal Data from a child, we will take appropriate steps to delete it.

13. Changes to this Policy

We may update this Privacy Policy to reflect changes in our practices, technology, legal requirements, or the Service. When we make material changes, we will update the “Last updated” date and provide advance notice where required by applicable law. We encourage users to review this Policy periodically.

14. Contact us

Questions, privacy requests, and concerns may be sent to:

Sol Foundry, Inc.
Privacy inquiries: support@hellosol.app
Trust Center: https://trust.hellosol.app
Incorporated in Delaware, United States

SolSol

Sol finds everything you said you’d do, and gets them started for you.

Sol by Sol Foundry Inc.

© 2026 Sol Foundry Inc. — All rights reserved

Social

XInstagramLinkedInWrite to us

Legal

Trust CenterPrivacy PolicyTerms of Service