Your recordings stay local.

What RecEase stores

Recordings, camera and microphone media, system or tab audio, thumbnails, names, folders, tags, favourites, captions, edit recipes, recording events, and recovery checkpoints stay inside your Chrome profile.

What RecEase sends

RecEase has no recording upload service, account system, payment flow, advertising tracker, or analytics identity. It does not transmit your recording content or library metadata to RecEase or Extension Crate.

On-page recording tools

Temporary access applies only to the tab where you invoke RecEase. The annotation layer does not inspect page text, form values, or keystrokes. When you enable cursor effects or auto-zoom, RecEase stores pointer and click geometry locally as recording events. Element blur stores geometry and privacy-safe identifiers rather than page text or form content.

Local processing

Codecs, background-effect models, WASM, fonts, and locales are packaged with the extension. RecEase does not use remote executable code or silently fall back to cloud transcription or processing.

Your control

Media leaves the Chrome profile only when you deliberately download a recording or export a video, GIF, caption file, or .recease project. Removing the extension may remove locally stored extension data; export important projects before uninstalling or clearing Chrome data.

Chrome Web Store Limited Use

RecEase uses screen, audio, camera, and interaction data only to provide the recording, editing, recovery, playback, and export features you request. The use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. RecEase does not sell this data, use it for advertising or credit decisions, transfer it for unrelated purposes, or allow human access to it.

Contact

Email privacy questions to support@extensioncrate.com.