Loopify Privacy Policy
Loopify records your screen and converts recordings to animated GIFs. Every recording stays on your device.
The short version. Loopify collects nothing. It has no servers, no analytics, no accounts, and no network requests of any kind. Your recordings are written to your browser's local storage and never leave your device unless you download them yourself.
What Loopify stores
All of the following is stored on your own device, using Chrome's extension storage APIs. None of it is transmitted anywhere.
| What | Where | Details |
|---|---|---|
| Screen recordings | chrome.storage.local |
MP4 (H.264) where your browser supports it, otherwise WebM. Up to 10 recordings are kept; older ones are dropped automatically. Stored base64-encoded, which adds roughly 33% to the file size. |
| Recording metadata | chrome.storage.local |
Filename, file size, timestamp, and format. |
| GIF export settings | chrome.storage.sync |
Quality, maximum resolution, frame rate, and maximum frame count. Synced across your own Chrome profiles by Chrome's built-in encrypted sync. |
| Storage limit | chrome.storage.sync |
Your configured cap. Defaults to 100 MB; adjustable, with a warning above 2 GB. |
| Recording state | chrome.storage.session |
Whether a recording is in progress, and when it started. Cleared when the browser closes. |
Recordings are never synced. Only the small settings above use chrome.storage.sync. Video data stays on the device that recorded it.
What Loopify does not collect
Loopify does not collect, store, or transmit any of the following:
- Personal information — name, email address, postal address
- Health information
- Financial or payment information
- Authentication credentials, passwords, or tokens
- Personal communications
- Location data
- Browsing history, page visits, or navigation patterns
- Analytics, telemetry, or usage statistics
- Website content, beyond what appears on screen in a recording you started
Permissions, and why each one is needed
| Permission | Why |
|---|---|
offscreen | Creates the hidden document that holds the MediaRecorder, so a recording keeps running while you switch tabs. |
storage | Saves recordings and settings locally. |
unlimitedStorage | Lets recordings exceed Chrome's default extension storage quota. |
notifications | Tells you when a recording has started, and when one has finished saving. |
No host permissions. No content scripts. Loopify cannot read, modify, or inject anything into the pages you visit — it has no access to them at all. Screen capture runs entirely inside the extension's own offscreen document via the browser's standard getDisplayMedia() API, which Chrome gates behind its own picker. You choose what to share, every time, and Chrome shows a sharing indicator for the duration.
Third-party services
There are none. Loopify makes no network requests. It contains no analytics, no error reporting, no advertising, no cloud storage, no external APIs, and loads no code from any CDN. The GIF encoder it uses (gif.js) is bundled inside the extension package and runs offline like the rest of it.
Your control over your data
Because everything is local, you can act on your data directly and immediately, without contacting anyone:
- View — every recording is listed with a preview on the Settings page.
- Export — download any recording as MP4 or WebM, or convert it to a GIF.
- Delete — remove a single recording, use Keep 3 most recent to prune, or Delete all recordings to clear everything. Deletion is immediate and permanent; no copy is retained.
- Limit — raise or lower the storage cap at any time.
- Remove everything — uninstalling the extension from
chrome://extensionsdeletes all recordings and settings with it.
Data sharing
Loopify does not sell or transfer user data to third parties, does not use data for any purpose unrelated to screen recording, and does not use data to determine creditworthiness or for lending purposes. Since no data ever leaves your device, there is nothing to share.
Verifying these claims
You do not have to take this on trust. The extension ships with no remote code, so what you install is the whole of what runs. You can inspect it yourself: open chrome://extensions, enable Developer mode, and use Inspect views to read the extension's source and watch its network activity. You will see no outbound requests.
Compliance
- Chrome Web Store Developer Program Policies — permissions are limited to the stated purpose, and all user data stays local.
- Manifest V3 — service worker architecture, minimised permissions, no remotely hosted code.
- GDPR (EU) — no personal data is collected or processed.
- CCPA (California) — no personal data is sold or shared.
Changes to this policy
This policy may be updated as the extension changes. Updates are reflected on this page and in the Chrome Web Store listing.
History
- v1.1.0 — August 2026: Host permissions and content scripts removed entirely; permissions reduced from twelve to four. Recording state moved to
chrome.storage.sessionso it no longer syncs between devices. - v1.0.0 — January 2025: MP4 recording via offscreen documents; storage management.
- v0.1.0 — December 2024: Initial release, WebM only.
Contact
For questions about this policy, contact the developer through the extension's Chrome Web Store listing. Expect a reply within a few business days.