Anime Maps (“AnimeMaps”) manages information handled through its website and mobile application under this Privacy Policy. Last updated: 2026-08-20

1. Operator and contact

Service: Anime Maps
Contact: animemapsx@gmail.com

2. Information we collect and store

• Account information: email address, login ID, display name, profile, bio, avatar, language, time zone and display preferences.
• Usage information: favorites, personal-calendar dates and categories, private notes and viewing history.
• Community information: ratings, comments, replies, likes, reports, support requests and operator responses.
• X and Instagram share information: the shared post’s source URL, shared text and a snapshot of event candidates produced during matching. These are stored with the share submission record to match events, confirm the candidate selected by the user and let operators handle unmatched submissions.
• Technical information: app version, OS, language, authentication sessions, connection data transformed for abuse prevention, and access logs produced by servers and infrastructure.
• Location: latitude and longitude submitted to the API when you use Nearby Events and included in its response. It is not designed for ongoing storage in your member profile, but coordinates may appear briefly in response caches, access logs or security logs. You can disable permission in device settings.

Profiles are public by default. While public, your user ID, display name, avatar and bio can be viewed by other users through the profile API without authentication. Published comments and replies show their body together with the author’s user ID, display name, avatar and public-profile status without requiring sign-in; the bio is not included in comment author information. You can change your profile to private in Settings. The public profile API then stops returning the profile for new requests. However, because that API uses response caching with max-age=60 and stale-while-revalidate=300, a public-profile response cached before the change may remain available briefly. The body and author user ID of comments and replies that remain published continue to be public. Other viewers see the author name as “AnimeMaps User” and no avatar.

3. Purposes

We use information to provide and secure the service, authenticate users, personalize displays, synchronize favorites and calendars, operate and moderate the community, prevent abuse, answer support requests, translate content, investigate failures, and improve quality and safety.

4. Automatic comment translation using Google

The full comment or reply text, source and target languages, source hash, one-time nonce, issued-at time, pseudonymous request ID and signature are sent by the AnimeMaps WordPress server to a Google Apps Script controlled by AnimeMaps and translated with Google LanguageApp. Account email, user ID, display name, favorites, private notes and current location are not attached to the translation request as separate fields. However, if a user writes a name, email address or other personal information in public comment text, that information is sent to Google as part of the full text. Do not put personal or confidential information in public comments. Google’s terms and privacy policy apply to Google’s processing.

5. Translation cache and retention

Original text and translated results are cached in the server database while the comment or reply remains, so the same text can be displayed without repeatedly sending it externally. An edit makes stale translations ineligible for display. Deleting or hiding a comment or reply removes its active translation cache and cancels its translation jobs. Separately, GAS temporarily stores translation results in Google Apps Script Script Cache for up to approximately six hours, after which they expire automatically (they may be evicted earlier because of capacity or other limits). Deleting or hiding a comment or reply does not let WordPress immediately erase this external temporary cache, so a result may remain until it expires. Technical metadata for completed and cancelled jobs is normally removed progressively after 30 days. Metadata needed for retries or failure investigation may remain until the issue is resolved.

6. Private notes

A favorite’s private note is returned only in its owner’s authenticated views. It is not included in public profiles, events, comments, calendar or image shares, or GAS translation. Notes are stored in the server database and backups, are not end-to-end encrypted, and may be accessed by operators where needed for maintenance, security, incident response or support. Do not enter passwords or other secrets. Removing a favorite also removes its note from the active database.

7. Calendar share links

Creating a calendar share makes a fixed snapshot containing the selected month and categories, event titles, scheduled dates, event start and end dates, and event images. Anyone who has the link can view it. The viewing period is at most 30 days from creation. Each user may have at most 20 active links; if a new link is created when that limit has been reached, the oldest active link may become unavailable before 30 days. A link can be revoked through a supported screen or the authenticated API. If the current app does not show a revoke control, contact the address above. Share links carefully. The active snapshot database row stores a hash instead of the link token itself, together with the owner’s user ID and the snapshot. However, the raw share link may be recorded in web/CDN access logs or security logs. Private notes are not included in the snapshot.

8. Storage, deletion and backups

Account information is retained while needed to maintain the account, and usage information while needed to provide features and operate the service safely. User deletion actions remove data from the active service database or erase its body as appropriate. A report’s reason, reporter-supplied details and snapshot of the reported body may remain in audit records after the original post is deleted or hidden. Records needed for security or legal matters may also be retained for a reasonable period. Backup copies are not deleted immediately; they age out through normal backup rotation and may temporarily reappear during disaster recovery.

9. Service providers, disclosure and operator access

Hosting, email and translation providers may process information only as needed to provide those services. We do not sell personal information.

We may disclose information with consent, when required by law, or when reasonably necessary to protect life, safety or the service. Authorized operators may access stored information where needed for service operations, maintenance, moderation, security, incident or support response, or legal compliance.

10. Security

We use reasonable measures such as access controls, encrypted transport, protected authentication tokens and separated privileges. No Internet transmission or storage system can be guaranteed absolutely secure.

11. Your choices and requests

Available app screens let you review, change or remove profile information, history settings, posts and favorites. For other access, correction, deletion or account requests, contact the address above in a way that allows us to verify the account holder.

12. Changes

We may update this policy when features or data handling change. Material changes will be announced on the site or in the application.