Privacy Policy

WIP Computer, Inc. ("WORK IN PROGRESS", "WIP Computer", "we", "us", or "our") builds a distributed operating environment for AI systems. This includes public websites, hosted account services, local software, agent-readable instructions, registries, relay and sync services, Memory Crystal, Bridge, Agent Pay, Kaleidoscope, LDM OS, and other products that link to this policy.

Different parts of the system process data in different places. Some features run locally on your device or in your own runtime. Some features use WIP-operated hosted services. Some features call third-party providers when you connect them or ask for an action that depends on them.

Information We Collect

• Account and identity data, such as handles, display labels, account identifiers, passkey credential IDs, public keys, device records, and scoped tokens.
• Authentication and authorization data, such as WebAuthn challenges, session state, device approval records, permission decisions, token metadata, and agent authorization history.
• User content, such as prompts, instructions, messages, selected files, uploaded media, images, agent requests, and other inputs you provide to a WIP Computer service.
• Generated content if a product stores, displays, relays, or returns it for you.
• Memory and context records when you use Memory Crystal or memory-related features. Depending on the product and settings, memory may be local-only, synchronized, encrypted, or connected to third-party tools you choose.
• Wallet, credit, payment, and spend-authorization metadata, such as displayed balances, authorization events, payment status, transaction identifiers, payment provider records, and abuse-prevention signals.
• Local runtime and extension metadata when needed to install, verify, update, or support software you choose to run.
• Operational data, such as IP address, user agent, timestamps, route identifiers, tenant identifiers, logs, rate-limit records, error reports, diagnostics, and security events.

Information We Do Not Collect Or Sell

• We do not sell personal data.
• We do not "sell" or "share" personal information as those terms are defined under California privacy law.
• We do not use advertising-network tracking.
• We do not receive Face ID, fingerprint, or other biometric data. Biometric approval happens on your device through the platform authenticator.
• We do not store passwords for WIP Computer passkey account surfaces.
• We do not receive passkey private keys from your device.

Local And On-Device Processing

Many WIP Computer products are designed to operate primarily on-device or inside a local runtime you control. Data processed locally may not transit WIP-operated infrastructure unless you enable or use a hosted account, synchronization, relay, payment, marketplace, registry, cloud, third-party integration, or support feature.

Local software may store configuration, logs, tokens, memories, extension data, generated outputs, or runtime state on your device. You are responsible for the devices, local accounts, agents, extensions, and credentials you configure.

Hosted Services, Relay, And Sync

Hosted services may process data needed to authenticate accounts, issue scoped tokens, authorize agents, route requests, synchronize state, operate registries or marketplaces, show wallet or credit balances, prevent abuse, and provide support.

Relay and sync features may process routing metadata, tenant identifiers, session identifiers, authorization headers, connection state, timestamps, rate-limit records, and logs. Where a relay feature supports end-to-end encryption today, such as supported Codex Remote Control daemon sessions, WIP Computer is designed to route encrypted payloads without reading the decrypted content. Operational metadata can still remain visible to run and protect the service.

Some WIP Computer memory and sync features are designed or intended to use end-to-end encryption or device-bound keys. That design goal does not mean every current feature is end-to-end encrypted today. We will describe product-specific encryption behavior where it matters.

Cookies And Local Storage

WIP Computer may use browser sessionStorage or local storage for session continuity, including tokens or agent identifiers such as lesa-token and lesa-agent. This storage is used to keep the product flow connected during a browser session, not for advertising-network tracking. Browser sessionStorage may clear when the tab or browser session ends, depending on your browser settings.

Third-Party AI Providers, Tools, And Infrastructure

WIP Computer may coordinate, route, authorize, log, display, or store actions without being the model provider, payment provider, package registry, MCP server, or developer tool for every action.

When you connect third-party AI systems, MCP servers, APIs, payment processors, software registries, package managers, developer tools, or hosted platforms, those interactions may also be governed by the third party's terms and privacy practices.

Kaleidoscope image generation currently uses xAI / Grok Imagine. When you request image generation through that flow, WIP Computer may send the prompt, selected image input, and related request metadata needed for the generation to xAI. xAI may process that information under its own terms and privacy practices.

Other AI or tool providers may receive prompts, context, files, media, credentials, tool arguments, generated content, metadata, or other information needed to perform actions you request or authorize.

We do not use your private prompts, uploaded files, memories, agent content, or private generated outputs to train third-party foundation models unless you explicitly choose a feature that sends that content to a third-party provider under its terms.

Payment And Wallet Infrastructure

Today, Kaleidoscope may show wallet or credit balances and may request user approval before calling xAI / Grok Imagine for image generation. WIP Computer may receive balance records, authorization records, request status, and abuse-prevention information needed to operate those features.

As the product develops, Agent Pay and payment features may support payment providers, card checkout, one-time payment links, x402-style paths, platform payment flows, bring-your-own-wallet modes, or similar payment infrastructure. Those future payment paths may involve additional third-party providers and payment metadata if and when they are enabled. Do not assume a displayed balance is real money unless the product clearly says it is real money and presents the applicable payment terms at the point of use.

How We Use Information

• Authenticate users, agents, devices, sessions, and scoped tokens.
• Operate Kaleidoscope, LDM OS, Memory Crystal, Bridge, Agent Pay, hosted relay and sync services, registries, marketplaces, and local-runtime support features.
• Route, display, store, synchronize, or return content and generated output at your request.
• Show balances, credits, authorization state, usage, and transaction history.
• Run requested AI generation, memory, agent, payment, install, registry, marketplace, relay, or developer workflows.
• Prevent abuse, fraud, unauthorized access, credential misuse, unsafe automation, and service disruption.
• Debug reliability issues, maintain security, provide support, and improve the services.
• Comply with legal obligations and enforce our terms.

Storage, Retention, And Deletion

Storage and retention depend on the product, feature, settings, and record type. Local runtime data may remain on your device until you delete it or uninstall the software. Hosted account records, security logs, payment metadata, authorization records, and operational records may be retained as needed to provide the service, secure the platform, comply with law, resolve disputes, prevent abuse, and maintain business records.

Memory features are designed to store and retrieve user-authorized context so your agents can maintain continuity. Depending on the product and settings, memory may be local-only, synchronized, encrypted, exported, deleted, or connected to third-party tools you choose.

Business Transfers

If WIP Computer is involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets, information may be transferred as part of that transaction, subject to this policy or another policy disclosed to you.

Your Rights And Choices

You may choose whether to use local software, hosted services, third-party integrations, relay, sync, payment, registry, marketplace, memory, and AI-provider features. Some features may not work without the data needed to operate them.

Depending on your location, you may have rights to request access, correction, deletion, portability, restriction, or objection for personal information. To request deletion, export, review, or correction of personal information associated with your use of WIP Computer services, contact hello@wip.computer.

Children

WIP Computer services are not directed to children under 13. If you believe a child has provided personal information to WIP Computer, contact hello@wip.computer.

Changes To This Policy

We may update this policy as WIP Computer products change. The updated date shows when the policy last changed. Continued use of the services after changes means the updated policy applies.

Contact

Questions about this policy can be sent to hello@wip.computer.