EF‑Map Privacy Policy

Last updated: 2026-08-09

Summary

EF‑Map aims to be privacy‑first. The majority of our telemetry is anonymous aggregate metrics only (see our transparency report). However, if you choose to link accounts or purchase a subscription, we store minimal account metadata to operate authentication and billing features. This page explains what we collect, why, and how to request access or deletion.

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 Web Workers. Your game log files are never uploaded to EF‑Map servers.
Local storage only: Parsed data (mining stats, combat events, travel history) is stored in your browser's IndexedDB. This data remains on your device.
No server transmission: We do not collect, store, or have access to your game logs or the analytics derived from them, unless you explicitly opt in to publish a leaderboard entry, in which case the published summary stats are stored under your wallet address.
User control: You can clear all locally stored log data at any time through your browser's settings or the app's data management options.

Future optional sharing: we may introduce further optional features such as opt‑in leaderboards or shared analytics. 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.

Data We May Store

If you choose to sign in or subscribe, 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) and optional display name if you link your Discord account via OAuth. Used only to show linked identity and ease login.
Subscription & billing identifiers: Stripe customer identifier and subscription status metadata (we do NOT store full payment card details). Used to manage access to paid features and quotas.
Internal customer number: A small integer we assign to manage subscription records and support workflows. This is an internal reference only and not published publicly.
Activity logs for subscription events: Webhook timestamps and minimal event metadata (created/updated/cancelled) used for troubleshooting and reconciliations.

Why We Store This

Account and subscription metadata enable user sign‑in, persist your subscription entitlements and quotas, and allow us to manage customer support and billing reconciliation. Wallet/address linkage is used for authentication, tribe membership checks, and optional encrypted tribe workflows.

Third Parties & Processors

We use third parties for authentication and payments:

Stripe — payment processing. We receive 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.

Storage & Retention

We retain the minimal account & subscription metadata for the time necessary to provide the service and to meet legal/billing obligations. For billing records (invoices, subscription history) we retain data for up to 7 years to meet bookkeeping requirements. Aggregate anonymous metrics are retained and rolled up as described in our analytics documentation.

Security

We protect data in transit using TLS. Access to internal project data stores is limited to a small number of operators. We do not request or store raw payment card data; Stripe handles payment credentials for legacy subscriptions. Tribe 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. Personal map notes never leave your browser.

Your Rights

You may request access, correction, or deletion of the account metadata we store. To make a request, email [email protected] (or [email protected] / [email protected] if privacy@ is not available). Include your wallet address or the email used for support requests and we will follow up with verification steps. We aim to respond within 30 days for routine requests.

Overlay Helper Note

The desktop overlay helper processes almost all data locally and does not collect personal information by default. If you use the helper and also choose to link accounts or subscribe, the helper will, by your explicit opt‑in action, communicate the minimal routing or account identifiers required to ef‑map.com (for example, to authenticate or retrieve subscription status). See the overlay helper distribution privacy file for the helper‑side statement.

Analytics

Our analytics are privacy‑first and aggregate‑only. They do not contain IP addresses, device IDs, or other personal identifiers. See the blog post Transparency Report for full details of the event model.

Blog articles carry no analytics script at all. Article views are counted by our server as it serves each page, 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.

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 in Offline Mode.

Cookies & Local Storage

We use browser localStorage for UI preferences (theme, display settings) and for content you choose to save locally, such as recorded camera flights. These stay in your browser and are never uploaded.
IndexedDB stores your parsed log data locally on your device.
No tracking cookies are used.

Contact

Questions, data requests, or concerns: [email protected] (fallback: [email protected] or [email protected]). You can also reach us through the Support page or Discord.

EF‑Map is operated by the EF‑Map Project. 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.