EF‑Map Privacy Policy
Last updated: 2026-11-14
Who is responsible: Michael Davis (in game: Lacal), an individual in the United Kingdom, is the data controller for EF‑Map: he decides what is collected and why. Contact: [email protected].
At a glance: what the operator can see
EF‑Map is run by one person, its sole operator. There are no adverts, nothing is charged, the Intelligence tools are free for any signed‑in player, and Stripe subscriptions are no longer offered. This is what reaches him; the sections below give the detail.
| Your data | Does the operator get it? |
|---|---|
| Game logs and Log Parser results | No. They are parsed and kept in your browser. Only if you publish a leaderboard entry are your cycle totals stored, with your character name and tribe. |
| Personal marks and notes | No. They never leave your computer. |
| Routes you plot | No. Routes are calculated in your browser. A shared route link is stored under a random id, with nothing about who made it. Statistics get counts such as the number of jumps, not the systems. |
| Your current system | No. EF Helper passes it to the map on your own PC and it goes no further. Clicking a system asks our server for that system's gates, kills and charting, the same as for any system you click, and those requests are not logged. Google Analytics never receives the system you are looking at or in. |
| Map searches | Not kept. System names are matched in your browser. What you type is also sent to our player and tribe search to suggest matches; it isn't linked to your account and isn't logged. |
| RootFit fits | Try Add and Help me fit ask our fit store about that exact setup. A setup is stored, anonymously, only if Usage statistics is on and your browser finds a better layout. Offline Mode stops all of it. |
| Tribe and alliance marks | Stored on our server, encrypted at rest. He could technically decrypt them, and has never opened them (see Security). Each member's reads and writes are counted, without content. |
| Things you publish | Yes. Community map charts, gate status reports and leaderboard entries are stored with your wallet and character name. Signed‑in players see who reported a gate; the operator and the moderators he appoints see who charted a system. |
| Signing in | Yes: your wallet address, a Discord id if you link one, and records of past Stripe subscriptions. Your character and tribe are read from the chain. |
You can check this yourself: open your browser's developer tools (F12), watch the Network tab while you use the map, and compare it with our Transparency Report.
Log Parser & Local Analytics
The Log Parser feature processes your EVE Frontier game logs entirely within your browser:
- 100% client-side processing: All log file parsing happens in your browser using a Web Worker. Your game log files are never uploaded to EF‑Map servers.
- Only what it needs: It reads the current cycle's game logs and Local chat logs (Local chat tells it which system you were in). Other files in the folder are skipped by name.
- Local storage only: Parsed data (mining, combat, travel and activity by system and day) is stored in your browser's IndexedDB. In Chrome and Edge the browser also remembers the logs folder you chose so Sync can read it again; the browser asks for your permission, and EF‑Map can only read that folder.
- Killboard pins: To show your PvP kills and deaths on the map, the panel downloads the public killboard timeline and picks out your character in the browser. Your character ID is not sent.
- No server transmission unless you publish: We do not collect, store, or have access to your game logs or the analytics derived from them, unless you sign in with your wallet and publish a leaderboard entry. Then only your cycle totals (such as ore mined, crude matter mined, estimated NPC kills, damage, jumps, systems explored, active time and longest session) are stored under your wallet address, with your character name and tribe. No systems, times or log lines are sent. Remove my entry in the panel takes it off the leaderboard at any time; to have the stored entry deleted as well, use the request process below.
- User control: "Clear my log data" in the Log Parser's menu removes all locally stored log data, and so does clearing this site's data in your browser settings.
Future optional sharing: we may introduce further optional features that share data. Any data sharing will be explicitly opt‑in: you must actively choose to participate, you retain full control, and you can opt out at any time. We will clearly indicate what data is shared before you consent.
Route Planning & Search
Routes, jump ranges and Smart Gate paths are calculated in your browser from map data it has downloaded; our server has no route‑planning endpoint, and Smart Gate access lists are downloaded whole, so it never learns which gates you route through. A route leaves your browser only when you choose to share or save it, for example as a link (stored under a random id with no expiry and nothing about who made it), or when it is sent to EF Helper on your own PC. Our usage counters and the Google Analytics route event carry counts and settings, such as the method, the number of jumps and waypoints (rough sizes such as "10 to 30 jumps" in our counters) and the calculation time, never a system. The search box matches system names in your browser, but anything you type there (two characters or more) is also sent to our player and tribe search to suggest matches, without your account, and neither the search service nor anything in front of it keeps a log of it.
Data We May Store
If you choose to sign in, we may store:
- Wallet address: Your SUI wallet address (if you choose to sign in / link a wallet). Used as an authentication key and to derive tribe membership where applicable.
- Discord account metadata: Discord identifier (user id), username and avatar if you link your Discord account via OAuth. Used only to show linked identity and ease login.
- Records from earlier subscriptions: Stripe subscriptions are no longer offered. If you subscribed in the past, we keep your Stripe customer identifier, subscription status, a small internal customer number (an internal reference, never published) and copies of the notices Stripe sent us when a subscription was created, updated, cancelled or paid, for bookkeeping and support. Payment notices include the billing name, email and address you gave Stripe. We never stored full payment card details.
- Tribe and alliance mark reads: no mark content is recorded. For each member, per space and per day, we count downloads of the space's marks (EF Helper's background sync included), Version history days opened, changes saved and marks added, with the time of their last activity, their wallet address, character name and the space's name. Only the operator can see these counts; other members never can. They are there so that unusual downloading, such as someone taking far more than they add, would stand out if marks leaked. They expire after 35 days.
Why We Store This
Account metadata enables sign‑in and per‑account features such as saved panels and usage quotas. Records from earlier subscriptions are kept for bookkeeping and support. Wallet/address linkage is used for authentication, tribe membership checks, and optional encrypted tribe workflows.
Each use of your data has a lawful basis:
| What we use it for | Lawful basis |
|---|---|
| Signing in, and the features you use while signed in | Contract: we need it to provide the service you ask for. |
| Things you choose to publish or link: leaderboard entries, community map charts, gate reports, a Discord account | Consent. Withdraw it at any time with Remove my entry in the Log Parser, Unlink in the account menu, or an email asking us to delete them. |
| Security and abuse protection: API request logs, the Turnstile check, rate limits, tribe and alliance read counts | Legitimate interests: keeping EF‑Map safe from scraping and misuse. |
| Usage statistics: Google Analytics, our own counters and the performance measurement | Legitimate interests: knowing whether the tools are used and run well. To object, turn off Usage statistics: on this browser that stops Google Analytics, the counters the map and RootFit send, and the performance measurement (Offline Mode stops all network features). Blog view and link counts are tallied on our server and hold counts only. |
| Replying to emails you send us | Legitimate interests: answering you. |
| Records from earlier subscriptions | Legal obligation: tax and accounting records. |
Partner API Request Logs
Ordinary use of the map in a browser is not logged this way. Two kinds of automated request are: requests made with an EF‑Map API key (see API access), and requests for the community map's data that come from a script rather than a browser. Each is logged with its time, method, host, route and result, the caller's IP address, what Cloudflare reports about that IP (approximate country, region, city, coordinates and time zone, the network's number and name, and the data centre that answered), the user agent, the request's origin, and the calling Cloudflare Worker's zone if there is one. The logs are used only to spot scraping, abuse of the API and keys being shared. Only the operator can see them; they are deleted automatically after 90 days and left out of database backups.
Third Parties & Processors
We use third parties for hosting, authentication, statistical analytics, and (in the past) payments:
- Cloudflare: hosts the site, runs our server code and carries every request, so it sees IP addresses in transit. It also stores data such as tribe and alliance marks, links to our own server through secure tunnels, and forwards email sent to @ef‑map.com. We have not turned on any Cloudflare feature that keeps request logs.
- Hetzner: hosts our own server in Falkenstein, Germany. It holds data including linked Discord accounts, records from earlier subscriptions, the partner API request logs and the RootFit fit store.
- Stripe: processed payments for earlier subscriptions, which are no longer offered. For past subscribers we hold a Stripe customer id and subscription status. We never store raw card numbers or full payment method details on our servers; Stripe retains and processes payment credentials according to their policy.
- Discord: optional OAuth login. We receive a Discord user id and basic public profile metadata when you link Discord.
- Cloudflare Turnstile: an invisible check that a real browser, not a script, is loading the community map's player-charted data. Cloudflare reads browser signals to make that check. EF-Map sends Cloudflare your IP address with it, receives a pass or fail, and ties the resulting 30-minute map pass to a one-way hash of your IP address; nothing from the check is stored. Cloudflare's handling of that data is set out in the Cloudflare Turnstile Privacy Addendum.
- Google Analytics: statistical usage information about the map, as described under Analytics below. Google processes that information for EF‑Map; it is not used here for ads or cross‑site tracking.
Where your data is processed. Our own server is in Germany, which the UK's adequacy regulations cover. Cloudflare, Google, Stripe and (if you link it) Discord are US companies, so they may process data outside the UK. For the US, transfers rely on the UK Extension to the EU‑US Data Privacy Framework where the provider is certified, and otherwise on the provider's standard contractual clauses with the UK Addendum. Anything you publish on the Sui blockchain is public by design and outside our control.
Storage & Retention
A sign‑in (on a paired phone too) ends after 7 days without use. Your wallet address, a linked Discord account and anything you publish are kept until you remove them or ask us to delete them, unless a section above gives a shorter period. Billing records from earlier subscriptions (invoices, subscription history) are kept for up to 7 years to meet bookkeeping requirements. Aggregate anonymous metrics are retained and rolled up as described in our analytics documentation. Deleted tribe and alliance bookmarks are kept for 30 days in that space's Recently deleted list, and one daily version of each tribe and alliance space is kept for 30 days, so members can restore them; both expire automatically (see the content policy). Deleted data can also remain in older backups of our server, which we keep only to recover from mistakes and never use for anything else.
Security
We protect data in transit using TLS. The map and EF‑Map's own pages (not yet RootFit or CivilizationControl) also tell your browser which sites they may contact. If one tries to reach a site that is not on that list (often a browser extension doing it), your browser may send us a short security report; we keep only a daily count per destination domain, never the page address or your IP address. Only the project's sole operator has access to its servers and databases; automated jobs and AI agents he runs act on his behalf. The community moderators he appoints can see the gate status reports and community map submissions they moderate, including who sent them, and have no other access to user data. We do not request or store raw payment card data; Stripe handled payment credentials for earlier subscriptions. Tribe bookmarks, alliance bookmarks and synced panel definitions are encrypted at rest (AES‑256‑GCM) with keys derived from server‑held secrets. This protects stored data but is not end‑to‑end encryption: because the server holds the keys, the operator could technically decrypt a space's marks. He has never opened any tribe's or alliance's shared marks and never will, he does not ask his tools (including AI agents) to display or copy them, and fixes to shared spaces are made without viewing or copying marks. Personal map notes never leave your computer.
Your Rights
You can ask for a copy of your data (in a portable, machine‑readable form if you like), or ask us to correct it, delete it or restrict its use. You can object to anything we do under legitimate interests, usage statistics included, and withdraw consent at any time. Some of this you can do yourself with the controls listed under Why We Store This; Delete your account & data explains deletion. To make a request, email [email protected]. Include your wallet address or the email used for support requests and we will follow up with verification steps. We reply within one month. You can also complain to the UK Information Commissioner's Office at ico.org.uk.
EF Helper (Desktop Overlay)
EF Helper is a Windows app. It reads your EVE Frontier game and chat logs on your PC to show mining, combat and the system you are in. To draw its windows inside the game, it loads its overlay into the game's process, where it hooks the game's DirectX 12 drawing and the game window's mouse and keyboard input so its windows can be clicked. It does not read the game's memory, capture the screen or read your clipboard. It makes no internet requests of its own: it serves its data on a local port on your PC (127.0.0.1), where the EF‑Map page in your browser reads it and sends it your route and marks. Anything that leaves your PC is sent by that page, under the rules on this page: the overlay's anonymous feature counts and any mark you save in game to a tribe or alliance space. With follow mode on the map shows the system you are in, but that system is kept out of what goes to Google Analytics. Discord Rich Presence is off by default; if you turn it on, the helper tells the Discord app on your PC what to show on your profile.
Analytics
EF‑Map uses two separate kinds of usage statistics, both to understand how the service is used and to improve it. Neither is used for advertising, remarketing, cross‑site tracking, or building a profile of you as a person.
First‑party counters. The map records anonymous aggregate feature counters (for example how often a tool is opened). Those events do not include IP addresses, cookies, device IDs, or other personal identifiers, and none are sent while Usage statistics is turned off on this browser or in Offline Mode. See the blog post Transparency Report for the first‑party event model. The fitting planner at /fit reports the same kind of anonymous aggregate counters under the same Usage statistics switch: which tools and views were used (for example Try Add, Optimize Space, the control deck or full screen), how its searches ended, and which module types were asked for in Try Add, as counts only. It never reports a layout, a fit code, a saved fit’s name or any identifier, and it sends no counters at all while Usage statistics is turned off on this browser.
RootFit community best fits. When you run Try Add in RootFit's 3D view, or Help me fit fills a ship's spare space, RootFit asks our fit store (activity.ef‑map.com, on our own server) whether a better layout is already known for that exact setup, so a proven layout can appear at once instead of after a long search. Nothing is sent before your first Try Add or Help me fit. The question contains the ship's sections, the modules already fitted and where they sit, and the module types you asked to add (for Help me fit, the containers and Structural Braces it may add and the balance of cargo against structure you chose): no account, fit name or fit code. A question alone never adds a setup to the store. For a setup the store already holds, it adds one to that setup's demand count, at most once a day per network, and not even that with Usage statistics off. A setup is stored only when Usage statistics is on and your browser then finds a better layout than the store's: RootFit sends that layout (module positions only). For each setup the store keeps the setup, its best layout and score, how often it was asked for, the best fill found for each ship section, and creation and update times, never who sent it. It stores no IP address, user id or request log; to limit abuse it counts requests per IP address prefix in memory only, and those counts expire within a day. If you are working on a fit you want to keep to yourself, turn on Offline Mode (Display Settings on the map, General tab, Modes) before using Try Add or Help me fit: RootFit then does not contact the store at all. With Usage statistics off (Display Settings, Interface tab, or the switch below), RootFit still asks the store, but nothing you send is stored.
Blog article views are also counted by our server as it serves each page, separately from Google Analytics below, and some article links to EF‑Map tools or the game's site route through a first‑party redirect (/go/…) that increments one aggregate counter per day, source article, and destination before forwarding you on. In both cases the stored data is counts only: no IP address, no cookie, no visitor or session identifier, no referrer, and no per‑person record of any kind. Because our server counts these as it answers the request, before any page script runs, the Usage statistics switch does not reach them.
We also record one anonymous performance measurement per visit, so we can tell whether the map actually runs well on the range of hardware people use rather than only on the machine it is developed on. It is a single coarse category combining which display mode you were in, whether your graphics are integrated or discrete, whether star bloom was on, and how smoothly frames were delivered compared with your display's own refresh rate (for example "kept up" or "missed some"). It contains no identifiers and no timestamps, it is counted rather than stored per visit, and it is deliberately never the detailed graphics‑card name, because that would be identifying when combined with screen size. It is not collected while Usage statistics is off or in Offline Mode.
Google Analytics. Usage statistics are on by default, because without them we cannot tell whether anyone uses a tool. The map, the blog, the information pages, RootFit at /fit and CivilizationControl at /civ-control load Google Analytics 4, and Google processes what it collects only to produce statistics for EF‑Map. Advertising, remarketing and Google Signals are switched off. A first‑party cookie (_ga) holds a random identifier for this browser so visits and their length can be counted; it is not your name, wallet or character, and it is not used across other websites. Google sees a coarse location derived from your IP address (the IP itself is not kept in Google Analytics) and standard device details. Each page is labelled with the part of the site it belongs to (map, blog, RootFit and so on); the label describes the page, not you. Google keeps the event-level data for two months, the shortest setting it offers; its standard reports keep only totals. Before the update of 10 November 2026 the map sent its full page address and title, which could include the selected system, a route or a search; that data ages out of Google Analytics within two months of the update.
On the map, Google gets page views, which panels you open and for how long, a few feature events such as a log parse or an EF Helper download, and for each route the number of jumps and waypoints, the method and whether Smart Gates were used. No event carries what you type in the search box, a character name or the systems on a route. Google never receives which system you are looking at or in, a route or a search: before anything is sent, the map takes every system, route, search and share out of the page address (only the path, campaign tags and the tool or timelapse a link opened are left, and ids in the path become :id), and Solar System View sends a fixed title instead of the system's name. Outside the map, Google gets the page address without its query string (campaign tags apart) and without ids in the path, so for example a shared RootFit fit code or a CivilizationControl gate is not sent. See the Transparency Report for the event list.
How to turn this off. You can object at any time, for free, and the site works the same either way. The simplest place is Display Settings on the map (Interface → Usage statistics), or the control below. One switch covers the map, the blog, RootFit and CivilizationControl. The in‑game browser keeps its own settings, so if you use CivilizationControl in game, turn it off there too (its Privacy & usage statistics link opens this page). Turning it off stops Google Analytics on this browser (the script is not loaded, events are not sent, and the analytics cookies are deleted) and stops our own counters on the map and RootFit. Offline Mode stops both, and embedded map views skip Google Analytics.
You can also open Display Settings on the map.
Cookies & Local Storage
- We use browser
localStoragefor UI preferences (theme, display settings, and whether you have turned usage statistics off) and for content you choose to save locally, such as recorded camera flights. These stay in your browser and are never uploaded. IndexedDBstores your parsed log data locally on your device.- Google Analytics, when allowed, sets first‑party analytics cookies on ef‑map.com as described above. There is no advertising cookie and no cross‑site tracking cookie from EF‑Map.
- A signed‑in session uses a first‑party
HttpOnlylogin cookie so you stay signed in. That is for sign‑in, not analytics.
Contact
Privacy questions and data requests: [email protected]. Other help: [email protected]. Reporting abuse: [email protected]. You can also reach us through the Support page or Discord.
EF‑Map is built and run by one player, Lacal (see About). This policy may be updated; the date above reflects the latest change. Rules for shared tribe content are covered separately by the Tribe Marks & User-Generated Content Policy.