SkribOS transcribes and summarises the audio you send it. That means it handles recordings of people talking — often people who are not you. This page says exactly what is stored, where it goes, how long it stays, and how to get rid of it.
It covers the SkribOS Telegram bot (@SkribOSBot), the web app at app.skribos.com, the SkribOS iPhone and Apple Watch apps, and this site.
/settings → Keep audio changes that, per chat, including switching it off entirely.An account is created the first time you use the bot. It holds your Telegram user ID, display name and username as Telegram reports them, your plan and role, your remaining bonus minutes, and your referral code. We never ask for an email address, a phone number or a postal address, and we have no way to see the ones Telegram holds.
Voice notes, audio files, video, documents, and media fetched from links you paste — Dropbox and YouTube among them. The file is downloaded to a working directory, converted, transcribed, and then deleted from that directory. It is only kept beyond that point if the chat's Keep audio setting says so; see Recordings below.
The transcript text, its timestamped segments and speaker labels, the AI-generated title and summary, and the detected language. These are stored so you can page through a long result in Telegram, search your archive later, and export it.
Notes on a transcript and notes pinned to a timestamp, custom titles and subtitles, tags, folders and auto-file rules, edits you make to a transcript or summary, dictionary words you add so names get spelled right, and any message you send with /contact.
A record of each job — duration, media type, file size and timestamps — which is what your daily quota is counted from. Payments are handled by Telegram Stars: we store the Telegram charge ID, the number of Stars, and your subscription's status and expiry. We never see or store card details — that transaction happens entirely inside Telegram.
Web sessions, magic-link login tokens and API keys are stored only as hashes; the usable value exists in your browser cookie or in the copy you were shown once. Share-link passwords are stored as an HMAC, never in the clear. Our servers keep operational logs (errors, job outcomes, timings) for debugging and abuse prevention.
A transcript is more useful when you can hear the bit you are reading, so SkribOS keeps a compressed copy of the audio by default and plays it back against the transcript's timestamps in the web app.
/settings → Keep audio decides this, per chat: Off, 7 days, 90 days, 1 year, or Always. Off deletes the media immediately after transcription. In a group, only an admin can change it, and a message is posted in the chat when they do — so nobody's recording is kept on a setting they could not see.Nothing is public until you make it so. Creating a share link mints an unlisted address for one transcript; the web app is excluded from search engines, and a link is only as private as the people you give it to.
In a group, the chat's own settings decide what gets transcribed, and the group's admins control them. When a setting that affects everyone changes — including audio retention — the bot says so in the chat. If a chat you are in has SkribOS active, voice messages sent there may be transcribed and stored in the account that owns that chat's settings.
If you use private-chat transcription, the messages that are transcribed are the ones you configured in /settings. Please only transcribe conversations you are entitled to record, and follow the law where you are — in some places that means telling the other person first.
SkribOS uses a small number of providers to do its job. Each one's own terms and privacy policy govern what they do with what they receive.
Receives your audio and returns the transcript, with timestamps and speaker labels. This is the only party your recordings are sent to for processing.
Receives the transcript text — never the audio — to produce summaries, titles, speaker names and tag suggestions.
Carries every message to and from the bot, and handles payments through Telegram Stars.
Contacted only when you paste a link from them, so the media can be fetched for transcription.
Hosts the bot, the API and the PostgreSQL database, and stores retained recordings.
Serves this marketing site. The app itself is not hosted here.
Distributes the iPhone and Apple Watch apps, and provides the crash and delivery reporting that comes with that.
We do not sell your data, we do not share it for advertising, and there are no advertising or analytics trackers on this site or in the app.
/settings controls transcription, retention and delivery per chat — including turning audio retention off before you send anything./apikey, and web sessions can be signed out./start → Account & Privacy → Delete Account permanently removes your account, every transcript, every note and every stored recording. It cannot be undone.Depending on where you live, you may also have the right to ask for a copy of your data, to have it corrected, or to object to how it is handled. The controls above cover most of this directly; for anything they do not, message us with /contact in the bot and we will handle it.
Traffic is encrypted in transit. Session tokens, login tokens and API keys are stored only as hashes, and share-link passwords as keyed hashes, so a copy of the database is not enough to sign in as you or to open a protected link. Access to production data is limited to those who operate the service. No system is perfect, and we do not claim otherwise.
SkribOS is not intended for children. Telegram's own terms set a minimum age for its users, and we expect the same of ours. If you believe a child's data has ended up here, tell us and we will remove it.
If this policy changes in a way that affects what we do with your data, the date at the top will change and the significant changes will be announced through the bot. The current version always lives at this address.
Send /contact <your message> in the bot — it reaches the team directly, and it is the fastest way to get an answer about anything on this page.