Privacy Policy

Salsa (“we,” “us,” or “our”) provides the Salsa websites, desktop and mobile applications, cloud workspaces, AI assistants, agent tools, and related communications (the “Service”). This policy describes the personal information we process, why we process it, who receives it, and the choices available to you. It covers salsas.app and Salsa services that link to this policy, including cloud.salsas.io.

We act as controller when we determine how to process account, billing, support, security, and website information. When we process workspace content on behalf of a business customer under its instructions, the customer is responsible for that processing and our customer agreement, including any applicable data processing agreement, governs our role. Direct requests concerning an employer-managed workspace to that organization; you may also contact us for help identifying the appropriate contact. This policy does not govern employment or job applications.

Local features can process and store information on your device. Cloud workspaces, synchronization, collaboration, connected services, hosted agents, and cloud AI or voice features involve processing outside your device. The location of processing depends on the feature, runtime, provider, and settings you use; installing a desktop app does not make every operation local.

This notice describes processing; it does not replace permission prompts or create consent where a separate affirmative choice is required. Our Terms of Service describe use of the Service and authorization of agent actions.

The information processed depends on what you provide, connect, authorize, or use. You may decline optional access; features that need that access may then be unavailable.

• Account and contact information: name, email address, profile image, account and organization identifiers, sign-in information, preferences, membership, and support correspondence. Sign-in providers can supply profile information and authentication identifiers. The public waitlist and native account age check calculate eligibility on your device from birth month/year; that entered value is not sent or retained by Salsa. We receive the eligibility confirmation and, for the public waitlist, its confirmation time.
• Workspace and assistant content: prompts, chats, messages, issues, plans, notes, documents, code, uploaded files, attachments, images, instructions, generated outputs, feedback, and content you share with other people or agents. We also process indexes, embeddings, summaries, references, and preferences derived from that content to retrieve relevant information and maintain context.
• Connected accounts: information made available through integrations you enable, such as email bodies, subjects, attachments, senders and recipients, message dates and threads, calendar events, contacts, files and their permissions, repository content, and collaboration messages. Access depends on the provider and permissions granted. OAuth authorization tokens, integration identifiers, and credentials you configure enable this access. Connect employer or third-party accounts only with the necessary authority.
• Agent activity: tool requests and results, approvals, execution history, task status, usage and cost records, and information sent to or received from services an agent uses for your task. A browser, computer-control, or file-access feature can process the screens, pages, files, or commands you make available to it.
• Voice, calls, and recordings: microphone audio, transcripts, generated speech, and, when enabled, camera or screen content, meeting recordings, participant details, and related summaries. Section 4 explains these features.
• Billing and transactions: plan, subscription, purchase, usage, invoice, payment-status, and billing-contact information. Payment processors collect payment credentials through their checkout; Salsa receives the information needed to administer the transaction. A task you authorize may also involve transaction information sent to an outside merchant.
• Device, usage, and security information: IP address, browser and operating-system information, device category, approximate location inferred from network data, timestamps, pages and features used, referrers and campaign parameters, clicks and scroll events, session identifiers where enabled, diagnostics, errors, and security logs. Website measurement and storage controls are described in Section 5.
• Other people and sources: invitations, shared workspaces, messages and documents may contain information about other people. We can receive information from workspace members, connected providers, customer administrators, and public pages or sources retrieved for a task. Provide others' information only when you have the necessary rights, notices, and permissions.

Sensitive information. Communications and connected files can contain confidential information or data about health, finances, beliefs, identity, or other sensitive matters even if we do not ask for it. Share only what is needed and lawful for the task. Merely uploading information does not establish a legal basis for every use of sensitive data. We use sensitive information to provide requested features, maintain security, and meet legal obligations, subject to applicable restrictions; this policy does not authorize unrelated sensitive-data advertising or profiling.

We use personal information to operate accounts and workspaces; connect authorized services; retrieve and summarize information; generate responses, code, and other outputs; plan and perform authorized tasks; collaborate; process subscriptions and usage; respond to support; maintain context and preferences; diagnose errors; measure and improve reliability and usability; prevent abuse; and comply with legal obligations. We send service notices, and marketing messages when you have opted in. You may unsubscribe from marketing without losing essential account or security notices.

AI inference, personalization, and training

