Someone recently suggested that EF-Map might be hiding or obscuring specific players' or tribes' activity. This couldn't be further from the truth—and it made me realize we should explain exactly how everything works.
This post is a complete breakdown of every major feature in EF-Map: what runs in your browser (client-side), what data we access, what requires login, and what we collect (spoiler: only anonymous aggregate stats, and I will send them to anyone who asks).
The core philosophy: EF-Map is a privacy-first mapping tool. We don't track users, we don't filter data by player or tribe, and nearly everything runs entirely in your browser. You don't even need to log in for most features.
The TL;DR: What Runs Where
✅ No Login Required
- 3D star map rendering and navigation
- Route calculation (point-to-point, multi-waypoint)
- Scout optimizer
- Reachability analysis
- Structure markers on the map (Smart Assemblies, gates, SSUs)
- Smart Gates (unrestricted gates only)
- Killboard viewing
- Live Event Tracker
- Solar System detail view
- System Finder, Blueprint Calculator, Log Parser, Yeet Planner
- Cinematic mode
- Route sharing (viewing and creating)
- Region statistics
- Search functionality
⚠️ Login Required (Character Connection)
- Smart Gates (restricted): Check which gates YOU have access to
- User Overlay (Tribe Folder): Tribe-shared bookmarks and notes
- EF-Map Overlay (Helper): Optional, only to save bookmarks to your tribe folder
🔐 Intelligence (Paid Tier, Login + Subscription)
The Intelligence tier unlocks for 100 EVE for 30 days per wallet, paid on-chain from the EVE balance in your in-game Wallet. It covers ten features: Intelligence Dossiers, Activity Tracker, Gate Activity, Economy, Smart Assemblies, SSU Finder, Event Search, Query Console, Panel Creator, and Custom Panels (the same list the app shows on the locked card). Each one is broken down below. The free map keeps showing structures, kills and live events regardless.
Feature-by-Feature Breakdown
🗺️ Routing (Point-to-Point, Scout Optimizer, Reachability)
What it does: Calculates optimal paths between star systems using A* or Dijkstra algorithms. The Scout Optimizer finds the best order to visit multiple waypoints. Reachability shows which systems you can reach with a given jump range.
How it works:
- 100% client-side – All pathfinding runs in Web Workers inside your browser
- The star system graph (24,000+ systems, stargates, distances) is loaded once when you open the map
- Route calculations never leave your device
- No server calls during calculation
What we track: Anonymous aggregate counters only – "X routes calculated" (not who, not which systems, not when).
Login required: No.
🏗️ Smart Assemblies
What it does: Shows player-built structures on the map with their status, owners, and locations. Structure types include: Network Nodes, Smart Gates, Smart Turrets, Smart Storage Units (SSUs), Smart Hangars, Manufacturers (Printers, Refineries, Shipyards, Assemblers), Portable Structures, and Decorative Structures.
How it works:
- Data comes from public blockchain events – the EVE Frontier blockchain emits events when structures are deployed, modified, or destroyed
- Our PostgreSQL indexer listens to these blockchain events and stores them
- The map fetches snapshots from our API and displays them
- No filtering by owner or tribe – every structure visible on-chain is visible in the tool
What we track: Nothing about which structures you view.
Login required: No for the structure markers on the map, which everyone gets. The Smart Assemblies browser panel (the searchable structure list, ownership breakdowns, and the SSU Finder tab) moved into the paid Intelligence tier in July 2026.
Why You See Every Structure
Smart Assembly data comes directly from blockchain events. We don't have a filter that says "hide structures owned by X" or "only show structures from Y tribe." The indexer captures all events, and the frontend displays all results. If a structure exists on-chain, it appears on the map.
🚪 Smart Gates
What it does: Shows player-built jump gates and optionally includes them in route calculations.
How it works:
- Smart Gate deployment/linking events come from the public blockchain
- Our indexer captures all gate data – origin system, destination, owner, access settings
- Three routing modes:
- None: Don't use Smart Gates (no login needed)
- Unrestricted only: Use public gates anyone can transit (no login needed)
- Unrestricted + restricted you can use: Includes gates you personally have access to (requires login)
Why login for restricted gates: To check if YOU can transit a restricted gate, we need to know your character ID to query the blockchain access list. Without login, we can only show unrestricted (public) gates.
What we track: Aggregate counter of Smart Gate route calculations (not which gates, not who).
📡 Live Event Tracker
What it does: Shows real-time blockchain events (kills, structure changes, gate activations) as they happen in the universe.
How it works:
- WebSocket connection to our event server
- Server broadcasts all blockchain events as they're indexed – no filtering
- Events are stored in your browser's IndexedDB (not on our servers) for 72-hour history
- No user-specific filtering – everyone receives the same events
- Since mid-2026 the events come from the Sui chain (EVE Frontier moved chains)
Why Some Events Might Seem Missing
Two reasons an event might not appear in your history:
- Blockchain hasn't emitted it yet – If the blockchain hasn't broadcast the event, we don't have it to relay. This isn't us filtering; it's waiting on on-chain data.
- Your browser wasn't connected – Events are stored locally in your browser's IndexedDB. If you didn't have EF-Map open (even as a background tab) when an event was broadcast, it won't be in your local history.
Searching your events: When you search in the Live Event Tracker, it queries your local browser database (IndexedDB) – not our servers. This means:
- We don't see your search queries
- We can't filter results by player or tribe (we never see the query)
- If an event isn't in your history, it's either because the blockchain didn't emit it or you weren't connected when it was broadcast
What we track: Connection count only (how many maps are connected, not who).
Login required: No.
💀 Killboard
What it does: Tracks PvP kills across EVE Frontier – who killed whom, where, with what ship.
How it works:
- Kill mail data comes from blockchain events
- Our indexer processes these events into structured kill records
- Data is exported as snapshots that the frontend fetches
- No filtering – all kills visible on-chain are in the killboard
What we track: Nothing about killboard views.
Login required: No.
🔍 SSU Finder (Intelligence)
What it does: Searches for Smart Storage Units (SSUs) across the universe with advanced filtering. It now lives as a tab inside the Smart Assemblies browser.
How it works:
- SSU data comes from blockchain events
- Advanced search runs server-side (queries are complex)
- Part of the Intelligence tier – this used to be its own Stripe subscription; it is not any more. New access comes only through the Intelligence unlock, paid on-chain in EVE. Anyone still holding an active legacy Stripe subscription keeps their access
- Search results are not filtered by owner/tribe – you see all SSUs matching your criteria
Why paid: This feature has ongoing infrastructure costs (indexing, storage, API). The Intelligence tier covers those costs.
What we track: Nothing about your searches.
Login required: Yes (Intelligence subscription).
🖥️ EF-Map Overlay (Desktop Helper)
What it does: Native Windows application that overlays route information on your game client.
How it works:
- Helper runs 100% locally on your PC
- Communicates with the EF-Map web app via local HTTP (127.0.0.1) – data never leaves your machine
- Displays route waypoints, tracks visited systems, and shows your current location
- Your live location and visited systems stay on your device – we never receive this data
- No login required to download or use basic features
Why login is optional: You can use the helper without logging in – follow mode, route overlay, and visit tracking all work without authentication. Login is only required if you want to save bookmarks directly to your Tribe folder, because the app needs to know which tribe folder to write to.
What Stays Local
- Your current system location – helper reads from game logs, never sent to us
- Visited systems history – stored in your browser's IndexedDB
- Follow mode state – communicated between helper and browser on localhost only
What we track: Helper connection status (aggregate count only – not who, not which systems you visit).
📝 User Overlay (Personal Marks and Tribe Folder)
What it does: Your own annotations on the map – personal marks just for you, and a shared bookmark folder for your tribe.
How it works:
- Personal marks never leave your browser at all. They live in localStorage on your own machine. There is no sync endpoint for them – I could not read them if I wanted to
- Tribe bookmarks are stored server-side, encrypted at rest with AES-256-GCM. The key is derived from a server-held secret, per tribe
- Access is checked against your actual on-chain tribe membership – you only ever see your own tribe's folder
- Login required for tribe bookmarks, to verify which tribe you are in
An honest correction from the original version of this post: this article used to say tribe notes were encrypted with keys derived from your wallet signature, so that I could not read them. That was true as a design when it was written, but in practice the end-to-end rollout never completed: it ran in a transition mode that kept plaintext copies alongside the encrypted ones until every tribe member had re-signed, and the numbers showed that state was never reached. So the everyday reality was plaintext sitting in storage anyway. In June 2026 I replaced that half-applied scheme with encryption at rest that actually covers one hundred percent of the data, which is more honest and strictly better than what was really there before, even though it is a weaker promise than the end-to-end design was supposed to deliver. The current model is encryption at rest with a server-managed key, which protects the stored data but does mean the server holds the key material. It is not operator-blind end-to-end encryption and I am not going to pretend it is. What I can say is that the data is a folder of map bookmarks with no location tracking in it, and I have no reason to look at it.
What we track: Nothing about note contents.
📊 Static Data Tools (Compare Regions, Blueprint Calc, Star Colouring, Module Mission)
What they do: Multiple features use static files extracted from the game client:
- Compare Regions – Compare structural and navigational statistics across EVE Frontier's regions
- Blueprint Calculator – Calculate crafting materials and production chains
- Star Colouring / Planet Counts – Visualize stars by planet count, class, or other metrics
- Module Mission – Checklist of all modules in the game for tracking your collection
How they work:
- Compare Regions uses the smaller universe map database (system positions, gates, regions)
- Star Colouring / Planet Counts uses the solar system database (detailed celestial data)
- Blueprint Calculator and Module Mission use JSON files generated from static game data
- All calculations are performed client-side in your browser
- Same data for everyone – computed from the same static dataset
- Databases and JSONs are downloaded once and cached locally
What we track: Nothing.
Login required: No.
📈 Activity Tracker
What it does: Visualize game, tribe, and player activity over time – structure deployments, state changes, and other on-chain events displayed as time-series charts.
How it works:
- Data comes directly from the blockchain – we read on-chain events from the Primordium indexer
- An aggregation job runs on our server, summarizing events into hourly buckets for fast visualization
- Charts show: structure online/offline state changes, activity by player or tribe, drill-down from Game → Tribe → Player
- No filtering or editorializing – we display exactly what the blockchain contains
- Anyone can verify the source data by querying the same on-chain tables
What we track: Nothing about who views activity data. The activity itself is public blockchain data.
Login required: Yes, this panel is part of the Intelligence tier now. The free live ticker strip in the top bar is a separate thing and stays free.
🎯 Intelligence Dossiers (Intelligence)
What it does: Profiles of a player, tribe or system – recent activity, kill history, gate networks, likely home territory – assembled from indexed chain data.
How it works: The lookup runs server-side against the same indexer database as everything else, because that is where the index lives. Everything in a dossier is public blockchain data; the panel just gathers it in one place. There is no data in a dossier that a player running their own indexer could not compile about you.
What we track: Aggregate usage counters.
Login required: Yes (Intelligence).
🚨 Gate Activity (Intelligence)
What it does: Shows who owns the jump-gate and catapult network, and who is travelling through whose gates.
How it works:
- A job on our server reads the indexer every 5 minutes and publishes one pre-computed snapshot of JSON
- Your browser downloads that snapshot and does all the filtering and sorting locally – there are no query parameters, so we never see what you look at inside it
- Everyone gets the same snapshot. One cached read serves every viewer
What we track: An aggregate open counter.
Login required: Yes (Intelligence).
💰 Economy (Intelligence)
What it does: On-chain economic activity – item flows in and out of storage, stockpiles, mint and burn, and which third-party tools are being used.
How it works: Same pattern as Gate Activity: a server job publishes one snapshot every 15 minutes, your browser explores it locally, everyone sees the same data. All of it is public chain state.
What we track: An aggregate open counter.
Login required: Yes (Intelligence).
🔎 Event Search (Intelligence)
What it does: Search across universe events beyond what the free live ticker shows.
How it works: Today it searches the event history your own browser has stored, locally. It sits in the Intelligence tier because it is the surface where server-backed history for whole cycles is planned to land. The free live ticker and your 72-hour local history are unaffected.
What we track: An aggregate open counter.
Login required: Yes (Intelligence).
🧮 Query Console (Intelligence)
What it does: Lets you ask the indexer your own questions – tables, leaderboards and over-time charts across ten datasets, with a plain-English assistant that can write the query for you.
How it works:
- This is the one feature where your specific question does run on our server, because it queries the live indexer database. The indexer's coverage starts at the Cycle 6 chain reset on 25 June 2026
- Your browser never sends SQL. It sends a restricted JSON description of the query, which the server compiles against a fixed set of datasets. Every query runs read-only with a 5 second timeout and hard row caps
- Rate limits per wallet keep the database healthy (burst and daily caps)
- Query text is logged anonymously – what was asked, never who asked it. There is no wallet column in that log. I review it to decide which datasets to build next
- The plain-English assistant sends your typed description to an AI model to draft the query. The draft always comes back for your review before anything runs
What we track: Aggregate run counters and the anonymous query log described above.
Login required: Yes (Intelligence).
🧩 Panel Creator and Custom Panels (Intelligence)
What it does: Build your own intelligence dashboard – up to 12 panels of up to 6 widgets each, drafted by AI from a plain-English description, picked from presets, or built by hand. Full write-up in the announcement post.
How it works:
- Panel definitions live in your browser's localStorage by default. Signed out, offline, never synced – they are yours
- Widgets run through the same restricted query pipeline as the Query Console, with the same read-only guarantees, caps and anonymous logging. Nothing auto-refreshes – widgets run when you open the panel or press refresh
- If you sign in, your panels back up to one encrypted document per wallet (AES-256-GCM at rest, server-managed key, same honesty caveat as tribe bookmarks). The storage key is a hash of your wallet address, so a listing of our storage cannot enumerate who subscribes
- Sharing a panel creates a frozen snapshot behind an opaque link with a 90-day expiry. It carries the panel definition only – no wallet, no account details, no results. Anyone can view the definition; running the widgets needs their own subscription
What we track: Aggregate counters (panels created, widgets run, AI drafts asked).
Login required: Yes (Intelligence) to run widgets; sync and sharing additionally need the sign-in.
What We Collect (And What We Don't)
We Collect: Anonymous Aggregate Statistics
We track:
- Feature counters: "Cinematic mode was toggled X times" (total, all users). When I first wrote this it was about a dozen counters. As of August 2026 it is 647 live counters, because every feature that shipped since brought its own – but the shape has not changed: totals across all users, never rows about a person
- Session buckets: "Y% of sessions lasted 5-15 minutes" (no user identity)
- Time sums: "Users spent Z total hours in cinematic mode" (aggregate)
- Device capability buckets: coarse counts of screen resolution, CPU cores, WebGL tier and similar, so we know what hardware to optimize for. Each is an independent counter with no join key, so they cannot be recombined into a fingerprint of you
You could view these stats yourself at /stats until 6 August 2026, when the dashboard went private. See the update at the end of this page, and ask me if you want the numbers.
We Don't Collect
- ❌ User IDs or wallet addresses (in analytics)
- ❌ Session IDs or browsing paths (our own stats have neither; GA4 sets its standard _ga cookie, covered below)
- ❌ IP addresses for tracking. Two honest caveats: Cloudflare, our CDN, sees IPs the way every CDN does; and if you use the plain-English AI features while signed out, a rate-limit counter keys on your IP for 48 hours and then expires. Neither is used to identify or follow you
- ❌ Which systems you route between
- ❌ What structures you click on
- ❌ Map and event searches – these run entirely in your browser and never reach us. The exception is the plain-English AI asks (System Finder, Query Console, Panel Creator, the AI command panel): the text you type is sent to our server to be turned into a query, and it is logged anonymously – what was asked, never who – so I can see which questions the tools fail to answer. There is deliberately no wallet, session or IP attached to those logs
- ❌ Device fingerprints
- ❌ Your location or visited systems (helper data stays on your device)
Wallet Addresses: When We Store Them
This list used to be one item (SSU Finder subscriptions). The product has grown, so here is the complete current inventory of places a wallet address touches our storage:
- Intelligence subscriptions store nothing at all. The entitlement lives on the blockchain. When you use an Intelligence feature we check the chain; there is no subscriber database on our side
- Panel backup (optional): if you sync custom panels, they are stored as one encrypted document keyed by a hash of your wallet, so our storage cannot even be listed to enumerate subscribers
- Paired devices: pairing a phone stores a device grant against your wallet for 7 days at a time, refreshed while you keep using it, so it stays revocable
- Rate-limit counters: query and AI-assist quotas key on your wallet for 48 hours, then expire. They hold a number, nothing else
- Things you deliberately publish: scout reports, stargate status reports, opt-in Log Parser leaderboard entries and arcade scores are stored against your wallet because attribution is the point of publishing them
- Legacy Stripe subscriptions: anyone still on the old SSU Finder subscription has wallet + Stripe customer ID in our database, as before. Stripe holds all payment data; we never see card details. No new subscriptions of this kind can be created
Where Does the Data Come From?
This is important: we don't generate player activity data – the blockchain does.
| Data Type | Source | Our Role |
|---|---|---|
| Star systems, stargates, regions | Game client extraction (our own in-house pipeline since August 2026) | Extract + ship as a static ~5 MB database your browser queries locally |
| Solar system detail (planets, moons, orbits) | Game client extraction | Ship as a static database, downloaded on demand and queried in your browser |
| Smart Assemblies | Blockchain events | Index + display |
| Smart Gates | Blockchain events | Index + display |
| Kills | Blockchain kill mail events | Index + display |
| SSUs | Blockchain events | Index + search |
| Live events | Blockchain (near-real-time via our indexer) | Relay to clients |
| Gate Activity / Economy / Activity Tracker panels | Blockchain events, aggregated | Pre-compute one shared snapshot on a schedule |
| Query Console / custom panel widgets | Blockchain events in our indexer database | Run your read-only query server-side, capped and timed out |
We don't control what the blockchain emits. If an event exists on-chain, our indexer captures it. If it doesn't exist, we don't have it. There's no manual curation or filtering step where we decide "show this, hide that."
Why Client-Side Matters
When we say "client-side," we mean the code runs in your browser, on your device:
- Route calculations: Your browser does the pathfinding. Our servers never see your start/end systems.
- Map rendering: Three.js renders 24,000+ stars locally. No server-side rendering.
- Search: Fuzzy matching runs in-browser against locally-loaded data.
- Settings persistence: Stored in your browser's localStorage, not our database.
The benefit: we literally can't see what you're doing because the computation happens on your machine.
The honest exceptions, so nobody has to dig for them: the plain-English AI features (System Finder search, Query Console assist, Panel Creator drafting, voice commands and the AI command panel) send the text you typed, or the audio you spoke, to a model hosted by Cloudflare, the same platform the site runs on, because a language model cannot run in your browser. The Ctrl+K command palette is different: it is a deterministic local parser and sends nothing. The Query Console and custom panel widgets run their queries on our server because that is where the indexer database lives. And the SSU Finder search runs server-side because the queries are heavy. Everything else on the list above stays local.
Web Analytics: What We Do Track
In the interest of full transparency: We use industry-standard web analytics to understand how the site is used. Here's exactly what that means:
📊 Google Analytics 4
We use Google Analytics 4 (GA4) to understand aggregate site usage. Here's what GA4 collects by default:
What GA4 Collects
- Page views – Which pages users visit (but not who)
- Approximate location – Country and city level (IP addresses are NOT stored in GA4)
- Device/browser info – Browser type, screen size, operating system
- Session statistics – Time on site, pages per session
- Custom events – We send events like "efm_route_planned" or "efm_panel_open" (with coarse detail like waypoint counts and panel names, never which systems or whose route)
- Core Web Vitals – Standard page-performance metrics (load time, input delay, layout shift), tagged with the CSS selector of the UI element involved so slow components can be found. UI element names, not your data
What GA4 does NOT collect (and we don't send):
- ❌ Your wallet address
- ❌ Your character name or ID
- ❌ Which systems you search for or route to
- ❌ Which structures you view
- ❌ Your in-game activities or tribe affiliation
What you'll see in DevTools: Requests to google-analytics.com and googletagmanager.com. These are standard analytics pings, not behavioral tracking.
📈 Our Custom Usage Stats
In addition to GA4, we collect our own aggregate-only usage statistics:
- What we track: Event type counters ("10,000 routes calculated today") and duration sums ("users spent X hours in cinematic mode") – 647 counters as of August 2026, one per feature action, all aggregate
- What we don't track: Who calculated those routes, which systems, or when
- How it works: Your browser batches events and sends them to
/api/usage-eventevery few seconds. No cookie, no session ID, no wallet, no free text
Inspect the payload yourself: In DevTools Network tab, filter for "usage-event" and click the request. The payload looks like:
{"events":[{"type":"route_calculated"},{"type":"cinematic_enter"}]}No user ID, no system names, no identifying information.
Why We Use Analytics
We use analytics to answer questions like:
- How many people use the Scout Optimizer vs basic routing?
- Is the new Solar System View feature being used?
- What's the typical session length?
- Which countries have the most users?
This helps us prioritize development. We don't use it to track individual behavior or target advertising.
Opting Out
If you prefer not to be included in analytics:
- Google Analytics: Install the Google Analytics Opt-out Browser Add-on
- Our usage stats: Use an ad blocker that blocks
/api/usage-eventrequests
The map will work identically without analytics.
Verify It Yourself: A DevTools Guide
Don't take our word for it. You can verify every claim in this post using your browser's Developer Tools. Here's how to fact-check us:
Opening DevTools
In Chrome, Edge, or Firefox: Press F12 or right-click anywhere and select "Inspect". Then use the tabs described below.
1. Network Tab: See Every Request We Make
Open the Network tab, then use EF-Map normally. You'll see every HTTP request the page makes.
What to Look For
- Web analytics requests – You'll see requests to
googletagmanager.comandgoogle-analytics.com. These are standard web analytics (see Web Analytics section below for what this collects) - Route calculations are silent – Calculate a route and watch the Network tab. No requests are made during pathfinding (it runs in Web Workers locally)
- Search is local – Type in the search box. No autocomplete requests to our servers
- Usage events are aggregated – You'll occasionally see a POST to
/api/usage-event. Click it and inspect the payload – it contains only event type counters, no identifying information
2. WebSocket Tab: Watch Live Events
Filter the Network tab by "WS" (WebSocket). You'll see the connection to our universe events server.
Click on it and view the "Messages" tab. You'll see:
- Incoming events only – The server broadcasts events; your browser doesn't send user-specific data back
- Event content – Each message contains blockchain event data (kills, structure changes) with no user tracking
3. Application Tab: See Your Local Data
Open the Application tab (Chrome/Edge) or Storage tab (Firefox).
What You'll Find
- IndexedDB → ef_event_history – Your 72-hour event history. This is stored in YOUR browser, not uploaded
- IndexedDB → ef_solar_system_db – Cached solar system database for faster loading
- localStorage – Your settings (accent color, panel positions, preferences). All local, never synced
4. Helper Traffic: Confirm It's Local-Only
If you use the EF-Map Overlay Helper, filter the Network tab for 127.0.0.1 or localhost.
All helper traffic stays on your machine. You'll see requests to http://127.0.0.1:38765/... – this is your local helper, not an external server. Your current system, visited systems, and follow mode state never leave your PC.
5. What You Won't Find
- ❌ Requests to Facebook, Mixpanel, Amplitude, or other behavioral analytics
- ❌ Your wallet address being transmitted to us (exceptions: signing in creates a session cookie derived from your wallet; Intelligence entitlement checks read the blockchain and store nothing; Smart Gate access checks and profile picture/character name lookups go directly to CCP's chain RPC and APIs – not stored by us)
- ❌ Route start/end systems being sent anywhere
- ❌ Your search queries leaving the browser
- ❌ Device fingerprinting scripts
- ❌ Your in-game activities being tracked individually
If you find something that contradicts our claims, please let us know. We're committed to transparency, and we'd rather fix a problem than hide it.
The Transparency Commitment
What We Promise
- No hidden filtering – All blockchain data we index is displayed without player/tribe filtering
- Stats on request – Published openly at /stats until 6 August 2026, and still available to anyone who asks
- Documented patches – Notable changes are written up on the blog
- Open process – Technical decisions are documented in our blog posts
- No login walls on the free map – the overwhelming majority of features work without connecting a character; the paid Intelligence tier is the exception, and every feature in it is itemized above
If you ever notice something that seems inconsistent with these principles, please reach out. We're committed to building a tool the EVE Frontier community can trust.
Summary Table: Login Requirements
| Feature | Login Required? | Why? |
|---|---|---|
| 3D Map Navigation | No | - |
| Route Calculation | No | - |
| Scout Optimizer | No | - |
| Reachability | No | - |
| Smart Assemblies (map markers) | No | - |
| Smart Assemblies browser + SSU Finder | Intelligence | Paid tier |
| Smart Gates (Unrestricted) | No | - |
| Smart Gates (Restricted) | Yes | Wallet session; your character is resolved on-chain to check gate access |
| Killboard | No | - |
| Live Events | No | - |
| Solar System View | No | - |
| Compare Regions | No | - |
| Live ticker strip (top bar) | No | - |
| Activity Tracker panel | Intelligence | Paid tier |
| Gate Activity / Economy / Event Search | Intelligence | Paid tier |
| Query Console / Panel Creator / Custom Panels | Intelligence | Paid tier; panel sync and sharing additionally need sign-in |
| Log Parser | No | Optional wallet only if you publish to the leaderboard |
| Scout Reports | Optional | Viewing is free; publishing signs the report with your wallet |
| Blueprint Calculator | No | - |
| Route Sharing | No | - |
| Search | No | - |
| Cinematic Mode | No | - |
| User Overlay (personal marks) | No | Local-only, never uploaded |
| User Overlay (Tribe bookmarks) | Yes | Tribe membership verification |
| EF Helper (desktop app) | Optional | Free app; login only to save bookmarks to your tribe folder |
Updates
Update, 9 August 2026. Tracked action clicks on blog articles. Blog articles still carry no analytics script, and article views are counted server-side as the Worker serves each page, storing only an article slug and a UTC date. New on this date: some article links to EF-Map tools and to the game's own site now route through a first-party redirect at /go/<destination>, which increments one aggregate counter per UTC day, source article and destination id, then immediately forwards you on. Stored fields, exhaustively: day, allowlisted article slug, allowlisted destination id, count, plus a per-day count of requests filtered as crawlers and the timestamps of when the document started and was last written. No IP address, no cookie, no visitor or session identifier, no referrer, and no individual event record. These counts exist so I can tell whether the articles actually send anyone to the tools, and they are deliberately labelled tracked clicks rather than conversions, because nothing in them identifies or deduplicates a person.
Update, 8 August 2026. A full refresh of this page, because the product had moved on and a transparency report that is out of date is worse than none. What changed: the Intelligence tier now exists and its ten features are each broken down above, SSU Finder is part of it rather than a standalone Stripe subscription, the star map data pipeline is fully in-house, the counter count and analytics sections were re-verified against the code, and the wallet-storage inventory is now complete rather than one bullet. The biggest correction is the tribe bookmarks section: the original text described wallet-signature encryption that was retired in June 2026, and the current server-managed model is now described honestly, including what it does not protect against. Everything on this page was re-checked against the actual source code on this date.
Update, 6 August 2026. The stats page is no longer public. When I wrote this it was about a dozen counters, page loads and routes and not much else. It has grown to 647, and it now covers which features people actually use and how the paid Intelligence product converts. That is fine for me to look at. It is less fine sitting on an open endpoint at game launch when somebody with real money turns up looking for a shortcut past eleven months of learning what Frontier players want. So I have put it behind my own login. What I collect has not changed. There is still no personal data, no IP addresses collected for tracking, no per-user anything, and the help panel inside the map lists every category I record. If you want the numbers, and especially if you are a student or you are building something in the Frontier community, just ask me on Discord and I will send them over.
Related Posts
- EF-Map Intelligence: What It Is, What Stays Free – The paid tier explained: what it costs, what it covers, and why the free map stays free
- Custom Intelligence Panels – Build your own dashboard; includes how panel storage, sync and sharing work
- The Query Console – Ask the indexer your own questions; the security model behind live queries
- Database Architecture: Blockchain Indexing – How we index on-chain data
- Smart Gate Authorization – How gate access checking works
Questions about how something works? Ask in our Discord. We're happy to explain any aspect of the system in detail.