Privacy Notice

Contact

For privacy questions or requests, contact Nicholas Hoff at nick@nicholashoff.com.

The short version

• Wilco can use local or cloud workspaces.
• Workspace files and terminal processes remain in the selected local or cloud runtime.
• Wilco stores conversation and execution records in Postgres. Commands and results use authenticated HTTP; AWS routes realtime notifications.
• When you use the Wilco Brain or voice transcription, the information needed for that request is sent through Vercel to OpenAI.
• Wilco does not sell your information or use it for advertising.

Information Wilco handles

Account and access

Clerk handles your name, email address, authentication, session, invitation, and legal-acceptance information. Wilco stores account status and the access grant that lets you use the private beta.

Machines and connections

Wilco stores registered environment and Desktop-client information such as a display name, platform, credential verifier, revocation status, and last-seen time. Short-lived login tokens and connection records are used to connect and route your sessions securely.

Workspace and terminal data

When you ask Wilco to show or change something, terminal input and output, workspace paths, file content, and Codex messages or results may pass through the Wilco backend. Wilco stores conversation and execution records in Postgres, while workspace files and processes stay in the selected runtime.

Wilco Brain

Brain requests can include your Wilco conversation, a bounded description of open workspaces and panels, visible file content and paths, tool inputs and results, and an optional screenshot when you ask Desktop to inspect or act on a webpage. This information is sent through Vercel to OpenAI to answer your request. Wilco persists chat messages, tool calls and execution results in Postgres so the Brain can continue the conversation.

Voice

Voice recording starts only when you choose it. The recording is sent through Vercel to OpenAI for transcription. Wilco does not intentionally retain the audio after the request. The returned transcript becomes Brain input if you submit it.

Basic analytics and diagnostics

Wilco records a small allowlisted set of product events and diagnostic timing spans, such as feature use, runtime readiness and failures, outcome, and duration. These records are connected to your internal Wilco user ID but do not contain prompts, messages, code, commands, terminal output, screenshots, audio, or arbitrary tool content. Operational logs use similarly limited metadata and safe error categories.

Why this information is used

Most processing is needed to create your account and provide the Wilco features you request. Limited security, reliability, and product analytics are used for Wilco's legitimate interests in keeping the beta safe, understanding whether it works, and fixing problems. Information may also be handled when necessary to meet a legal obligation.

Account, authentication, and connection information is needed to use Wilco. Without it, Wilco cannot create or connect your account. Brain, screenshot, voice, and external-web features are optional and process their related content only when you choose to use them.

Wilco does not use your information for advertising, sell it, or make automated decisions about you that have legal or similarly significant effects.

Services involved

Wilco currently uses:

• Clerk for accounts, authentication, and invitations;
• Vercel to host the website and run its API routes;
• PlanetScale Postgres for application records and analytics;
• AWS for realtime routing, artifact storage, and logs;
• OpenAI for the Wilco Brain, optional visual grounding, and voice transcription; and
• your configured Codex/OpenAI service for Codex threads and delegated work.

These services may process information outside Germany or the European Economic Area. Wilco relies on the providers' applicable contractual and transfer safeguards where required. External websites opened in Desktop and provider-owned Codex services also apply their own privacy terms.

How long information is kept

• Account, access, and registered-device information is kept while your account and the service remain active, or until it is no longer needed.
• Analytics records remain in Postgres until they are deleted manually.
• Sanitized hosted operational logs are kept for no more than 90 days.
• Temporary login and connection records use short automatic expirations.
• Provider systems and backups follow the applicable provider settings and deletion schedules.

The end of the private beta does not automatically delete your account or information because Wilco may continue into another beta or regular launch.

Your choices and requests

You can ask to access, correct, export, restrict, or delete information linked to your Wilco account, or object to processing based on legitimate interests. Email nick@nicholashoff.com. Wilco may need to confirm the request using your verified account email.

Some information may remain temporarily where needed for security, legal obligations, legal claims, or provider backup expiry. Deleting Wilco data does not automatically delete local files, external-site data, or provider-owned Codex history.

If European data-protection law applies, you may also complain to the data protection authority responsible for your location.

Cookies and local storage

Wilco uses cookies and local browser storage needed for authentication, security, and requested product features. The private beta does not use advertising cookies or nonessential behavioral tracking, so it does not show a separate cookie banner.

Changes

This notice may change as the beta evolves. Material changes will be shown with a new effective date and, when appropriate, presented for acceptance.