Effective date: October 24, 2026
Anira is developed and operated by Hadrien Patin, France ("Anira," "we," "us," or "our"), who is responsible for the personal data processed to provide Anira.
Contact: [email protected]
This Privacy Policy explains what information is processed when you use Anira and its related backend and support services, why it is processed, where it goes, how long it is kept, and your choices and rights.
1. Summary
- Anira is an independent iOS client for discovering anime and manga, organizing AniList lists, and tracking episodes and chapters. It does not stream anime or provide manga chapters to read.
- AniList stores your AniList account and synchronized lists. Anira's backend processes the requests needed to display and update that information.
- Signing in creates an Anira service account linked to your AniList numeric account ID. Your AniList authorization token is encrypted on our server. Your device stores a separate Anira session credential in the iOS Keychain.
- We use Mixpanel for product analytics, Sentry for crash and error reporting, and RevenueCat with Apple for purchase and subscription management.
- Mixpanel identifiers are kept separate from AniList, Anira account, and RevenueCat identifiers. Pseudonymous identifiers can still constitute personal data.
- We do not sell personal data or share it for cross-company behavioral advertising.
- Deleting your Anira account does not delete your AniList account or cancel an App Store subscription.
2. Information on your device
Anira processes information locally to display the app and keep your work consistent, including:
- app preferences, navigation state, search and filter selections;
- recently loaded catalog information, cover images, profile information, account preferences, and library entries;
- drafts and records of submitted changes that need confirmation, including the relevant account and title identifiers and edited fields;
- an Anira session credential, stored in the iOS Keychain;
- identifiers, preferences, and temporary records used by the analytics, diagnostic, and purchase services described below.
Private API responses are held in memory rather than stored in a persistent response cache. Public artwork may be cached on disk. Records needed to resolve an uncertain list or preference update are stored in the Keychain so the app can check what happened without blindly repeating the change.