Transparency

MMOBASE uses CCP's official EVE SSO and ESI API. This page gives the plain-English version of what the app can access, what it cannot do, and where the source code can be reviewed.

MMOBASE never sees, asks for, or stores your EVE Online password.
Frontend open source
Backend open source
CCP SSO only
User-controlled access

Open source and GitHub

The frontend and backend are public so players, developers and security-minded EVE users can inspect how MMOBASE works. This is the main transparency step: you do not have to rely only on this page.

Frontend

MMOBASE website and dashboard UI

Contains the public site, dashboard pages, screenshots, transparency page, privacy pages and frontend code.

Backend API

EVE auth, syncing and server logic

Contains the Node.js backend that handles EVE OAuth, ESI requests, character data, wallet/asset processing and API endpoints.

Why this matters

EVE players are right to be careful with third-party tools. Publishing the backend makes it easier for the community to check what data is requested, how SSO tokens are handled, and whether the app is doing what it claims to do.

How MMOBASE Handles EVE Login

MMOBASE uses CCP login, not your EVE password. You approve specific ESI permissions, MMOBASE receives approved tokens, and those tokens are used to build dashboard views for your linked characters.

No EVE password access

You log in through CCP. Your EVE password never touches MMOBASE.

Approved ESI data only

The app can only request data covered by the permissions you approved.

Dashboard snapshots

Some wallet and asset values are saved so trends can be shown over time.

Access can be revoked

You can remove MMOBASE from CCP authorised applications to stop future ESI access.

What MMOBASE uses

The aim is to use only the data needed for the dashboard features. The exact scope list may change as features are added or cleaned up.

Character and account overview

  • Character name, ID and portrait
  • Corporation/alliance display where available
  • Skill points, queue and progression context
  • Current ship and location when approved

Wallet, market and history

  • Wallet balance and wallet journal
  • Transactions where available
  • Market orders where approved
  • Saved wallet snapshots for trend views

Assets and valuation

  • Assets, ships and item locations
  • Station/location resolution where possible
  • Estimated item values
  • Saved asset snapshots for dashboard history

How EVE SSO works

MMOBASE does not log into your EVE account. You are sent to CCP, CCP shows the permission prompt, and after approval MMOBASE receives tokens that can read the approved ESI data. If you revoke MMOBASE through CCP account management, future refreshes for that character stop.

What MMOBASE does not do

MMOBASE is a dashboard and tracking tool. It is not designed to control your account or make in-game decisions.

Account safety

  • Does not see or store your EVE Online password
  • Does not ask you to type your EVE password into MMOBASE
  • Does not control your EVE client
  • Does not sell your character data to advertisers

In-game safety

  • Does not move your ISK
  • Does not move your items
  • Does not sell ships, contracts or market items
  • Does not make in-game decisions for you

Current limitations

MMOBASE is still in active development. The main area still being improved is asset valuation accuracy, including cleaner pricing logic, better handling of unusual assets and clearer empty/loading states. Feedback, bug reports, code review and ESI knowledge are welcome through GitHub.

Revoke access

You stay in control of your character connection.

Open CCP account management

Go to your EVE Online account area.

Find authorised apps

Look for third-party or authorised applications.

Remove MMOBASE

Remove access for the character you no longer want linked.

Disconnect locally

Use MMOBASE account tools to remove local linked data when available.

For Reddit and security reviewers

Security concerns are welcome. The frontend and backend are public on GitHub, so the most useful feedback is specific: which permission concerns you, what data you think should not be stored, or what wording/code path needs improving.

Current focus before wider release: keep RLS locked down, reduce unused scopes, document each dashboard tab clearly, and improve asset valuation accuracy.