OliMat Data Explorerby OliMat Systems
Home / Privacy
Privacy policy

Your data is processed locally.

OliMat Data Explorer requires no account and does not transmit your files to OliMat servers.

1. Scope

This policy applies to the OliMat Data Explorer desktop application and the olimat.systems portal. Last updated: July 24, 2026. In case of doubt, the Spanish version of this policy prevails.

2. Data that stays on your machine

Opened files, queries, results, SQL favorites, recent list, dictionary and preferences are processed or stored on the user's machine. OliMat does not receive them.

3. Network connections

The application has no analytics telemetry and never sends the content of your files. These are the only connections it may make, and every server involved logs — like any web server — ordinary technical data (IP address, date, requested URL and User-Agent):

Basemaps: when using online maps, tiles are requested from the chosen provider (OpenStreetMap, OpenTopoMap, CyclOSM or Humanitarian OSM Team), which receives the technical coordinates of the visible tiles under its own policy. Already-requested tiles are stored in a local cache (in line with OpenStreetMap's policy, which requires caching and forbids bulk or anticipatory downloads — the app performs none) and reused offline as well.

Update check (optional, disabled by default): it only runs if you allow it in the first-run prompt or enable it under Help ▸ Check for updates on startup. If enabled, once a week it requests version.json on olimat.systems to announce new versions; only the application identifier and its version (User-Agent) plus your IP address travel, and the server's access statistics allow estimating active installations. You can disable it any time and the application works the same without it.

DuckDB extensions: the required extensions (Excel, spatial, encodings) ship with the installation. Only if one were missing and a feature required it would the engine try to download it from the official extensions.duckdb.org repository; without a connection, that feature shows an error and the rest of the app keeps working.

Oracle: connections to Oracle databases are initiated and configured by the user with their own credentials; the password is never stored.

4. Web portal

The static portal needs no tracking cookies. If analytics, forms or payments are added in the future, this policy will be updated before enabling them, explaining what information is processed.