AI features may send prompts, relevant workspace or connected content, tool results, attachments, and conversation context to a model running locally or to a cloud provider. Cloud services can include OpenRouter and the model providers it routes to, as well as providers configured directly by you or your organization. Generating an answer or retrieving saved context is different from training model weights.

We do not use your private User Content to train our AI models by default. Optional training participation requires an affirmative opt-in through the Data settings where available; you can turn it off for future participation. Participation is subject to your authority over the data, applicable customer agreements, and source-provider restrictions. An individual setting cannot override an organization's agreement or another person's rights. Disabling participation does not disable processing needed to answer your requests, maintain your saved context, or secure the Service.

Provider retention and use depend on the selected service, account, and applicable terms. Salsa's training preference is not a control for a separate provider account. For a provider or API key you configure, review its privacy and training settings before sending confidential information. We do not promise that every provider has zero retention. Restricted connected-service data remains subject to the restrictions below regardless of model choice or training preferences.

Google API data and Limited Use

When you connect Google, the permissions shown during authorization determine which Google services and data are available. Google sign-in alone does not grant access to your Gmail or Drive content. We use information received from Google APIs to deliver the user-facing features you request, such as finding information, summarizing communications, or taking an authorized action.

Salsa's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements, and the Google Workspace API User Data and Developer Policy where applicable. These restrictions also apply to data derived from that information:

• We do not sell Google user data, use it for advertising or creditworthiness/lending decisions, or use it to train, fine-tune, or improve general-purpose AI models. Optional Salsa training participation does not authorize those uses.
• Transfers are limited to providing or improving appropriate, prominent user-facing features with the required consent; security; applicable legal requirements; or a merger, acquisition, or asset sale with explicit prior user consent where Google's policy requires it. General sharing provisions elsewhere in this policy do not expand these permissions.
• Human access is limited to documented affirmative agreement to view specific data, necessary security or legal purposes, or aggregated and anonymized information used for internal operations as permitted by Google's policy.
• AI and other providers processing Google data on our behalf may process it only for the permitted service purposes and permitted security/legal needs, not for their own general-purpose model training or unrelated secondary uses.

You can disconnect Google in the integration controls or revoke access through your Google Account connections. Revocation stops future authorized access through that connection; request deletion of previously imported information separately as described in Sections 7 and 8.

Legal bases where required

We may use aggregate or deidentified information to understand service performance and develop features. We maintain deidentified information in that form and do not attempt reidentification except to test deidentification as legally permitted. Deidentification does not remove applicable Google data-use restrictions. New incompatible purposes require an appropriate legal basis and additional notice or consent where required.

The optional website voice and chat assistant is powered by Onzoe. Enabling it loads Onzoe's service and can transmit your messages, microphone audio when activated, transcripts, and interaction information for speech recognition, responses, and speech synthesis. The website's functional preference controls loading this feature; browser microphone permission controls microphone access. Opening chat is not permission to record a meeting.

In-app voice, In-View calls, screen sharing, and recording are separate features. Depending on the feature and provider you select, audio and other media can be processed locally or remotely. Saved recordings, transcripts, summaries, and files can remain in your device or workspace until removed under its controls and retention arrangements. Transient voice processing is not a promise that every recording or transcript is immediately deleted.

Activate capture and sharing only with appropriate permissions. Participants and people shown in shared material may have privacy and recording rights; provide notice and obtain required consent before recording or sharing. You can stop capture or revoke microphone, camera, screen, and related permissions through the app or operating system. That does not recall media already shared or automatically delete saved recordings.

We use cookies and browser or device storage for sign-in, security, preferences, consent choices, and enabled features. Authenticated Salsa services can use session cookies even though public marketing pages use browser storage for their preferences. Blocking essential storage can prevent sign-in or break features.

Before an analytics choice, the public site uses first-party cookieless measurement with identifiers held only in page memory, not persistent visitor storage. It can send the current URL, referrer, campaign information, page and click/scroll/submit events, timestamps, and coarse device/geographic information. Cookieless does not mean that requests contain no personal information: network requests include an IP address, and URLs can contain information you put in them. If you accept analytics, first-party identifiers enable returning-visitor and session measurement.

