Joi · Privacy information
Privacy and data handling
Joi is Eng’s personal AI assistant using Personal Hermes. It is one person’s private integration, not a service offered for public account connections. This page distinguishes the public informational website from the private assistant.
The public website
This static site has no signup form, email capture, tracking scripts, advertising, Google sign-in or account-connection feature. It does not request Google permissions or receive Google authorization tokens. A hosting provider may process ordinary network request information, such as IP addresses and access logs, under its own practices. Emailing the contact address sends the information you choose to include through email providers.
Google data and its purpose
With account authorization and within the granted permissions, the private assistant can access and use email messages and related information, Calendar events, Drive files, Docs documents, Sheets spreadsheets and Contacts information to carry out authorized tasks. Those tasks can involve reading, summarizing, organizing, drafting or making authorized changes in the relevant service. Not every connected account has the same permissions; access can expire or be revoked.
The purpose is to assist Eng with the work he authorizes. The public website does not display his Google data, private conversations or task records.
Storage and external processing
Google authorization tokens are retained privately on the operator’s computer, not on this public website. Task records, retrieved material and generated outputs may also be retained privately on that computer.
Processing is not always local. Depending on the task and configuration, selected content, prompts and tool results may be sent to configured external AI model or tool providers to perform the task. Their systems, settings and terms can affect processing, logging and retention. The fact that credentials are stored locally does not mean that all Google-derived content stays on the computer.
There is no single retention period stated here for every private record, backup or external provider. Storage and deletion depend on the record, the operator’s actions and the provider involved. Do not send passwords, authorization codes or other secrets to the public contact address.
Control, revocation and deletion
The account holder can choose whether to grant permissions, stop using the integration, and review or remove the app’s access in Google Account settings under linked apps or third-party connections. Google provides instructions for reviewing and removing app access.
Revoking access stops future access through the revoked grant; it does not itself erase material already retrieved, private task records, outputs or copies held by a provider. To remove private assistant records or local credentials, stop the relevant integration and ask the operator to review those records and any backups or provider-held copies. Changes to assistant records do not automatically delete the original messages, files or events in Google.
For privacy questions or requests concerning access, correction or deletion, contact joilee219@gmail.com. Describe the request without including secrets or unnecessary sensitive material. Applicable privacy rights and any limits depend on the circumstances and governing law; this page does not promise a particular legal outcome or automatic deletion from every system.
Google data-use requirements
Use of Google API data is subject to the Google API Services User Data Policy and, for Workspace data, the Google Workspace API user-data requirements, including applicable Limited Use restrictions. These rules limit permitted uses and transfers of data. This description of applicable requirements is not a Google endorsement, verification or security certification.
Changes
This information should be updated when the integration’s data practices change. A website update by itself does not authorize a new use of Google data; appropriate notice and consent are needed where required.