ClearRec
§

Help · Contact

Talk to a real human.

ClearRec is built and maintained by a small team in Kushtia, Bangladesh. Every email goes straight to the person who writes the code — no support tier triage, no chatbot, no canned reply.

Typically within 24 hours, every day of the yearAsia/Dhaka (UTC+6)One inbox, one developer

Email support

[email protected]

Bug reports, feature ideas, partnership questions, press — all land in the same inbox. Include your extension version (v1.0+), what was being recorded, and what you expected.

Based in

Kushtia, Bangladesh

Khulna Division · Asia/Dhaka (UTC+6)

Response time

Typically within 24 hours, every day of the year

01

Who you're talking to

ClearRec is the work of M. H. Tawfik, lead developer & owner at Soft Web Grove. When you email [email protected], you're emailing the person who ships the code.

02

Quick answers

  • Does ClearRec upload my recordings anywhere?

    No. Every recording is encoded by Chrome's MediaRecorder API and written to your Downloads folder via Chrome's built-in download manager. ClearRec has no backend server — read the Privacy Policy for the full breakdown.

  • The trimmer won't open my saved recording. What now?

    Open chrome://extensions, find ClearRec, and turn on Allow access to file URLs. Without that flag the trimmer falls back to a manual file picker on each open.

  • Export hangs at 0% — is something broken?

    GIF encoding warms up ffmpeg.wasm the first time, which can take 4-6 seconds before the progress bar starts moving. Subsequent exports in the same trimmer tab start immediately.

  • How do I report a bug or request a feature?

    Email [email protected] with the page URL or app that was being recorded, what you expected, what happened, and your extension version. A screenshot or short clip of the issue helps enormously.

Looking for the long-form list? See the full FAQ on the home page.

03

Writing a useful bug report

The fastest way to a fix is to include:

  • ClearRec version (shown in the popup footer)
  • Browser + OS (e.g. Chrome 134 on macOS 14)
  • The app or page that was being recorded
  • The quality tier and format selected
  • What you expected vs. what you saw
  • A screenshot or short screen recording if visual