Privacy Policy
Version of 22 September 2026
This document sets out what data Lunaris collects, why, and what a User can do about it. Using the Service means accepting this Policy; a User who does not accept it stops using the Service.
1General provisions
1.1This Privacy Policy (the “Policy”) sets out how data a User provides while using the Service is collected, used and protected.
1.2The Policy covers the website lunaris.cc, the client software and the accompanying services.
1.3Data is processed under Federal Law No. 152-FZ of 27 July 2006 “On Personal Data” and other applicable law of the Russian Federation.
2What is collected
2.1The following categories of data are collected:
- account identifiers: username, email address, internal identifier;
- technical data: IP address, browser, device and operating system;
- a hardware identifier of the device a licence is bound to;
- interaction history: launch logs, support requests, activity in the account area.
2.2The hardware identifier is an irreversible hash computed from device characteristics. It cannot be turned back into a description of the hardware, and it exists only so that one subscription runs on the User's device rather than spreading further.
2.3The Service does not ask for passport data, identity documents, photographs, tax numbers or anything beyond the list above.
2.4Passwords are not stored in the clear: what is kept is the output of a cryptographic hash, from which the original cannot be recovered.
3Why the data is needed
3.1The data is used only to:
- provide and maintain the Service's functionality;
- recognise the User and protect their account;
- contact the User about support and notifications;
- diagnose errors and improve how the Service works;
- meet obligations to payment providers in the course of a payment.
3.2It is not used for advertising profiles and it is not sold.
4Disclosure to third parties
4.1Data is disclosed to third parties only where:
- the law requires it;
- disclosure is needed to perform obligations to the User, including processing a payment;
- the User has given explicit consent.
4.2Only what a transaction requires is passed to the payment provider. Card details are handled by the provider and are never passed to the Service.
5Storage and protection
5.1Data is kept for as long as the purposes of processing require, and within the periods the law sets.
5.2Reasonable technical and organisational protections are applied. Absolute security of data sent over public networks is not guaranteed.
6The User's rights
6.1A User may:
- find out what data about them is processed, and why;
- require that data be corrected or brought up to date;
- require that data be deleted, or withdraw consent to processing, unless obligations to payment providers, requirements of state authorities or other lawful grounds for retention prevent it;
- object to processing for purposes this Policy does not provide for.
6.2Requests go to Discord. A reply follows within a reasonable time, not exceeding 30 days.
7Liability
7.1Sending information over the internet carries risk, and the User acknowledges this.
7.2The Administration is not liable for disclosure, loss of, or unauthorised access to data caused by the User or by third parties: a compromised password, a lost device, malicious software.
8Changes to this Policy
8.1The Administration may change this Policy.
8.2The version in force is published on this page. Using the Service after a new version is published means accepting it.
9Contact
9.1For anything concerning data processing, the User writes to Discord.
9.2The conditions of use are set out in the Terms of Use.