時間 jikan-edge / privacy

Privacy

jikan-edge is a stateless-by-design API: no accounts, no cookies, no client-side storage. This page explains, plainly, what actually happens to a request.

Last updated 2026-08-10 · applies to the maintainer's public instance at jikan.lucashdo.com (and its legacy hostname jikan-edge.lucas-hdo.workers.dev, the same Worker) — see the note on self-hosted copies below.

What this API does not do

  • No user accounts, no login, no API keys.
  • No cookies. No localStorage/sessionStorage. Nothing set in your browser.
  • No analytics or tracking scripts on this site or in API responses.
  • No IP address is ever written to this application's own database.

Rate limiting

Every request's IP (via Cloudflare's CF-Connecting-IP header) is checked against two counters — a short burst window and a per-minute sustained one — to decide whether to answer 429. That check happens in Cloudflare's Rate Limiting service, in memory, per the configured window. This application never persists the IP anywhere; it is used for that one comparison and then discarded.

Request logs

Cloudflare Workers Observability is enabled for this deployment, which means Cloudflare's own infrastructure logs requests (method, path, status, timing) for operating and debugging the Worker. Those logs are Cloudflare's, governed by Cloudflare's privacy policy, not something this application controls or exports elsewhere. The metrics this application itself emits (console.log, visible only in that same Cloudflare log stream) record route, cache status and timing — never an IP address, never a request header.

Cached MyAnimeList data

The core of this API is a cache: public MyAnimeList pages (anime, manga, character, person, club, producer and user-profile pages) are fetched, parsed and stored in this deployment's own database so repeat requests don't re-fetch MyAnimeList. That includes public MAL usernames and whatever a user has made visible on their own MAL profile — the same data anyone can already see by visiting that profile directly. Nothing private or login-gated is fetched; a profile MyAnimeList itself hides (private profile, login required) is not accessible here either.

If you'd like data about your MyAnimeList account removed from a specific instance's cache, contact that instance's operator — for the maintainer's public instance, open a GitHub issue.

Third parties

Cloudflare is the infrastructure this runs on (Workers, D1, Rate Limiting) — see their own privacy policy for what they collect operating that infrastructure. MyAnimeList is the public source this API reads from; this project only fetches pages MyAnimeList already serves to anyone, at a rate designed to stay light on their servers.

This is MIT-licensed, self-hostable software. This page describes the maintainer's own public deployment. Anyone running their own copy on their own Cloudflare account controls their own instance's data, logs and retention — this policy doesn't speak for them.

Changes to this page

This page is a plain-language description of how the code actually behaves, kept in the same repository as that code. If the handling described here ever changes, this page changes in the same commit — see the changelog or the file history on GitHub.