Privacy Policy
This policy explains the categories of data the current Decubed preview may handle, why that data is used, and the choices available to the user.
What Decubed Handles
Depending on the features you use, Decubed may handle:
- account identifiers and authentication state
- workspace configuration
- prompts, messages, thread history, and outputs
- files and metadata you choose to attach or open
- tool approval decisions and permission settings
- diagnostics, performance logs, and product analytics
The exact data involved depends on which providers, tools, and platform surfaces you connect.
Why Data Is Used
Decubed may use the data above to:
- authenticate users and linked services
- deliver model requests and tool actions
- persist threads, memory, and workspace settings
- prevent abuse, fraud, and service misuse
- debug failures and improve product reliability
- meet legal, security, and operational obligations
Decubed does not need every category of data for every workflow.
Local-First Product Behavior
Decubed is designed around a local-first workspace model, but some flows may still involve remote systems, including:
- hosted model providers
- linked account transports
- crash reporting or product analytics
- support and operational systems
When a workflow crosses into a remote system, the handling of that data may also be subject to the terms and privacy rules of that provider.
Providers, Tools, And External Services
If you connect a model provider, account, or tool, data may be transmitted to that third party as part of the workflow you approve.
Examples include:
- prompts sent to a hosted model API
- calendar data retrieved through an approved tool
- files inspected before a sharing or export action
Decubed does not control the retention or secondary use practices of third-party services. Review the providers and tools you decide to connect.
Analytics And Diagnostics
Decubed may collect technical diagnostics needed to operate the preview, such as:
- crash events
- performance timing
- request or feature health signals
- coarse device or browser information
These signals are used to keep the service reliable and to understand where the product needs work.
Retention
Data is retained only as long as reasonably needed for:
- the active product workflow
- service operation and recovery
- debugging and abuse investigation
- legal or security obligations
Retention can vary between local state, operational logs, and third-party provider systems.
Your Choices
You can reduce the amount of data handled by:
- keeping workflows on local runtimes where available
- limiting which providers and tools are connected
- reviewing approvals before actions run
- removing files or workspace content you no longer need
Some deletion and export capabilities may depend on the current preview surface and the platform you are using.
Security
Decubed uses reasonable technical and organizational measures to protect the service, but no system can promise perfect security.
You are also responsible for:
- securing your own devices
- protecting linked provider accounts
- reviewing who can access your workspaces and exports
Children
The preview is not intended for use by children without appropriate legal authority and supervision.
Changes
This policy may change as the product, platform, or provider integrations change. The current version posted on this route controls once published.
Contact
Questions about this policy should be sent through the current Decubed contact channel published on this site or inside the active product build.