AI SecretaryPrivacy policy
Version of 3 November 2026
This page describes what data the AI Secretary service (a Telegram bot and the app inside it, “the service”) processes, why, who receives it, how long we keep it and how to delete it. The policy covers two groups of people: owners, who connected the bot to their Telegram account, and contacts, who write to an owner in Telegram.
1. Who processes the data
Data controller: LazaPlaza LLC, registration No. 10105884, 8 The Green, Suite A, Dover, Delaware 19901, USA (“we”). For questions about data, write to [email protected]. Questions about payments and refunds go to the /paysupport command in the bot.
We control owners’ data. We process contacts’ messages and bookings on the owner’s behalf: the owner decides which chats the bot can see and can delete them at any time.
2. What data we process
Owner data
- Telegram ID, name, app language, time zone;
- bot settings and the knowledge base: services, prices, address, schedule, answers to common questions, topics the bot does not answer;
- the fact, date and version of consent to data processing;
- payment details for the subscription in Telegram Stars or by card through Stripe: payment ID, amount, paid period, and for Stripe payments also the email for the receipt. We do not receive bank card details;
- voice messages, photos and price list files the owner sends for the knowledge base: voice messages are turned into text, photos and files are read by the model. The recordings and files are not kept after processing, only the text the owner confirmed stays;
- the source tag that brought you to the bot (for example, this website);
- “Bad answer” marks, the answer to the survey about the bot’s usefulness and connection events (mode choice, questionnaire, first booking, payment): we use them to improve answers and to see at which step owners stop;
- if the owner connected a Click account: its Service ID, Merchant ID and Secret key. They are stored encrypted with the owner’s key and are only used to check Click notifications about prepayment.
Contact data
- Telegram ID, name and app language;
- message texts in the chats the owner opened to the bot in their Telegram profile. The bot does not see the owner’s other chats or phone numbers;
- voice messages, video notes and audio in AI Secretary mode: the service sends the recording for recognition and keeps only the text. The recording itself is not kept; the text is kept like other messages;
- requests and bookings: name, service, date and time, contact details if the contact gave them; visit marks and the owner’s notes in the client card;
- if the contact tapped “Remind me” and started the reminder bot: their Telegram ID in that bot and the link to their bookings, to send reminders;
- if the contact paid a deposit through the owner’s Click account: the Click transaction number, amount and status. Click receives the card details; the service does not see them.
Owner’s calendar
If the owner connected Google Calendar, the service only receives busy time from the main calendar, without names, descriptions or guests of meetings. Before each booking the service asks for busy time again, so as not to book a client into time that was just taken. The service adds client bookings to a separate calendar that it creates itself. The service uses data received through Google APIs only to book clients and does not pass it to third parties, except in the cases described in this policy. This use complies with the Google API Services User Data Policy, including the Limited Use requirements.
Service data
Technical logs, metrics and analytics events. They contain no message texts: only IDs, time, event type, usage and errors.
This website
The mooveup.co/bot website does not set cookies and does not use visitor counters. The website hosting keeps standard request logs.
3. Why we process data
- so that the bot can reply to contacts on the owner’s behalf, book, reschedule and cancel their visits, send reminders and pass difficult questions to the owner;
- to send the owner notifications and a daily summary;
- to recognise voice messages, process the owner’s price list and voice messages for the knowledge base, and take prepayment for bookings to the owner’s account if the owner connected it;
- to keep track of the subscription, limits and refunds;
- to find errors, protect the service from abuse and answer support requests.
We do not use data for advertising, do not sell it and do not pass it on for purposes unrelated to the service. The legal basis is the owner’s consent, given with the “I agree” button before starting, and the performance of the subscription contract. Without consent the bot doesn’t reply to anyone.
4. Who receives data
| Recipient | What and why | Where |
|---|---|---|
| Telegram | Message delivery, payments in Stars | under Telegram’s rules |
| Anthropic | Only in AI Secretary mode: the incoming message text, earlier messages of the chat and the knowledge base, to write a reply; photos and price list files the owner sends for the knowledge base. Model training on this data is turned off | USA |
| DigitalOcean | Servers, database, backups and the deletion log | Germany (Frankfurt) |
| ElevenLabs | Only in AI Secretary mode: contacts’ voice messages and the owner’s voice messages for the knowledge base, to recognise the text. Training on this data is turned off in the account settings | USA |
| Only if the owner connected Google Calendar: busy time and booking events | under Google’s rules | |
| The owner’s calendar server (Apple, Google and others) | Only if the owner subscribed their calendar to the link from the app: service, time and client name in bookings | under that service’s rules |
| Click | Only if the owner connected their account: deposit amount and number. The contact makes the payment on Click’s side | Uzbekistan |
| Stripe | Only if the owner pays for the plan by card through a link instead of Stars: amount, email for the receipt. Stripe receives the card details; the service does not see them | USA and EU |
| Monitoring services (Sentry) | Errors and metrics without message texts | Germany (EU) |
Data is stored outside Uzbekistan. By accepting the terms in the bot, the owner agrees to this cross-border transfer. In the free redirect mode, messages are not passed to anyone except Telegram.
5. How long we keep data
| Messages | 30 days, then deleted automatically |
|---|---|
| Voice recordings | not kept: only the recognised text, like other messages |
| Photos and price list files | not kept after processing: the knowledge base text stays |
| Bookings | 12 months after the visit |
| Client cards | 30 days after the client’s last message; if the client had a booking, 12 months after it |
| Requests | 90 days |
| Link to the reminder bot | while the client card exists (up to 12 months after the last booking) or until the contact blocks the bot |
| Prepayment data | like the booking: 12 months after the visit |
| Click account keys | until the owner turns off prepayment or deletes their data |
| Knowledge base and settings | while the owner uses the bot |
| Service data without texts | up to 12 months |
| “Bad answer” marks and the survey | 90 days |
| Database backups | 14 days |
| Consent and payments | kept after the account is deleted: they are needed for accounting |
If the owner turned off the bot in their Telegram profile, the data is deleted after 30 days, and the bot warns 3 days before. After deletion, data disappears from backups within 14 days. If the database is ever restored from a backup, deleted accounts are removed again before launch.
6. How we protect data
- message texts, names, contact details and the knowledge base are stored encrypted, and each owner has their own key;
- all connections use TLS;
- message texts do not go into logs, metrics or analytics;
- our staff do not read messages. The owner can open access for support for 24 hours to look into a problem, and every view is logged.
7. Your rights
The owner can at any time:
- see the consent version and access settings: the /privacy command;
- correct the knowledge base and settings in the bot or in the app;
- export the knowledge base and requests to a file: /privacy → “Export data”, once a day;
- pause the bot (/pause) or turn it off in their Telegram profile;
- delete all data with the /delete_my_data command: the bot goes quiet at once, the data is deleted within 24 hours, and then a report comes.
A contact can ask the owner to delete the messages and booking or write to us at [email protected]: we will delete their data from that owner’s account and tell the owner.
If you think we have violated your rights, write to us. You also have the right to contact the personal data protection authority of your country.
8. Age
The service is for businesses. Only adults can connect the bot.
9. Changes to this policy
If we change how we process data, the bot tells the owner and asks them to accept the new version of consent. The version date is at the top of the page.
10. Contacts
LazaPlaza LLC, registration No. 10105884, 8 The Green, Suite A, Dover, Delaware 19901, USA. Email [email protected].