Terms and privacy

Using Eve Stars

Eve Stars is a free map and route planner for EVE Online, run by players, not a company. By using this site or its route API you accept these terms and this notice; if you do not, please do not use it.

• It is offered as it is, with no warranty of any kind, and you use it at your own risk. Routes, jump ranges and the live data from CCP and EvE-Scout can be wrong or late: check before you undock.
• As far as the law allows, Eve Stars and the players who run it are not responsible for any loss or harm that comes from using it, in the game or out of it.
• Use it fairly. Do not try to break or overload it, or to get around its limits or who it lets in. A route API token is yours alone: keep it secret. Access can be withdrawn where it is misused.
• The site may change, pause or stop at any time.

In short

What Eve Stars keeps is about your characters in the game, not about you: it has no real name, email address, password or payment details. Without signing in, the server keeps nothing about you beyond the logs below. What it keeps is used to give you what you ask of the site and to keep it running and safe, and for nothing else.

In this browser

The site keeps in this browser your settings, which include some of your characters' ids and a copy of what every route avoids, your route history and saved routes, the structure and upgrade lists you load, the sighting relay's key, a link to a sighting file if you choose one, and that you accepted this notice. What you ask of a route, such as its stops, what it avoids and where it may land, is sent to the server to plan it.

Cookies

Eve Stars has no advertising, tracking or analytics cookies, and runs no analytics. Signed out, it sets no cookies at all. Signing in sets three, each needed for signing in:

• a session cookie that keeps you signed in, for 30 days from when you last used the site;
• one that protects a sign-in while it is under way, for 10 minutes;
• one that tells the page how the sign-in went and for which character, for 2 minutes.

Cloudflare, which carries the site's traffic, may set a security cookie of its own.

When you sign in with EVE

You sign in on CCP's own page, so Eve Stars never sees your password. For each character you add, the server keeps:

• its id and name, and the code EVE gives for the EVE account it is in, which changes if the character is sold;
• its corporation and alliance, looked up again about every hour;
• the permissions you granted (full or Lite), its EVE tokens, encrypted, whether CCP still honours them, and when that was last checked;
• when it was added and last signed in, and any cyno mark or Jump Drive Calibration level you give it.

And for your account: your main character, groups and watched systems; what every route avoids, if you keep a list in Settings, and when it last changed; when the account was made and last used; each browser you are signed in with, and when it was last used; and each route API token, kept as a fingerprint with its name, whether it may send, when it was made and last used, and the character it was made through. A sign-in under way is kept, with the page to come back to, until it is finished or soon after its 10 minutes run out.

What the server asks CCP, and when

With the permissions you granted, the server asks CCP about your characters:

• while a signed-in page is open: where they are and whether docked, what they fly, whether they are online and when they last logged in or out, their jump fatigue, and their skills, of which only Jump Drive Calibration is used;
• when a tool of yours uses the route API: whether they are online and where they are;
• when the map or a tool of yours asks for them: which Ansiblex gates they can see, and who owns those;
• when you or a tool of yours sends a route: to set it as waypoints in your game client, and nothing is set until then;
• once a day, for any character not used for a week: to renew its sign-in, so you are not signed out for being away;
• about every hour: each character's corporation and alliance, which are public.

But for the corporation and alliance, kept as above, what it learns this way is held only in the server's memory, until it restarts, and is not stored. A route sent through the route API is held in memory for up to a day, with the characters it was sent to and where they set out from, so a tool can ask how it went or send it again safely.

The route API's access list

Who may use the route API is decided by an access list in the game. The server reads it every five minutes, with the sign-in of one of its managers, and keeps the names, ids and access of the characters, corporations and alliances on it, including people who have never used the site, and that manager's character, its EVE account code and its EVE tokens, encrypted. Each read replaces the last.

The sighting relay

If you use the sighting relay, what your own program sends about your characters, such as where they are and in what ship, is passed through the server to your map and kept nowhere.

Logs

To keep the site running, the server logs the requests it answers, such as the address a route was asked for, with its systems. It keeps how your browser describes itself, with your IP address masked, and not your cookies, tokens, language, country or the page you came from. Log lines can name a character or its id: each sign-in is logged with the character's name and id and the number of its account here. Logs are deleted after 14 days, but for a second copy of the application's own lines, kept five weeks at most.

Who else is involved

• CCP Games runs EVE's sign-in and ESI, which the server asks about your characters. Portraits and other images load in your browser straight from CCP, which sees your IP address.
• Cloudflare carries all traffic to the site, so it sees your IP address and what is sent, and may handle it outside your country, including in the United States.
• EvE-Scout provides the wormhole data. Nothing about you is sent to it.
• A tool you give a route API token to can do what that token allows: read your characters, plan and send them routes, and read or replace what every route avoids.

Nothing is sold, shared for advertising, or given to anyone else.

How long it is kept

An account is kept until you remove it, or until it has gone 12 months with no sign-in, no signed-in visit and no route API use. Then it is deleted with its characters and everything kept about them, and CCP is told each character's access has ended. A browser's session ends after 30 days unused.

Your choices

• Sign out at any time, in the Pilot section. That ends this browser's session; the rest is kept.
• Remove a character there: it is deleted, with its corporation, alliance and places in groups, and CCP is told its access has ended. A route API token made through it keeps its name until you remove the token. Removing the last character deletes your account, with its groups, watched systems, avoid list, sessions and route API tokens.
• Ending the access on CCP's own site stops Eve Stars reading the character within 20 minutes. The server deletes its tokens when it next tries to use them, within eight days at most, and keeps the rest of its record until you remove it or the account expires.
• Clear this site's data in your browser to forget what it keeps there.
• Ask what is kept about you, or to have it corrected or deleted, by writing to the corporation below. If you think your data has been mishandled, you may complain to your data protection authority.

Contact and changes

Eve Stars is run by the EVE Online corporation EVEStars.net [MAPPR]. To reach it, send an EVE mail to its CEO, Aurelie Ciel. If this page changes, the date at its top changes, and the map asks you to accept it again.