Clico uses only the sources enabled for that surface and request.
How Clicohandles your data
You choose when Clico can use the page, app, file, voice or account context needed for a task. Here is what may leave your device, what each Clico surface stores and which controls stay with you.
PageScreenVoiceFile
The active client gathers the text, image, audio, file or account data the task needs.
Remote processing is used when the selected model, speech service, tool or connected app needs it.
Clico does not upload a continuous screen or browsing history.
When Clico can observe
Access follows the surface you are using, the task you start and the permissions you grant.
Desktop for Mac
With macOS permission, Clico can use screen, accessibility, microphone and file context when you start a task. Desktop task history is primarily stored on your Mac, while relevant context may be processed online.
Chrome Extension
Clico captures page context after you open it or start a context aware workflow. Depending on the feature, that can include selected text, the active field, the page URL and visible page content.
Web Agent
Clico uses the prompts, files and connected services you provide for a task. Conversations and run state are stored in the cloud so work can continue and be reviewed.
What leaves your device
A model request, transcription, online tool or approved action may require the relevant part of your context to leave your device.
- 01
You choose the context
You open Clico, select content, attach a file, begin a voice interaction or approve access to a connected service.
- 02
Clico prepares the request
The active client assembles the prompt and the page, screen, app, voice, file or account context needed for the task.
- 03
Relevant context is sent
Clico sends the material needed for the request. It does not upload a continuous screen history or a background index of your browsing.
- 04
The required provider processes it
The task may use Clico infrastructure and a selected AI, speech, search, extraction or connected service provider.
- 05
The result returns to Clico
The result appears in the surface you used. Storage differs across Extension, Desktop and Web, as described below and in the Privacy Policy.
How Clico handles each type of data
The purpose, storage path and controls depend on the information and the Clico surface using it.
Screen and app context
Used for requests you start on Mac and for page context you invoke in Chrome. Relevant excerpts or images may be sent for model or tool processing.
Voice and transcripts
Audio starts when you begin a supported voice or recording workflow. Audio may be processed by a speech provider, while transcripts and summaries can follow a different storage lifecycle.
Tasks, files, history and memory
Desktop history is primarily local. Extension records and Web Agent conversations use separate cloud storage. Files and generated artifacts follow the surface and task that created them.
Account and billing
Clico processes identity, account, subscription and usage information. Payment providers handle full card details. Clico receives limited billing and transaction records. See current plans, credit allowances, and Stripe checkout details.
Connected accounts and actions
Clico uses an account after you authorize it and a task needs it. Sensitive operations require your request, authorization or approval.
Diagnostics and reliability
Limited crash, error, performance, app and operating system information may be used to keep Clico secure and reliable. Raw task content is excluded from support diagnostics by default.
Chrome Extension details
The Extension needs broad site permission so it can work inside supported pages and frames. That technical permission does not mean every page is continuously read or sent.
When page content is used
- After you open Clico or start a feature that requests page context.
- Selected text and editable field content can be used for writing and rewriting.
- Visible headings, tables, messages and document text can be used when a workflow needs broader page context.
- Another open tab is used only when you explicitly select it through a supported tab context feature.
What is excluded or limited
- Password fields and payment fields are excluded from ordinary page capture.
- Clico does not use browser history, bookmarks, cookies or website session tokens as task context.
- Clico does not create a continuous background index of the pages you visit.
- Local files are used only when you choose a feature that accepts a file or attachment.
History and deletion
- Recent Extension chats may be cached in browser storage.
- Prompts, responses, action type and limited page metadata may be stored in account linked cloud records.
- Deleting an available Extension chat removes it from active use and redacts its primary stored prompt and response.
- Uninstalling the Extension does not by itself delete cloud account or billing records.
Controls you can change
You can narrow access at the product, browser, operating system and connected service level.
Task and context
Choose what you ask, select or attach, and close or stop a workflow when you are done.
System permissions
Review or revoke Chrome site access and macOS screen, accessibility, microphone and file permissions.
Connected services
Disconnect a connected account in Clico and revoke access with the provider when needed.
History and privacy requests
Use the deletion controls available in each surface, or email hey@tryclico.com for an access or deletion request that spans Clico systems.
The plain language guide, backed by the full policy.
This page explains product behavior. The Privacy Policy covers legal bases, providers, retention, rights, transfers and contact details.