Русская версия →

Fleet ManagerONLINE

Terms of Use

In force from 25 August 2026

In short. Use the service freely — that is what it is for. Do not take its code: not into your own project, not into your own copy of the site. What we store is listed in section 5, and it is exactly as much as the fleet split needs.

1. What this service is

Fleet Manager Online is the site at fleetmanager.linkpc.net. It splits fleet windows between pilots and keeps the roster honest against the real fleet in EVE Online.

It is a hobby project. It is not owned by, affiliated with, or endorsed by CCP hf. It runs on goodwill: no guaranteed availability, no scheduled support, no charge.

2. Who may use it

Access is through official EVE Online single sign-on (EVE SSO) only. We have no password of our own and we never see your EVE password — CCP does not give it to us.

Access may be restricted or withdrawn at any time: by community rules, by a decision of fleet leadership, or because of behaviour that spoils the service for others. A ban covers every character belonging to the same person and always records a reason.

3. What you are permitted to do

You are granted a revocable, non-exclusive, non-transferable right to use the service — and nothing else. No rights in the service itself, its code, its design, its guide texts or its data structures pass to you.

One technical point worth being explicit about. For the site to work at all, your browser must download its client side — JavaScript, stylesheets and markup — and you can open and read them there. That does not place them in the public domain and does not grant you any right over them. Exactly one thing is permitted: letting your browser execute them while you use the site.

4. What is not permitted

By using the service you undertake not to:

If you find a vulnerability, please report it privately (contacts at the foot of the main page) rather than demonstrating it in public. That is far more useful to everyone.

5. What data is stored

The service needs data from EVE in order to do its job at all. What is kept:

WhatWhy
Your characters' ids and names, corporation and alliance To group every character under one person, draw the roster, and apply access rules
The order and ticked state of characters in your list So signing in from another computer does not mean adding them all again
Fleet membership, assigned windows, tags and roles The window split itself
Time spent in fleets The activity report for fleet leadership
Hulls a character has been seen flying Fleet composition, and the "you forgot to declare a ship" hint
Which sections of the service you opened — a guide, a utility, the fit window, a tab of the admin panel — and how many times So leadership can see which parts of the service are actually used, and which guides a pilot has never opened. The last 50 entries per person are kept, plus a running count per section. This record keeps only that a section was opened — never what you did or clicked inside it. Visible to the top administrator only
What happens in a fleet: the fleet screen its owner saw, moment by moment (who is in it, how many windows each pilot was assigned and has in the game, the queue, the settings), and every action anyone in the fleet took in the app So administrators can review how a fleet was run and check a complaint about the window split. Kept 30 days. Visible to administrators only
Characteristics of the computer you sign in from: graphics card, screen, CPU, timezone, installed fonts; in the PC app — the Windows, CPU, motherboard, graphics card and memory identifiers The "one PC — one pilot" rule: two accounts on one computer do not get a double share of windows. Only one-way hashes are kept, never the values themselves, for 90 days. Visible to the top administrator only
A snapshot of skills, the training queue and implants — if you granted that permission at sign-in Checking whether a character can actually fly a given fit
An ESI refresh token To refresh the skill snapshot once a day without your involvement. Stored encrypted, with the encryption key held outside the database.
Optional: permission to set autopilot waypoints in your game client — only if you ticked "Allow setting the in-game route" at sign-in Jump Navigation's "Set route in game" puts the route's stations into your cyno pilot's autopilot, and only when you press that button. It writes waypoints and reads nothing
Logs of fleet leadership actions, and the reason for a ban So decisions can be reviewed afterwards

The data is used inside the service only. We do not sell it, pass it to third parties, or use it for advertising.

Withdrawing access. Remove a character from your list on the setup screen — its skill snapshot goes with it. To revoke the permission completely, use your own EVE Online account settings, on the third-party applications page.

6. No warranty

The service is provided "as is". It may be unavailable, it may calculate something wrong, it may lose data. We accept no liability for the consequences of using it — including ships, time and patience lost in a fleet.

7. Changes

These terms may change. The date at the top of this page always shows the edition in force. Continuing to use the service after a change means accepting the new edition.

8. Contact

Contact details are at the foot of the site's main page: Discord, Telegram, email fleetmanagercontact@gmail.com and an EVE Online character.