Legal

Privacy
Policy

Last updated — March 12, 2026

Clipzr is a Windows screen recording tool built for creators. We believe your recordings are yours — they never leave your machine. This document explains exactly what we collect, what stays local, and the limited analytics we use to improve the app.

§ 01

What stays on your device

The following data is recorded locally during a Clipzr session. None of it is transmitted to any server — it lives only in your system's temporary folder and is processed entirely on-device.

Screen recording
Your screen is captured via Windows GDI (gdigrab). The output is an H.264 MP4 file written to %TEMP%\screen_recording.mp4. No audio is recorded. The system cursor is excluded from the raw capture.
Cursor movements
Cursor position (x, y), click state (left button down/up), and cursor type (arrow, pointer, text, etc.) are sampled every 100 ms during recording. Events are saved to %TEMP%\cursor_movements.json. Timestamps are Unix epoch milliseconds.
Exported video
When you export, Clipzr composites the cursor overlay onto the recording and encodes the result to a location you choose. The export is performed locally in your browser runtime via WebCodecs — no file is uploaded.
🔒

Your screen content, cursor data, and exported video are never uploaded, synced, or shared. They exist only on your computer.

§ 02

Analytics & diagnostics

Clipzr uses two third-party analytics services to understand how the app is used. These tools only observe interactions with the app's user interface — they have no access to your recordings, cursor data, or exported files.

Microsoft Clarity

Project ID: vumnisi3as
Clarity Privacy ↗

Session heatmaps, click maps, scroll depth, and anonymised session recordings of the UI. Clarity may capture which buttons you click and how you navigate the editor — it cannot see your screen recording content.

Google Analytics 4

Measurement ID: G-XZKMNX15DF
Google Privacy Policy ↗

Page views, session counts, basic device/OS info, and usage events (e.g. export initiated). No personally identifiable information is sent.

📊

Both services receive only UI interaction signals. Your recording content is never exposed to them.

§ 03

What we do not collect

  • —The contents of your screen recordings
  • —Your cursor movement or click data
  • —Any audio (Clipzr does not record audio)
  • —Your name, email address, or account information
  • —File paths or export destinations
  • —Any data from your clipboard or other applications
§ 04

Data retention

Temporary recording files (screen_recording.mp4 and cursor_movements.json) are written to your OS temporary directory. They are overwritten each recording session and are subject to your operating system's normal temp file cleanup policies.

Analytics data retained by Microsoft Clarity and Google Analytics is governed by their respective retention policies (typically 13 months for GA4).

§ 05

System permissions

Clipzr requests the following Windows capabilities at runtime:

Screen capture

Used exclusively to record your screen via the Windows GDI capture API (gdigrab). The Clipzr UI window is excluded from the capture.

Cursor position & state

Read via the Windows API (GetCursorPos, GetAsyncKeyState) to track your cursor for the overlay effect. This data is never sent externally.

Filesystem (Temp + chosen export path)

Write access to %TEMP% for recordings, and write access to the export destination you select via the save dialog.

§ 06

Children's privacy

Clipzr is not directed at children under 13. We do not knowingly collect any personal information from children. The analytics tools we use (Clarity and GA4) are configured without demographic targeting.

§ 07

Changes to this policy

We may update this policy as Clipzr evolves. Material changes will be noted with an updated date at the top of this page. Continued use of the app after changes constitutes acceptance of the revised policy.

§ 08

Contact

Questions about this policy or how Clipzr handles data?

→privacy@clipzr.com