Misriah Industry Materials Group emblemMisriah Industry Materials GroupMIMGC // EXECUTOR COMMAND NETWORK

COMMAND NETWORK

Administration

Focused administration tools and records.

SECURITY & READINESS

Controlled by design.

EVE-VERIFIED ACCESS
ACCESS CONTROL

Two enforcement layers

The login page is public, but command data is not. EVE SSO establishes the pilot identity; current MIMGC membership, verified titles, Owner approval, and server-side permissions independently protect every restricted route and action.

CURRENT SESSION
Checking…
PORTAL ROLE
Pending
DEFAULT POLICY
Deny unless granted
EVE INTEGRATION

Scoped authorization controls

  • Developer Agreement accepted Owner confirmed YC128.07.21
  • Application scopes registered 19 selected read-only ESI permissions
  • Authorization compatibility safeguard 19 read-only scopes requested; trained skills and the live training queue are active
  • Exact callback active https://command.mimgc.net/api/auth/eve/callback
  • Protected token lifecycle Access tokens stay in memory; refresh credentials are encrypted at rest
  • Phase 3B release YC128.07.22 Consent, synchronization, revocation, and personal dashboard controls
  • Phase 3C validated Character and corporation synchronization confirmed by the Owner/Executor
  • Phase 3D EVE-only sign-in Title mapping, Owner approval, freshness checks, and revocation remain enforced
RECOVERY

Backups and accountable change

Exports contain manual command records, role assignments, audit history, and non-sensitive ESI connection metadata. Refresh credentials and private ESI snapshots are deliberately excluded.

LAST SNAPSHOT // NONE YET

PRIVACY & COMPLIANCE

Know what the network knows.

Effective YC128.07.21 // Updated YC128.07.26 // Review January 2027

WHAT IS COLLECTED NOW

For members, the selected EVE character ID and name form the portal identity. The network also retains role assignments, audit history, approved scope and consent records, separately encrypted refresh credentials, synchronization metadata, minimized ESI summaries, and current membership/title evidence.

OPERATIONS DATA

With express consent, a synchronization may collect online status, current solar system or docked location, active ship type, and current fleet membership. The latest snapshot replaces the prior location snapshot; no route or exact-coordinate history is retained.

WHAT IS NOT COLLECTED

No EVE password or retained access token. Mail, contacts, live coordinates, plotted routes, gameplay controls, clones, implants, corporation contacts, and unrelated private scopes remain outside the active packages. Raw corporation pages are not retained by Phase 3C.

WHY IT IS USED

Only to operate MIMGC/M-CON administration, enforce permissions, coordinate authorized work, investigate changes, and recover owner-controlled records.

VISIBILITY & RETENTION

Personal character data follows the connected portal account. Phase 3C corporation data is restricted to the Owner and Directors. Phase 3D title evidence is visible to the connected member and Owner; non-owner access fails closed after 30 days without reverification.

TOKEN PROTECTION

A one-time authorization code and PKCE verifier exist only during sign-in. Access tokens remain in server memory only. Phase 3B, Phase 3C, and Phase 3D refresh credentials use separate identity-bound encryption contexts and are never included in backups.

CONTROL & REVOCATION

Each package requires explicit consent and has an independent disconnect control. Phase 3D verification never grants access by itself; the Owner must approve an allowed role, and lost membership fails closed.

PLAYER SAFETY

The network is an external management tool. It does not issue game commands, automate mining, hauling, markets, combat, or otherwise control an EVE Online client.

PROCESSORS & SOURCES

Portal hosting and storage use OpenAI Sites and its Cloudflare runtime. Character authorization and game data come from EVE SSO, ESI, and EVE’s public image service. No advertising or analytics tracker is added by this portal.

PHASE STATUS

Phase 3B and Phase 3C synchronization are confirmed. Phase 3D enrollment is open to verified MIMGC pilots. Phase 3E restricted enrollment is open to verified M-CON pilots. Both remain deny-by-default and Owner-approved, and alliance access is isolated from MIMGC command data.