← Attaché

Attaché — Privacy Policy

Effective 12 September 2026. Applies to the Attaché desktop application, the

Attaché website, and the Attaché Cloud subscription service.

Attaché supports both local desktop use and an account-based cloud workspace.

Local features can work without an internet connection. Cloud conversations,

Mind synchronization, mobile access, and cloud employees send and store the data

described below so they can work across devices and while your PC is off.


1. What stays on your computer

Everything below is stored under %USERPROFILE%\.attache\, in a folder for

each account on the machine. Local-only use does not upload these stores.

When you connect the cloud workspace, supported memory, notes and workspace

context can synchronize to your cloud account as described in section 3.

WhatWhere
Facts Attaché remembers, and session summariesusers/<account>/memory.json
The vector index used to search that memoryusers/<account>/memory.vectors.npz
Your settings — wake word, home city, widgets, permissionsusers/<account>/settings.json
Notes and drawings you pin to chartsusers/<account>/chart_notes.json
Brokerage, exchange and CRM credentials you linkusers/<account>/credentials.json
Your local sign-inusername and a PBKDF2-HMAC-SHA256 password hash

Accounts on the same computer have separate memory, settings and credentials.

Local-only data is not backed up by us, so we cannot recover it if you delete

the folder or lose the machine. Back up local files as you would any other

personal data.

2. What leaves your computer, and when

Attaché contacts a network service only when a feature needs one.

The language model. On the free tier, Attaché can answer entirely on your

machine using the model bundled with the installer — nothing leaves. When it

uses a cloud model instead (for speed, or when a question needs one), your

message and the recent conversation are sent to that provider: Groq,

OpenRouter or Google Gemini. On paid models, they are sent to Anthropic or OpenAI

through Attaché Cloud. Relevant source notes and tool results can also be

included in a request to complete your assignment. Providers process the request under their own terms and

privacy policies.

Speech recognition. Talk and the wake word use your browser engine's

built-in speech recognition. On Windows this is Chromium's implementation,

which sends captured audio to a Google speech service for transcription.

This is the browser's behaviour, not something Attaché adds, and we cannot

change it. If that is not acceptable to you, leave the microphone features off

and type instead — everything works by typing.

Memory search. Facts are turned into vectors by a model bundled with the

app, on your machine. If that model is unavailable and you have supplied a

Google Gemini key, Attaché can fall back to Gemini's embedding service, which

means the text of a fact is sent to Google. Without a key, it falls back to

a local word-overlap search instead and nothing is sent.

Data you ask for. Charts, quotes and headlines come from Yahoo Finance;

general news from BBC RSS; weather and other lookups from their respective

public sources. These requests reveal what you asked about — a ticker symbol, a

city — to those services.

Accounts you link. If you link a brokerage, exchange, CRM, Google or

Microsoft account, desktop tools contact that service from your computer.

Connections you migrate to cloud employees are stored encrypted in your cloud

account and used from Railway, including scheduled work while your devices are

off. Provider access tokens, refresh tokens and required OAuth client details

are stored for those connections. Employees can read account data, create or

update CRM records, and send email according to the permissions you grant;

email recipients must be explicitly allowed. Relevant account results may be

included in model requests and your private action history. Brokerage and

exchange access remains read-only: Attaché reads balances and positions and

does not place orders.

Camera. Head tracking, if enabled, is processed on your machine. No video

or image is transmitted or stored.

3. What Attaché Cloud stores

Attaché Cloud includes a free workspace and optional paid model access. If you

create an account and use cloud features, we store on our server:

recipients, job results, tool action history and completed deliverables

Cloud data is associated with your account. Source notes, conversation context

and relevant tool results are sent to the selected model provider to perform

your request. Credentials themselves are not included in model prompts.

Payments are handled by Stripe. Card details go to Stripe directly; we

never see or store them.

4. What we do not do

fingerprinting. Operational request logs, usage counters, job status and

private action history support the cloud service.

their own purposes.

5. Children

Attaché is not directed at children under 13, and we do not knowingly collect

personal information from them.

6. Your choices and rights

For local data, control is direct: delete a fact in the

Memory panel, clear a credential in Settings, or delete

%USERPROFILE%\.attache\users\<account>\ to remove everything for that account.

You can pause cloud employees and disconnect their cloud connections in the

Agents screen. Disconnecting removes the stored cloud credential but cannot

recall a provider request already in flight. Archiving a cloud note hides it

from active work; it does not erase all retained copies or prior job results.

For an Attaché Cloud account, you may ask us to export or delete the account

data listed in section 3 by writing to the contact address below. Depending on

where you live you may have rights of access, correction, deletion, portability

or objection under laws such as the GDPR or the CCPA; we honour these requests

regardless of where you are.

7. Security

Local passwords use PBKDF2-HMAC-SHA256 and cloud passwords use bcrypt. Local

credentials are stored on the PC. Migrated cloud connection credentials use

authenticated encryption with an account-specific key derived from a server

secret. Credentials are not returned by connection-list endpoints.

Traffic to model providers, market data sources and Attaché Cloud uses HTTPS.

No system is perfectly secure. Attaché runs on your machine, and its data is

only as protected as that machine — anyone with access to your unlocked

computer, or to a backup of it, can read these files.

8. Changes

If this policy changes materially we will update the effective date above and

publish the new version at the address below before it takes effect.

9. Contact

Questions, requests or complaints: lennycruz4.lc@gmail.com

Current version: https://attache-cloud-production.up.railway.app/privacy