Lanka privacy policy
This policy explains which personal data Lanka (lanka.bot) processes, why, who receives it and how long it is kept. Last updated on 24 October 2026. Every statement here describes what the service does today. When the service changes, so does the policy.
1. Who we are and our two roles
The service is provided by the Lanka team ("we"). For anything about your data, write to support@lanka.bot.
Lanka holds two kinds of data, and we play two roles:
- Bot owners' data: the people who sign in to Lanka and build bots. Here we are the data controller. Sections 2, 3 and 5 are about them.
- Bot visitors' data: the people who write to our users' bots. Here the controller is the bot's owner, and we process the data on their behalf as a processor. Section 4 is about them.
2. Bot owners' data
| What | Where from | Why |
|---|---|---|
| Telegram id, name, username, profile photo | Sign-in through Telegram | Your account and sign-in |
| IP address and time of your latest sign-ins | At sign-in | Account security |
| Bots: name, token from @BotFather | You enter them | So the bot works. The token is stored encrypted |
| Flows, texts, buttons, variables, broadcasts, panels, settings | You create them | Providing the service |
| Media: pictures and files you upload into flows | You upload them | The bot sends them to visitors. The files sit in public storage at an address known only to your bot and to whoever you show it to |
| Script secrets and payment provider tokens | You enter them | So your scripts and invoices work. Stored encrypted |
| Lanka API keys | You create them | Access to the API and the Claude Code plugin. We keep only a hash and the first few characters, for recognition |
| Connected apps: the AI chat's name, when it was connected and last used | You connect a chat | The chat's access to your bots (section 5). The tokens themselves are stored as hashes |
| Which editor page is open and its session name | While the editor is open | So an AI chat finds the page you are working on |
| Active visitors and messages sent per month | Automatically | Plan limits |
| Technical logs and error reports | Automatically | Finding and fixing failures |
The legal basis is the performance of a contract (providing the service under the Terms of use) and our legitimate interest in the security and reliability of the service.
We do not sell data or show ads. The only third-party analytics is Google Analytics, described in section 3.
3. Cookies and browser storage
- The session cookie keeps you signed in, and the "remember me" cookie keeps you signed in for up to two weeks. Lanka does not work without them, so they need no consent.
- The browser's local storage keeps the interface language, collapsed panels and similar display settings. It never leaves your device.
-
Google Analytics. On the site and in the owner's app we count visits with Google Analytics: which pages are opened, where the visit came from, the device and browser type, the approximate city from the IP address, and a few events such as an access request, a sign-in and the first bot created. Google Analytics sets the
_gaand_ga_*cookies for up to two years and does not store the IP address. The counter starts only after your consent in the cookie banner, and does not load without it. You can withdraw consent in the same banner, or switch off the collection on every site with Google's browser add-on. There is no analytics in the bots or the Mini Apps. - Google Maps. The "Location" step in the editor shows a Google map. When you open such a step, your browser connects to Google's servers, and Google sees your IP address under its own policy. Bot visitors never load the map.
There are no other cookies, advertising ones included.
4. Bot visitors' data
When a person writes to a bot built in Lanka, Lanka stores:
- data from Telegram: id, name, username, language, the Telegram Premium flag;
- messages in both directions, button presses, answers to questions;
- variables the bot's flows record (for example a phone number, an address or an order, when the bot's owner asks for them), the state of the conversation, audience membership;
- data the visitor submits in the bot's Mini Apps;
- payments in the bot: the amount, the currency, Telegram's payment identifiers, the refund status. Card data never reaches Lanka. Telegram and the bot owner's payment provider handle it;
- access to closed channels and groups the bot granted or revoked.
What the bot collects is the owner's decision. We process this data only to run the bot as its owner configured it, and never for our own purposes. The owner sees this data in Lanka, can correct or delete it, and answers to visitors as the controller.
Visitors: for questions about your data, contact the bot's owner. If you cannot reach them, write to us at support@lanka.bot. We will pass the request on to the owner, or help where we can.
5. AI chats
You can connect an AI chat (Claude on claude.ai, ChatGPT or another) to Lanka. It works through the MCP server at https://lanka.bot/mcp and the OAuth protocol. Only you can do this, on Lanka's consent page.
A connected chat can, on your behalf:
-
read the list of your bots, their flows with steps and texts (published and drafts alike), the bot's
app.*data values, panels, broadcasts, linked channels, Mini Apps, and which editor page you have open; -
write flow drafts, the bot's
app.*data values, panels and broadcast drafts, upload pictures by link, and delete what you confirm to it. Flow and broadcast drafts never reach visitors until you publish or send them in Lanka yourself. The bot'sapp.*data and panels change at once.
Whatever the tools return to the chat goes to its provider (Anthropic, OpenAI or another), which processes it under its own terms. We send it nothing ourselves. Data leaves only in answer to requests from the chat you connected. The chat's tools never hand out bot visitors' messages or personal data.
You can disconnect a chat any time on the Integrations page, under "Connected apps", or in the chat's own settings. Its tokens stop working at once. A chat's access token lives one hour and is renewed while the connection stands.
6. Who receives data
Only the providers Lanka cannot run without:
| Who | What for | Where |
|---|---|---|
| Hetzner Online GmbH | The server and the database | Finland (EU) |
| Cloudflare, Inc. | DNS and the R2 storage for media and encrypted backups | Global network, under Cloudflare's policy |
| Functional Software, Inc. (Sentry) | Error reports. We send no IP addresses, cookies or request bodies there | Germany (EU) |
| Telegram | The platform the bots' messages and the sign-in go through | Under Telegram's policy |
| Google LLC | Google Analytics: visit statistics for the site and the app (section 3), only with your consent | USA, a participant in the EU-U.S. Data Privacy Framework, under Google's policy |
Three transfers depend on your choices, and you answer for them as the bot's owner:
- scripts in your flows send data to the third-party services you configured;
- payments in the bot go through Telegram and the payment provider you connected;
- an AI chat receives what its tools return (section 5).
We disclose data to public authorities only on a lawful request.
7. How long we keep data
- Account and bot data: as long as the account exists.
- A visitor's data: as long as the bot exists, or until the owner deletes the visitor. Deleting a visitor deletes their messages too.
- After a bot or an account is deleted, the data leaves the database at once and the backups within 30 days, when the copy expires.
- Database backups: daily, encrypted, kept for 30 days.
- Server logs live no longer than the application container, which is replaced on every update. We keep them nowhere else.
- Error reports in Sentry: 90 days, Sentry's setting.
- Google Analytics statistics: 14 months, our setting in Google.
- Connected chats' tokens: until you disconnect the chat. An access token expires after an hour.
Bots, visitors and connected apps the owner deletes themselves. To delete your account entirely, write to support@lanka.bot. We do it within 30 days.
8. Security
Connections are HTTPS only. Bot tokens, script secrets and payment provider tokens are encrypted in the database. API keys and connected chats' tokens are stored as hashes. Backups are encrypted before they are uploaded, and the key to them is kept away from the server. Only Lanka's administrators have access to the server and the database.
9. Your rights
You can ask for access to your data, a copy of it, its correction or deletion, a restriction of processing, or object to it. Write to support@lanka.bot. We answer within 30 days.
If you believe we violate your rights, you can complain to the Ukrainian Parliament Commissioner for Human Rights, or, if you are in the EU, to the data protection authority of your country.
10. Children
Lanka is meant for people aged 18 and over. The owner of a bot aimed at children is responsible for parental consent where the law requires it.
11. Changes
We announce material changes to this policy at least 30 days ahead, in Lanka or through Telegram.