Personal AI AssistantTelegram · MAX · browser
For entrepreneursFor executivesAI secretaryFor wedding and event planners
How it worksPriceArticles
Try it

Who it’s for

For entrepreneursFor executivesAI secretaryFor wedding and event planners

More

How it worksReviewsPriceFAQArticlesRussian
Log in to your account

Assistant Privacy Policy

Version of October 30, 2026 (English translation; the Google Photos section added on October 30, 2026)

This is a translation of the Russian version; in case of discrepancies the Russian version prevails.

In short

  • The assistant gets access to your Google Calendar, to the Google Drive files it created itself, and to the photos from Google Photos that you selected yourself. Only after you tap “Allow”.
  • The data is needed only to carry out your request. We do not use it for advertising, sale or training AI models.
  • The access key is kept on our server in a separate restricted folder. You can revoke it at any time.
  • People on our side do not read your Google data. There are three exceptions, listed in section 6.
  • You can turn off access and delete your data at any time: section 8.
  • From Google Photos the assistant receives only the pictures you selected yourself: it does not see your whole library. We delete the copies within 30 days: section 9.

1. Who we are

The “Personal AI Assistant” app (Личный ИИ-ассистент; the assistant) works in Telegram and, at your request, accesses your Google Calendar and Google Drive, as well as the photos you selected in Google Photos. The data is processed by sole proprietor Vitaly Andreevich Shirin (INN 860235728888, OGRNIP 321784700270216, St. Petersburg, Russia).

This page is the assistant’s privacy policy as regards Google data. What the assistant does with Google and which permissions it asks for: the app page.

2. What data we receive from Google

Only after you have signed in with Google and tapped “Allow”. We receive:

  • From Google Calendar: the names of your calendars and the events in calendars you own: title, time, location, participants. Only when you ask about them or ask to create an event.
  • From Google Drive: only the files the assistant created itself. The assistant does not see any other files on your Drive.
  • From Google Photos: only the photos and videos you selected yourself in the Google Photos picker. Details are in section 9.
  • Access key: a special code by which Google knows that you have allowed the assistant access. We do not receive or see your Google account password.

We do not request your email or contacts. The assistant does not see your whole Google Photos library.

Events sometimes contain data of other people — meeting participants. The assistant shows it only to you and only at your request. We process this data on your instructions and only to carry out your request (Part 3 of Article 6 of Federal Law No. 152-FZ). You are responsible to these people for the lawfulness of the processing.

3. Why we use this data

Only to carry out your request: show your schedule, create an event, save a file to your Drive or share it, receive the photos you selected and do with them what you asked for. There are no other purposes.

If a new purpose appears, we will first change this page and ask for your consent.

4. Where and for how long we store it

  • The access key is kept on our server in Russia, in a separate restricted folder of your assistant. Other clients and staff have no access to this folder.
  • We delete the key immediately when you disconnect Google. If you have not renewed your payment, we delete it 30 days after the end of the paid period.
  • We do not make permanent copies of your calendar data and files. So that a change can be undone, the assistant remembers what an event was like before it was edited or deleted: title, time, location, description. For files — only the name and version number, without the content. This record is deleted together with the access key. Deleted data disappears from the server backup within three days. Information that was needed for a reply remains in your conversation with the assistant on our server. It is kept together with the conversation and deleted at your request (section 8).
  • Files on Google Drive created by the assistant are stored by Google, not by us. They stay with you until you delete them yourself.

5. Who we share data with

We do not sell data. It is received only by: the language model provider and the image model provider (below), Telegram — as part of your conversation, and the people you yourself asked to share a file with.

Anthropic PBC (USA)

This is the developer of the language model that composes the assistant’s replies.

  • What it receives: your message and the information from your calendar, file or selected photo that is needed to reply to it.
  • Why: only to compose a reply to you. There is no other purpose.
  • What it does not receive: the Google access key and passwords. They are hidden from the model.
  • Training: models are not trained on your data. This setting is turned off in our account.
  • How long it keeps data: up to 30 days. If Anthropic’s safety system decides that a conversation violates the service rules — up to 2 years.

The data goes to the USA. Russian law does not recognize this country as ensuring adequate protection of personal data, so from there on the data is protected by the company’s own rules.

OpenAI (USA)

This is the developer of the model that creates images.

  • What it receives: only if you asked to make an image based on your photo or file — that picture or file as a reference, and the text of the request.
  • What it does not receive: access keys and passwords.
  • Training: data sharing for training is turned off in our OpenAI organization.
  • How long it keeps data: under its own terms for programmatic access.

The data goes to the USA; what this means is described above under Anthropic.

