Privacy · Clifzo

Scope and processing routes

This notice covers the Clifzo website and its Chrome and Edge extensions. The homepage and similar entry points offer server resolution. A download workspace opened by the extension uses local extension resolution, downloading and merging. Their data flows and retention differ as set out below. Local media processing does not mean that the workspace webpage, website infrastructure, statistics or advertising process no data.

Website server resolution

When you use server resolution, we process submitted page links, controlled options, task status and results, and operational fields such as task ID, platform, provider, status, duration, bytes and error category. Work IDs, titles, public creators, publication times and media durations support recent content analysis and are stored separately from long-term operational records; covers appear only in short-lived result previews. Full submitted links are not shown in traffic dashboards, sold or used for advertising profiles. Local extension downloads do not submit server-resolution jobs through this route.

Server retention and abuse-prevention records

These periods apply to server resolution, not to local extension media caches. Public server-task credentials stay in page memory, not long-term browser storage or page URLs. Resolver results and source-format URLs default to 5 minutes, server-task temporary files to 6 hours, redacted task logs to at most 3 days, and security audit records to 30 days. Work metadata expires 7 days after the first submission; retries do not extend this. Work IDs, titles, creators and other work metadata are then unavailable. Public source-page links, stripped of credentials and tracking fields, remain with task records for diagnostics even when resolution fails or work metadata expires. Aggregate statistics and operational task records may be retained long term; deployment settings may change short-lived result, file and audit periods. To detect API abuse, we separately record IP addresses, times, endpoint types, status codes and durations for task submissions and login requests, for at most 7 days and only accessible to administrators, without request bodies, full URLs or credentials. These short-lived IP records may link task IDs to their first submission origin; reuse or retries do not extend retention. To observe request distribution, these short-lived records may include country, state or province, city and IP-estimated coordinates on an approximately 1 km grid from Cloudflare, for at most 7 days and only accessible to administrators. Grid detail is not location accuracy: the estimate may reflect a carrier or proxy exit, not a precise address. We do not collect device GPS or send IPs to other geolocation services.

Data processed locally by the extension

The extension requests HTTP/HTTPS website access at installation. Automatic capture is enabled by default, without a separate activation step. It observes accessible pages and media responses, reads work information from pages or APIs, and keeps discovered source-page, media and cover URLs, titles, types, sizes, dimensions and durations. Packaged resolver, download and merge code runs locally. Media transfers from its source or CDN to your device without passing through Clifzo servers. Local requests may use your existing source-site login session: the browser may send the corresponding source cookies, and the extension may temporarily set Referer, Origin or User-Agent headers. Sources and CDNs receive normal network request information under their own policies. The extension does not send raw source-cookie values, original webpage or API responses, or media-file bytes to the Clifzo workspace as task payloads.

Information shared with the website workspace

The workspace webpage receives source-page URLs, platform, work titles, public creators, cover URLs, duration, media URLs and format, codec, quality and size information, plus task IDs, status, progress, errors, browser download IDs and filenames. Source or media URLs may retain temporary signatures, expiry values or other source query parameters. Treat these URLs as potentially containing access credentials and do not share them publicly. A launch record bound to the destination tab and page messages transfer this information; the workspace URL contains a random launch fragment identifier rather than the full media link. Results enter the webpage memory. The normal local flow does not submit them as server-resolution jobs, and the workspace component does not write a persistent task history. However, scripts in that webpage can access information passed to it. Refreshing the workspace can synchronize tasks explicitly attached to that tab from the extension again; closing the website does not cancel downloads in the extension task tab. After reopening the browser, use Downloads in the extension to manage records and open a workspace for an individual task if needed. Displaying a cover also makes a browser request to its image source.

Extension settings and session information

Language preferences remain in extension local storage without an application expiry until changed or the corresponding extension data is cleared. Browser session storage holds the current capture status, a session copy of granted site origins, discovered media and workspace launch information. Website access permissions granted by the browser are managed separately and may persist across restarts; clearing session data does not revoke those permissions. Closing the source tab removes its capture record. The popup Clear list action clears resource items, not all page context, temporary media or saved files. A successfully claimed launch record is deleted; unclaimed records become unusable after 1 hour, which is not a scheduled deletion guarantee. Browser restart or disabling, reloading or updating the extension clears browser session storage. Temporary request-header rules also live in the browser session and are removed through normal release and related download-completion or interruption cleanup paths. Context such as source-tab ID, platform and session mode is kept in browser session storage so it can be checked after the extension background worker sleeps. This context contains no raw cookie values. HTTP/HTTPS website access is required at installation; cookie-reading permission remains optional. The browser manages these permissions separately and they may survive restarts. Switching the popup back to the default browser session stops explicit reading for new tasks; it does not revoke granted permissions or end tasks in already-open workspaces. Close a workspace to stop its local session. Restrict website access in extension details to stop future capture; restore access and reload the source page to resume. Removing the extension revokes all its permissions.

Local download tasks, checkpoints and cleanup

