Back to ReelCap – Web Demo Screen Recorder

Privacy Policy

ReelCap – Web Demo Screen Recorder

Privacy Policy — ReelCap

Last updated: 2026-09-01

ReelCap ("the extension") is a screen recorder that runs entirely inside your web browser. Recording, editing and exporting — including the paid Pro features — happen on your own device; your video never reaches our servers, or anyone else's. An optional account exists for two purposes only: trying the Pro tools (a free account includes 10 uses) and buying or restoring a Pro plan.

Data we collect

No recordings, ever. ReelCap does not collect, store on any server, transmit, share, or sell your recordings, microphone audio, camera video, browsing history, or page content. Every recording is captured, composited and encoded locally on your own device. Settings and a local cache of your plan status and remaining free-tries balance are stored in your browser via the standard extension storage. There is no analytics and no telemetry.

If you create an account, and only then, we store what an account requires: your email address, an authentication record, your subscription status, and — for free accounts — how many of your included Pro tries you have used. Payment card details are handled by our payment processor (Paddle) and never reach us.

Pro features and your account

The three paid features — click auto-zoom, MP4 export and GIF export — are computed entirely in your browser, exactly like the free ones. Paying does not change where your video goes; it goes nowhere.

The account exists so your free tries and any purchase can follow you to another machine. The extension makes no network request of any kind until you take an explicit action — pressing "Sign in" on a locked Pro control or "Restore purchase" in its settings. After that it re-checks https://reelcap.xeviora.com/api/ext/entitlement about once a day; that request carries your session cookie and nothing else: no recording data, no page URLs. When you use one of your included free tries, the extension additionally reports a single counter tick so your remaining balance stays correct across devices — that is the only usage information that ever leaves your browser.

You can delete your account and its subscription record at any time by emailing us; deletion removes the email address and authentication record from our database.

Payments

Payments are processed by Paddle, which acts as the merchant of record for Xeviora. Checkout runs on xeviora.com; Paddle collects and processes the billing details needed to complete the sale under its own privacy policy. We receive from Paddle only your subscription status and the identifiers needed to keep it in sync — never your full card number.

Permissions and why they are needed

  • tabCapture — Captures the rendered video (and optional audio) of the active tab you choose to record. It only starts on an explicit action by you.
  • offscreen — Runs an offscreen document, the only MV3 context allowed to use getUserMedia and MediaRecorder, to grab the stream, mix audio, composite the canvas, and encode the WEBM file.
  • activeTab — Grants one-time access to the current tab only when you start a recording, so its stream can be captured.
  • scripting — Injects the self-drawn cursor and click-ripple overlay into the page being recorded on demand. ReelCap does not run a persistent content script.
  • tabs — Reads the active tab's title/URL to name the recording and route the finished clip to the local preview page.
  • storage — Persists your settings and the recording state so an in-progress recording survives the service worker being recycled.
  • unlimitedStorage — Lets long recordings be buffered locally without hitting the small default storage quota.
  • Host access (<all_urls>) — Required so the highlighted cursor and click ripples can be drawn on whatever page you record, and so the extension can ask reelcap.xeviora.com about your Pro plan. Access happens only when you start a recording; ReelCap does not run a persistent content script and reads no page content.

Microphone and camera are not requested in the manifest. They are granted at runtime through the browser's standard getUserMedia prompt, only if you enable them, and the streams are mixed/composited locally and never transmitted.

Where your recordings live

A finished recording is written to your browser's local IndexedDB so the preview tab can play it back, and it is saved to your own Downloads folder when you click download. Converting to MP4 or GIF reads that same local copy and writes the result locally too. Nothing is uploaded — we operate no service that could receive a video. Discarding a recording in the preview tab deletes it from local storage.

Remote code

ReelCap does not load or execute any remote code. All JavaScript and WebAssembly are bundled in the extension package.

Changes

If this policy changes, the "Last updated" date above will change accordingly. The current version is published at: https://reelcap.xeviora.com/privacy

The previous address, https://xeviora.com/reelcap-privacy, still points to the same policy.

Contact

Questions? Contact support@xeviora.com — the earlier address, tiger.hu.liu@gmail.com, still reaches us as well.