ANIIMOLAB
Privacy
Your AniimoLab identity and checklist remain separate from your game account.
Google sign-in
Google provides an account identifier, verified email and display name. We use these to identify your AniimoLab account and associate your collection. We do not receive your Google password, request game credentials or ask for Gmail, Drive or contacts access.
Account collection and cookies
Collection access requires sign-in. Saved species and form IDs are stored under your account in PostgreSQL. Cloud progress stays in browser memory rather than a guest checklist. Essential Secure, HttpOnly session cookies maintain sign-in; the database stores token hashes. Signing out invalidates the current session.
Backups and your choices
You can export a checklist backup, merge a supported backup, or reset the current checklist after confirmation. Resetting a checklist does not delete your account. To request access, correction or deletion, contact the operator; ownership must be verified. Backups may retain earlier data under the existing retention policy. Older guest checklists are not automatically imported into this guide.
Website requests
Cloudflare processes website and image requests for delivery and operation. This guide does not include your identity, email or collection in analytics parameters. Public pages use Google Analytics 4 and Cloudflare Web Analytics to understand visits and performance. GA4 does not receive account or collection contents, search queries, or URL fragments; local previews do not load GA4. A temporary same-tab return path can be saved during sign-in; it contains no credentials or collection contents.
Contact
Sending email shares the information you choose to include with your email provider and the site operator at contact@aniimolab.com. Do not send passwords, login codes or game credentials.
Popular entity page views
Visits to public Aniimo, item, skill and location detail pages help choose homepage cards, including direct arrivals and refreshes. An eight-day Secure, HttpOnly cookie holds a random browser token; PostgreSQL stores its keyed hash, entity type and ID, visit time and publication ID. The homepage ranking uses up to seven days of deduplicated visits. It does not use your account, collection, search text, referrer or raw IP. Identified automated requests are excluded, but no filter can guarantee every recorded visit came from a person. Older records are removed by scheduled maintenance.