AnimeBookmark Tracker
AnimeBookmark Tracker Privacy Policy
This policy explains how AnimeBookmark, the service and brand behind AnimeBookmark Tracker, handles information when you use the Chrome extension and its connected AnimeBookmark account and API features.
This policy is specific to AnimeBookmark Tracker. It covers the extension, its sign-in flows, the dedicated https://animebookmark.com/extension-signup/ account-setup page, optional access to tracking-ready streaming services, presentation-only information about Coming Soon services, and the AnimeBookmark account and API activity the extension creates. Other use of the AnimeBookmark website may involve separate website features and choices.
Privacy at a glance
- Tracking is off by default. You must sign in, review the disclosure, grant optional access to a tracking-ready service, and enable that provider before playback inspection begins.
- Playback tracking is currently available for eligible Crunchyroll and Netflix anime episodes. Amazon Prime Video, Disney+, HIDIVE, and Hulu are displayed as Coming Soon with disabled controls; they request no site permission and do not run playback tracking in this release.
- Qualified watch evidence and an account-scoped episode match can update your AnimeBookmark Bookmarks and watched-episode progress only after the viewing session ends and final checks pass.
- The extension does not request broad browser-history access, Chrome's broad tabs permission, access to every website, or Incognito access.
- You can disable one provider without disabling another, disable reminders, correct a match, sign out, uninstall, or contact the AnimeBookmark Privacy Officer about access, correction, or deletion.
- AnimeBookmark does not sell Tracker user data or transfer it to advertising platforms, data brokers, or information resellers.
Identity and scope
AnimeBookmark operates AnimeBookmark and AnimeBookmark Tracker. The responsible contact for this policy is the AnimeBookmark Privacy Officer at [email protected].
This policy applies when the Tracker signs you in to AnimeBookmark, sends you to its dedicated extension account-setup page, stores extension settings, accesses an enabled tracking-ready streaming-service page, records eligible playback evidence, asks you to confirm an anime or episode, or requests the resulting Bookmark and watched-episode update from the AnimeBookmark API.
The Tracker's single purpose
The extension does not use this data for general browsing analytics, advertising, profiling, market research, credit decisions, or an unrelated product purpose.
Current streaming-service capabilities
This table is the authoritative public list of provider-specific behavior for this policy. Tracking available means the provider can inspect an eligible episode page and create the evidence flow described below after opt-in. Coming Soon means the provider is presentation-only: its disabled control requests no permission and stores no provider choice, intent, consent, activation, site-access state, watch evidence, match state, or runtime state.
| Service | Status in this release | Optional origin | Provider-specific behavior |
|---|---|---|---|
| Crunchyroll | Tracking available | https://crunchyroll.com/* and https://www.crunchyroll.com/* | After explicit provider consent and access, the packaged bundle is registered across the two exact Crunchyroll origins so it can follow provider navigation. On non-watch routes it can perform passive video and DOM lifecycle checks, but exact watch-route validation prevents metadata collection, a watch session, local evidence, matching, or AnimeBookmark tracking API traffic. On an eligible watch route it can inspect the bounded title, episode, and HTML video fields described in this policy. |
| Netflix | Tracking available for anime episodes | https://www.netflix.com/* | After explicit provider consent and access, a URL-only route bootstrap can recognize a transition to an exact numeric /watch/<id> route. The full tracker bundle is injected only on an authorized exact watch route; credited playback tracking and evidence begin only after one eligible episodic player, visible episode labels, and anime classification pass the checks described below. |
| Amazon Prime Video | Coming Soon; presentation only | None in this release | The current version shows a colored Coming Soon card and a disabled settings control. It does not request site access, store a provider choice or enable intent, inject a script, inspect a page or video, collect or upload playback data, request a match, or update Bookmarks. |
| Disney+ | Coming Soon; presentation only | None in this release | The current version shows a colored Coming Soon card and a disabled settings control. It does not request site access, store a provider choice or enable intent, inject a script, inspect a page or video, collect or upload playback data, request a match, or update Bookmarks. |
| HIDIVE | Coming Soon; presentation only | None in this release | The current version shows a colored Coming Soon card and a disabled settings control. It does not request site access, store a provider choice or enable intent, inject a script, inspect a page or video, collect or upload playback data, request a match, or update Bookmarks. |
| Hulu | Coming Soon; presentation only | None in this release | The current version shows a colored Coming Soon card and a disabled settings control. It does not request site access, store a provider choice or enable intent, inject a script, inspect a page or video, collect or upload playback data, request a match, or update Bookmarks. |
AnimeBookmark Tracker is an independent service and is not affiliated with, endorsed by, or sponsored by any streaming service listed in this policy.
Your choices before and during tracking
- An AnimeBookmark account and sign-in are required before information can synchronize with your account.
- Provider access is optional and provider-specific. No streaming-service origin is granted at installation.
- Each tracking-ready provider stays off until you review the in-extension disclosure, affirmatively accept it, grant that provider's exact optional site permission, and enable it.
- Enable All Tracking requests only the exact current tracking-ready provider options—Crunchyroll and Netflix—and optional generic desktop reminders in one direct gesture. It does not include disabled Coming Soon controls or create authority for an unnamed future provider. A provider made tracking-ready in a later release remains off until you take a new action.
- Choose specific tracking options lets you enable or disable individual tracking-ready providers and reminders. It also shows disabled Coming Soon controls for services that are not available yet.
- Desktop match reminders are optional, require separate Chrome notification access, contain no anime or episode title, and are off by default.
- Disabling tracking, signing out, or uninstalling clears the applicable local state described below, but it is not a request to delete data already accepted by the AnimeBookmark server.
Data categories handled
The Chrome Web Store treats data as handled when it is collected, transmitted, used, shared, or stored locally. The table therefore includes local-only processing as well as information sent to AnimeBookmark.
| Category | Specific data | Source | Purpose | Location |
|---|---|---|---|---|
| Account identity | AnimeBookmark user ID, email, display name, and selected avatar URL/source | You, your AnimeBookmark account, or your Google basic profile | Identify the correct account, show the profile, and isolate consent, evidence, and matches by account | AnimeBookmark server and restricted extension storage |
| Authentication | Password submitted for password login; AnimeBookmark access and refresh tokens; Google subject, email/profile, transient Google token or one-time chooser handoff; session IP and user agent | You, Chrome Identity/Google, and request metadata | Sign in, maintain sessions, prevent abuse, and protect account access | Extension session/local storage and AnimeBookmark server |
| Streaming-service browsing context | Enabled provider hostname, provider media ID, sanitized canonical watch URL, and relevant timestamps | The current enabled tracking-ready provider page | Identify the episode being tracked, bind the correct page, and deduplicate evidence | Locally and, for consented evidence, the AnimeBookmark server |
| Website and episode content | Bounded provider-specific series, season, episode-number, episode-title, structured metadata, and safe AnimeBookmark catalog presentation | The current enabled tracking-ready provider page and AnimeBookmark catalog | Determine whether the content is eligible and help the user confirm the correct match | Locally and on the AnimeBookmark server as needed |
| Netflix anime eligibility | One consistent title identity, its eligible or ineligible result, and the Genres and This show is ... taxonomy labels used to derive that result; fetched HTML is not persisted | A credential-free request to the matching Netflix title page | Fail closed unless Netflix explicitly classifies the episodic title as anime | Bounded tab memory only; the classification data is not sent to AnimeBookmark |
| Playback activity | Duration, watched timeline ranges, credited playback time, visible/hidden time, maximum position, bounded seek/pause/stall counts, and session/observation times | The eligible HTML video element on the enabled page | Calculate tracked coverage, reject implausible evidence, and determine whether final checks pass | Local journal and AnimeBookmark server after consent |
| Match activity | Suggested candidates, prompt/candidate challenges, confirmation, correction, presentation, retry, and expiry state | Your actions and the AnimeBookmark API | Save or correct the account-scoped anime and episode match | Locally and on the AnimeBookmark server as applicable |
| Bookmark and progress state | Projection status and the resulting Bookmark creation or exact episode watched update | AnimeBookmark API | Show whether a qualified exact match updated your Bookmarks | AnimeBookmark server and short-lived status locally |
| Extension settings | Tracking-ready provider-enabled choice, consent version/time, setup state, notification preference, activation binding, permission intent, and retry metadata | Your choices and the extension | Enforce consent and operate the Tracker safely | Restricted Chrome storage |
| Network and security data | Request IP, user agent, timestamps, rate-limit/session/security data, and sanitized error diagnostics when enabled | HTTP requests, infrastructure, and backend errors | Authentication, abuse prevention, security, reliability, and troubleshooting | AnimeBookmark server and the service providers listed below |
Google Sign-In
- The extension requests only the openid, email, and profile OAuth scopes.
- The basic profile information used can include Google's stable subject identifier, email address, display name, and profile image.
- AnimeBookmark uses this information only to create, identify, link, and authenticate the correct AnimeBookmark account and show the safe account summary.
- The fast sign-in path can send a short-lived Google access token to AnimeBookmark for validation. The extension and backend do not persist that Google access token.
- The explicit account chooser uses Google's hosted authorization-code flow with PKCE. The extension receives only a short-lived, single-use AnimeBookmark handoff code. It does not store Google's authorization code, PKCE verifier, access token, or the Web OAuth client secret.
- Pending OAuth handoff records become eligible for deletion after approximately 10 minutes, ready handoffs after approximately 2 minutes, and consumed handoffs immediately.
- The extension does not request Gmail, Drive, Calendar, Contacts, or other Google-service content.
- A Google-hosted avatar can cause a standard image request to Google. This does not grant the extension general browsing access to Google.
Optional streaming-service access and page inspection
Only a tracking-ready provider that the signed-in user explicitly enables can run a playback tracker. Packaged isolated scripts inspect only the provider-specific route, lifecycle, bounded page, and HTML video fields described in this policy. The extension may query tabs matching an enabled provider to start or stop that provider's tracker, but it does not keep a general tab inventory. Incognito operation is not allowed.
The Tracker ignores videos shorter than five minutes. Crossing its displayed 80% coverage target is not an automatic watched result; the viewing session must end, every timeline and plausibility check must pass, and an exact account-scoped match must exist before Bookmarks can update.
Crunchyroll
After Crunchyroll is enabled, its packaged tracker bundle is dynamically registered across only https://crunchyroll.com/* and https://www.crunchyroll.com/* so it can follow the site's navigation lifecycle. On a non-watch route, the bundle can scan for candidate video elements, attach passive video listeners, and observe DOM mutations to detect route or player changes. Exact watch-route validation prevents those lifecycle checks from reading or storing episode metadata, starting a coverage session, creating local evidence or match state, or contacting an AnimeBookmark tracking or mapping API.
On an eligible Crunchyroll watch route, evidence uses a provider media ID and a sanitized canonical watch URL. Query parameters, fragments, credentials, locale, and title slugs are removed. The adapter can read bounded page and Open Graph titles plus series, season, and episode fields exposed in JSON-LD metadata. For matching only, it can derive at most three normalized numeric episode hints from those bounded labels. These hints do not enter the watch-evidence journal.
Netflix route handling
Netflix can change from Browse to Watch without loading a new document. After Netflix is enabled, a small isolated route bootstrap on the exact Netflix origin reads only location.href in memory to distinguish an exact numeric /watch/<id> path from every other route. It ignores query parameters and fragments and sends the service worker only a fixed provider/version wake-up. It does not send the URL or media ID and does not inspect the Browse-page DOM, title, video, profile, account data, cookies, or other page content.
The service worker independently rechecks the signed-in account, Netflix consent and activation, optional site grant, top-level non-Incognito sender, and current exact watch route before it can inject or repair the full tracker. Leaving the watch route, disabling Netflix, signing out, removing permission, or provider cleanup stops or resets that route handling.
Netflix anime eligibility request
An exact Netflix watch route and visible episode labels are not enough to start tracking. The Netflix adapter makes a bounded HTTPS GET request to https://www.netflix.com/title/<watch-id> and follows only a consistent Netflix title identity.
The Netflix eligibility request
- Omits cookies and other credentials
- Sends no referrer
- Bypasses the browser cache
- Asks only for HTML
- Is time-bounded and size-bounded
- Is processed locally to read one consistent title-metadata group containing Netflix's Genres and This show is ... taxonomy labels
Tracking starts only when that taxonomy explicitly classifies the title as anime. The adapter retains only the resolved Netflix title identity and its eligible or ineligible result in bounded tab memory; it does not persist the fetched HTML. Failed, pending, malformed, oversized, ambiguous, conflicting, or explicit non-anime results fail closed. No playback card, credited coverage, match request, local watch journal entry, or AnimeBookmark watch API traffic is created for the rejected interval, and time observed while classification is pending is not backfilled.
Because this is a direct request to Netflix, Netflix necessarily receives the requested title-page path and ordinary network information such as the device's IP address and user agent. The request does not include an AnimeBookmark account identifier, AnimeBookmark token, watch evidence, match choice, or referrer.
Netflix tracking additionally requires one eligible player and unambiguous visible structured series-and-episode labels. It rejects movies, live playback, previews, trailers, explicit non-anime titles, and ambiguous or multiple-player states, and suspends evidence credit while a visible advertisement is identified.
Data not read from provider pages
The Tracker does not read provider login credentials, cookies, form values, DRM data, CDN or media-resource URLs, advertising identifiers, or unrelated browsing history or website content. It does not capture, persist, or upload full DOM snapshots from signed-in provider pages. As disclosed above, the Netflix eligibility request transiently parses a bounded title-page HTML response for one consistent taxonomy group and does not persist that HTML.
Data stored by the extension
Trusted extension contexts use chrome.storage.session and restricted chrome.storage.local. Passwords are never stored in extension storage. Chrome local storage is not described as end-to-end encrypted or automatically encrypted at rest.
| Local item | Retention or bound |
|---|---|
| AnimeBookmark access token | Browser session in chrome.storage.session |
| Rotating refresh token | Restricted local storage until logout, revocation, expiry, account replacement, or environment reset |
| Minimal account summary | Restricted local storage until logout, account replacement, or environment reset |
| Tracking-ready provider or reminder enable intent | Held in trusted session storage for up to 5 minutes and bound to the exact account, environment, and requested option; cleared on success, denial cleanup, failure, disable, logout/account change, migration, or expiry |
| Tracking-ready provider choice and consent | Account/provider scoped until disable, logout/account change, re-consent/reset, or environment reset as applicable |
| Activation ID | Recreated for each enablement and used to reject stale trackers. A content tracker receives only its opaque provider activation binding and never the AnimeBookmark account ID |
| Unsent watch-evidence journal | Up to 7 days; maximum 25 live sessions and 1 MiB serialized data |
| Match and prompt state | Maximum 80 media records plus 160 displayed-session markers, with a combined 256 KiB limit. A pending or recoverable lookup record may retain at most three normalized mapping-only episode-number hints with fixed source categories; the hints are excluded from the watch-session journal. A display marker contains only the provider, provider media ID, random playback-session ID, display timestamp, and a Boolean indicating whether that session finished the prompt and may show Manage episode match. The Boolean contains no match choice. Match records and markers are pruned after 30 days; short-lived prompt and candidate challenges expire after 20 minutes |
| Projection-status presentation cache | Up to 15 minutes; maximum 25 records. The popup receives only the fixed version and status, not internal account, session, catalog, mapping, or source-URL identifiers |
| Enable All Tracking aggregate | No global enableAll choice or future-provider authority is stored; the aggregate button is derived from current tracking-ready provider and reminder choices |
| Coming Soon providers | No provider choice, enable intent, optional site grant, consent, activation, script registration, runtime, journal, match, or projection state is created in this release |
Chrome storage is limited to trusted extension contexts. Rebuilding the same installation for a different API environment triggers a fail-closed reset that removes authentication, provider consent, optional site access, and unsent evidence before the new environment is trusted.
Data sent to AnimeBookmark
Authentication and profile
- The extension's Create account link opens https://animebookmark.com/extension-signup/ in a separate browser tab. Registration remains a first-party AnimeBookmark website flow rather than collecting a new password inside the extension.
- That dedicated page and its password-registration, email-verification, and Google account-creation requests do not initialize or send events through AnimeBookmark's Google Analytics, Reddit, or X marketing integrations; do not create or update AnimeBookmark marketing-analytics or ad-attribution identifiers; do not call AnimeBookmark's site-event endpoint; and suppress backend advertising auth-conversion events. This suppression remains tied to a pending password registration through email verification.
- Google's operational identity resources may still load when you choose Continue with Google, and Resend processes the verification email when password registration requires verification. These providers are used only for the account functions described in this policy.
- Password login sends the email address and password to the AnimeBookmark API over HTTPS solely to authenticate. The extension does not store the password, and the backend stores a salted one-way password hash instead of plaintext.
- Google login sends only the transient authentication material and basic profile identity described above.
- AnimeBookmark issues its own session tokens and may store a hashed refresh-token record with session IP address and user agent for session security.
- The popup can request the current safe profile summary and selected avatar.
Watch evidence
- Only after the current tracking-ready provider's disclosure is accepted can the extension create or send cumulative checkpoint and finalization snapshots.
- No watch snapshot is journaled before 30 credited playback seconds.
- The ordinary first checkpoint is at 60 credited seconds; a qualifying lifecycle finalization may be journaled after the 30-second floor. Later cumulative checkpoints may follow.
- Uploads can contain schema and qualification-policy versions; provider, provider-media, playback-session, and revision identity; the sanitized canonical watch URL; duration and exact watched ranges; bounded series, season, episode-number, and episode-title metadata; visible and hidden playback totals; maximum position; bounded seek, pause, and stall counts; and session and observation timestamps.
- The API binds each request to the authenticated AnimeBookmark account and independently calculates qualification. The extension never sends a completed Boolean, client-selected catalog IDs, or a command to toggle a Bookmark.
- Raw playback-rate samples, cookies, form values, DRM data, and unrelated page content are not uploaded.
- Uploads are authenticated and account-linked. Failed deliveries can remain in the bounded local journal and retry with controlled backoff until success, expiry, or a permanent rejection.
Episode matching
- After 30 seconds of unique credited coverage, the extension can request an account-scoped mapping suggestion independently of its watch-evidence checkpoints.
- The suggestion request contains provider, media, and session identity, duration, and bounded episode metadata. Crunchyroll can include at most three normalized mapping-only episode-number hints with fixed source categories; Netflix supplies only its strict visible episodic label. The request does not contain raw watched ranges, coverage metrics, the source URL, cookies, or client-supplied catalog IDs.
- You can confirm a match, search for alternatives, correct a match later, or close the prompt without sending a decision. Closing does not stop tracking or watch-data delivery, and the extension does not use prompt-frequency or per-episode snooze timers.
- After you finish the displayed prompt, Manage episode match appears separately below the tracking card for that exact playback session. Clicking it opens the side-panel manager. If the short-lived review challenge has expired, that click can request a fresh passive challenge only after the extension revalidates the same account, activation, document, provider media, and playback session; popup polling does not refresh it.
- An exact confirmation saves the selected anime and episode for your account.
- If the anime is known but the exact episode is absent, the server stores a catalog-pending anime identity. It does not fabricate an episode or update your Bookmarks until an exact episode can be verified.
- Your choice remains account-scoped. It does not become a global provider mapping or change another user's data.
Bookmark and watched-episode actions
Only new, consented, finalized evidence that passes server qualification and has an exact account-scoped match is eligible for library projection. The backend can idempotently add the anime to your AnimeBookmark Bookmarks if needed and mark only the exactly matched episode as watched. Rewatch evidence remains distinct while the canonical Bookmark and watched state stay deduplicated. The extension does not send an unrestricted client command to toggle arbitrary Bookmarks or watched state.
Optional desktop notification
Desktop match reminders are optional, off by default, and require separate Chrome notification permission. The desktop notification is generic and does not contain the anime or episode title; those details appear only after you open the extension's review interface. Your operating system may display a notification on the lock screen.
Data the Tracker does not handle
- Broad Chrome browsing history or a general tab inventory
- Incognito activity
- Provider or Google passwords read from web pages
- Captured, persisted, or uploaded full DOM snapshots from signed-in provider pages, or unrelated provider content; the separately disclosed Netflix title-page HTML is handled transiently only to derive the bounded taxonomy result
- Gmail, Drive, Calendar, Contacts, or other Google-service content
- Precise GPS location, payment-card details, health information, or personal communications
- Personalized advertising profiles or data-broker transfers
- Remote executable code
Password login does transmit the password you enter to AnimeBookmark over HTTPS for authentication. The extension does not store it and does not read passwords from supported streaming-service pages.
Permissions and host access
| Permission or access | Reason |
|---|---|
| storage | Stores the AnimeBookmark session, account-scoped tracking-ready provider choices and consent, bounded unsent evidence, match state, and small setup, retry, and presentation records. Coming Soon services store no provider choice or enable intent. |
| identity | Supports Google authentication using only openid, email, and profile |
| scripting | Registers or injects only packaged isolated tracking scripts after a tracking-ready provider is enabled, consented, and granted exact site access |
| alarms | Schedules bounded delivery, retry, expiry pruning, registration recovery, match maintenance, and short progress-status follow-ups |
| sidePanel | Shows user-invoked alternate candidates and match-correction controls bound to the currently detected episode |
| https://api.animebookmark.com/* | Supports AnimeBookmark authentication, profile, watch evidence, matching, and Bookmark-update status |
| Exact optional streaming origins | Includes only https://crunchyroll.com/*, https://www.crunchyroll.com/*, and https://www.netflix.com/*. Each supports the explicitly enabled tracking-ready provider described in the capability table. No Amazon Prime Video, Disney+, HIDIVE, or Hulu origin is requested in this release. |
| Optional notifications | Shows a generic match-ready reminder after separate opt-in; off by default |
You can remove optional site and notification access through the extension controls or Chrome's extension settings. Removing access stops the corresponding local feature but does not delete server data already accepted by AnimeBookmark.
Limited Use commitments
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
AnimeBookmark Tracker's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- User data is used only to provide, maintain, secure, or improve the Tracker's single purpose.
- Transfers occur only when necessary for that purpose, security or abuse prevention, legal compliance, or a merger or acquisition with consent required by Chrome policy.
- User data is not sold or transferred to advertising platforms, data brokers, or information resellers.
- User data is not used for personalized, retargeted, or interest-based advertising.
- User data is not used for creditworthiness or lending.
- Humans do not read user data except with your specific consent for support, for security or abuse investigation, to comply with law, or in permitted aggregated or anonymized internal operations.
Security safeguards
- HTTPS/TLS protects user-data transmission in transit.
- Passwords are not stored in the extension, and backend password records use a salted one-way hash.
- AnimeBookmark access and refresh tokens are separated between session and restricted local Chrome storage.
- Refresh-token records are hashed on the server.
- Account, provider, consent, environment, activation, and request-sender checks help prevent cross-account or stale-context use.
- Local journals and caches have capacity and time bounds.
- Streaming-site access is optional, exact, and provider-specific; the extension does not request <all_urls>.
- Canonical evidence URLs are reduced to the provider's strict watch identity: Crunchyroll query strings, fragments, credentials, locale, and title slugs are removed, while Netflix uses only an exact numeric https://www.netflix.com/watch/<id> URL.
- The Netflix title-page eligibility request is HTTPS, credential-free, no-referrer, cache-bypassing, time-bounded, and size-bounded.
- Executable JavaScript is packaged with the extension. Remote responses are processed only as data and are not executed as code.
- API authorization controls associate Tracker data with the authenticated account.
- Sentry reporting is configured to exclude or scrub request bodies, headers, cookies, query strings, IP addresses, emails, usernames, and credential-shaped fields.
No storage or transmission system is perfectly secure. AnimeBookmark does not claim end-to-end encryption, verified encryption at rest, absolute security, or anonymous watch evidence.
Retention
Local extension retention
The local limits in Data stored by the extension apply. Disabling a tracking-ready provider clears that provider's local consent, activation, unsent evidence, match, provider-specific reminder, and presentation state for the account. Signing out clears the local AnimeBookmark session and applicable account-scoped state. Coming Soon providers have no stored provider choice, permission intent, host grant, consent, activation, or watch state to retain or clear.
Server and infrastructure retention
- Account-linked watch evidence, quota counters, confirmed and pending episode mappings, library-projection records, refresh-session security records, and related operational records currently have no automatic expiration. They remain until the account is permanently deleted or AnimeBookmark adopts a different verified retention rule.
- Application, PM2, Nginx, Cloudflare, and Sentry records do not currently share one fixed automatic expiration period. They may remain until infrastructure rotation, provider-configured expiration, or manual deletion.
- Technical logs may include IP address and user-agent information, request time, method, query-free route or URL, response status/size/time, rate-limit and security events, error messages, and stack traces.
- Manual MongoDB backups do not follow a fixed schedule or guaranteed automatic deletion period. Backup data remains until the applicable archive is manually deleted or replaced.
- Disabling tracking, signing out, or uninstalling is not a server deletion request. A Bookmark update already authorized by uploaded finalized evidence may finish after local tracking is disabled.
User controls, access, correction, and deletion
| Control | Effect |
|---|---|
| Disable a tracking-ready provider | Stops that provider's trackers, unregisters its scripts, attempts to remove its optional site permission, and clears its consent plus unsent local watch and match state for that account without disabling another provider. It does not delete uploaded server records. |
| Coming Soon provider controls | Remain disabled and make no permission request or settings change. No provider choice, site access, or watch state exists for those services in this release. |
| Disable all tracking | Attempts each tracking-ready provider's normal cleanup and reminder cleanup, preserving authentication, server-acknowledged evidence, confirmed mappings, and completed Bookmark and watched updates. |
| Disable desktop reminders | Clears the preference and reminder state. Chrome permission removal is best effort. |
| Correct a match | Future eligible Bookmark updates use the confirmed replacement. Already-saved watched progress is not automatically undone. |
| Sign out | Clears the local AnimeBookmark session and account tracking state and attempts backend token revocation. It does not delete uploaded watch evidence or mappings. |
| Uninstall | Removes the extension from Chrome but does not send a server-deletion request. |
| Request access, correction, or deletion | Email [email protected] from the address associated with your account. AnimeBookmark may request additional information to verify ownership. |
Permanent account deletion is completed administratively rather than through a self-service account button. Verified deletion removes the live AnimeBookmark account, refresh sessions, Bookmarks and sharing state, watched progress, pending Bookmark imports, announcement-read receipts, extension watch evidence and quotas, confirmed and pending mappings, and library-projection records.
Deletion exceptions
- A limited administrative deletion or audit record containing the deleted account ID and email may remain for security and accountability and currently has no automatic expiration.
- Request, security, diagnostic, provider-email, and support records may remain according to their applicable retention.
- Manual backups may retain deleted data until the applicable archive is manually deleted or replaced.
- A separately created newsletter subscription is not automatically removed by account deletion and requires its own unsubscribe or removal action.
Revoke Google authorization
You can review and revoke AnimeBookmark's Google connection from your Google Account's third-party connections page. Signing out of the extension is not necessarily the same as revoking Google authorization, and revoking Google authorization does not delete AnimeBookmark server data.
Children and audience
AnimeBookmark Tracker is not directed to children under 13, and AnimeBookmark does not knowingly collect personal information from children under 13. If you believe a child under 13 has provided information through the Tracker, contact the AnimeBookmark Privacy Officer so the situation can be reviewed.
Changes to this policy
This page shows the current Last updated date. Material changes will be described or communicated before a new use begins where required. If extension data use changes, AnimeBookmark will update the in-extension prominent disclosure and consent version before collecting or using data under the changed practice.
AnimeBookmark works to keep this policy, the extension interface, Chrome Web Store listing and privacy declarations, Google OAuth consent configuration, and runtime behavior consistent.