Asking what happens to it next is fair. Below is the exact path for a Telegram video note or a direct browser upload: what happens to the clip, what remains, what leaves our server and how to delete your history.
Senti writes a Telegram video note or direct browser upload to a temporary file, analyses it and deletes that file immediately. The deletion also runs when analysis fails. We do not put videos into storage, keep individual frames or forward the file anywhere. A Telegram video note remains in your Telegram chat until you delete the message; a direct browser upload does not enter Telegram.
The measured indicators and technical notes of the check-in: duration, size, hour of recording, type, check-in number, date, source and any selected context. Telegram history is tied to your Telegram id. Direct-browser history is tied to a secure HttpOnly cookie retained for up to 180 days. This is what your history, personal baseline and dynamics are built on.
This is the place where data leaves our server, and it is usually the part nobody shows. We are showing it.
So that the snapshot reads like human language, the list of indicators is sent to a language model through OpenRouter. What travels is exactly a text list: indicator label, number, unit, state and confidence, plus two notes – whether the face is clearly visible and whether speech was detected. No video, no frames, no audio, no name and no Telegram id are in that request.
The text is assembled on our server from the very same numbers. The server also re-reads the model's answer and rejects it if it drifts into report language or into judgements about emotions. The model does not decide anything: the set of indicators and their limits are fixed before it is called.
Yandex Metrica is running (counter 111157661): visits, button clicks, scroll depth and session recording – Webvisor. With a separate choice to allow it, Google Analytics 4 also records public-page visits and clicks to the product, using the page URL without query parameters. No video, measurement result or Telegram ID is sent to Google Analytics. Without your permission, the Google tag does not load. It records behaviour on the website pages; there is nothing to type here, we have no forms.
No third-party analytics script runs in the Mini App. It loads Telegram's official Web App SDK and a script-free counting pixel. Telegram check-ins and history are served against a verified Telegram signature. In an ordinary browser, history is served only to the current secure HttpOnly cookie session.
We do not sell or pass your check-ins to third parties and we do not train a model on your videos – there is nothing to train on, the video is not stored. Inside the team, disk access belongs only to the people who keep the service running.
Senti does not diagnose, and does not determine illnesses, hormones, mental state or “true emotions”. The snapshot is a point of observation worth comparing only with yourself, and it does not replace a doctor or a therapist.
Open History in Senti and choose Delete history. After a separate confirmation, Senti removes the saved check-ins for the current Telegram or browser session. Access, payment records, technical service events and the introductory-use count remain. Message the team if you also want the remaining linked records removed.
A Telegram video note stays in your chat with the bot – that is Telegram's storage, not ours. You can delete the message in the chat like any other. A direct browser upload does not enter Telegram.
Because it would not be true. We really do not store the video, but we do store the numbers: without them there is no history and no personal baseline – the reason Senti exists.
The Senti team on Telegram. People answer, not an autoresponder.
If nothing is left unanswered – your first clip does not have to prove anything.
Open Senti in Telegram