Ensemble home

Privacy policy

Effective 13 November 2026. This policy covers the hosted Ensemble service at ensemblework.com, including Ensemble Node and the hosted features used by connected desktop apps and CLIs. If you run a separate self-hosted instance, its operator is responsible for that instance's data practices.

Data we store

We store your account email, name, password hash if you use a password, linked login provider identifiers, session records, the notes, tasks, context and files you choose to save, and for 30 days a log of your AI activity (described below). Login with Google, GitHub or Microsoft requests only identity information; mail and repository connectors require separate authorization.

How data is used

Your data is used to operate your workspace. Verification and reset emails are delivered through Resend. Cloudflare Turnstile processes browser signals to prevent signup abuse. If you use model features, relevant inputs are sent to the model provider you select. Provider usage may incur charges to your own account. We do not sell your personal data or use it for advertising.

Google user data and Limited Use

Ensemble'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. These commitments also apply to information derived from Google user data.

Google data we access and the features it supports

Google sign-in and Google Workspace access are separate authorizations. Signing in does not by itself grant access to your Gmail, Calendar or Drive. When you connect Google Workspace, the products you switch on and the permissions you grant determine what Ensemble can access:

Productivity use, not advertising or general model training

We use Google user data only to provide or improve prominent user-facing productivity features: organizing your tasks, notes, people, files and meetings; showing your schedule; finding or importing information you request; and providing the assistant, summaries, briefs or workflows you use or configure. Connecting Google does not start a wholesale mailbox or Drive import.

We do not sell, rent or trade Google user data, transfer it to advertising platforms or data brokers, use it for advertising or retargeting, or use it to determine creditworthiness or lending eligibility. We do not use Google user data, including derived data, to develop, improve or train generalized or foundational AI or machine-learning models.

Sharing and AI processing

Google data is not public merely because you connect an account. Content you save into a shared space, page, task or conversation becomes available according to the sharing permissions you choose. You can also direct Ensemble to send content to another connected app or to an agent on your paired computer.

When an AI feature uses Google-connected content, relevant message text, file content, calendar information or derived workspace context may be sent to the model provider or AI agent you select to produce the requested result. This includes user-facing summaries, briefs and configured workflows, not only manually typed chat requests. Google connector access and refresh tokens are not included as model context.

Hosted included models are processed through Microsoft Azure AI Foundry. Microsoft's published data-processing terms state that prompts and completions are not used to train base models without permission or instruction; Ensemble does not authorize training on Google user data. Other APIs and AI plans you configure have their own processing, retention and security-monitoring terms. Use only provider accounts and settings compatible with Google's Limited Use requirements, including excluding this data from general model training. No-model-training commitments do not mean that every provider has zero retention, and we do not claim a universal zero-data-retention agreement.

Necessary infrastructure providers process data to deliver the service, including Microsoft Azure for hosted model/file services, Cloudflare for network delivery and abuse protection, Vercel for web hosting, and Resend for account emails. These transfers are limited to the applicable user-facing service and permitted security or legal purposes, not advertising or model training. Processing locations depend on the service and your selected provider configuration; processing is not guaranteed to remain in one country.

Storage and security

Hosted storage includes your Google account/connection identifiers, granted scopes, encrypted OAuth access and refresh tokens, synchronization state, contact metadata you sync, cached calendar events, and the content you choose to attach, import or save. Google-derived content and generated results can also remain in your tasks, pages, files, meeting notes and conversation history, and for 30 days in your AI activity log. Imports are copies in your workspace; disconnecting Google does not automatically erase those copies.

Hosted web connections and Google API connections use HTTPS. Stored OAuth tokens are encrypted at the application layer with AES-256-GCM, and account/space access controls restrict access to workspace records. These measures are not a claim that all content is end-to-end encrypted: the service and selected processors must handle readable content when delivering an authorized feature. The operator has administrative access to the infrastructure.

Human access

We do not routinely read your Google messages or files. Human access to Google user data is limited to your affirmative agreement to access specific data, necessary security purposes such as investigating abuse, compliance with applicable law, or aggregated information used for permitted internal operations consistent with Google's policy. Infrastructure administration does not authorize unrelated reading, advertising use or model training.

Retention, revocation and deletion

Connection information is kept while the connection is in use. Workspace copies and derived content are retained to provide your saved workspace until you remove them or delete your account, subject to the feature's retention and Trash settings. This is separate from the content-free operational records described below.

