Privacy policy
What AniNex does
AniNex is an independent browser extension that displays MyAnimeList episode discussions on Crunchyroll. This policy covers the extension and its discussion service. AniNex is not affiliated with Crunchyroll, MyAnimeList, or AniList.
Information we handle
- Episode information: the anime title, season number, and episode number read from a supported Crunchyroll page. While AniNex is enabled, it automatically sends these values to the AniNex discussion service to find matching comments. This information reveals which episode you are viewing.
- Show searches: if Crunchyroll provides no title, or you use “Wrong show?” or “Choose the show”, the search text you type is sent to the AniNex discussion service, which searches AniList (or MyAnimeList when AniList is unavailable). Search text is sent in the request body and is not written to the service’s request logs.
- Choices saved on your device: the show you pick is saved in the extension’s local storage, keyed by the Crunchyroll series and season, so later episodes use it. It leaves your device only as the chosen MyAnimeList entry number in discussion requests. Up to 200 recent choices are kept; “Back to automatic matching” deletes one, and removing AniNex deletes all of them.
- Connection and service logs: hosting infrastructure receives and logs IP addresses, request times, browser user-agent information, API paths, response statuses, and timing information. The application’s own log lines record request timings and cache outcomes only, not anime titles, search text, or user identifiers. To limit abuse, the service keeps each client’s IP address in memory for at most one minute to count recent requests; it is not written to storage.
- Public discussion content: comments, author names, avatars, links, and episode ratings retrieved from MyAnimeList and displayed in the discussion panel.
- Support messages: if you email us, we receive your email address and the information you choose to include to respond to your request.
The extension does not send Crunchyroll passwords, account cookies, payment details, or form data from Crunchyroll pages to the discussion API; the only text you type that it sends is a show search in AniNex’s own picker. It does not access Chrome’s or Firefox’s stored browsing-history database. Its API requests omit browser credentials and the page referrer. AniNex has no user account system, advertising SDK, or analytics SDK.
How information is used and shared
Episode information is used to resolve the matching anime and discussion thread and return comments. Operational logs support running and securing this service. Support messages are used to respond to you.
- AniNex / Heroku: the discussion service at aninex-60a22ea8db43.herokuapp.com receives the episode request. Heroku hosts it and processes connection and request logs.
- AniList and MyAnimeList: the backend sends title searches, anime identifiers, episode lookups, or discussion identifiers to resolve and retrieve public discussions. These backend requests originate from our server; the application does not forward the extension user’s IP address to these services.
- Cover images: picker results show cover images that your browser loads directly from AniList’s image host (
s4.anilist.co), or from MyAnimeList’s (cdn.myanimelist.net) when AniList is unavailable, without a page referrer. - External image hosts: displaying forum images and avatars can send your IP address and ordinary connection information directly to their hosts. Browser settings determine whether existing cookies are sent. AniNex suppresses the page referrer on these images.
- Linked websites: opening a MyAnimeList, YouTube, or other external link visits that service under its own privacy practices. YouTube links do not automatically load an embedded player.
- This page: the AniNex service on Heroku serves this policy page, and visits are logged like other requests. The page contains no analytics, external fonts, embedded media, or scripts.
Retention and caching
The service’s Heroku log history keeps only the most recent 1,500 lines. Older lines are discarded as new requests arrive, so how long a line is kept depends on how busy the service is and can be several weeks. Third-party providers govern their own records under their policies.
To answer repeat lookups quickly, the service briefly caches public anime and discussion information in bounded server memory: title searches, show-picker searches and season relationships for up to one hour, title-to-anime matches for up to six hours, episode-to-thread mappings and anime details for up to 24 hours, episode lists for up to 10 minutes, and assembled forum posts for up to one minute. Cache entries are not linked to individual viewers or IP addresses, and all of them are cleared whenever the service restarts, which happens at least daily.
Support correspondence is handled through email. Contact us if you would like your support correspondence deleted, subject to applicable retention obligations. Third-party services have their own retention practices.
Your choices
Disable or remove AniNex in your browser’s extension manager to stop future requests from the extension. No AniNex account is required. For questions about information already handled, or to request access or deletion where applicable, contact us below.
In-video timed comments are disabled and excluded from the current release. The release does not create or synchronize timed reactions and does not run in private or incognito windows. Data saved by an earlier prototype is not automatically erased by an update.
Security and Limited Use
The extension communicates with the discussion API over HTTPS. We limit the information sent to the fields needed for episode discussions.
AniNex’s use of user data complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. User data is used only to provide or improve the extension’s disclosed discussion functionality and its related operation and security.
We do not sell user data, use it for personalized advertising, transfer it to data brokers, or use it to determine creditworthiness or for lending. Transfers are limited to providing this functionality, legal requirements, security needs, or a business transfer with prior explicit user consent. Human access to user data is limited to explicit consent for specific information, security investigations, legal requirements, or aggregated and anonymized internal operations.
Contact and policy updates
Contact the AniNex developer at ani-nex-support@aninex.mozmail.com with privacy questions or requests. Please avoid sending passwords or other unnecessary sensitive information.
We will update this page when these practices change and revise the date above. Where required, changes will also be disclosed in the extension or store listing.