Extension downloads run in a separate extension task tab, so refreshing or closing the website workspace does not cancel them. Closing the task tab or browser interrupts active transfers. Task records stay in extension storage and contain the original post page, platform, selected format, task state and completed-block metadata, without cookies or request headers. A minimal HLS source plan is stored separately in extension-private storage so captured HLS can recover its source after reopening the browser; Native posts still resolve their source again when continued and may contain temporarily signed media URLs. This plan is excluded from public task records, website task messages and logs, and is removed on completion, cancellation or deletion. Input media, committed blocks, HLS segments and merged output may use local disk in the extension origin’s private file storage (OPFS). After reopening the browser, use Downloads in the extension to continue. The extension resolves the post again and checks its original format and source before reusing completed blocks. HLS rechecks the playlist and AES key digests, reuses complete segments that pass local content checks, and downloads incomplete segments again. Playlist, media URL or key changes keep the cache but prevent mixing it with new media. Ordinary direct sources without byte-range support still restart safely. Missing account context or unavailable formats require selecting or reconnecting the source. Paused, interrupted, network-failed and unsaved tasks keep recoverable data until completion or explicit cancellation and deletion. The old 24-hour cleanup rule does not apply to these checkpoints. Successfully saved media is cleaned up where possible; task records remain until deleted, with a 100-task limit and no automatic eviction. Older caches without checkpoints may be reclaimed when later tasks start. Locked files, damaged records or browser storage eviction can prevent recovery or deletion; neither a fixed deletion deadline nor resumability for every source is guaranteed. Delete individual records and caches in the extension task page, or use browser storage tools for the extension origin. Clearing ordinary browsing history or Clifzo website data does not establish that extension private files are gone. Saved files and browser download history are separate and must be managed separately.

Website visit statistics and your choices

Public pages, including the download workspace, may run our own anonymous usage statistics. The statistics request deliberately sends only a random browser ID and a visit-event ID, not workspace source/media URLs, titles, query parameters or the launch fragment. The browser UUID defaults to 30 days. Server keyed hashes and hourly counts last at most 32 days; this statistics table does not retain raw IP addresses, user agents or browsing URLs, and is not linked to task content. Infrastructure receiving a request still encounters normal IP and request information; limits on this statistics table do not mean all infrastructure is log-free. The Anonymous usage settings control, Do Not Track or Global Privacy Control can stop our own statistics. This control is not a general advertising-consent switch and does not automatically disable Google advertising or delete downloaded files.

Cloudflare Web Analytics

Public content pages on the production website also use Cloudflare Web Analytics for visits and page performance. The download workspace, including language variants, and admin, server-job, API and error pages do not deliberately load this script. It does not use cookies or localStorage to identify visitors. It may collect page paths, referrers, browser information and loading or interaction performance; performance diagnostics can also include page elements and source URLs for resources such as images. The current official script removes query strings, fragments and URL credentials from reported page and referrer URLs. Cloudflare processes these data under its own policies, separately from the 30-day and 32-day periods for our own statistics above. Before loading, we check the anonymous-statistics preference, Do Not Track, Global Privacy Control and whether preference storage is readable, and skip the script when measurement is disallowed. Cloudflare does not provide an interface to unload its measurement listeners on the current page. Preference changes therefore apply on the next page load; a script already loaded may finish measuring the current page, and changing the setting does not automatically refresh the workspace.

Local resolution and optional source-site sessions

Native resolver code is packaged as WASM and reads source-page or API metadata locally. Downloads and merging also run locally; media transfers directly from its source or CDN to your device. By default, the browser sends source cookies under its own rules without the extension reading their raw values. Only after you choose “Allow site session access (optional)” and grant permission does the extension read cookies from the verified source tab’s cookie store and partition, for current requests to that platform’s official metadata endpoints. Temporary cookie rules match the exact request URL, extension initiator and processing tab; they are not used for media or CDN requests. Raw cookies remain briefly in local memory and browser-session request rules, never entering WASM, the Clifzo workspace, server APIs, logs or persistent storage. Sources still receive the relevant requests and session information under their own policies.

Website advertising, third parties and network paths

Cloudflare, the separate API, sources and advertising providers may operate outside your country or region. Public Clifzo pages, including /download and its language routes, may load Google AdSense Auto ads and measurement resources. Admin, server-job and API pages do not deliberately load these advertising scripts. Google and its partners may receive IP addresses, browser or device information and ad interactions, and use cookies or similar technologies to serve and measure ads, including based on prior visits to this or other sites, subject to applicable consent choices, browser settings and their policies. The links below explain their practices and personalized-ad controls. Clifzo code does not explicitly send work results as advertising API fields. However, advertising scripts run in the workspace webpage environment: local processing and extension isolation do not guarantee that these webpage scripts cannot access displayed work information or media URLs in page messages. This describes a technical access boundary, not a finding that any advertising provider actually read a particular work record.

Managing data and contacting us

Revoke website access or disable the extension in your browser to stop future capture; revoking permission does not itself delete existing records or files. Website browser data, extension storage, source-site cookies, Google ad preferences and saved downloads have separate browser or service controls. For access, deletion of identifiable website records or complaints, email clifzo@kitt.tools and include a non-sensitive request ID where possible. We cannot remotely delete extension files kept only on your device. Never email passwords, cookies, temporarily signed media links, tokens or other credentials.