Cookie Policy
Donate
Last updated: March 15, 2022
ENCRYPTED SUPPORT LP ("us", "we", or "our") uses cookies on the https://www.kicksecure.com
website (the "Service"). By using the Service, you consent to the use of cookies.
Our Cookies Policy explains what cookies are, how we use cookies, how third-parties we may partner with may use cookies on the Service, your choices regarding cookies and further information about cookies.
What are cookies[edit]
Cookies are small pieces of text sent by your web browser by a website you visit. A cookie file is stored in your web browser and allows the Service or a third-party to recognize you and make your next visit easier and the Service more useful to you.
Cookies can be "persistent" or "session" cookies. Persistent cookies remain on your personal computer or mobile device when you go offline, while session cookies are deleted as soon as you close your web browser.
How ENCRYPTED SUPPORT LP uses cookies[edit]
When you use and access the Service, we may place a number of cookies files in your web browser.
We use cookies for the following purposes:
- To enable certain functions of the Service
- We use both session and persistent cookies on the Service and we use different types of cookies to run the Service:
- Essential cookies. We may use essential cookies to authenticate users and prevent fraudulent use of user accounts.
Where can you find more information about cookies[edit]
You can learn more about cookies and the following third-party websites:
- AllAboutCookies: https://allaboutcookies.org/
- Network Advertising Initiative: https://thenai.org/
What types of cookies does we use and for what purposes?[edit]
Functionality[edit]
These cookies help the our Sites work and are essential in order to enable you to move around our Sites and use their features. These cookies are useful for remembering your username in the login field, maintaining your session and remembering previous actions, keeping you logged in (if selected), and more.
Here are a few examples:
wiki:
| Name | Expires | Category | What does it do? | |
|---|---|---|---|---|
| wikiUserID, wikiUserName, wikiToken | 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. | |
| UseDC, UseCDNCache | 365 days | Functionality | Helps load balancing on our servers, makes sure all contributors see a uniform chronology of wiki edits. | |
| wiki_session, wikimwuser-sessionId | When user exits browser | Functionality | Manage sessions. Provides functionality such as logging in to our wiki. | |
| wikiPostEditRevision | 20 minutes | Functionality | Allows editing. This uses a temporary cookie for each revision ID so separate saves will never interfere with each other. |
phabricator:
| Name | Expires | Category | What does it do? |
|---|---|---|---|
| phusr, phsid | 5 years | Functionality | Helps identify you to the issue tracker, and keeps you logged in. |
discourse forums:
| Name | Essential | Expires | Description |
|---|---|---|---|
| Y | Session | Used during account creation | |
| destination_url | Y | Session | Used during login to redirect to the requested page |
| sso_destination_url | Y | Session | Used during SSO (single sign on / social) login to redirect to the requested page |
| fsl | Y | Session | Full screen login client setting |
| theme_key | Y | Forever | Client theme personalization. Only used when “Make this my default theme on all my devices” unselected. |
| cn | Y | Forever | Client clear notifications. I’m counting this as user input instead of personalization because it doesn’t make sense to ‘undo’ or change cleared notifications. |
| _bypass_cache | Y | Session | Used with ‘fsl’ for full screen login |
| _t | Y | 1440 hours | User authentication token cookie. SiteSetting.maximum_session_age.hours.from_now |
| _forum_session | Y | Session | Session cookie |
| dosp | Y | next page view | Temoporary cookie that informs client denial of service protection is in place. |
| __profilin | N | Session | Developer only, used by rack-mini-profiler to bypass work |
Preferences[edit]
These cookies store your preferences, so that they can be remembered the next time you use our Sites, for a more customized experience. These cookies are useful for recognizing and maintaining your language preference, remembering changes you have made to text size, fonts and other display preferences, so 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 don’t like 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. |
| wikicookiewarning_dismissed | 30 days | Preferences | Remembers that you have acknowledged our top banner. |
| flyInBannerIdDismissed | 365 days | Preferences | A fly-in-notification will appear on some pages after some time. If the notification is dismissed this cookie will be filled with the id of the banner so this specific banner will not be shown again |
| nocache | 365 days | Preferences | Disables server side cache. Requests most recent version. Only set on request through manual click. super menu -> Debug Helper -> Activate nocache (true) server cookie for my browser.
|
| ctbc_hide-sitenotice-banner-01 | 365 days | Preferences | Disables banner. |
Performance and Analysis[edit]
These cookies count the number of visitors and collect information about how you use of our Sites. This allows us to better understand your user experience on our Sites and helps us improve them for you and other users - for instance, by making sure users are finding what they need easily. Other examples include:
- remembering pages visited, and actions taken on the our sites 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.
We currently don't use any of these.
Third-Party[edit]
We will never use third-party cookies on our Sites 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. When a third party provides these kinds of services, they may require the use of a cookie in order to provide their services.
If you ever come across a third-party cookie transferred to your device during your access of our Sites, where 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), please report that cookie to us at adrelanos(at)kicksecure.com (Replace (at) with @.)Please DO NOT use e-mail for one of the following reasons:
Private Contact: Please avoid e-mail whenever possible. (Private Communications Policy)
User Support Questions: No. (See Support.)
Leaks Submissions: No. (No Leaks Policy)
Sponsored posts: No.
Paid links: No.
SEO reviews: No.
.
What are your choices regarding cookies[edit]
While this is not a comprehensive list, below are some of the things that you can do to limit use of cookies.
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.
If you'd like to delete cookies or instruct your web browser to delete or refuse cookies, please visit the help pages of your web browser.
Please note, however, that if you delete cookies or refuse to accept them, you might not be able to use all of the features we offer, you may not be able to store your preferences, and some of our pages might not display properly.
- For the Chrome web browser, please visit this page from Google: https://support.google.com/accounts/answer/32050
- For the Internet Explorer web browser, please visit this page from Microsoft: https://support.microsoft.com/en-us/topic/how-to-delete-cookie-files-in-internet-explorer-bca9446f-d873-78de-77ba-d42645fa52fc
- For the Firefox web browser, please visit this page from Mozilla:
- For the Safari web browser, please visit this page from Apple: https://support.apple.com/guide/safari/manage-cookies-sfri11471/mac
- For any other web browser, please visit your web browser's official web pages.
Please note, that instructions for configuring or deleting local storage may be different from configuring or deleting cookies depending on your browser.
Attribution[edit]
This Cookies Policy for ENCRYPTED SUPPORT LP is based on:
Where can I find more information?[edit]
Please read through our Privacy Policy for more information. If you have any further questions, contact adrelanos(at)kicksecure.com (Replace (at) with @.)Please DO NOT use e-mail for one of the following reasons:
Private Contact: Please avoid e-mail whenever possible. (Private Communications Policy)
User Support Questions: No. (See Support.)
Leaks Submissions: No. (No Leaks Policy)
Sponsored posts: No.
Paid links: No.
SEO reviews: No.
.
A secure by default operating system with the latest security research in place.
At
Kicksecure we value freedom and trust, supporting Open Source and Freedom Software
2012-
2024 ENCRYPTED SUPPORT LP
We believe security software like Kicksecure needs to remain Open Source and independent. Would you help sustain and grow the project? Learn more about our 12 year success story and maybe DONATE!