XAutoFollow Privacy Policy

Last updated: 10 October 2026. Applies to the Chrome Web Store update version 3.2.0, including the packaged name “XAutoFollow - HeraklitBey”.

Publisher: tanerce83. Contact: taner@hotmail.fr. Chrome extension ID: fdmcppmjjchemgdgeejkaegdpghhalig.

Purpose and information handled

XAutoFollow manages selected accounts and follow/unfollow queues using your own X session. It processes X usernames, account IDs, display names, profile images, biographies, follower/following counts and lists, target accounts, queues, filters, settings, action history, counters and safety events. Usernames and account identifiers can be personal information. This information is used for account selection, relationship checks, queue management, history and safety limits.

Local storage

Settings, account lists, queues, history, counters and safety records are stored in chrome.storage.local in your Chrome profile. Chrome Sync is not used. The extension does not apply an additional encryption layer to these local records; people with access to your device/profile may access them.

Cookies, session information and account checks

The extension uses the cookies permission to read the ct0 CSRF cookie on x.com or twitter.com. If necessary, a packaged script on the X page reads the same cookie from document.cookie. The value is used in the X-Csrf-Token header to authorize requests to X.

The active account is identified from the X page and X account-verification responses. Before actions, the extension checks account identity and compares the current page's CSRF value with the expected session value to detect session/account changes. A cookie alone is not treated as proof of account identity. Missing or mismatched session information stops operations.

The extension does not persist the ct0 value or your X password in its local records. It does not read auth_token through the cookies API. The browser includes the X session cookies required for authenticated requests to X. Cookie/session values are not sent by the extension to the developer, advertising, analytics or licensing services, and they are not included in the optional Desktop queue transfer.

Network requests and sharing

This release sends no information to advertising, analytics or licensing servers. License enforcement is disabled; no 90-day trial expiration or time-based license lock applies. All features are available in this release.

Retention and deletion

Queues remain until processed or edited. Target and account lists remain until updated or the extension is removed. Main follow history retains the latest 2,000 records. Legacy quota account IDs are pruned over 48 hours. The persistent safety quota records operation-attempt times for the last 24 trusted hours, together with the last trusted time and local-clock information. When trusted time cannot be verified, quota records are retained and automation stops. Other settings and safety/activity records may remain until cleared or the extension is removed. Updates preserve local records.

Export can save supported settings, targets, queues, blacklist and main follow history to a file you control. Exported files are not encrypted by the extension. Uninstalling the extension deletes its local Chrome extension data; exported files and data held by an optional Desktop application must be deleted separately. Uninstalling does not reverse actions already taken on X. Contact the publisher for questions about access, correction or deletion; the publisher does not receive your local account lists or session cookies.

Permissions

Limited use and security limits

XAutoFollow's use and transfer of information received through Chrome permissions follows the Chrome Web Store User Data Policy, including the Limited Use requirements. Information is used only for the described account-management features. It is not sold, used for advertising, used for credit/lending decisions, or used or transferred for unrelated purposes. No remote executable code is loaded.

Rate limits, authorization errors, verification challenges, detected account restrictions, repeated network errors and time-validation failures can stop automation. Safety controls reduce some operational risks but do not guarantee compliance with X's rules or prevent account restrictions.