1. Who processes the data
Operator / Betreiber: AiKlient is operated by a private individual based in Rīga, Latvia; registration as a self-employed person is in progress. Contact: info@aiklient.com or @aiklient_bot (opens in a new tab) in Telegram.
For the data of the professionals who use the service (account holders) we are the data controller. For the data of their clients we are a processor: that data belongs to the professional, who decides what is collected and why; we store and process it only on their instructions, under the data processing agreement in section 5 of the Terms of Service.
2. What data we process
| Whose | What | Why |
|---|---|---|
| The professional's account | Telegram ID, Telegram username and name; email address and name from Google if you sign in with Google; phone, if given in the bot; language; bot, service and schedule settings | Running the account, login, notifications, subscription |
| Google Calendar connection (optional) | Encrypted access key to your Google account, the email address of the connected Google account, the ID of the “AiKlient” calendar we create, and busy intervals of your primary calendar for the next 60 days (start and end only — no titles, descriptions, places or attendees) | Showing your bookings in your Google Calendar; not offering clients the times when you are busy (section 11) |
| The professional's invoicing details | Business name, registration number, VAT number, IBAN, address — only if you enter them | Generating invoices for your clients; our own invoices to you |
| The professional's acceptance of the terms | Date and version of the terms accepted | Proof of the contract |
| Their clients' | Name, Telegram chat ID or WhatsApp number, phone; at the professional's choice — email, address and notes; bookings and booking history; a review, if the client writes one in the bot | Booking an appointment, reminders, contact between professional and client |
| Their clients' opt-out | The "do not send" flag when a client declines "time to book again" and review requests | Honouring the client's refusal of messages |
| Bot conversation logs | Text of the client's messages to the bot, buttons pressed, the bot's replies (including replies generated by AI from the professional's data), chat ID, time | The professional sees what clients ask and what the bot answers; handling complaints; quality control of bot replies by the operator |
| Support requests | Text of the request, attachments (png, jpg, webp, pdf), who sent it and when | Helping the professional |
| Technical | Times of requests to the service, errors, message identifiers (container logs) | Availability, troubleshooting, protection against abuse |
We do not collect health data, payment cards or identity documents. Payments for the professional's services go directly to them — card details never pass through the service.
3. AI answers
If the professional switches on AI answers, the text of a client's question, together with the professional's public data (services, prices, hours), is sent to Anthropic PBC (USA) to generate a reply. Anthropic does not use this data to train its models. The reply and the question are stored in the conversation log (section 2) and deleted automatically after 90 days. The professional can switch AI answers off at any time.
4. Legal bases
- Performance of a contract (Art. 6(1)(b) GDPR) — to provide the service the professional registered for.
- Legal obligation (Art. 6(1)(c) GDPR) — keeping invoicing details and issued invoices for the period required by accounting law, and honouring a person's opt-out from messages (ePrivacy Directive 2002/58/EC and the national law implementing it).
- Legitimate interest (Art. 6(1)(f) GDPR) — security, troubleshooting, protection against abuse, proof of the contract, encrypted backups.
- Instructions of the controller (Art. 28 GDPR) — for the clients' data and conversation logs; the professional ensures the collection is lawful and informs their clients.
5. Who we share data with and transfers outside the EU
We do not sell data and do not share it for advertising. Data passes through the providers the service cannot work without:
- Telegram Messenger Inc. — delivery of bot messages (message text, chat ID). On the sign-in page (/app/login) the Telegram login widget is loaded from telegram.org, so Telegram receives your IP address and browser version when the page opens. Telegram's servers are partly outside the EU; the transfer is necessary to provide the service you asked for through Telegram (Art. 49(1)(b) GDPR).
- Meta Platforms Ireland Ltd — WhatsApp, if the professional uses that channel (message text, phone number). Meta may process data in the USA under the EU–US Data Privacy Framework and the European Commission's standard contractual clauses.
- Anthropic PBC (USA) — the text of a client's question, only when AI answers are enabled (section 3). Transfer under a data processing agreement and the European Commission's standard contractual clauses; the data is not used to train models.
- Google Ireland Ltd — four uses: (a) Google Sign-In: if you log in with Google, we receive your email address and name, and Google learns that you use AiKlient; (b) email: notifications and invoices to professionals are sent from info@aiklient.com through Gmail, so Google processes the recipient address and the message; (c) Google Drive: encrypted backup copies only — archives are encrypted on our server before upload (AES-256), the key never leaves us, so Google cannot read them. (d) Google Calendar: only if you connect it, see section 11. Google may transfer data to the USA under the EU–US Data Privacy Framework and standard contractual clauses.
- Revolut — subscription payments by professionals are made through a Revolut checkout link. Revolut processes the payment data as an independent controller under its own privacy policy; we only see the payer's name, amount and the reference code you enter.
The data itself is stored on a server in Latvia, in the European Union. The public website loads no scripts or fonts from third-party networks.
6. How long we keep it
| Data | Period |
|---|---|
| Professional's account, settings, clients' data, support requests | For as long as the account exists. "Delete account and all data" in the web account deletes it immediately; a request by email is fulfilled within 30 days. Backup copies are overwritten within 60 days. |
| Invoicing details and issued invoices | For the period required by accounting law (in Latvia currently 5 years), even after the account is deleted. |
| Bot conversation logs | 90 days, then deleted automatically; immediately when the account is deleted. |
| A client's data at the client's request | Deleted immediately when the client chooses "Delete my data" in the bot (/privacy) or the professional deletes the client card. |
| Technical logs | Rotated automatically — days, not months. |
| Google Calendar connection | While the calendar is connected. “Disconnect” in the web account or deleting the account deletes the access key, the busy intervals and the account email at once and removes the “AiKlient” calendar from your Google account; if you revoke access at Google, the key and the busy intervals are deleted at the next sync, within minutes. |
If the subscription lapses, the data is kept so that access can be restored; it is deleted on the professional's request as above.
7. Your rights
By law you may: obtain a copy of your data, correct it, delete it, restrict processing, object to it, and receive your data in a machine-readable form.
Professionals can correct their data in the web account and delete the account themselves (More → "Delete account and all data"). A copy of the data in JSON form is sent on request by email.
Clients of a professional can see their bookings in the bot ("My bookings"), delete their data themselves (/privacy → "Delete my data") and opt out of "time to book again" and review requests (/privacy → "Stop these messages", or /stop; the button is in every such message). Other requests go to the professional — it is their data. If a request reaches us, we pass it on and help technically.
Requests: info@aiklient.com. We answer within 30 days. If our answer does not satisfy you, you may lodge a complaint with the Latvian Data State Inspectorate (Datu valsts inspekcija, dvi.gov.lv (opens in a new tab)) or with the supervisory authority in your own country.
8. Security
Connections to the website, the web account and the bot are encrypted (HTTPS). Login is without passwords (Telegram Login or Google), session cookies are signed and protected against cross-site requests, every request to data is filtered by the professional's account. Server access is restricted to the operator; backups are made daily and leave the server only in encrypted form. The operator may log into a professional's account for technical support — every such login is recorded in a log and the professional sees a notice in the account.
9. Cookies and local storage
There are no advertising trackers. Visit statistics for the public website are collected by our own Umami instance on our server in the EU: no cookies, no identifiers, the IP address is not stored, only anonymous aggregates (page, country, device type, referrer). The public website sets nothing in your browser until you choose a language or colour theme; the web account uses only the cookies needed for login:
| Name | Type | Purpose | Lifetime |
|---|---|---|---|
| aik_session | Cookie (HttpOnly) | Signed login session of the web account | 30 days |
| aik_in | Cookie | Flag "logged in" (value 1, no personal data) so the website can show "Open account" instead of "Log in" | 30 days |
| aik_out | Cookie (HttpOnly) | Flag "logged out on this device" (value 1): the next login from this device asks for confirmation in Telegram | 1 year |
| aik_nonce | Cookie (HttpOnly) | Random token binding the login to the browser that opened the sign-in page | 30 minutes |
| aik_next | Cookie (HttpOnly) | The page of the web account you opened before signing in, to return you to it after login | 15 minutes |
| lang | localStorage | Language you chose on the website or in the account | Until you clear browser data |
| theme | localStorage | Light or dark theme you chose | Until you clear browser data |
These are strictly necessary for the service you requested, so no consent banner is shown (Art. 5(3) ePrivacy Directive).
10. Changes
If this policy changes, we will update the date at the top and notify professionals in the bot or by email at least 14 days before the changes take effect.
11. Google Calendar and Google user data
Connecting Google Calendar is optional. A professional can do it in the web account: Calendar → “📅 Google Calendar” → “Connect Google Calendar”. We then ask Google for two permissions only:
- Make secondary Google calendars, and see, create, change and delete events on them (
calendar.app.created). We create one calendar named “AiKlient · business name” in your Google account and keep your bookings in it: client name, service, staff member, time, status and a link to the booking in AiKlient. This permission does not let us see or change your other calendars or events. - View your availability in your calendars (
calendar.freebusy). We read only the busy and free intervals of your primary calendar for the next 60 days — no titles, descriptions, places or attendees — so that the bot does not offer clients the times when you are busy.
We also receive the email address of the Google account you connect, to show you which account is connected.
How we store it. The access key (refresh token) is stored encrypted on our server in Latvia (EU). Busy intervals are kept only for the next 60 days and refreshed every few minutes. The calendar ID and the account email are kept while the calendar is connected.
Use and sharing. We use Google user data only to provide the calendar features described above. We do not sell it, do not share it with third parties, do not use it for advertising and do not use it to develop, improve or train generalized artificial-intelligence or machine-learning models. Nobody reads it, except with your permission when you ask for support, for security reasons, or where the law requires it.
Disconnecting and deletion. “Disconnect” in the web account removes the “AiKlient” calendar from your Google account, revokes our access at Google and deletes the access key, the busy intervals and the account email from our server immediately. Deleting your AiKlient account does the same. You can also revoke access at any time in your Google Account settings (myaccount.google.com/permissions (opens in a new tab)).
AiKlient's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (opens in a new tab), including the Limited Use requirements.