AniBloom · Privacy

Privacy & service data

Last updated: November 3, 2026

AniBloom is a public, catalog-only service for Nuvio. It has no AniBloom account or sign-in feature. Catalog requests are processed by AniBloom's server and may involve third-party data services described below.

Information handled by AniBloom

Network and request metadata. When you visit the website or call an addon endpoint, the hosting platform receives ordinary connection information such as your IP address, request path, headers, and timing. The hosting platform's own logging and processing are governed by its policies.
Rate-limit identifier. For catalog request limiting, AniBloom reads the client IP supplied by the hosting platform, validates it, and derives a truncated SHA-256 digest. That digest—not the raw IP—is used as the client identifier in the application limiter and its Upstash key. This does not mean the hosting platform never receives or logs the original IP.
Catalog request parameters. Catalog requests can include a catalog identifier, offset, and optional search text. The search text is used in catalog retrieval/filtering and is included in AniList GraphQL variables for the relevant catalog request. The addon does not ask for your name, email address, Nuvio account credentials, or AniList account credentials.
Catalog data. AniBloom retrieves anime titles, identifiers, schedules, relationships, and related catalog fields from AniList, then resolves provider identifiers where needed. These are catalog/media fields, not information submitted as a personal profile.

Third-party services and data flows

AniBloom's server makes HTTPS requests to third-party services to retrieve catalog data and map media identifiers. Depending on the catalog and which identity fallbacks are needed, requests may involve:

AniList: the primary GraphQL source. Requests include catalog query variables such as page/season/date filters and, for relevant requests, the search text. AniList also returns titles, identifiers, schedule details, and media relationships used by later stages.
The Movie Database (TMDB): fallback title searches and external-ID lookups. AniBloom sends media titles/search terms or provider IDs needed to resolve a match. A server-side TMDB API token is sent in the authorization header; it is not sent to the browser.
IMDb suggestion service (IMDb privacy information): title suggestions or known IMDb-ID validation when that fallback is used.
Kitsu (service): external-ID mapping lookups used by the rolling-catalog fallback.
Identity-mapping datasets and APIs: ARM, Fribb's anime-lists dataset, AniBridge mappings, AniMap, IDMapper, Anime Mapper, and AnimeAPI (including its TSV/dump sources). Depending on the fallback stage, AniBloom requests mapping datasets or sends AniList/MAL identifiers to resolve provider IDs.
Upstash: provides the distributed request-rate limiter. AniBloom uses the hashed client identifier as the limiter identifier; the raw client IP is not used as the Upstash limiter key.
Vercel: hosts the website and addon API. Vercel receives requests and associated network metadata as part of providing its hosting and network services.

These services operate independently and have their own privacy terms and operational practices. AniBloom does not control their processing, infrastructure logs, or retention. A provider may receive its own server-side request metadata, including the AniBloom server's network address and request details.

Cookies, analytics, and accounts

The AniBloom homepage's current application code does not set analytics or advertising cookies, use browser local storage, or load a third-party analytics script. Its client-side script is used for page navigation and reveal-on-scroll presentation. AniBloom does not provide user accounts, sign-in, or user profiles. The homepage Support development button links to Buy Me a Coffee; opening that destination is a separate interaction with that service. This statement describes AniBloom's current code; it does not describe cookies or tracking that a third-party site may use after you follow an external link.

Storage and retention

AniBloom uses temporary caches for catalog responses, provider mappings, and rate-limit state to operate the service. Current configured examples include 60-second AniList response caching, rolling-catalog freshness of 30 seconds with up to 5 additional minutes for stale fallback, seasonal-catalog freshness of 1 hour with up to 24 additional hours for stale fallback, and up to 24-hour lifetimes for some mapping caches. These are operational cache settings for catalog data, not a promise about the retention of hosting logs or third-party records. AniBloom does not currently publish a verified retention period for Vercel request logs, Upstash service records, or every external provider. Please consult the linked providers' current policies for their handling of information.

Your choices and questions

You can stop using AniBloom at any time. Because AniBloom has no user account or personal profile feature, it does not offer an in-app account deletion control. This does not delete hosting-platform or third-party records that those services may hold.

For questions or corrections to this disclosure, use the AniBloom GitHub issue tracker. Do not post personal, sensitive, or account information in a public issue. There is currently no separately published private privacy-request channel.

Changes to this page

This page may be updated when AniBloom's code, providers, or data flows change. The date above indicates the latest revision of this disclosure.