Privacy Policy
Socrat: the Telegram bot @socratesaiai_bot and the website socrat.surf. Personal data controller: the owner of the Socrat service (legal name, registration code and address to be added).
Data questions: @som_mos_oms on Telegram.
Contents
Google user data
Connecting a Google account is optional. If you connect one, Socrat asks Google for access to the following and uses it only to do what you ask in the chat:
- Gmail (
gmail.modify): reads new mail to tell you in one sentence who wrote and what they want, finds and summarises messages when you ask, and prepares reply drafts. It sends, archives or labels a message only on your command. - Google Calendar (
calendar): shows your events and creates or changes an event when you ask. - Google Drive (
drive.file): only the files you open with Socrat or that Socrat creates for you. - Google Sheets (
spreadsheets): reads and edits the spreadsheets you point it to. - Your e-mail address (
userinfo.email): to show which account is connected.
What we keep. The access tokens, encrypted with AES-256-GCM, and, for mail, the messages the assistant has processed and the drafts it prepared. Whatever the assistant reads from Google at your request becomes part of your conversation with it (the answer and the result of the action) and is kept and deleted like the rest of the conversation: see sections 12, 15 and 16.
Who receives it. To write a summary, an alert or a draft, the necessary text is sent to the language model named in section 14, only on hosts that keep nothing after answering (zero data retention). We do not sell Google user data, do not use it for advertising, and do not use it to develop, improve or train generalised AI or machine-learning models.
People. No one on our side reads your Google data, unless you ask us to look into a problem and agree to it, it is needed for security (for example, investigating abuse), or the law requires it.
Socrat's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Disconnecting. /disconnect_google (or /apps → Google) removes the tokens from our server at once; you can also revoke access in your Google Account under Security → Third-party apps and services. /delete_account deletes everything the bot keeps about you.
12. Data we process
- Telegram: ID, name, username, language. Telegram does not give bots your phone number, IP address or location — we get them only if you send them.
- Messages — yours and the bot's replies, with the results of the bot's actions (searches, work with files and services).
- Files: documents, photos and videos you send or the bot creates; text extracted from them, descriptions and tags.
- Voice and video notes — only the recognised text. The recording itself is deleted after recognition.
- Memory about you: facts the bot picks out of conversations itself — work, family, pets, addresses, contacts, plans, preferences, and if you write about them, health and emotional state. These are sensitive data.
- Search indexes — numerical representations (embeddings) of your messages and files for searching memory.
- Vault and cards: documents, passwords, PINs and card details you ask the bot to keep. They are encrypted with AES-256-GCM, and every decryption is logged. Once they are saved, the bot deletes the message you sent them in from Telegram and replaces it with a placeholder in the history, the message log and the search index.
- Connected services you connect: Google tokens (Gmail, Drive, Sheets, Calendar), API keys and app passwords for email, Notion, Slack, Monobank, your own AI keys, MCP server headers. Encrypted with AES-256-GCM.
- Email: messages the bot processes and reply drafts.
- Telegram Business: if you connect the bot to your business account — messages in those chats in both directions, with the other people's names and usernames. Kept only after you have accepted these terms.
- Groups: group messages the bot receives, member names, group memory.
- Payments and credits: the fact, amount and ID of a payment, balance and spending.
- Consent: time, terms version, your Telegram ID, username and name.
- Message log: messages the bot received and sent in the last 30 days. A private chat gets there only after your consent, secrets typed during a step-by-step service connection never.
13. Purposes and legal bases
- Performance of the agreement — answers, memory, files, search, integrations.
- Your consent — sensitive data (health, emotional state) and transfers outside Ukraine.
- Legitimate interest — security, abuse prevention, investigating failures.
- Legal obligations — payment records.
We do not sell data, show ads, use advertising or analytics trackers, or train our own models on your data.
14. Who receives data
To carry out a request, the necessary part of the data goes to:
- Telegram — message delivery.
- OpenRouter (USA) and the models it routes requests to. Answers, memory, chat thread titles, file and photo descriptions, summaries and email drafts are currently produced by a language model hosted on Google Cloud (Vertex AI); when it is unavailable, by a fallback model hosted by Inceptron or Baseten (USA). Also via OpenRouter: Perplexity — embeddings, Voyage AI — ranking, Microsoft and Mistral — speech recognition, OpenAI — text-to-speech (when enabled), Recraft, Google and xAI — images, Cloudflare — PDF parsing.
- Search: Keenable (web) and Serper (images) — receive search queries written by the bot.
- Maps and weather: Open-Meteo, MET Norway, OpenStreetMap — coordinates or a place name when you ask about them.
- Telegram Stars and Crypto Pay — payment; Crypto Pay receives your Telegram ID in the invoice.
- Services you connect (Google, email, Notion, Slack, Monobank, MCP servers) — only what the task needs.
- Websites the browser agent visits for your task receive what the agent types into them.
Requests to the language models that write the answers (main and fallback) go only to zero-data-retention (ZDR) hosts: the host keeps no request after answering. Speech recognition (Microsoft, Mistral), Perplexity embeddings and Google images currently work the same way. Without zero retention, under the providers' own policies: Voyage AI ranking, Recraft and xAI images, OpenAI text-to-speech, Cloudflare PDF parsing, search. Providers operate in various countries, including the USA. By tapping «Accept» you consent to these transfers.
Text recognition in photos and scans (OCR) and image background removal run on our server, without sending anything out.
15. Retention
- Temporary files — up to two hours; browser agent sessions close after about 30 minutes idle.
- The message log — 30 days. Everything else — while you use the Service or until deleted (section 16).
- Payment records are kept as long as accounting requires, even after account deletion.
16. Your rights and deletion
You can find out what data about you we process, get a copy, have it corrected, restrict or object to processing, withdraw consent (this does not make earlier processing unlawful) and request deletion. Complaints: the Ukrainian Parliament Commissioner for Human Rights; in the EU, your national data protection authority.
- /profile, /profile_tree — what the bot remembers about you.
- /clear — removes the current conversation's history from the bot's context and search. It stays in the message log for up to 30 days.
- /export — a copy of your data as one ZIP file. Keys, tokens and the vault are named there, without their values.
- /delete_account — deletes everything the bot keeps about you: profile, memory, history, vault, cards, connections, emails, files, business chat messages, search index and message log; it cancels your reminders and stops your personal bots. What stays: payment and credit records (accounting), the fact of deletion, your complaints, skills you published and the memory of groups you were in.
- What /delete_account leaves is deleted on request: @som_mos_oms on Telegram. We do it within 30 days and may ask you to confirm the account is yours.
- /disconnect_google removes Google tokens from our server. Revoke access in your Google account settings separately.
17. Other people's data
By sending other people's data (contacts, emails, business chats, groups) you confirm you have the right to do so and, where required, have told them. We process business chat data on your instructions.
18. Security
The vault, cards, and the keys and tokens of connected services are encrypted (AES-256-GCM), and access to the vault and cards is logged; connections to providers use HTTPS. No protection is absolute: if a breach affects you, we will tell you and, where the law requires, the supervisory authority.
19. Automated decisions
The bot makes no decisions with legal effects concerning you: the AI only answers and carries out your instructions.
20. Contacts
@som_mos_oms on Telegram
See also the Terms of Use.