Last updated: 2025‑11‑19
EF‑Map aims to be privacy‑first. The majority of our telemetry is anonymous aggregate metrics only (see the Usage Stats page and the blog post about privacy‑first analytics). 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.
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.
We use third parties for authentication and payments:
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.
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 tribe encryption workflows, we rely on user wallet signatures and keys; encrypted payloads are handled per-feature documentation.
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.
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.
Our analytics are privacy‑first and aggregate-only. They do not contain IP addresses, device IDs, or other personal identifiers. See the blog post Privacy‑First Analytics for full details of the event model.
Questions, data requests, or concerns: [email protected] (fallback: [email protected] or [email protected]).
EF‑Map is operated by the EF‑Map Project. This policy may be updated; the page date above reflects the latest change.