Lisa
Private assistant · single user

Lisa is a private personal AI assistant.

Lisa works for one person, its owner, through a private Telegram chat. It is not a public service: there are no sign-ups, no customer accounts and no other users.

How Lisa works

Lisa runs on a privately administered server and acts only on its owner's requests.

  1. The owner asksThe owner sends Lisa a request in Telegram.
  2. Lisa interprets itLisa uses an external AI model provider to understand the request and work out a response.
  3. Lisa acts, if authorizedIf the request involves a service the owner has connected, Lisa uses that service on the owner's behalf and replies in Telegram.

Google integrations

Lisa is designed to add integrations one at a time. Google Calendar is the only one currently being set up. Everything else in this section is a possibility, not something Lisa can do now.

Google Calendar

Currently being configured
  • Read the owner's schedule and answer questions about it, such as what is planned for a given day or when the owner is free.
  • Create and edit events when the owner asks.
  • Send invitations to the people the owner names, at the owner's request.

Optional future integrations

Gmail

Not enabled

Finding and summarizing the owner's personal emails, preparing replies, and sending messages when the owner authorizes it.

Google Contacts

Not enabled

Looking up people and their email addresses, for example to address an invitation or a message.

Google Tasks

Not enabled

Reading and managing the owner's personal tasks and task lists.

Drive, Docs and Sheets

Not enabled

Working with the owner's personal files, documents and spreadsheets, preferably through access to individually selected files rather than the whole Drive.

These are possibilities, not current capabilities. Lisa has no access to Gmail, Contacts, Tasks, Drive, Docs or Sheets, and does not request permission for any of them.

How permissions work

  • Each integration is enabled separately, and only if the owner chooses to enable it.
  • Lisa requests only the permissions needed for features that are implemented and enabled. It does not request permissions in advance for features that might be built later.
  • Mentioning a possible integration on this website does not give Lisa access to it.
  • Adding an integration requires a separate Google authorization step where applicable, and an updated privacy policy before the new access is used.

The Google permission Lisa currently requests

Lisa requests exactly one Google permission (OAuth scope):

https://www.googleapis.com/auth/calendar

Google describes this permission as: “See, edit, share, and permanently delete all the calendars you can access using Google Calendar.”

What the permission technically allows

It is a broad permission. It is not read-only, and it is not limited to events Lisa created. It covers every calendar the owner's Google account can access, including changing or deleting events and calendars and changing how calendars are shared.

What Lisa is intended to do with it

Read the owner's schedule, create and edit events, and send invitations when the owner asks. These limits come from how Lisa is built and operated. Google does not enforce them; Google enforces only the permission itself.

Privacy

To carry out a request, Lisa sends the relevant information, which can include calendar details, to an external AI model provider, and replies through Telegram. The privacy policy explains what data Lisa accesses, why, where it is processed and stored, who it is shared with, and how access can be revoked.

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.