Animus AI Blocker Early Access Privacy Policy

Effective date: 2026-09-07

Firefox-specific scope — updated 8 September 2026

The desktop Firefox label-only release processes supported AI-generation labels, associated post text and media references locally. Settings, corrections, hashed post preferences and bounded diagnostics remain in Firefox-managed local extension storage. It does not refetch media, verify Content Credentials, run visual AI models, upload feed content or transmit analytics. Its background downloads a small signed JSON safety configuration on startup and periodic checks, without cookies, credentials, browsing content, account or installation identifiers. These essential configuration requests occur in every privacy mode. Cloudflare receives ordinary connection metadata such as IP address, request time and browser-provided user agent to deliver and protect the service. No location lookup or IP-based profiling is performed by the extension. The support, hosting, retention and contact terms below also apply to Firefox; references below to Chrome media analysis and Chrome-specific storage describe the Chrome build only. Local Firefox data can be reset or removed by clearing extension data or uninstalling the extension.

Animus AI Blocker is a browser extension that identifies strong evidence that an image or video was AI-generated and, when the user enables protection, replaces the matching feed post with a reversible notice. The Early Access release is designed to operate locally and to collect as little data as possible.

Data processed on the device

To provide filtering, Animus AI Blocker can inspect already-loaded images, video frames, media addresses, Content Credentials, platform-provided AI labels, and text associated with the same post. This processing occurs on the user's device.

Animus AI Blocker stores the following in Chrome's local extension storage:

• protection, sensitivity, privacy, and per-site settings;
• local media fingerprints and decisions needed to avoid repeating work;
• user corrections such as Not AI, including a hashed platform/post identifier for a whole-post display preference when a stable identifier is available; raw post URLs are not stored for this preference, and the hash is not exported in diagnostics or sent to Animus AI Blocker;
• up to 512 local Early Access feedback records containing only the user's AI/not-AI claim, supported platform, image/video category, decision category, and whether the post was filtered;
• aggregate filtered/displayed/uncertain counts;
• bounded, content-free performance and reliability measurements, such as rounded decision latency, media category, supported platform, and failure counts;
• the last verified signed safety configuration and its version; and
• a random installation-scoped token reserved for a future opt-in report service. In the evidence-first Early Access policy, report transmission is disabled.

The extension does not store raw media copies, page text, browsing history, account names, post identifiers, or page URLs as product analytics. Transient pixels used for local analysis are discarded after processing.

The options page can export bounded Early Access information only after an explicit click. Export beta feedback creates the correction/miss records alone. Export beta diagnostics creates one release-bound file combining those records with bounded numeric speed, reliability, cache-count, correction-count, and settings summaries. Both exclude raw media, fingerprints, URLs, post/account identifiers, content text, and per-record timestamps; neither is transmitted automatically or grants Animus AI Blocker commercial model-training rights. Sharing an exported file is a separate user action.

Data sent from the device

In the initial evidence-first Early Access release:

• No feed images, videos, frames, post text, page URLs, fingerprints, corrections, or usage analytics are sent to Animus AI Blocker.
• Local Early Access feedback records are not transmitted automatically.
• Experimental on-device models, cloud analysis, network intelligence lookup, and community reporting are disabled by the signed launch policy.
• The public build retrieves a small signed safety configuration from an Animus AI Blocker-operated HTTPS endpoint hosted by Cloudflare. This request does not include browsing content or an Animus AI Blocker account identifier. Cloudflare processes network metadata such as IP address, request time, user agent, and security information to deliver and protect the service. Our public information, privacy, and support pages are also hosted by Cloudflare.
• When Animus AI Blocker reads media or Content Credentials that the current site has already made available, the browser may request that resource directly from the originating website. Selecting Private mode prevents Animus AI Blocker background HTTP(S) media refetches; inaccessible media then remains visible.

If Animus AI Blocker later offers shared verdicts, cloud checks, crash reporting, synchronization, or a training-data contribution program, those features will be separately gated, clearly disclosed, and opt-in where required. A browser update will not silently turn ordinary browsing into model-training data.

How data is used

Local data is used only to provide and improve the user-facing filtering experience on that device: applying settings, avoiding repeated classification, honoring corrections, explaining decisions, and allowing the user to inspect content-free diagnostics.

Animus AI Blocker does not sell browsing data, use it for personalized advertising, build advertising profiles, or permit humans to read a user's browsing content. Animus AI Blocker's use of Chrome permissions and any user data obtained through them is limited to providing or improving the extension's single purpose, in accordance with the Chrome Web Store User Data Policy and its Limited Use requirements.

Sharing

The evidence-first Early Access extension does not automatically share feed content or locally stored decisions with Animus AI Blocker or third parties. Cloudflare processes the ordinary hosting requests described above. If you email support, your email provider and our support mailbox provider process your email address, message and any attachments you choose to send. We use that information to answer your request, not for advertising or model training. Do not send private feeds, passwords or material you do not have permission to share. Data may also be disclosed when required by law or necessary to investigate security abuse, subject to applicable law.

Retention and deletion

Local settings and decisions remain in Chrome extension storage until the user resets them, clears extension data, or uninstalls Animus AI Blocker. The options page provides controls to export a privacy-safe local summary and reset local decisions. Uninstalling the extension removes its Chrome-managed local storage under Chrome's normal behavior.

Any application request logs retained under Animus AI Blocker's control are security-limited and kept for no longer than 7 days, unless a longer period is required for a documented security incident or legal obligation. The initial static website and policy service add no application database, analytics script, log-export service or custom request-logging code.

Cloudflare's independently managed service and security records are separate from Animus AI Blocker-controlled application logs. Their retention is governed by Cloudflare's applicable terms and privacy practices; the limit above is not a promise that Cloudflare deletes all network metadata within that period. Cloudflare's privacy notice is available at https://www.cloudflare.com/privacypolicy/.

Voluntarily sent support emails are kept while the request is being handled and for up to 90 days after it is closed, unless a documented security incident or legal obligation requires longer retention. You may request deletion through the contact address below. Email-provider backups and independently managed security records are governed by that provider's practices.

Security

Animus AI Blocker verifies signed, expiring safety configuration before it can authorize automatic intervention. Network communication in a public build must use HTTPS. The extension fails open—leaving content visible—when evidence, configuration, or processing is unavailable or uncertain.

Children

Animus AI Blocker is not directed to children under 13 and does not knowingly collect personal information from children. The Early Access extension has no account system.

Changes

Material privacy changes will be reflected in an updated policy and, when required, an in-product notice or consent step before the changed processing begins.

Contact

Operator: Faiza Khan Country or jurisdiction: India Privacy and support email: faizakhan1485@gmail.com