Privacy
ARGUS is a free, non-commercial map. It stores as little as it can.
Without signing in
You see the front page only. The server keeps a per-address request counter in memory to limit abuse; it is never written to disk.
Visitor counting (no cookies)
To know roughly how many people use ARGUS, each page view is folded into a per-day row keyed by a visitor hash: SHA-256 over a random salt, your IP address and your browser's User-Agent string. A view counts once the page has loaded in your browser (it sends one small request to /api/visit). The salt is random per UTC day and kept only for that day – in the database, so a server restart does not count you twice – and deleted when the day turns. After that the hash cannot be turned back into an address, and two days cannot be linked. Alongside the hash the row keeps the day, a view counter, your country (from a local copy of the DB-IP country database – no lookup service is called), the referring site's host name, your browser and operating-system family and your preferred language. Nothing of this is written to a cookie or sent to a third party. Rows older than 400 days are deleted.
When you sign in with EVE Online
Signing in uses CCP's single sign-on. ARGUS never sees your EVE password.
What ARGUS may read (ESI scopes)
Every login asks for the same seventeen scopes – no wallet, no mail, no market:
| Scope | Reads | Used for |
|---|---|---|
esi-location.read_location.v1 | the solar system you are in | your marker on the map (one per linked character) |
esi-location.read_ship_type.v1 | the hull you fly | shown next to your name, picks the capital hull |
esi-location.read_online.v1 | whether you are in the game | ARGUS polls only while you play |
esi-ui.write_waypoint.v1 | sets waypoints in your client | SET DESTINATION / send a route |
esi-skills.read_skills.v1 | your jump-drive skill levels | range and fuel in the capital planner |
esi-characters.read_fatigue.v1 | your current jump fatigue | the capital planner starts from your real timer |
esi-fleets.read_fleet.v1 | your fleet and, for the boss, its members | FLEET layer and tab |
esi-corporations.track_members.v1 | where corp members are (directors only) | CORP member list |
esi-characters.read_corporation_roles.v1 | your in-game corporation roles | directors and the CEO get CORP ADMIN |
esi-clones.read_clones.v1 | home and jump clones | LOGISTICS |
esi-assets.read_assets.v1 | where your things are | asset markers and values in LOGISTICS |
esi-search.search_structures.v1 | structures your character may use | finding Ansiblex gates, docks and cyno beacons the alliance may use |
esi-universe.read_structures.v1 | which system a structure is in | Ansiblex gates, clones and assets in structures |
esi-corporations.read_structures.v1 | your corporation's structures, fuel and timers (directors and station managers only) | STRUCTURES overview, fuel warnings, automatic reinforce timers |
esi-characters.read_notifications.v1 | your EVE notifications – only structure and moon ones are read | attack, lost-shield/armor and fuel alerts for your corporation's structures |
esi-industry.read_corporation_mining.v1 | your corporation's moon extractions (directors and station managers only) | moon chunk timers on the ops board |
esi-alliances.read_contacts.v1 | your alliance's contacts and their standings | who counts as blue in the structure scan |
You can revoke the token at any time on the EVE website under Third-Party Applications.
The server stores, in a small SQLite database:
| What | Why | How long |
|---|---|---|
| Your character id and name | to show who is signed in | until you delete your data |
| An encrypted refresh token | to read your location without logging in again | until you delete your data or revoke the app at https://community.eveonline.com/support/third-party-applications/ |
| A session id (the browser cookie) | to recognise your browser | 30 days without use |
| Login history: time and country of each login, login count | so the operator can see who uses the map and spot abuse | until you delete your data |
A role (user or admin) and, if an administrator blocked you, the time of that | access control | until you delete your data |
| Your public corporation and alliance ids (looked up from ESI, refreshed hourly) | to highlight your alliance on the map | until you delete your data |
Your in-game corporation roles as ESI reports them (esi-characters.read_corporation_roles.v1, e.g. Director, Station_Manager), whether you are your corporation's CEO (from its public ESI sheet), for which corporation and when they were read | so directors and the CEO can open the corp administration and hand out ARGUS rights, and so a corporation can let in-game roles count as ARGUS roles | read at login and then hourly; void as soon as you change corporation; until you delete your data |
| ARGUS corp roles a director gave you (FC, structure manager, intel officer, marker manager), with who gave them and when | they decide what you see and may change on the ops board, the corp markers and the alliance intel channel | until a director takes them back, you leave the corporation, or you delete your data |
| Your corporation's permission settings and the corp administration's change log (who changed which role or right of whom, when – character ids and names) | shown to the corporation's directors and CEO | the last 200 changes per corporation; lines naming you go when you delete your data |
| Your watchlist (system and region ids you chose to watch) | so it follows you across devices | until you remove the entries or delete your data |
| Your home system (set by hand, or learned from your home clone) | to draw the little house on the map | until you change it or delete your data |
| An account id linking characters you added with Add character | to switch characters without logging in again | until you delete your data (which removes every linked character) |
| A Discord webhook URL, encrypted like the token, plus which alert kinds and ISK floor you chose, the time of the last post and a failure counter | to post alerts to your Discord channel while nobody has the map open | until you remove it or delete your data |
| Corporation markers (staging, home, cyno, watch systems with a note, your character id and name as author) | shared with every member of your corporation who signs in | until a member removes them |
| Ansiblex gates found by your structure search (structure id, both systems, the gate's name, the owning corporation and its alliance, your character id as finder) | shared with every member of your alliance who signs in, marked own, blue or other | until your next scan replaces them, or two weeks after nobody confirmed them |
| Ansiblex gates from a list you pasted (the two systems of each gate, your character id as importer, the time) – the list itself is read in your browser and never uploaded | shared with every member of your alliance who signs in, marked as from a list | until you import again or remove them, or 30 days after the import |
| Docks, cyno beacons and cyno jammers found by your structure search (structure id, system, type, name, the owning corporation and its alliance, your character id as finder) – docks and beacons only when own or blue, jammers whoever owns them | shared with every member of your alliance who signs in: as map markers and landing points for the capital planner | until your next scan replaces them, or two weeks after nobody confirmed them |
Your alliance's standings towards corporations and alliances (from esi-alliances.read_contacts.v1, read during a structure scan; contacts that are characters are skipped and never stored) | to tell blue structures from others | until the next scan by a member replaces them |
| Structure id → solar system (and the structure's name, type and owning corporation) for structures your token could see | so clones, assets and corporation members can be placed on the map without asking ESI again | indefinitely (structure positions are not personal data) |
| Web Push subscriptions (the push service's endpoint URL and keys for each browser you enabled), which alert kinds and ISK floor you chose, last delivery and a failure counter | to send alerts to your device while ARGUS is closed | until you disable push there, the push service reports the subscription gone, or you delete your data |
| Intel reports you send (system, kind, count, note, your character id and name, time) – typed in, or parsed by the intel channel reader (then also the channel's name) | shown to your alliance (or corporation) for 30 minutes | 30 minutes, or until replaced or deleted |
| Ops board formups and timers you add (system, EVE time, doctrine or note, FC name, structure kind and owner side, corp-only or alliance, your character id and name as author, whether reminders went out) | shown to your corporation, or your alliance when you chose so – to each pilot only when their own corporation lets them see formups or timers – with reminders to those of them who enabled them | until two hours after a formup's time or one hour after a timer ran out, or until deleted |
Your corporation's structures as ESI lists them for its directors and station managers (esi-corporations.read_structures.v1: structure id, type, system, name, state and its timer, fuel expiry, reinforce hour, services, unanchoring time), its moon extractions (esi-industry.read_corporation_mining.v1: structure, moon and its name, start, chunk arrival, natural decay), when each list was read last and the character id and name of the pilot whose token read it | the STRUCTURES overview, fuel warnings and the automatic reinforce and moon timers on the ops board – shown only to pilots of that corporation whose corporation lets them see structures | the latest copy only, replaced on every read; a corporation's copy is deleted when nobody refreshed it for 30 days; the pilot's name goes when they delete their data |
From your EVE notifications (esi-characters.read_notifications.v1), if you are a director or station manager: only structure and moon notifications (attacks, lost shields/armor, destroyed, fuel, services offline, low power, anchoring, moon chunk ready or fractured) are read; ARGUS keeps a key per event (type, structure or moon, minute) so a second pilot's copy is not handled twice, and the facts it acted on: structure, system, type, shield/armor/hull left, the attackers' corporation and alliance names and the next timer – in the structure log, the last attack per structure and the ops timer it made. Every other notification is skipped unread and nothing of the text is stored | attack, timer and fuel alerts for your corporation | 14 days |
| Your alliance's suggested intel channel (its name, the character id and name of who set it, time) | shown to every member of your alliance who signs in | until the setter or an administrator changes or removes it |
| D-scan and local reports you share with SHARE: the folded D-scan (type, name as pasted, count, how many on grid) or the pilots in local (character ids and names, their corporation and alliance ids, names and tickers), the system, your character id and name, the time | anyone signed in to ARGUS who has the link | 30 days |
| Feedback you send with the FEEDBACK button (kind, message, the page you were on, language, your character id and name, time) | so the developer can read it and ask back | until an administrator deletes it; not removed by Delete my data |
Setting an in-game destination sends the system id to ESI with your token and nothing else; ARGUS does not store it. The jump-freighter planner reads your jump-drive skill levels from ESI when you ask it to; the levels, the hull you picked and alert settings stay in your browser's local storage, never on the server.
Your location and ship are read from ESI only while a tab of yours is open and visible, are pushed to that tab, and are not stored. With several characters linked by Add character, this holds for each of them: the map shows all of them at once, and only to you. The same holds for your fleet (which fleet you are in and, if ESI allows it, its member list), for the corporation member list (read on request, for directors, shown in your tab only), and for your clones and assets (read on request, shown in your tab only, never stored). The structure lists are read with a director's or station manager's token whether or not they have the map open, for as long as they used ARGUS within the last 30 days. Likewise the structure scan for your alliance (gates, docks, cyno beacons and jammers, and – with the contacts scope – who is blue) runs by itself every few hours with the token of a member who used ARGUS within the last 30 days; members take turns.
No IP addresses and no location history. Cookies are limited to the session cookie and a ten-minute login cookie. Administrators can see the list of characters, their login times and countries, and the anonymous visitor statistics described above – nothing else.
D-scan and local
A pasted D-scan is read in your browser and stays there unless you share it. A pasted local list is sent to the server, which looks the names up at ESI (character ids, corporations, alliances – all public) and asks zKillboard for each pilot's kill statistics to rate the threat. Names, ids and the statistics are kept in the server's memory for up to half a day so the next scan is faster, never written to disk, and not linked to you. Own, blue and red come from your alliance's standings. Only SHARE stores a report (see the table). The OVERLAY window is your browser's own picture-in-picture window; nothing extra is sent.
Intel channel reader
The CHANNEL tab can read an in-game intel channel from EVE's chat logs. You pick the Chatlogs folder yourself (Chromium's File System Access API, read only); the browser keeps that permission and the folder handle in its own storage (IndexedDB) on your computer. Then:
- Only the files of the channels you tick are read, and only in your browser. ARGUS lists the other channels by their file names to let you choose; their contents are not opened. Local chat and private conversations are never offered, and a picked file whose header says it is local or a private conversation is refused.
- Each line is parsed in the browser. Only the facts it recognises – solar system, kind (hostiles, camp, bubbles, clear), count, ship names, time and the channel's name – are sent to the server, as an intel report like a typed one. The line itself, pilot names and anything else said in the channel are never uploaded.
- Several readers of the same channel are folded into one report on the server; reports expire after 30 minutes.
Disconnect in the tab forgets the folder. Nothing of the chat logs is ever stored on the server.
Deleting your data
Use Delete my data in the character card. It removes the character, every character linked to it, the encrypted tokens, all sessions, the login history, the watchlist, the home system, the Discord webhook, the push subscriptions, your in-game and ARGUS corp roles and the corp change-log lines that name you immediately. It does not remove feedback you sent, corporation markers (they belong to the corporation), your corporation's structure overview and structure log (they belong to the corporation too; your name as the pilot who read them is removed), Ansiblex gates, docks, beacons and jammers shared with your alliance (they fall away two weeks after no member confirmed them; gates from a pasted list 30 days after the import), the alliance's standings or the alliance's suggested intel channel; intel reports expire on their own after 30 minutes, ops board formups and timers a few hours after their time. Settings kept in your browser's local storage (alerts, layers, planner skills, the picked intel channels and the Chatlogs folder handle) stay until you clear the site data. You can also revoke ARGUS in your EVE account's third-party applications; the stored token then stops working.
Data sources
Map data comes from CCP's Static Data Export and ESI, kill data from zKillboard, wormhole data from EVE-Scout. Their own terms apply to the data they publish.