Overview
Privacy for a local-first engineering workspace
01Implaced is built around a local-first workspace model. Your projects, workspace files, agent state, and local outputs are intended to stay on your machine unless you choose to connect services, sign in, request support, attach files, or send content through a provider route.
Account
Account and identity data
02When you sign in, we may process basic account information such as your email address, authentication provider identity, user identifier, and session metadata. This helps secure your account, keep workspace identity consistent, and connect support conversations to the right user.
Workspace
Local project and workspace data
03Local workspace paths, logs, project state, agent context, and related files may be stored in your local ImplacedWorkspace directory so the app can operate consistently across sessions. Local project files are not meant to leave your machine unless you choose a connected flow that sends them.
AI providers
Model-provider requests
04When you use AI features, prompts, selected code, tool output, project context, or other content you intentionally send may be processed by the AI provider, gateway, or relay you configure. Provider handling depends on the service you choose, the settings you enable, and the API keys or accounts you provide.
Support
Support messages, screenshots, and logs
05When you contact Support inside Implaced, your messages and any files you attach, such as screenshots or logs, may be uploaded so the Implaced team can diagnose issues and respond. Attachments are only sent when you choose to attach them.
Credentials
API keys and secrets
06Implaced is designed to keep sensitive keys out of source code. When an agent needs a credential, the Secure Vault flow can collect it and store it locally in your environment rather than embedding it into project files.
Diagnostics
Operational and diagnostic information
07We may process limited operational information needed to run the product, improve reliability, support authentication, diagnose failures, and protect the service. This may include app version, platform, operating system information, support ticket metadata, and error details you choose to share.
Retention
How long information is kept
08We keep information for as long as needed to provide the product, operate support, maintain security, comply with obligations, and improve the preview release. Local workspace data remains on your device unless you remove it or choose to send it through a connected flow.
You control what you send to providers and Support. You can avoid attaching files, choose which content to provide to AI features, manage your provider configuration, and contact us about account or privacy questions.
We may update this Privacy Policy as Implaced evolves. When changes are meaningful, we may update the date above, publish a notice, or use in-app announcements so users can understand what changed.
For privacy questions, account requests, or support-related privacy concerns, contact the team through Support so the conversation can be handled with the right context.