Use Cookie Settings in the footer to reject analytics or change your analytics and functional choices. Rejecting analytics stops this site's analytics transmission, including cookieless events. The public-site analytics code also stops transmission when your browser sends Global Privacy Control (GPC) or Do Not Track (DNT). These controls do not disable operational security logs, requested features, or your organization's workspace records. You can also remove stored identifiers in your browser settings.

Salsa Analytics does not use session replay: it does not record keystrokes, form-field values, passwords, DOM snapshots, or video-like replays. Click measurement can include the label and destination of the element clicked. Website fonts are self-hosted. We do not sell personal information or share it for cross-context behavioral advertising. Public sponsorships or affiliate links may generate aggregate campaign reporting or referral compensation; private workspace content is not an advertising product. Information you deliberately submit to a sponsor or outside site is subject to that recipient's notice.

We disclose information as needed for the purposes above, with the following recipients. Google API data is additionally limited by Section 3.

• Service providers: hosting and infrastructure providers (including Google Cloud and DigitalOcean where used), model and inference services, Onzoe and other selected voice/media providers, payment processors, email delivery, support, and security providers. The data disclosed depends on the function they perform. A model router and its selected model provider can both process the request. We do not represent that all providers retain data for the same duration or under identical terms.
• Workspace participants and administrators: people who can access content according to your sharing choices, workspace roles and the organization's arrangements. Publicly published material may be accessible beyond your workspace. A private conversation and a shared team artifact can have different audiences.
• Recipients of authorized tasks: connected applications, message recipients, websites, merchants, and other parties with whom Salsa interacts under your instructions and permissions. Sending a message, publishing a file, or completing a transaction can disclose information outside Salsa. Such recipients may act as independent controllers and retain their own copies.
• Professional advisers and authorities: legal, accounting and other advisers; authorities or other parties when reasonably necessary to comply with applicable law or valid legal process, investigate abuse, protect security and rights, or establish or defend claims.
• Business transactions: counterparties and advisers in a proposed or completed financing, merger, acquisition, reorganization, or sale, subject to appropriate confidentiality, applicable law, and source-provider restrictions. Any successor's use remains subject to applicable privacy obligations and required notices or consent.
• At your direction: other recipients you choose or specifically authorize.

Third-party sites and services have their own terms and privacy practices. A link or integration does not make their practices part of Salsa's policy. Review the provider and sharing destination before connecting or publishing.

We retain personal information for the period needed for its stated purpose, taking into account your account and customer relationship, the type and sensitivity of information, security and recovery needs, contractual instructions, legal recordkeeping, and the time needed to address disputes. There is no single retention period for all features.

• Accounts, workspace content and saved media: retained to provide the account and requested history or collaboration, subject to applicable deletion requests and customer arrangements. Device-only copies and backups remain under the device owner's control.
• Connected data: disconnecting or revoking a token stops new access through that connection. It does not automatically erase imported files, messages, summaries, indexes, or outputs already saved. Identify the connection and data in your deletion request so related copies and derived records can be addressed.
• Support, waitlist and contact records: retained to handle your request and necessary follow-up; you may ask to leave the waitlist or delete information through the contacts below.
• Billing, consent and security records: retained where needed for accounting, fraud prevention, demonstrating choices, or legal obligations. Records of marketing opt-outs may be retained so we continue honoring them.
• Backups and audit history: deleting an item from an interface may not immediately remove it from backups or retained audit records. Where an exception justifies retention, access and use are restricted to that purpose. Recovery copies are addressed through the applicable backup lifecycle and deletion process. An immutable audit design does not itself remove your statutory rights.

Contact privacy@salsas.app to request account or data deletion, including imported information, recordings, or derived indexes. We will explain applicable exceptions or limitations and respond within the time required by law. Removing an app does not delete a cloud account, and deleting information in Salsa does not delete independent copies held by another recipient or provider. When information is no longer needed and no valid retention basis remains, we delete it or deidentify it as appropriate and permitted.

You can update available account settings, change sharing permissions, disconnect integrations, revoke provider access, change device permissions, and manage website choices through Cookie Settings. Data export and backup controls are available in supported runtimes; contact us if a needed access, correction, export, or deletion control is not available in your interface. Unsubscribe from marketing using the message's instructions or contact us; essential service notices may continue.

Depending on your location and applicable law, you may request confirmation of processing; access to information and disclosures about its sources, purposes and recipients; correction; deletion; a portable copy; restriction; withdrawal of consent; or objection to processing based on legitimate interests, including direct marketing. Withdrawal does not invalidate processing before withdrawal.

