Privacy Policy

Effective date: 15 October 2026

Contents

1. About Lisa and this policy
2. Google data Lisa accesses and why
3. Other information Lisa processes
4. Processing and storage
5. Sharing and disclosure
6. Google API policies and Limited Use
7. Retention and deletion
8. Revoking Google access
9. Changes and future integrations
10. This website
11. Contact

1. About Lisa and this policy

Lisa is a personal AI assistant that its owner uses through a private Telegram chat. It runs on a privately administered server, and its owner is both the person who operates it and its only user. There are no customer accounts and no other users.

This policy describes how Lisa accesses, uses, stores and shares data, with particular attention to data received from Google APIs (“Google data”). It covers only what Lisa does today and, separately, what would change if optional integrations were enabled in the future.

2. Google data Lisa accesses and why

2.1 Google Calendar (currently being configured)

Lisa requests one Google permission, https://www.googleapis.com/auth/calendar. Google describes it as allowing an app to “see, edit, share, and permanently delete all the calendars you can access using Google Calendar.” It is not read-only and not limited to events Lisa creates. Lisa's intended use is narrower, as described below, but that narrower use is a limit in how Lisa is built and operated. Google does not enforce it.

Data Lisa may access

Calendar identifiers and names; event titles, dates, times and time zones; event descriptions and locations; organizers; attendees, including their names and email addresses; and invitation responses. Calendar data can include information about other people, such as the organizers and guests of the owner's events.

Why Lisa uses it

To fulfil the owner's requests: answering scheduling questions (for example, what is planned for a given day or when the owner is free), creating and editing events, and sending invitations to the people the owner specifies.

2.2 Possible future integrations (not enabled)

The integrations below are possibilities only. Lisa does not currently access email, contacts, tasks, or Drive, Docs or Sheets files, and does not request permission for them. If the owner enabled one of them in the future, Lisa would expect to access the following data, for the following purposes:

Gmail

Email messages and their details (senders, recipients, subjects, dates and labels), attachments where needed, and drafts, in order to find and summarize the owner's emails, prepare replies, and send messages the owner authorizes.

Google Contacts

Names, email addresses, phone numbers and other contact details, in order to look up people and recipient addresses.

Google Tasks

Task lists, task titles, notes, due dates and completion status, in order to read and manage the owner's tasks.

Google Drive, Docs and Sheets

Names, details and contents of files, documents and spreadsheets, in order to find, read, summarize, create and edit them at the owner's request. Access to individually selected files is preferred over access to the whole Drive.

None of these would be enabled without the steps described in section 9.

3. Other information Lisa processes

Apart from Google data, Lisa processes the messages, voice notes and files the owner sends it in Telegram, its own replies, its conversation history, short memory notes it keeps about the owner's preferences, and operational logs. Google data can become part of any of these, as described in the next section.

4. Processing and storage

• Server. Lisa runs on a server hosted on Oracle Cloud Infrastructure and administered privately by the owner. Like any hosted server, it is accessible to its administrator, and the underlying infrastructure is operated by the hosting provider.
• Google credentials. The OAuth credentials that let Lisa access Google Calendar are stored on that server. They are not stored in this website or its source files.
• AI processing. To interpret and fulfil a request, Lisa sends the request and the relevant data, which can include Google data, to an external AI model provider. This also applies to background processing of the conversation, such as summarizing long conversations. See section 5.
• Delivery through Telegram. Lisa's replies, which can contain Google data, are delivered to the owner through Telegram and are kept in the Telegram chat.
• Persistence. Google data can persist in Lisa's conversation history, in its memory notes, in local files Lisa creates while working, and in operational logs on the server. Copies of Lisa's data can also exist in encrypted backups of the server, which are stored in the owner's own Google Drive.
• Personal, non-confidential use. Lisa is intended for the owner's personal, non-confidential matters. It is not intended to process client, deal or fund materials.

5. Sharing and disclosure

Lisa does use external providers, and they process data, including Google data. Two different things happen, and they are described separately below.

5.1 Providers that process data to operate Lisa