You can disconnect Google in Settings → Connections. This deletes the stored connector credentials and stops new access through that connection; Ensemble also attempts to revoke the OAuth grant at Google. You can independently revoke access in your Google Account third-party connections. Revocation does not automatically delete files, tasks, notes, contacts or conversations already saved in Ensemble, or delete your Ensemble account.

Delete saved content using its workspace controls or Settings → Data. The Everything erasure removes workspace content but intentionally keeps account authentication and connector configuration; disconnect Google separately if you also want to stop access. Deleting your account in Settings → Data → Danger zone removes active hosted account records and stored Google connection credentials, subject to the active-run checks.

Storage cleanup, recoverable deleted copies, infrastructure backups and provider security logs have separate cleanup or retention periods. Deleting active records does not instantly purge every backup or copy already transferred to a provider, shared recipient or your computer. Backup copies are for service recovery, not continued use of a deleted workspace. We do not promise a universal 30-day or immediate purge across all storage and providers.

Usage analytics

To understand how Ensemble is used and what to improve, we log how signed-in people use the hosted Hub: which screens you open and how long you actively use them (only while the tab is visible and you have used it in the last minute), named actions such as opening the assistant or the command palette, the size of your browser window, and whether you use the web or the desktop app. The server also records actions you take, such as creating a task or uploading a file, and the model calls the Hub makes with their token counts. This log never contains your content: no titles, text, file names or prompts, and identifiers are removed from addresses before they are stored. It is tied to your account, kept on the operator's own server for up to two years, used by the operator to improve the service and shown back to you as your own active time in the Weekly recap, and not sold, shared or used for advertising. It is included in your data export, removed when you delete everything or your account, and is not used by Vercel or any third-party analytics service.

AI activity log

Separately from the usage log above, when you use AI features we keep a log of that work for 30 days so the operator can see how Ensemble served you and improve the features you use. For each request to a model or an AI agent, in chats, Ask Ensemble, routines, summaries, briefs, meeting and document automations, Ensemble Node and agent tasks, it records what was sent (your request, Ensemble's instructions and the context given), what came back, which model, provider, AI plan or computer handled it, how long it took and the tokens it reported. It also records the tools those models and agents used with their inputs and results, including an agent's own commands and file changes on your computer, errors with their technical details, and the warnings and errors the hosted service and your connected computers logged while doing this work.

Before anything is stored, keys, passwords and other known secret formats are removed, pictures and attached files are recorded only by their type and size, and long text is shortened. The log is tied to your account, kept on the operator's own server, deleted automatically after 30 days, included in your data export, and removed when you delete your people and app information, everything, or your account. It is not sold, shared or used for advertising. Google user data in this log is used and accessed only as the Google section above describes.

Security and control

Hosted data is separated by account. Passwords are hashed; saved provider credentials are encrypted at rest. The server decrypts credentials when making authorized provider calls. The service operator has administrative access to hosted infrastructure. Do not store secrets or sensitive regulated data in this early testing service.

You can export account data in Settings → Account and manage workspace exports and deletion in Settings → Data. Exports exclude credential secrets. Account deletion removes active hosted records and revokes devices; it does not remove local files or data already sent to another provider. Infrastructure backups and provider logs may retain records until their normal retention expires.

Deletion logs

After account deletion, we keep a minimal operational log for up to 90 days: a keyed identifier derived from the email, the deletion date and an expiry date. This log contains no readable email, name, profile, workspace content or feedback. It does not prevent signing up again; a repeat deletion replaces the previous log. The identifier is pseudonymous, not anonymous. The log is restricted to the service operator and is not shared externally or sent to a model. To request erasure of the log, use the support email below.

Monthly AI credits

Deleting data does not restore credits already used. To enforce the monthly allowance, we retain a separate keyed identifier derived from the account email, the UTC month and the charged amount, including pending reservations. It contains no readable email, prompts, replies or workspace content. This pseudonymous record survives account deletion so signing up again with the same email does not renew the allowance. Ended months are removed after a two-day settlement grace period. Usage details are erased when you delete everything; the monthly amount remains until that expiry. Your usage in other apps and external AI plan balances are not fetched.

Cookies

We use essential session and login-flow cookies, plus local UI preferences. These cookies keep you signed in and protect login flows.

Contact and changes

For privacy requests you cannot complete in Settings, email support@ensemblework.com.

Do not send Google content, tokens or other secrets by email.

Material policy changes will be reflected on this page. If a Google data use changes beyond the purposes you authorized, we will disclose that change and obtain the necessary consent before that new use.