Clio Assistant

Privacy Policy

Effective date: September 27, 2026.

Clio Assistant is a private, personal-use agent operated by Alejandro Perez. It helps organize the account owner’s information by reviewing authorized email, updating a personal knowledge vault or Notion workspace when requested, and filing approved email attachments into Google Drive folders using the owner’s specified file structure. This policy describes the information processed by Clio Assistant, how it is used, where it may be stored or processed, and the choices available to the account owner.

Information Clio Assistant may access

Access depends on the Google OAuth permissions and other integrations the account owner enables. Clio Assistant accesses only information relevant to an authorized request or workflow. Depending on those permissions, information may include:

Clio Assistant does not access unrelated Google accounts, Notion workspaces, or local folders merely because they exist. It does not require access to every listed service; access is limited to the permissions and integrations actually enabled by the owner.

How and why information is used

Clio Assistant reads authorized emails to identify useful personal information, tasks, dates, decisions, and attachments. At the owner’s request, it may summarize or classify relevant information, add durable information to a suitable personal-vault or Notion page, and file approved attachments in the correct Google Drive folder according to the owner’s folder structure and naming rules. When an existing knowledge destination is suitable, Clio Assistant is intended to update that destination rather than create duplicate email archives.

Information is used to carry out the owner’s personal productivity and filing instructions, maintain links or provenance to source email and Drive files, and return the requested result. Clio Assistant does not use the information for advertising, marketing, sale, or profiling. It does not automatically send email, delete information, archive messages, publish files, or share content with other people without the owner’s authorization.

Service providers and disclosure

Clio Assistant is not a public service and does not sell Google user data. It does not disclose data to third parties for advertising or unrelated purposes. To perform a task, relevant information may be processed by the services the account owner has connected or instructed Clio Assistant to use. These may include Google services where the original information is held or a file is saved, Notion when the owner requests a vault update, and the AI model provider configured for Clio Assistant when relevant content is submitted for analysis or summarization.

Only information reasonably needed for the requested task should be sent to a connected service. Those providers process information under their own terms and privacy practices. Clio Assistant does not authorize those services to use the information for Clio advertising or unrelated purposes. The owner can avoid a destination service by not authorizing it or not requesting a workflow that uses it.

Where information is stored and how long it is retained

Gmail remains the source for email unless the account owner separately changes it. Clio Assistant does not create or retain a separate email archive as its normal filing method. When the owner requests filing, an approved attachment may be copied or saved to the selected Google Drive folder; the email and its original attachment are not deleted by Clio Assistant. Summaries or durable facts are written to Notion or a personal vault only as requested, preferably into an existing relevant destination rather than as duplicate email records.

To complete a task, relevant content may be present temporarily in Clio Assistant’s processing and conversation/session context. Session records may include the owner’s instructions, relevant excerpts, tool results, summaries, and links so the task can be completed or the conversation continued. Those records are kept in the private Clio operating environment under its configured session-retention controls; there is no claim that every transient copy is erased immediately after a task.

Copies saved to Google Drive or Notion remain in those services until the owner removes them. The owner can remove an attachment from its destination folder or delete/update a Notion/vault entry. Temporary processing and session records can be removed using the available Clio session/data controls or by contacting the operator. The exact retention period for connected AI and cloud service providers is governed by their applicable terms and settings, not by this website.

Security and access

Google access is controlled by the OAuth permissions granted by the owner. Local filesystem access is limited to locations explicitly made available for a task. Clio Assistant uses connected services to carry out requested work and the public information website does not expose email, Drive, Notion, filesystem content, credentials, or an account login. No networked system can guarantee absolute security; access should be granted only to the services and data needed for the owner’s workflows.

Access control and revocation

Access is controlled by the OAuth permissions granted to Clio Assistant. The account owner can revoke Google access at any time through Google Account security settings or the associated Google Cloud project. Revoking access stops future requests to the revoked Google services, but it does not automatically remove copies already saved to Google Drive, Notion, a personal vault, or Clio session records; those must be removed from their respective locations.

Your choices

The account owner chooses which Google permissions to grant, which files and directories to make available, and which productivity workflows to request. The account owner may withdraw Google access, stop a workflow, remove retained information, or remove local files directly. Withdrawing authorization may prevent Clio Assistant from completing features that depend on that information.

Clio Assistant’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Changes to this policy

This policy may be updated when Clio Assistant’s functionality or data practices change. The current version is always published at this URL. Any new use of Google or filesystem information will remain subject to the account owner’s authorization and the limitations described here.

Contact

For questions about this privacy policy or Clio’s handling of information, contact the operator:

Alejandro Perez — wialejoo@gmail.com