• AI model provider. Lisa currently uses OpenAI models through the owner's personal ChatGPT subscription. Requests and the relevant Google data are sent to OpenAI for processing. In the owner's ChatGPT account, the setting that allows content to be used to improve OpenAI's models is turned off. OpenAI's handling and retention of the data is governed by OpenAI's own terms and privacy policy and by the owner's account settings, not by this policy. If the owner switches Lisa to a different AI provider, Google data will be sent only to a provider whose terms and settings do not allow it to be used to train or improve generalized AI models, and this policy will be updated.
• Messaging. Telegram delivers and stores the conversation between the owner and Lisa, under Telegram's own terms and privacy policy.
• Hosting. Oracle Cloud Infrastructure provides the server on which Lisa runs and stores its data.
• Google. Google processes Lisa's Calendar requests as the provider of Google Calendar.
• Other services the owner connects. If the owner asks Lisa to use Google data with another service the owner has connected to Lisa (for example, to add a meeting to a note or to another calendar), the relevant data is sent to that service and stored there under that service's terms.

5.2 People the owner asks Lisa to contact

When the owner asks Lisa to invite people to an event, Google Calendar sends those people an invitation. The invitation includes event details such as the title, time, location, description and organizer and, depending on the event's settings, the list of other guests. Lisa sends invitations only to people the owner specifies. If a future integration such as Gmail were enabled, the same principle would apply to messages: information would be disclosed only to recipients the owner authorizes.

5.3 What Lisa does not do with Google data

• It does not sell Google data, or transfer it to advertising platforms, data brokers or information resellers.
• It does not use Google data for advertising, including retargeting or personalized advertising.
• It does not use Google data to determine creditworthiness or for lending.
• It does not use Google data to train or improve generalized AI or machine-learning models.
• It does not use Google data for any purpose other than carrying out the owner's requests.

Google data may be disclosed if required to comply with applicable law, or where necessary for security purposes.

6. Google API policies and Limited Use

Lisa's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including the Limited Use requirements.

In practice, this means that Google data is used only to provide features the owner directly requests; it is transferred only to the providers described in section 5 to provide those features, or where necessary for security or to comply with law; and it is not used for advertising, sold, used for credit or lending decisions, or used to train generalized AI models.

7. Retention and deletion

There is no fixed retention period. Google data stored in Lisa's conversation history, memory notes, local files or logs is kept until the owner deletes it. Apart from routine rotation of some log files, Lisa has no automatic deletion schedule, and this policy does not promise automatic or immediate deletion.

Because the owner is Lisa's only user, deletion is done by the owner directly. The controls that currently exist are:

• deleting individual conversations, or pruning older conversations, from Lisa's conversation history on the server;
• erasing or editing Lisa's memory notes;
• deleting local files and logs on the server;
• deleting the stored Google credentials from the server;
• deleting messages in the Telegram chat using Telegram's own controls;
• managing data held by OpenAI through the ChatGPT account's data controls, subject to OpenAI's policies;
• removing backup copies from the backup repository. Until then, backups keep data that has been deleted elsewhere.

Deleting data from a database or file may not immediately remove every copy, for example from database journals, logs or backups.

8. Revoking Google access

The owner can revoke Lisa's access to Google at any time in Google Account settings, at myaccount.google.com/connections, by selecting Lisa and removing its access. Deleting the stored credentials from the server also stops Lisa's access.

Revoking access stops Lisa from accessing Google data from that point on. It does not, by itself, erase data Lisa has already stored, such as conversation history, memory notes, local files, logs, Telegram messages, data held by the AI provider, or backups. Those must be deleted separately, as described in section 7.

9. Changes and future integrations

This policy does not authorize future Google integrations. Before Lisa enables a new integration, accesses a category of Google data not described here, or materially changes how Google data is used or shared, this policy will be updated and, where applicable, Lisa will request a separate Google authorization so that the owner can consent to the change before it takes effect.

The effective date at the top of this page shows when the policy last changed.

10. This website

This website is a static information site. It has no logins or forms, and it uses no cookies, analytics, tracking or third-party embeds. It is hosted on Cloudflare, which processes standard technical information such as IP addresses in order to deliver and protect the site, under Cloudflare's own policies.

11. Contact

Questions about this policy or about Lisa can be sent to motovetal@gmail.com.