Privacy Policy

1. General provisions

1.1. This Policy explains what data BlueSadness receives when you use the website, dashboard, software products, API, cloud features, support, Telegram bot and Discord bot, why this data is needed and how it is protected.

1.2. The BlueSadness Administration acts as the data controller for the operation of the Service. Use of the Service is also governed by the User Agreement and the Public Offer.

1.3. If a User does not agree with this Policy, they must stop using the Service. Registration and certain features may require separate confirmation of consent.

2. Data we process

2.1. Account data:

• username, UID, password hash, role, profile settings and preferred language;
• identifiers, names and available details of linked Telegram and Discord accounts;
• avatar, profile visibility and notification preferences.

2.2. Technical and security data:

• registration and recent login IP addresses, request times, action sources and security logs;
• browser, device, operating system, client version and network request details when sent to the Service;
• for public pages viewed without authorization: a hash of the technical session identifier, IP address, normalized page route, aggregated view and action counters, first and last activity times, and the external referrer hostname when available; form contents and URL parameters are not stored in this statistic;
• hardware identifier (HWID), authentication tokens and other data required to protect the account and product access.

2.3. Usage and purchase data:

• BSC balance, purchases, activations, subscriptions, discounts, keys, payment statuses and identifiers;
• cloud configs, localizations, sharing settings and related activity history;
• support requests, user messages, attachments and read receipts;
• uploaded images, including avatars, menu backgrounds and ESP preview characters.
• imported Warface profile data, including the original XML, gameplay statistics, nickname, game profile identifier, clan, season and weapon details returned by the profile source.

2.4. BlueSadness does not request passport details or receive full bank card details. Payment details are processed by the selected payment provider under its own terms.

3. How data is used

3.1. Data is used only for purposes related to operating the Service:

• registration, login, social account linking and access recovery;
• providing products, subscriptions, cloud features, purchases and payments;
• support, user chat and delivery of selected notifications;
• protecting accounts and preventing fraud, attacks, restriction bypasses and rule violations;
• measuring interest in public pages and the registration funnel using aggregated unauthenticated activity;
• error diagnostics, stability analysis and improvement of Service features.

4. Legal bases for processing

4.1. Depending on the context, data is processed to perform the User Agreement and orders, based on the User’s consent, to comply with applicable legal requirements, and to maintain security and protect the legitimate interests of the Service and its users.

4.2. A User may choose not to provide optional data. Features that require such data may then be unavailable.

5. Data sharing

5.1. BlueSadness does not sell personal data. Information may be shared only to the extent necessary:

• with Telegram and Discord for account verification, bot commands and notifications;
• with payment providers to create and verify payments;

5.2. Third-party services process data under their own policies and may operate in other countries. Users should review those terms before using the relevant feature.

6. Storage and deletion

6.1. Data is retained while an account exists or for as long as it is needed to provide a feature. After account deletion, certain records may be retained as necessary for security, dispute resolution, transaction records and legal compliance.

6.2. An unverified registration is deleted automatically after the period shown on the activation page. Uploaded files are kept until they are replaced, the related feature is deleted, or the account is deleted, unless longer retention is required under section 6.1.

6.3. Daily aggregates of unauthenticated public-page activity are automatically deleted after 90 days. Obvious automated clients are excluded where they can be identified.

6.4. Cached IP geolocation data is normally refreshed after 30 days and entries not used for 180 days are deleted automatically.

6.5. A statistical anomaly assessment is stored only with the current imported profile statistics and is replaced or invalidated when those statistics change.

6.6. Backups may be retained for a limited period and are deleted on a rotation cycle. Backup data is not used for ordinary Service operations.

7. Data security

7.1. Data is protected using access controls, encrypted network connections, password hashing, secure tokens, event logging, backups and other organizational and technical measures.

7.2. No method of transmission or storage is absolutely secure. Users must protect their password, devices and linked social accounts and notify support of suspicious activity.

8. User rights and controls

8.1. In account settings, a User can change language, profile visibility and notification preferences. Individual messages and user content can be deleted through the relevant feature where the interface provides that option.

8.2. To request access, correction or deletion of data, a User may contact support or email support@nightzen.cc. The Administration may verify account ownership before processing a request.

9. Cookies and local state

9.1. The website uses only technical cookies and local state required for login, security, saving user preferences and aggregated guest analytics described in this Policy.

9.2. Telegram, Discord and payment providers may use their own cookies on their domains. Those cookies are governed by the respective services’ policies.