Services the work goes through

  • Telegram: your conversation with the assistant goes through it.
  • Timeweb (Russia): the hosting provider whose server the assistant runs on. It does not use the data.
  • Intermediate servers in Germany and the Netherlands: they pass the data through in encrypted form and cannot read it.

6. What we do not do and who sees your data

Data from your Google, we:

  • do not use or transfer for advertising;
  • do not sell;
  • do not transfer to data brokers;
  • do not use to determine creditworthiness;
  • do not use or transfer to create, train or improve AI models.

People on our side do not read your Google data. There are three exceptions:

  • you yourself asked for help with specific data;
  • it is necessary for security: for example, to investigate a failure or abuse;
  • it is required by law.

Only the administrator has full access to the server.

Limited Use disclosure. We comply with Google’s requirements for user data. The statement required by Google’s rules:

The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements. The use of information received from Photos APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

7. How we protect data

  • Connections with Google and between servers use secure channels.
  • The access key is hidden from the AI model and does not appear in logs or notifications.
  • The Google Photos access key is stored in encrypted form (AES-256).
  • Each assistant’s folder is protected by access rights from other clients and staff.
  • If data nevertheless reaches unauthorized persons, we will notify you and Roskomnadzor (the Russian data protection authority) within the time limits set by law.

8. How to turn off access and delete data

  • Turn off: tell the assistant to disconnect Google. We will delete the key immediately.
  • Revoke access in Google: open myaccount.google.com/permissions, select “Личный ИИ-ассистент” (Personal AI Assistant) and remove its access. There is a single entry for the whole app: removing it turns off Calendar, Drive and Google Photos at once.
  • Google Photos: tell the assistant to disconnect Google Photos. We will delete the key on our side immediately. If Calendar and Drive are not connected, we will also revoke access in Google ourselves (section 9).
  • Delete data: write to shirin.sur@yandex.ru and include your Telegram username so we can find your data. We will delete it within 7 working days and let you know. We will keep only the payment details: the law requires us to keep them for 5 years.
  • Find out what data we hold about you, or correct it: same address. We will reply within 10 working days.
  • If you are a participant in someone else’s meeting: decisions about your data are made by the calendar owner. Write to us and we will forward your request to them.

If you believe your rights have been violated, you may contact Roskomnadzor or a court.

9. Google Photos

Google Photos is connected separately from Calendar and Drive: also with “Sign in with Google”, and only after you tap “Allow”. The assistant asks for one permission — to see the photos and videos you selected yourself (Google calls it photospicker.mediaitems.readonly).

  • What the assistant receives: only the photos and videos you selected in the Google Photos picker, up to 200 at a time. It does not and cannot see your whole library, albums or other pictures. It does not change or delete anything in Google Photos.
  • How: it downloads what you selected to the restricted working folder of your assistant on our server in Russia: photos in original quality, videos as a copy. Google itself removes location data from photos. The assistant deletes the selection session in Google right after the download.
  • Why: only to do with these pictures what you asked for. The assistant does not recognize people in photos by their faces and does not group pictures by faces.
  • What Anthropic receives: the selected photos needed to reply to your request. From a video the model receives a few frames: the sound of the video is not transcribed, and the model does not watch the video file itself. The model does not receive the Google Photos access key.
  • What OpenAI receives: only if you asked to make an image based on your photo — that picture as a reference (section 5).
  • Storage: downloaded copies are kept in your assistant’s restricted folder for no longer than 30 days and are deleted automatically. The access key is kept there in encrypted form (AES-256) and is deleted right after you ask to disconnect Google Photos, or 30 days after the end of the paid period if you have not renewed. Deleted data disappears from the server backup within three days. What the assistant told you about the pictures stays in your conversation with it (section 4).
  • People in your photos are also people whose data we process: on your instructions (Part 3 of Article 6 of Federal Law No. 152-FZ) and only for your request. Select only pictures you are entitled to share.
  • What we do not do: everything in section 6 applies to Google Photos too. Pictures are not used for advertising, not sold, not transferred to data brokers, not used to train AI models, and people on our side do not look at them except in the three cases in section 6.
  • Turn off: tell the assistant to disconnect Google Photos — we will delete the key on our side immediately. If Calendar and Drive are not connected, we will also revoke access in Google ourselves. If they are, Google records the access together with them, as one app: you can remove it at myaccount.google.com/permissions, by selecting “Личный ИИ-ассистент” (Personal AI Assistant) and removing its access, but then Calendar and Drive will be turned off too. To delete downloaded copies earlier than 30 days, write to the address in section 8.

10. Zoom, Miro, Qtickets and Timeweb Cloud

