xTaskjs 1.0 is live: role-based accounts, documentation, and a customizable interface.

Privacy

Cookie and privacy details for xtaskjs.io.

This page summarizes the data the site stores for authentication, language preferences, account security, and account operations.

Essential cookies only

The public site currently uses cookies for authenticated sessions, temporary login verification, and locale selection.

Account information

If you register, the application stores the profile and security fields required to operate your account.

Access protection

Registration and login events can include network and device metadata used to secure accounts and review sign-ins.

Overview

How this site handles data

  • Public browsing does not require an account, but account features process user data when you sign up or log in.
  • Security-related values such as passwords, verification codes, and reset codes are stored as hashes rather than in plain text.
  • Cookie and local storage usage is limited to site operation, language selection, and interface preferences.

Cookies

Cookies and browser storage

The site currently uses the following identifiers in the browser:

  • xtask_session: Keeps authenticated users signed in securely for up to 8 hours.
  • xtask_login_challenge: Stores a temporary verification challenge during login and expires after 10 minutes.
  • xtask_locale: Remembers the selected site language for up to 1 year.

Browser local storage

Theme preference is stored in local storage under the key xtask-theme. It is kept in your browser and is not sent to the server as an HTTP cookie.

Accounts

Information stored for user accounts

When an account is created or maintained, the application can store:

  • full name, username, and email address
  • password hash instead of the raw password
  • email verification, two-factor, and password reset hash values with expiry times
  • communication preferences such as news updates and newsletter subscription choices

Security

Access and security metadata

To protect accounts and make sign-in activity visible to the user, the application can store:

  • registration IP address and registration country information when available
  • login event history with IP address, country, region, city, location label, user agent, and timestamp
  • session and login challenge cookies with short, security-focused lifetimes

Use

Why the data is used

  • to create and maintain user accounts
  • to verify email ownership, reset passwords, and complete secure sign-in flows
  • to remember the selected language and preserve authenticated sessions
  • to review account access activity and respond to suspicious login behavior

Contact

Questions and updates

If the site begins using additional optional cookies or changes how personal data is processed, this page should be updated to reflect that behavior.