Privacy Policy

Who runs YoRecord

YoRecord is made and run by Jan Drábek, a sole trader established in the Czech Republic. You can reach us at [email protected].

There is no account

YoRecord has no sign-up, no login and no user database. We do not ask for your name or email address to record, edit, export or share. We hold no email addresses of free users. If you buy Pro, Polar shows us the email you paid with; we use it only to answer you.

Your recordings stay on your device

Recording, editing and rendering to MP4 run inside your browser. Finished recordings are saved in your browser's own storage (IndexedDB, database yorecord-library) on the device you recorded on. We cannot see them, they do not sync between devices, and clearing the site's data in your browser deletes them for good. Download what you want to keep.

Settings such as your Pro licence key, custom branding, an uploaded logo and editor preferences are kept in the same browser storage (localStorage), on your device only.

What leaves your browser, and when

The items below are every way your recording, or something made from it, leaves your browser. Analytics, described further down, is separate. Captions (item 1) are on by default, and error reports (item 5) are sent when something breaks. Everything else happens only when you use that feature.

1. Captions: the audio

By default, when you stop a recording and it opens in the editor, the recording's audio track is sent to our server on Cloudflare and forwarded to Groq for transcription with the Whisper speech model. Only the audio is sent, never the video. Our server keeps no copy of the audio or the transcript. It writes one operational log line per request (a fixed file name, the audio size and the model used), which Cloudflare retains for a limited time as part of its logging.

The recorder says this before you start, next to its switch "Add captions and chapters automatically". Turn the switch off and the audio is not sent; this browser remembers your choice for later recordings. A recording with no audio sends nothing. In every other case (a video you import, a recording you open again, a take added to the end of an earlier one, or with the switch off) the audio is sent only when you ask for captions in the editor, for example with "Caption it for me".

2. Chapters, AI suggestions and titles: the transcript

When captions are made, by default or on request, the transcript text is then sent through the same server to a Groq language model to make chapters and a suggested title. Using the editor's AI suggestions sends it the same way. Not the audio, not the video. Our server stores nothing from the request; its log line records how many captions were sent and the generated title.

3. Share links: the rendered video

Creating a share link uploads the finished MP4 to our storage on Cloudflare (R2) so the link can play. Plainly: anyone who has the link can watch the video. There is no login on the viewer page. The link contains a long random id that is not practical to guess, but that is not the same as private. Do not share a recording that shows passwords, tokens, inboxes or other people's personal information.

• Free share links are deleted automatically after 31 days. Deletion is age-based and runs some time after the period ends, so we promise the link works for at least that long, not that it vanishes on the day.
• On Pro, a link you create is kept alive for as long as your subscription is paid, up to a per-customer limit shown on the pricing page. After you cancel it follows the free schedule from its last renewal.
• You can turn a link off early from the device that created it (the editor's share screen). The key that allows this lives only in that browser's storage, so if you clear the site's data we cannot revoke the link for you from the app. Email us the link and we will remove it.
• A revoked or expired video can keep playing from Cloudflare's cache for up to five minutes after removal. Links created before 22 August 2026 have no revoke key and no cache limit, so for those only the 31-day deletion applies.
• On Pro, sharing sends your licence key through our server to Polar so the link can be enrolled for renewal. Our server keeps your Polar customer id and the list of enrolled links (their ids and sizes), and asks Polar about once a week whether the subscription is still active. It does not store the key.
• Anyone opening a share link sends the usual web-request data (IP address, browser) to Cloudflare, which serves the video. We keep no log of who watched. Opening a link sends a page view and a "link opened" event to Google Analytics (see below), carrying the link's id. For videos published by the agent tool, the moment playback starts is also reported to our server, as the link id only.

4. Pro licence: the key

When you paste a Pro licence key, it is sent to Polar, our payment provider, to check that it is valid. Only the key is sent. Polar is the merchant of record for Pro: it collects your email and payment details at checkout under its own privacy policy, and we do not receive your card number. The key is then stored in your browser and is not checked again unless you paste it again or share a link on Pro (above).

5. Error reports: what was on screen when something broke

We use Sentry (servers in the United States) to learn about crashes. Nothing is sent from a healthy session. When an error happens, Sentry receives the error, technical details about your browser, your last clicks and page URLs, recent console lines (which can quote an error message, not your recording), and a replay of what the page looked like leading up to it. In the editor that replay includes the video preview, which draws your actual recording. A few frames per second of whatever you recorded can therefore leave your browser in a crash report. Text you typed into fields is masked, images and video elements are blocked, and the interface text is readable. We think knowing why the editor crashed is worth this for the people it happens to, but you should know it happens. If you would rather it did not, use a browser extension that blocks sentry.io; the app works without it.

Analytics

We use Google Analytics 4 on yorecord.com to count page views and product events such as "recording started" or "export completed". It sets cookies and sends your IP address to Google, which processes it under Google's privacy policy. Events describe what the product did, not what your recording contains: no video, audio, transcript or file names are sent. An event can carry a share link's id, the page URL (which in the editor includes a recording's local id) and the text of an error message. Analytics does not run on localhost or on preview deployments. You can block it with a content blocker or Google's browser add-on without affecting the app.

Hosting

The site and its servers run on Cloudflare. Like any host, Cloudflare sees the IP address and request details of everyone who loads a page or uploads a file, and processes them under its own policy. We do not build profiles from those logs. When you export, the video encoder is downloaded from our Cloudflare storage; if that fails your browser fetches it from unpkg.com instead, which then sees your IP address.

The agent tool

YoRecord for AI agents is a separate path with its own rules. When you approve an agent at /approve, the tool saves an upload token on your computer (in ~/.config/yorecord). Videos it uploads are public to anyone with the link and are deleted after 7 days. Our server keeps, per token, a count of uploads, bytes and narration characters, when the token was approved, and whether it was revoked; it stores no IP address and no user agent. Weekly statistics count uploads, refusals and which agent videos were watched, by link id. Narration, if the agent uses it, sends the sentence to be spoken to xAI through our server, which forwards the sentence, the chosen voice and language, and nothing about you. Deleting the token file stops the tool on that machine; to cancel the token itself, email us and we will block it on our side.

What we do not do

• We do not sell or rent data about you.
• We do not train AI models on your recordings. The providers named above process each request under their own terms, linked where they are named.
• We do not show ads or use advertising trackers.
• We do not keep a copy of your recordings, transcripts or licence keys on our servers.

Your choices and rights

Because almost everything lives in your browser, you delete it yourself: remove a recording in the library, or clear the site's data. To remove a shared video, revoke it from the share screen or email us the link. To exercise any other right you have under the law of your country (access, correction, deletion, complaint), write to [email protected]. We answer from a person, not a system.

Changes

When the product changes in a way that changes where data goes, we update this page and the date at the top. The changelog lists product changes with dates.