Privacy Policy
Scope and operator
This policy applies to Asa Hermes Drive, operated by Letech AI Company. Contact: asachyau@gmail.com. Policy version: 1.0. It applies when these pages are published; it does not claim earlier practices or settings were identical.
Data accessed and purposes
Depending on the authorised task, the integration accesses Google account information returned by the API, Drive file names and metadata, file contents, folders and relevant permissions. OAuth credentials support the authorised connection. The data is used for requested file searches, document review, report preparation and approved file operations. The current Drive grant is broad read/write access, not a technical read-only restriction.
AI processing and transfers
Hermes operates in a private computing environment. Relevant prompts, excerpts and attachments may be transmitted to OpenAI through the configured Codex connection for the requested task. The operator has confirmed that the connected account’s Improve the model for everyone setting is off. OpenAI states that opting out excludes new personal-account conversations and Codex tasks from model training. This does not establish zero provider retention or deletion of previously processed data. Any additional processor or separate cloud-environment data-sharing setting must be reviewed before it receives Google user data; processing must not exceed the purposes disclosed here.
Permitted use and Limited Use
The operator limits Google user data use to the authorised, user-facing document features described here. Google user data is not sold, used for advertising or used to train general-purpose AI models. Transfers are limited to supporting those features with user consent, necessary security purposes, or legal requirements, subject to the Google API Services User Data Policy, including its Limited Use requirements. These restrictions also apply to information derived from Google user data. This policy is an operating commitment, not a claim of Google verification or certification.
Storage and retention
Working files, generated outputs and conversation history may persist beyond a single request. There is no fixed retention period. OAuth credentials are stored separately in protected private files. Copies may also exist in backups or service-provider systems; this policy does not promise an automatic backup purge, a fixed provider retention period or exclusive access by the chat user. Administrative access may be necessary to operate the environment.
Revocation and deletion requests
The account owner can revoke access through Google Account third-party connection settings. Revocation prevents further access using that authorisation but does not itself erase downloaded files, outputs, history, backups or provider-held copies. Send review or deletion requests to asachyau@gmail.com. Requests are reviewed individually, including which copies can be identified and removed and any technical or legal limitations. There is no guaranteed response or deletion deadline, and immediate deletion from every backup or provider system is not promised.
Security
The Google API connection uses HTTPS. The connector stores OAuth state in access-restricted private files and is designed not to display credentials in routine output. Security also depends on account, device, hosting and DNS controls. No system is guaranteed secure.
This public website
This static site provides application and policy information; it does not provide a Google login form or display Drive documents. The supplied site code contains no analytics, advertising scripts, forms or cookies. Cloudflare Pages serves the site and may process ordinary connection information, such as IP addresses and request metadata, under its own policies. This statement is not a promise that the hosting provider keeps no logs.
Policy changes
Updates will be posted on these pages. Additional notice and consent must be obtained before using Google user data for a materially new purpose not already disclosed. Questions may be sent to the contact above.