Media Wiki:Cookie statement

From Antispoofing Wiki

As stated in our Privacy policy, AntiSpoofing Wiki strongly believes in the values of privacy and transparency. To that end, we have created this Cookie Statement as a clear reference guide to the use of cookies on the site. The Cookie Statement explains how we use cookies (and other locally stored data technologies), how we use third-party cookies, and how you can manage your cookie options. For more information on our privacy practices, please visit the Privacy policy page.

AntiSpoofing Wiki is a non-profit organization that actively collects some types of user information using a variety of commonly-used technologies. These include tracking pixels, JavaScript, and locally stored data technologies, such as cookies and local storage.

What is a cookie?

A "cookie" is a tiny data file that we transfer to your computer, mobile phone, or any other device that you use to access the AntiSpoofing Wiki Site. The cookie is primarily used for authentication and tracking. Every cookie expires after a certain period of time which varies depending on the function of the cookie and your browser configuration.

Cookies are often categorized based on how long they remain active before they expire. A "session" cookie expires when you close your web browser or mobile application. A "persistent" cookie remains in your device, even after you close your browser or mobile application and expires according to the duration set by the site, or when you delete it manually.

You may remove or disable cookies through your browser settings. For more information on how to manage your cookie options, please see Section 3 of the Cookie Statement below.

For more information on cookie types and relevant key terms, please read through our Privacy Policy Glossary.

What types of cookies does AntiSpoofing Wiki use and for what purposes?

Cookies are not required in order to read or edit the AntiSpoofing Wiki Site. We use the information we receive from cookies and other locally-stored data technologies to make your experience with the AntiSpoofing Wiki Site better and safer. Through cookies, we seek to gain a greater understanding of user preferences and interactions with the AntiSpoofing Wiki Site, and to generally improve our services. Cookies are required in order to login and for your edits to be associated to a user account; without cookies, your edits will be anonymous and not linked with an account.

We use cookies, JavaScript, tracking pixels, and other locally-stored data technologies to accomplish different purposes. Below is a list of the categories of cookies we use and their respective purpose.


Functionality cookies help in the working of the AntiSpoofing Wiki Site and are essential in enabling you to move around the site and use its features. These cookies are useful for retaining your username in the login field, maintaining your session, remembering previous actions and keeping you logged in (if selected) etc.

Here are a few examples:

Name Expires Category What does it do?

{$wgCookiePrefix}* Token

365 days, if the user chooses ‘Keep me logged in’. Otherwise omitted. Functionality Provides ‘Keep me logged in’ functionality.
{$wgCookiePrefix}* UserID, UserName 365 days, if the user chooses ‘Keep me logged in’. Otherwise 30 days. Functionality Helps identify you to the wiki, and keeps you logged in.
loginnotify_prevlogins 180 days Functionality Verifies that you are logging in from a known device.

This affects the threshold for how many unsuccessful login attempts trigger a notification to the user.


{$wgCookiePrefix}* Session

When user exits browser Functionality Manage sessions. Provides functionality such as logging in to AntiSpoofing Wiki.


These cookies store your preferences, so that they can be remembered the next time you use the AntiSpoofing Wiki Site and provide a more customized experience. These cookies are useful for recognizing and maintaining your language preferences and remembering changes you have made to display (such as text size and fonts). Preference cookies ensure that we can provide you with the look and feel that you want, and more.  

Here are a few examples:

Name Expires Category What does it do?
stopMobileRedirect 30 days Preferences Tells us not to redirect to the mobile site if you donot allow that.
uls-preferences Local Storage, not a cookie Preferences Allows you to set preferences for the Universal Language Selector functionality.
hidewatchlistmessage- [watchlistMessageId]

● where watchlistMessageld is the Id of the message being hidden

28 days Preferences Allows a user to hide a watchlist message.
userFontSize Local Storage, not a cookie Preferences Keeps track of your preferred font size on the mobile site.
preferredEditor Local Storage, not a cookie Preferences Keeps track of your preferred editor on the mobile site.

Performance and Analysis:

These cookies count the number of visitors and collect information about how you use the AntiSpoofing Wiki Site. This allows us to better understand your user experience on the AntiSpoofing Wiki Site and helps us improve them for you and other users — for instance, making sure that users are easily

finding the information they need. Other examples include:

  • remembering pages visited, and actions taken on the AntiSpoofing Wiki Site so we can optimize the pages;
  • remembering if users get error messages from web pages;
  • storing your most recently read articles directly on your device, so they can be retrieved quickly;
  • remembering the topics searched so that we can optimize the search results we deliver to you;
  • remembering the list of articles you are following on your watchlist so that we can recommend similar articles that you may be interested in.

Here are a few examples:

Name Expires Category What does it do?
centralnotice_bucket 7 days Performance and Analysis Helps us understand the effectiveness of notices provided to users through the CentralNotice extension.
ext.popups.core.previewCount Local Storage, not a cookie Performance and Analysis Helps us understand the effectiveness of Hovercards.
WMF-Last-Access 30 days Performance and Analysis Helps us calculate Unique devices accessing our site.


We never use third-party cookies on this site unless we get your permission to do so. These cookies would allow us to render services provided by third parties, such as "like" and "share" buttons. These kinds of services necessitate the use of a cookie in order to maintain adequate services.

If you ever come across a third-party cookie transferred to your device during your access of the AntiSpoofing Wiki Site, when you did not take any action to authorize the use and/or transfer of that cookie (such as one that may have been mistakenly placed by another user or administrator), kindly report that cookie to us at

What are my cookie options?

While this is not a comprehensive list, below are some of the things that you can do to limit use of cookies and other locally-stored data technologies on your device. While cookies and other locally-stored data technologies may not be necessary to use our site, some features may not function properly if you disable them.

You can:

  • remove or disable specific locally-stored data on your browser’s settings (you can reset your web browser to refuse all cookies or to indicate when a cookie is being sent);
  • use a browser that can block third-party cookies; or
  • install a plug-in to block locally-stored data, if one is available.

Turning off the browser’s cookies will prevent tracking pixels from tracking your specific activity. A tracking pixel may still record an anonymous visit from your IP address, but unique information will not be recorded. If you do not want to receive tracking pixels, you will need to disable HTML images in your browser-based email client, and that may affect your ability to view images in other emails that you receive.

Where can I find more information?

Please read through our Privacy policy for more information. If you have any further questions, contact


Please note that in the event of any differences in meaning or interpretation between the original English version of this document and a translation, the original English version takes precedence.