What RONA stores and why
Plain-language summary for every pilot who logs in.
Logging in asks EVE to confirm which character you are, with the publicData permission (the character's public profile). We store the character's name, corporation and alliance, and nothing else.
Member audit
Skills, skill queue, wallet journal and market transactions, contacts, implants and jump clones, location, current ship, personal mining ledger, and your assets (so leadership can search inventories) with the names of the structures they're in, loyalty points and faction warfare enlistment. Visible to you and to leadership roles that are allowed to audit your corporation.
EVE permissions: esi-skills.read_skills.v1, esi-skills.read_skillqueue.v1, esi-wallet.read_character_wallet.v1, esi-characters.read_contacts.v1, esi-clones.read_clones.v1, esi-clones.read_implants.v1, esi-location.read_location.v1, esi-location.read_ship_type.v1, esi-industry.read_character_mining.v1, esi-assets.read_assets.v1, esi-universe.read_structures.v1, esi-characters.read_loyalty.v1, esi-characters.read_fw_stats.v1
Moon mining (director)
Your corporation's moon extractions and refinery mining ledgers. Needs the Station Manager or Accountant role in game.
EVE permissions: esi-industry.read_corporation_mining.v1, esi-universe.read_structures.v1
Structures (director)
Your corporation's structures, fuel, state timers, fitted modules, and the in-game notifications about attacks on them. Needs the Station Manager and Director roles in game.
EVE permissions: esi-corporations.read_structures.v1, esi-assets.read_corporation_assets.v1, esi-universe.read_structures.v1, esi-characters.read_notifications.v1
Corp & alliance contacts
Your corporation's and alliance's contact lists (standings), used to spot dealings with hostiles. Any member can read them in game; RONA keeps them in sync.
EVE permissions: esi-corporations.read_contacts.v1, esi-alliances.read_contacts.v1
Killboard
Your recent kills and losses, so they show on the alliance killboard. Killmails are public in game once anyone links them; this just makes sure none are missed.
EVE permissions: esi-killmails.read_killmails.v1
Corporation killmails (director)
Every kill and loss of your corporation, for the alliance killboard. Needs the Director role in game.
EVE permissions: esi-killmails.read_corporation_killmails.v1
Wormhole mapping
Where you are, whether you're online and what you fly, read every few seconds only while you have tracking switched on for a map, so the map can follow you and draw the holes you jump.
EVE permissions: esi-location.read_location.v1, esi-location.read_ship_type.v1, esi-location.read_online.v1
Corporation audit (director)
Your corporation's member list (with last login and ship), wallet division names, balances and wallet journals, and the corporation's assets and hangars, so leadership can see who is registered and where the corporation's ISK comes from. Needs the Director role (Accountant is enough for wallets).
EVE permissions: esi-corporations.read_corporation_membership.v1, esi-corporations.track_members.v1, esi-wallet.read_corporation_wallets.v1, esi-corporations.read_divisions.v1, esi-assets.read_corporation_assets.v1, esi-universe.read_structures.v1
Buyback contracts (leadership)
Reads the item exchange contracts sent to the buyback, so RONA can match them to quotes. For a corporation buyback, use a character in that corporation.
EVE permissions: esi-contracts.read_corporation_contracts.v1, esi-contracts.read_character_contracts.v1
Save doctrine fits to EVE
Lets you push a doctrine fit straight into your in-game fitting window.
EVE permissions: esi-fittings.write_fittings.v1
Suspicious-activity checks. Leadership can see when shared trades, ISK transfers or personal contacts involve someone the corporation or alliance has set as hostile. Those flags stay with leadership even if you later stop sharing.
Auth check. To tell whether you've added every character you play, RONA looks in the wallet journals you share for ISK you repeatedly gave to, or traded with, characters that aren't added. You and leadership see those as "possible alts"; leadership can clear a wrong guess.
Activity history. Member audit keeps a short daily summary of each shared character (how much happened in each 4-hour band of the day, ISK by kind such as bounties or market sales, and NPCs killed for bounties) so the account overview can show 13 weeks of activity after EVE's 30-day journal has moved on. Only you and leadership roles allowed to audit you see it.
Taking it back. On the Characters page, "Revoke" cancels the permission at EVE's login server and deletes the data collected under it. Removing a character revokes everything for it.
Tokens are stored encrypted and are only used by the background jobs listed above, at the pace EVE's API cache allows.