United States

California and other applicable state laws may provide rights to know/access, correct, delete, and obtain a copy of personal information; opt out of sale, sharing, targeted advertising or certain significant profiling; and limit specified uses of sensitive information. We do not sell personal information or share it for cross-context behavioral advertising, including information about minors. We do not use sensitive information for unrelated advertising. See Section 5 for how public-site analytics responds to GPC. This Service is not offered to make legally binding eligibility decisions about you; AI suggestions should not be treated as such decisions.

You may use an authorized agent where applicable. We may verify your identity and the agent's authority using information proportionate to the request. You will not be discriminated against for exercising applicable rights. If we deny a request, we will explain the reason where permitted. You can appeal by replying to the decision or emailing privacy@salsas.app with “Privacy appeal”; we will handle appeals and provide regulator information as required by the applicable state law.

EEA, United Kingdom, Switzerland, and other regions

Applicable European and UK data protection law may provide the access, correction, erasure, portability, restriction, objection and consent-withdrawal rights above. Switzerland's data protection law provides its own applicable rights; it is not governed simply by EU membership rules. You may complain to the competent supervisory authority, including an EEA authority, the UK Information Commissioner's Office, or the Swiss Federal Data Protection and Information Commissioner. Brazilian users may exercise applicable LGPD rights, including confirmation, access, correction, portability, deletion or anonymization where applicable, and consent withdrawal.

Send requests to privacy@salsas.app. We aim to respond within 30 days and will comply with the deadlines, exceptions and extension notices required by your applicable law. We will ask only for verification reasonably necessary to protect your information. For customer-controlled workspace data, we may refer or assist your request with the relevant organization.

Salsa operates from the United States. Cloud infrastructure, model providers and other recipients may process information in the United States or other countries depending on the service and configuration. Those countries may provide different protections from your home jurisdiction; local processing is not a guarantee of data residency for connected or cloud features.

Where applicable law requires a safeguard for an international transfer, we must use an appropriate mechanism, such as an applicable adequacy determination or approved contractual clauses with the required supplementary measures. Contact privacy@salsas.app for information about the mechanism and safeguards applicable to your data.

The Service is not intended for children under 13, or under 16 in the EEA or United Kingdom, and a higher applicable local minimum takes precedence. Eligible users who cannot legally agree to the Terms independently must involve a parent or guardian as required. Connecting an account or completing an age check does not waive these requirements.

We do not knowingly collect information from users below the applicable minimum age. If you believe a child has provided information contrary to these requirements, contact privacy@salsas.app. We will investigate and take the deletion and other steps required by applicable law. The eligibility check described in Section 2 does not send Salsa the birth month/year entered.

We use technical and organizational safeguards designed to protect information, including authenticated access, permission checks, protected credential storage, encrypted network connections, and execution controls appropriate to the feature. Sandboxing and approval controls reduce risk but cannot guarantee that every action or output is correct or that a provider cannot access data it must process. Transport encryption is not a blanket promise of end-to-end encryption against Salsa or AI providers.

Agents can misunderstand instructions, generate incorrect outputs, or encounter malicious instructions embedded in messages, documents or websites. Review permissions, recipients, costs and consequential actions; limit connected access to what is needed; and promptly report suspected unauthorized activity. See the agent authorization terms and security overview. No system guarantees absolute security. We will provide breach notices where required by applicable law.

Last updated October 23, 2026. This revised policy takes effect November 22, 2026. Until then, the previous Privacy Policy remains applicable. This advance notice describes expanded coverage of existing Salsa features and clarifies processing and controls; it does not itself enable new data collection, grant an agent new authority, or opt you into training.

We will update the revision date when this policy changes. For material changes to how we collect, use or share information, we will provide at least 30 days' advance notice by email or a prominent website notice, and obtain fresh consent where required. Continued use is not a substitute for consent where law or a provider's policy requires an affirmative choice. Prior versions remain available through the revision links.

For privacy questions, access, correction, export, deletion or appeals, email privacy@salsas.app. For legal matters, email legal@salsas.app. General support is available at hola@salsas.app.

The canonical policy is salsas.app/privacy. The same notice covers the Salsa website, supported applications and cloud services described above.