#1 where
The server is in Russia
Procurement platforms, Bitrix24 and other Russian systems see a Moscow address. Foreign models are reached through our tunnel - it is part of the plan, nothing to set up on your side.
Cloud · data
Your data lives
in its own cell
Every client gets a fenced-off piece of the server: their own agent, their own disk, their own keys. This page covers where all of it sits, who can look inside, and what happens at night when backups run.
The basics
Four rules everything rests on
None of these is a policy clause. They are how the server is built - it does not know how to work any other way.
#2 backups
Backups every night
At night the cell is packed into an archive and encrypted before it leaves the server - only ciphertext travels to storage, and there is nothing there to decrypt it with. Backups are kept for fourteen days. We have run a restore from zero: a working cell comes back from the backup, not a "should come back".
#3 secrets
Secrets go one way
Keys and passwords you enter in the dashboard are never shown back - not to you, not to us, not to support. They can only be replaced. You cannot steal them through the dashboard, because the dashboard does not give them out.
#4 limits
Dangerous actions need a code
Abilities that can change or delete something are enabled with a separate confirmation: a code arrives in your Telegram. The dashboard password alone is not enough - even a stolen password cannot switch the dangerous abilities on.
How it works
How storage is arranged
Everything your agent knows - conversations, settings, collected reports - lives in its cell: a separate container with its own disk. A neighbouring cell cannot reach it: the network between cells is closed at the server level, a rule in its configuration rather than a line in a staff manual.
- Nightly backups. The archive is encrypted on the server itself; the decryption key never reaches the storage machine. Backups live fourteen days, older ones are erased.
- Audio recordings older than thirty days are erased automatically. Text transcripts stay - they are the working material.
- Documents you send. A file you hand the agent to work through lives in the cell for a day and is erased. The summary the agent made from it stays in the conversation.
- Deletion. Ask us to close the cell - we stop it, wipe it and confirm. The nightly backups live out their fourteen days and disappear with the rest.
Honestly
Who sees your data
"Nobody, ever" sounds great and is not true of any cloud. The truth looks like this:
- Us, as the people running the server. We have technical access to the machine - it cannot be maintained otherwise. We open an agent's conversation in exactly one case: when we are debugging a problem together with you, and we say so out loud.
- The model provider sees the text the agent sends it - true of every service built on large models. Which model your agent runs is your choice in the dashboard, including Russian ones - Sber and Yandex with your own keys.
- Your systems see the agent as a regular employee: in Bitrix it works under the access you granted and leaves a trail in the history, like a person would.
Current state
What is not there yet
- No second factor at login: the dashboard accepts email and a password of ten characters or more. Enabling dangerous abilities is protected separately - by a code in Telegram.
- The dashboard sends no email. A forgotten password is solved with a one-time link: write to us, we issue one - you set the new password yourself, and no password ever appears in the conversation.
- No certifications or attestations yet. If your industry requires them - say so before we start, and we will honestly discuss whether we fit you today.
- Outage notifications do not reach clients yet: our watchdog checks the cells around the clock and the on-duty person fixes things. A Telegram notification for you is in the works.
This page changes when the service changes, not once a year. What appeared and when - in the changelog.
Questions
Ask about your data before signing
We will show you how things work on a live example - no "let me check with the technical team".