Privacy policy

Effective date: 20 October 2026. Publisher: Transcrib Si.

This policy explains what happens to data when you use the Transcrib Si service and the transcrib.si website. It is written for people, not lawyers. If anything here is unclear, write to support@transcrib.si and we will explain it in plain words.

1. Who is responsible for your data

Transcrib Si publishes and operates the Transcrib Si service. We are the controller of the personal data described below, and we decide why it is processed and how long it is kept.

2. What we collect

Account data

• Your email address.
• A hash of your password. We never store the password itself.
• Your account identifier, plan and the date the account was created.

Content data

• The audio and video files you upload.
• The transcript, timestamps, speaker labels and edits we produce from them.
• The language and settings you chose for each file.

Usage data

• How many files you uploaded per day and how many minutes of audio were transcribed per month, so we can apply the plan limits and show you your usage.
• For API keys: the name you gave the key, its prefix, when it was created, when it was last used, and whether it was revoked. The key itself is stored only as a hash.

Billing data

• Your Stripe customer identifier, your plan, subscription status and the end of the current period.
• Invoices. Stripe handles card numbers and bank details; we never receive or store them.

Technical data

• IP address, user agent, request timestamps and error logs, kept for security and to diagnose faults.
• The session token that keeps you signed in. It is stored in your browser's local storage and, for the sign-in flow, in an http-only cookie named tsi_session.

Communications

• Emails you send us, including support requests and security reports.

What we do not collect

• Card numbers, CVVs or bank credentials.
• Advertising identifiers. We run no advertising and no cross-site tracking.
• The contents of the files on your computer that you never upload.
• Fingerprints of your device. We do not read fonts, canvas or audio characteristics to identify you.

3. Why we use it

• Content data — to produce the transcript you asked for, to show it back to you, and to export it in the format you choose.
• Account data — to create and protect your account, and to send you service messages about billing or changes.
• Usage data — to enforce the daily file limit and the monthly fair-use allowance, and to show you where you stand.
• Billing data — to take payment, issue invoices and handle refunds.
• Technical data — to keep the service running, to prevent abuse and fraud, and to investigate security incidents.
• Communications — to answer your questions and to keep a record of what we agreed.

We do not use your audio or your transcripts to train models for other customers, and we do not sell your data to anyone.

4. Who receives your data

Your files are processed on the infrastructure that runs our own transcription engine. Those servers are outside the United States, so uploading a file means a transfer of its content outside the US. If you are in the EEA, the UK or Switzerland, write to us and we will tell you which transfer mechanism we rely on for your region.

• Our transcription infrastructure — the servers running our own transcription engine, which receive your audio and return the transcript. This is required to do the job you asked for.
• OpenAI, for clean English only — when the recording is entirely in English and the fallback is switched on in the configuration, the audio file is sent to OpenAI's transcription API instead. This happens only for that case, and only for the file you sent. The rest of the recordings are transcribed by our own engine.
• Stripe — for payments, subscriptions and invoices.
• Our hosting and email providers — they run the servers and deliver messages to you, under written data-processing terms.

Nobody else receives your data. We do not sell it, we do not share it for advertising, and we do not hand it to data brokers. The page-view counter described in section 7 is our own code on our own server; it is not a third-party service and it does not leave our infrastructure.

5. How long we keep it

• Audio files and transcripts — until you delete them in the app. There is no automatic deletion of finished transcripts in the current version of the service; deleting a transcript removes both the text and the file from the live system right away.
• Drafts — a file uploaded without an account waits for an account for 24 hours, then it expires and the file is removed from the storage.
• Chunked uploads — the parts of an upload that was never finished are removed when the upload session is dropped.
• Technical logs — 30 days.
• Billing and tax records — as long as the law requires us to keep them.
• Account data — until you close the account, then deleted within 30 days, except records we are legally required to keep.

6. Your choices and your rights

Depending on where you live, you may have the right to access your personal data, correct it, delete it, export it, object to certain processing, withdraw consent and complain to a regulator. We do not treat people differently for exercising these rights.

• Edit or delete a transcript — do it in the app. Deleting removes the file and the text.
• Close your account — write to support@transcrib.si with the subject "Close account". We delete the account data within 30 days.
• Get a copy of your data — write to us. We answer within 30 days.
• Object, restrict or complain — write to us first. If you are in the EEA or the UK, you can also complain to your local data protection authority.

We do not sell personal information and we do not share it for cross-context behavioral advertising, so we do not offer an "opt out of sale or sharing" mechanism.

7. Cookies, local storage and the consent banner

The site sets no advertising cookies and no tracking pixels. On your first visit it shows a banner with two choices: "Only necessary" and "Allow analytics".

• Until you choose — nothing is measured and no analytics request leaves your browser.
• "Only necessary" — the site keeps working in full; the analytics code is never loaded. The choice is stored in the local storage of your browser under the key ts_consent.
• "Allow analytics" — the page-view counter is loaded. It sends the path of the page, the language of the page and, if you arrived from another page of this site, that path. It sends no cookie, no identifier and no IP address, and it is not shared with anybody.

The counter on our side keeps one number per pair "day + page + language". It tells us which pages people read; it does not tell us who they are.

The other things the site keeps in the local storage of your browser are the session token (ts_token), the draft of a file uploaded without an account (ts_draft), the cached user (ts_user), the light or dark theme choice (ts_theme) and, for the sign-in flow, an http-only cookie tsi_session. Clearing your browser data removes all of them.

You can change the choice at any time: change the cookie choice. Tools that work entirely in your browser — the subtitle converters, the filler word remover — do not show the banner at all, because they send nothing anywhere.

8. Security

Traffic is encrypted with TLS. Passwords and API keys are stored only as hashes. Access to production systems is limited to the people who need it. The details are on the security page.

9. Children

The service is not for children under 13, and not for anyone under the age of digital consent in their country. We do not knowingly collect data from children.

10. Changes to this policy

We may update this policy as the service changes. The effective date at the top always shows the current version. If a change materially affects how we use your data, we will tell you by email before it takes effect.

11. Contact

Support and privacy questions: support@transcrib.si
Legal questions: legal@transcrib.si
Publisher: Transcrib Si