Privacy

Two separate things: what the ModelSaar gateway does with your requests on your machine, and what this website does when you visit it.

The gateway

ModelSaar runs where you install it. By default it binds to 127.0.0.1, authenticates every request with keys it generated into files with mode 600, and talks only to the backend addresses in your configuration. It sends no telemetry, keeps no response cache and logs no prompts; decision records hold metadata (task labels, token counts, capability flags, outcome) and at most a short, redacted upstream error excerpt.

• Local-only by default. security.locality_mode: local_only makes only deployments with locality local eligible or advertised. Ollama's cloud-forwarded models are detected and excluded; a generic endpoint's locality is whatever you declared, recorded as a trust assumption. Nothing derived from a request leaves the gateway before policy filtering: tokenizer counts are requested only from deployments that already passed locality, enablement, health and capability filters, and the optional classifier must be a local deployment unless you opt in twice.
• Remote media is never fetched. Image URLs must be inline data: URLs; unknown content types are rejected before dispatch.
• No model-generated code is executed by the gateway. The evaluation harness runs model-written Python only inside an isolation sandbox, or skips the task.
• Exposure beyond your machine is explicit. Binding to a LAN address requires security.allow_lan: true; keys then travel over plain HTTP, so put TLS or a private network (Tailscale, WireGuard) in front and never send the admin key off the host.
• What it cannot prove. That an opaque backend is truly local, or what your backend does with the request after it arrives. ModelSaar records the evidence it has (locality_evidence in the status output) and nothing more.

The full defaults table, with the code path for each guarantee, is in Privacy and security of the gateway.

This website

modelsaar.com is a static site. It uses no analytics scripts, no cookies, no forms, no accounts, no newsletter and no third-party embeds; its fonts are served from this site. The hosting provider keeps standard access logs (IP address, user agent, requested URL, time) for operating the service — see the hosting section below for who that is. We do not combine those logs with anything else. The install.sh script served here downloads the ModelSaar source from GitHub at a pinned commit; GitHub's own privacy terms apply to that request.

If this changes (for example, if we add privacy-respecting aggregate analytics), this page will say so and describe exactly what is collected and for how long.

Hosting

The site is published as static files from the project repository through GitHub Pages (GitHub, Inc.), whose servers keep the access logs described above. The domain's DNS is managed at Cloudflare; no Cloudflare proxy or analytics feature is enabled for this site.

Security reports

Report a vulnerability in the gateway as described in the security policy. Please do not file security reports as public issues.