Cloud · data

Your data lives on its own server

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.

Terms and prices are on the pricing page; the general description of the service is on the cloud page.

Back to the cloud overview

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.

#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 included in the 2,490 RUB a month (half an hour of support a month is included), nothing to set up on your side. A personal VPN+ for your own devices is sold separately, see pricing.

#2 backups

Backups every night

At night the server 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. A full working server comes up from a backup.

#3 secrets

Secrets go one way

Keys and passwords you enter in the cabinet are never shown back - not to you, not to us, not to support. They can only be replaced. You cannot steal them through the cabinet, because the cabinet 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 cabinet 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 on its own server with its own disk. Other clients' servers cannot reach it: the network between them is closed, a rule in the 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 on the server for a day and is erased. The summary the agent made from it stays in the conversation.
Deletion. Ask us to close the server - 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 cabinet, 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 cabinet accepts email and a password of ten characters or more. Enabling dangerous abilities is protected separately - by a code in Telegram.
The cabinet 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 watches clients' servers 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".

Discuss your task

Cloud - When you would rather not run your own server: the agent runs on ours.
Pricing - What is free, what is paid and what is sold separately.
How it works inside - Connectors, the ways data gets lost and what already works.
Personal data processing - What is stored, for how long and where data goes.