Privacy Policy
Last updated: July 2026
This Policy explains how Товарищество с ограниченной ответственностью "GeoAxis", the company operating the Tindavo platform ("we"), processes personal data when you use our website and SI assistant platform. Customer data is stored in the European Union and processed under the GDPR.
1. Data we collect
Account data (name, email, company), billing data, usage data and technical logs, and what you send through the platform: messages and uploaded knowledge-base files. We do not sell personal data.
2. How we use data
To provide and run the service, sign you in, take payments, generate assistant replies, prevent abuse, comply with the law and — only with your consent — for analytics and product emails.
3. Legal bases
Contract performance, our legitimate interests, legal obligations and your consent (for non-essential cookies and marketing).
4. Who helps us process data (sub-processors)
Where we have a data-processing agreement (DPA) with a provider, processing follows it; otherwise the provider’s terms of service and privacy policy apply. In particular, Vercel (its DPA does not cover our current plan) and DeepSeek (its API terms include no DPA) process data without a DPA. SI providers use content only to produce a reply and, under their API terms, do not train models on it. A new provider is added to this list before it starts processing data.
| Vercel (US, servers in the EU) | hosting of the website, dashboard and API. |
|---|---|
| Neon (US, database in the EU) | database: accounts, assistants, conversations, knowledge base. |
| Cloudflare R2 (US, storage in the EU) | your knowledge-base files and daily database backups (the last 30 copies), which also contain conversations and customer contact details. |
| GitHub (GitHub, Inc., US) | daily database backup: a full copy of the database is created and test-restored on GitHub’s servers in the US; the copy itself is stored in Cloudflare R2. |
| Upstash (US, servers in the EU) | cache of the latest messages of an active conversation, request limits. |
| Clerk (US) | sign-in and account management: name, email, session data. |
| Anthropic (US) | the model that writes assistant replies: the question, conversation context, knowledge-base fragments. |
| DeepSeek (PRC) | the model that writes assistant replies: the question, conversation context, knowledge-base fragments. |
| OpenRouter (US, plus the country of the model’s hosting provider) | a backup route to the same model when DeepSeek is unavailable: the question, conversation context, knowledge-base fragments. |
| OpenAI (US) | knowledge-base search: fragments of your documents and the search query. |
| Cohere (Canada / US) | ranking of search results: the query and candidate fragments. |
| Inngest (US) | background job queue: inbound channel messages and document processing. |
| Langfuse (Germany, servers in Ireland, EU) | model call log: question, answer, quality metrics. |
| Sentry (Functional Software, Inc., US) | error monitoring: technical identifiers and error metadata, no message text; an error report may include a customer’s phone number or messenger account ID (for example, a WhatsApp number). |
| PostHog (US) | product analytics in the dashboard: the owner’s actions in the interface and technical identifiers; customer conversations never reach it. |
| Resend (US) | emails from the service: recipient address. |
| Paddle (Paddle.com Market Ltd, United Kingdom) | payment operator: billing and invoicing data; card details never reach us. |
| Meta Platforms Ireland (WhatsApp Cloud API, Messenger Platform, Instagram Messaging) | only if you connect WhatsApp, Messenger or Instagram: messages between a customer and your assistant, the customer’s page-scoped identifier and, for Messenger and Instagram, the identifiers of your Facebook Page and Instagram account. |
| Google LLC (YouTube Data API) | only if you connect YouTube: the id and title of your channel, public comments under your videos (author name, text, time), draft replies and the replies you approve; the access token to your channel is stored encrypted. Tindavo’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. By connecting YouTube you also agree to the YouTube Terms of Service (https://www.youtube.com/t/terms); Google’s privacy policy: https://policies.google.com/privacy. You can revoke access at any time in Tindavo (Channels → YouTube → Disconnect) or at https://myaccount.google.com/permissions. |
| Telegram (Telegram FZ-LLC, UAE) | only if you connect Telegram: messages between a customer and your assistant; if you connect the owner’s Telegram bot — notifications to you about customers from any connected channel (for example, WhatsApp): name, phone number, the question and request details, and your replies to them. |
| Twilio (US) | only if you connect a phone number: the caller’s number and the call recording. |
| Your browser’s push service (Google, Apple or Mozilla, depending on the browser) | only if you enable notifications: the subscription address and the notification text. |
5. Where data is stored
Core customer data — the database, files, cache and model log — is hosted in the European Union. Some providers above — in particular Sentry, GitHub, the SI providers (including OpenRouter) and Paddle — operate outside the EU/EEA, including in the United States and the People’s Republic of China; where we have a data-processing agreement with such a provider, the transfer is covered by it with the safeguards the GDPR requires (see section 4).
6. How we protect data
All traffic to tindavo.com, the dashboard, the chat page and our APIs is encrypted in transit (HTTPS/TLS). The database and files are hosted in the European Union by providers that encrypt stored data at rest. Access tokens of the accounts you connect (Google / YouTube, Meta, Telegram) are additionally encrypted by us (AES-256-GCM) before they are stored and are used only by our servers for the actions you have enabled. Each business’s data is separated at the database level (row-level security), so one account cannot read another account’s data. Staff access is limited to operator tools with separate access keys, and every operator action is recorded in an audit log. Google user data (your YouTube channel id and title, public comments under your videos, draft replies and the replies you approve) is used only to show you the comments, prepare draft replies and publish the replies you approve. To prepare a draft, the comment text is processed by the model and search providers listed in section 4 — only for this purpose; a reply is published only after you approve it. We do not sell Google user data, do not share it with advertisers or data brokers, do not use it for advertising and do not use it to train language or other machine-learning models; we transfer it to third parties only as needed to provide these features or when required by law. Comments, drafts and approved replies are kept for 12 months and are deleted earlier together with your account. When you disconnect YouTube, we revoke our access at Google and stop reading your comments.
7. Your rights (GDPR)
If you are in the EU/EEA, you may request access to your data, its correction, deletion, restriction of processing and portability, object to processing, and lodge a complaint with a supervisory authority. Write to us at the address below.
8. How long we keep data
We delete data automatically once its period expires: conversations with the assistant — 12 months after the last message; customer profiles and enquiries — 24 months; phone call recordings — 90 days; the answer cache — 30 days. Bookings and the payments linked to them are kept longer: they are primary accounting documents, and their period is set by the legislation of the Republic of Kazakhstan. Backups — the last 30 daily copies, older ones are overwritten. To delete your account with all its data, write to admin@geoaxis.kz from the address linked to the account — the procedure is described on the “Data deletion” page.
9. Contact
For privacy questions, to exercise your rights and for deletion requests, email admin@geoaxis.kz. The data operator is Товарищество с ограниченной ответственностью "GeoAxis", BIN 260840022626, Казахстан, город Астана, район Есиль, Проспект Ұлы дала, дом 71, 010000.