What happens to your recording

Recordings are processed locally

When you start recording, the browser hands the page a live media stream. That stream is encoded by MediaRecorder, which produces chunks of video data. Those chunks are kept in an array in the tab’s memory and joined into a single file object when you stop. The preview player reads that file object directly from memory.

Recordings are not uploaded to our servers

There is no upload endpoint in this application. No API route accepts video, no database stores recordings, and no cloud storage bucket is connected. You can confirm this yourself: open your browser’s developer tools, switch to the network panel, and record something. You will see the files that make up the page load once, and nothing carrying video afterwards.

No account is required

Nothing identifies you here: no registration step, no credentials, no profile, no address to surrender. Every feature works on first visit.

Microphone and camera are opt-in

Microphone and camera access are requested only when you enable those features and press start. If you leave them off, the app never calls getUserMedia() at all, so no prompt appears and no device is opened. If you deny a prompt, recording continues without that source rather than failing.

Screen sharing is controlled by the browser

The website cannot secretly start screen capture. Screen capture can only begin from a direct interaction with a control on the page, and the browser then shows its own picker where you choose the screen, window or tab. While sharing, your browser displays a persistent indicator and a sharing bar.

You can stop at any time

Stop from the recorder page, or stop from your browser’s sharing controls. Either route ends the capture cleanly and leaves you with the recording made so far.

What gets cleaned up, and when

• Stopping a recording stops every screen, microphone and camera track immediately.
• Deleting a recording revokes its object URL with URL.revokeObjectURL() and clears the stored chunks, so the browser can reclaim the memory.
• Closing or reloading the tab discards anything you have not downloaded.

What we do not claim

We are not going to tell you that we collect absolutely nothing, because a website cannot technically guarantee that. Serving this page involves ordinary web infrastructure, and depending on how it is hosted, that infrastructure may process basic technical information such as HTTP requests, IP addresses, user-agent strings and timestamps in server or CDN logs. That is a property of the internet, not of this application.

What we can say precisely is this: the application contains no code that transmits screen content, microphone audio, webcam video or recording files anywhere. There is no media analytics, no session-replay tooling, and no third-party script that observes what you record. Fonts are bundled with the app rather than loaded from a font CDN, so opening the page does not tell a third party you were here.

If you are running your own copy of this project, the hosting provider you choose determines what request logs exist. The source code is the part we can be exact about.

Who is responsible for this site

The operator of screen-recording-software.com is the data controller for the limited processing described below, and can be reached at contact@screen-recording-software.com. [Insert your legal entity name and registered address here before publishing — the GDPR and several national laws require a controller to be identifiable, and an email address alone is not always sufficient.]

What the hosting layer processes

Serving a web page means a server receives a request. Depending on the host, that request may be logged with an IP address, a timestamp, the page requested and a user-agent string, and kept for a short period for security and diagnostics. That processing is carried out by the hosting provider acting on the operator’s behalf, under the legitimate interest of keeping the site available and secure. It is ordinary web infrastructure, it applies to every site you visit, and it is entirely separate from your recordings, which never reach a server at all.

If you are in the EU, the UK or another region with comparable rules, the lawful basis for that minimal processing is legitimate interest rather than consent, because it is technically unavoidable in serving the page and involves no profiling or marketing.

Cookies

None are set. No session cookie, no preference cookie, no third-party cookie. Your choices on the recorder page live in the tab’s memory for as long as the tab is open and vanish alongside it, which is why a refresh returns everything to its defaults. Nothing reaches local storage either.

Analytics

There is no analytics script on any page. No visit counter, no heatmap, no session replay, no advertising pixel. We do not know how many people use this site, which is a trade we made deliberately.

Children

The site is not aimed at children and collects nothing from anyone, so there is no age-gated data to worry about. A child using it is subject to the same arrangement as anyone else: their recording stays on their device.

Your rights over your data

Regulations such as the GDPR, the UK GDPR and the CCPA give you rights to see, correct, export, erase and object to the use of personal data an operator holds about you, and to complain to a supervisory authority. We hold none — no account, no email unless you write to us, no recording, no behavioural profile. If you do email us, that message sits in an inbox like any other correspondence, and you can ask for it to be deleted.

Changes to this policy

If this policy changes, the revised version will appear here with a new date. Should a change ever make the arrangement less private than it is today, it will be stated at the top rather than folded quietly into a paragraph.

Asking us something

If anything here is unclear, or you want to raise a concern about how the site behaves, write to contact@screen-recording-software.com. Since no recording ever reaches us, there is no stored footage for us to hand over, correct or delete on request — there is nothing held to act on.

Questions

The FAQ covers file formats, system audio and browser support. The how it works page walks through the technical pipeline in more detail.