If you have connected Zoom (a video meeting service), Miro (an online whiteboard service), Qtickets (a Russian ticket sales service for event organisers) or Timeweb Cloud (cloud servers), you create a key for the assistant in your own account and paste it on our page. We do not receive your password for the service.

  • What the assistant does in Zoom: at your request, it creates meetings and shows upcoming and past ones: the topic, time, duration and the link for participants. It does not read meeting recordings, transcripts or participant lists.
  • What the assistant does in Miro: at your request, it reads boards (the text of sticky notes, cards, frames and shapes) and adds or changes items.
  • What the assistant does in Qtickets: at your request, it shows your events, sales and guest list — read only. The AI model does not receive guests’ names, e-mail addresses or phone numbers. At your direct request the assistant can export the buyer list of your event as a file (names, emails, phone numbers). The AI model never sees the file; it is delivered to you in the chat, and no copy is kept in your assistant’s home for longer than 7 days. You are responsible, as the organiser, for any further use of this data. It does not issue refunds, create promo codes, edit events or write to guests.
  • The Qtickets token: it cannot be limited — it opens your whole organiser account. At the "view only" level the assistant only reads; with "full control" it acts on your commands, and refunds, deletions and bulk changes happen only after you press "Confirm". If you suspect a leak, issue a new token in Qtickets or contact their support.
  • Guests in Qtickets are other people: obtaining permission to process their data is the organiser’s responsibility. Information about guests that the assistant has shown you stays in the conversation history and is deleted together with it.
  • What the assistant does in Timeweb Cloud: on your commands, it creates, configures and deletes your cloud servers. Before any paid action (creating a server, changing a plan) and before deletion it shows what it will do and how much it costs, and waits for your "Confirm". You pay Timeweb yourself. How you use your servers is your decision and your responsibility.
  • What Anthropic (USA) receives: only the information needed to reply to your request, including what the assistant has read in Zoom, Miro, Qtickets or Timeweb Cloud. The model does not receive the key.
  • Storage and deletion of the key: the key is kept in your assistant’s restricted folder on our server in Russia. We delete it no later than the next working day after you tell the assistant to “disconnect Zoom” or “disconnect Miro”, immediately after “disconnect Qtickets” or “disconnect Timeweb”, and, if you have not paid for the subscription, 30 days after the end of the period. Requests to Zoom and Miro go through our intermediate server in Germany, which does not store the data; requests to Qtickets stay within Russia.
  • Request path to Timeweb Cloud: Requests to Timeweb Cloud and connections to your server go through an intermediary server in Germany, like requests to Zoom and Miro. The key is stored on our server in Russia; Timeweb responses (server number, address, status) are kept in a closed folder of your assistant; the action log contains no key or connection parameters.
  • Data on Miro boards: according to Miro, boards are stored in the EU (Ireland, Germany), but may also be processed in the USA. If your boards contain information about other people, you put it there and you are responsible for your right to share it; the assistant works with it only at your request.
  • Where the services are: Zoom Communications, Inc. and RealtimeBoard, Inc. (Miro) are companies from the USA. Qtickets is a Russian service. Timeweb Cloud is a Russian company.
  • Miro and Russia: Miro does not serve accounts from Russia and may close the account. The assistant contacts Miro through our servers outside Russia. Connect Miro only if you accept this risk.
  • Disconnect: tell the assistant “disconnect Zoom”, “disconnect Miro”, “disconnect Qtickets” or “disconnect Timeweb”. We will delete the Zoom and Miro keys no later than the next working day and the Qtickets and Timeweb keys immediately. You can also cut off access immediately in the service itself by deleting the app or issuing a new token.

11. Changes

A new version is published on this same page; the date is shown at the top. The assistant will notify you in advance of material changes.

12. Contacts

Questions and requests: shirin.sur@yandex.ru.

Operator: sole proprietor Vitaly Andreevich Shirin (INN 860235728888, OGRNIP 321784700270216, St. Petersburg, Russia).

Back to home · Connecting Google

Personal AI Assistant© 2026 Vitaly Shirin

Who it’s for

For entrepreneurs For executives AI secretary For wedding and event planners

Useful

All articles What is a personal AI assistant AI assistant vs ChatGPT How to build an AI assistant 10 executive tasks

Contact

Trial bot in Telegram Channel @vitaly_shirin_ai (in Russian) Reviews on Yandex Maps (in Russian)
Public offer (in Russian) Customer personal data policy (in Russian) Website privacy policy (in Russian) Assistant privacy policy Bot personal data policy “Invite Friends” program rules Connecting Google Russian

Provider: sole proprietor Vitaly Andreevich Shirin, OGRNIP 321784700270216, St. Petersburg, Russia. Contact: Telegram @vet091, email shirin.sur@yandex.ru.