Privacy Policy
Revision of 18 August 2026
This Policy sets out the categories of data processed, the purposes and conditions of processing in connection with the Sightline application and its associated online service, and the rights of the user in respect of their data.
1. Definitions
- Application — the Sightline software installed by the user on the user's own computer.
- Service — the server component of the project, providing user accounts, synchronisation and public profiles.
- Operator — the private individual responsible for the operation of the Service.
- User — any person using the Application or the Service.
- Account — the set of data identifying a User within the Service.
2. Operator and enquiries
Sightline is a non-commercial project operated by a private individual. The Service is in operation; as at the date of this revision, no public builds of the Application have been released.
Enquiries concerning data processing may be submitted by either of the following means:
- the “Report a problem” function within the Application;
- the Issues section of the client repository: github.com/Feelyamon/Sightline/issues.
Enquiries are answered within 30 calendar days of receipt. No charge is made for handling an enquiry.
3. Modes of use
3.1. Without an Account
The Application reads information about the current battle through the local interface made available by the game on the User's computer and stores that information in a file on the same computer. No data is transmitted to the Operator.
Those functions of the Application that do not involve the Service — viewing stored battle history, statistics and charts — do not require a network connection. However, information about new battles cannot be obtained unless the game is running, and War Thunder itself requires a network connection in order to start and to take part in battles. Accordingly, in the absence of a connection the Application remains operable in respect of previously accumulated data but receives no new data.
3.2. With an Account
Creation of an Account is voluntary. Where an Account exists, battle records may be transmitted to the Service for the purpose of cross-checking records between users and displaying a public profile. Declining to create an Account does not restrict any other function of the Application.
4. Categories of data processed
4.1. Data that does not leave the User's computer
- battle information: date and time, duration, outcome, vehicles used, number of targets destroyed, losses and assists;
- information about battle participants: in-game nicknames, team, vehicle and performance;
- the User's settings and notes about other players.
4.2. Data transmitted to the Service where an Account exists
- Login and password. The password is stored solely as an irreversible hash. The password cannot be recovered from the hash, including by the Operator.
- Account recovery code. Displayed to the User once upon issue; stored as an irreversible hash.
- In-game nickname, interface language and Application settings.
- Battle records to the extent set out in clause 4.1, including the in-game nicknames of participants.
- Technical information: the version of the Application and of the operating system, for the purpose of establishing the circumstances in which errors arise.
- Profile image, where uploaded by the User.
4.3. Data that is not processed
- email address; collection of such data is not provided for by the functionality of the Service;
- name, date of birth, sex, postal address or telephone number;
- payment details;
- the contents of the computer's storage, the list of installed programs, files or screen images;
- text or voice communications within the game;
- information about the User's activity outside War Thunder.
4.4. Information transmitted when a problem report is submitted
Where the User submits a report about a problem, information about the software and hardware environment may be attached to it: the name and version of the operating system, the processor model and number of cores, total and available memory, details of the graphics adapter and its driver version, the resolution and scaling of displays, the versions of the components the Application is built on, how long the Application has been running since it was started, and the most recent lines of the in-game interface that the Application was unable to interpret.
That information is processed solely for the purpose of establishing the causes of a malfunction. It is not collected on an ongoing or background basis: it is compiled at the moment the report is composed and is transmitted only together with it.
Before the report is sent, the User is shown the complete list of values to be transmitted. The User may disable their transmission, in which case the report is sent without them.
5. Processing of other players' in-game nicknames
The Application records the in-game nicknames of persons who took part in the same battle as the User. Such persons may not be users of the Application, and the conditions of that processing are therefore set out separately.
- Only in-game nicknames and battle events displayed by the game to all participants of the relevant battle are recorded. Information not displayed by the game is not collected.
- An in-game nickname is a pseudonym chosen by the player and public within the game. The Operator does not associate a nickname with a real identity.
- No other information about such persons — including network addresses, device information or data from external sources — is collected.
- Upon the request of a person whose in-game nickname is contained in the records of the Service, the relevant information shall be deleted in accordance with clause 2.
6. Purposes of processing
- providing the User with information about the User's own results;
- cross-checking records of the same battle received from different users, in order to identify inaccurate information;
- producing the public profile of a User who has created an Account;
- establishing the number of users and identifying faults in the Application and the Service.
Data is not processed for any other purpose. Data is not disclosed to advertising systems, is not used for profiling beyond the purposes stated, and is not sold.
7. Retention periods
| Category of data | Retention period |
|---|---|
| Battle history on the User's computer | Until deleted by the User. The Operator has no access to it |
| Battle records held by the Service | The 500 most recent battles per Account; earlier records are displaced |
| Cumulative totals (battles, victories) | For as long as the Account exists |
| Access sessions | 90 days, or until terminated by the User |
8. Rights of the User
The User is entitled to:
- obtain information as to the categories of data processed about them, as set out in clause 4 of this Policy;
- request deletion of the Account and the records associated with it;
- withdraw consent to processing by deleting the Account.
These rights are exercised in the manner set out in clause 2 of this Policy.
A limitation of which the Operator gives express notice: records of the same battle may be transmitted to the Service independently by several of its participants. Deletion of a User's Account results in deletion of that User's own records but does not affect records of the same battle held by other persons, such records constituting their own data.
9. Security measures
The Operator applies organisational and technical measures intended to protect data against unauthorised access, alteration and disclosure. The particulars of those measures are not disclosed.
The Operator does not warrant absolute security of data; no such warranty can be given in respect of any information system. Should unauthorised access to data be identified, the Operator will notify Users, stating the categories of data affected, the time of the incident and the recommended course of action.
10. Minors
The Application is not intended for use by persons under the age of 13. No deliberate collection of such persons' data is carried out. Where it is established that an Account has been created by a person under that age, the Account shall be deleted upon request.
11. Disclosure to third parties
Data is not disclosed to third parties, save where disclosure is necessary in order to comply with a request of a competent authority made in accordance with the law.
12. Amendment of this Policy
The date of the revision is stated at the beginning of this document. Where the conditions of processing change materially, the Operator will notify Users. The User's consent is recorded by reference to a specific revision of this Policy.