Privacy & access
seecop is built so visitors get the full picture without ever holding the keys to it. This page describes exactly who sees what, and why the model matters.
The lab's keys, not yours
Every feed and lookup runs on credentials the operator holds. Visitors never enter, see, or manage an API key. That keeps costs and rate limits on the operator's side and means one signed-in link gives you a fully paid-up picture — not a shell that asks you to bring your own keys.
Sign-in
Access is gated by an identity provider in front of the site. You sign in with your email address and a one-time PIN; there is no password and no cloud-provider account to create. Only allow-listed addresses get in. See Getting started for the steps.
Who sees what
| Surface | Signed-in visitor | Operator (local) |
|---|---|---|
| Map layers & live telemetry | Yes | Yes |
| AI assistant | Yes | Yes |
| API key values & admin settings | No | Yes |
| Server config, secrets, tokens | No | Yes |
| Shell, desktop, file access | No | Yes |
The public surface exposes the map and the assistant. Requests for key values, admin actions, or server internals are refused for signed-in visitors and only served to the operator working locally.
Local AI by default
The assistant runs on a model hosted on the lab's own hardware. Your questions and the lookups they trigger stay within the lab rather than being forwarded to an external LLM provider. That is a deliberate privacy choice, not just a cost one.
Polite collection
seecop reads public, third-party feeds. Lookups take a single target at a time, identify themselves to each upstream service, and cache results briefly to avoid hammering anyone. It does not run intrusive scans. Use it for authorized and lab purposes only.