← NatusAI OSINT

PRIVACY

Privacy, in plain words

NatusAI OSINT is a window onto public information: flights, ships, cameras, news, markets and more, gathered onto one map. We built it so you can use it without telling us who you are. This page says what that means in practice, and, where a feature needs to ask another service for something, exactly which one.

No account required

You can explore the map without signing up or logging in. Your requests still reach our hosting infrastructure and the services described below.

Self-hosted analytics

We use cookie-free Umami to measure page visits on our own analytics service. Only valid campaign labels in utm_source, utm_medium, utm_campaign and utm_content are included; other page query parameters and fragments are excluded. We do not send custom investigation events.

Browser-stored preferences

Your settings, recent-history list and saved AI key stay in your browser. Requests and temporary shared predictions use our server as described below.

Your AI key is yours

Used only for the request you make, passed straight to the provider you chose, and never stored on our servers or written to a log.

The short version

  • Most of what you see comes from public sources. To show it, our server asks those sources, much as your browser would.
  • When you look something up, the question goes to the service that holds the answer, and only for that lookup.
  • Your preferences and history live in your browser. Clearing this site’s data in your browser removes all of it.
  • Features that use AI run on the key and provider you choose, and we pass your request straight through.
  • The application uses your connection address for rate limiting and approximate location. Hosting and third-party services also process ordinary network requests.
  • This instance runs on OVH through Coolify. Self-hosted Umami records page visits at analytics.natusai.com. It receives only lowercase campaign labels (letters, numbers, underscores and hyphens, at most 64 characters each) from utm_source, utm_medium, utm_campaign and utm_content; other page query parameters and fragments are excluded.

What stays on your device

These are kept in your browser’s own storage on this device. We never receive them unless a feature you use needs one, like your AI key for a NatusAI request. Clearing this site’s data in your browser settings removes them all.

Your AI key for NatusAIKept for this browser tab only, and gone when you close it, unless you tick “Remember on this device”.
Your NatusAI settings and recent predictionsWhich provider and model you use, whether replies are read aloud, and a list of your last 25 predictions so you can reopen them.
Your NatusAI Assist conversationFor this tab only, so a reload does not lose it.
Areas you draw on the mapSo a refresh does not wipe your work.
How the map looksYour Style Studio colours and the last city the map opened on.
Your market watchlist and recent fingerprint searchesSo they are there next time. The search list can be cleared from the search panel.

When we reach out to other services

NatusAI OSINT asks public services for information and caches some published feeds and lists. Here is what that involves, by what you are doing. Each service treats what it receives under its own privacy policy.

Opening the map

So the map can open over your part of the world, our server asks an IP location service roughly where your connection is. It is a city-level guess, it is not stored, and if it cannot tell, the map opens on a well-covered city instead. The map itself (its tiles, the satellite view when you switch to it, and the typefaces) loads from the services that draw it, as with any website that shows a map.
Which services, exactly
  • ipapi.co, then freeipapi.com, then ip-api.com · your connection’s IP address, asked from our server, to place the map
  • CARTO (basemaps.cartocdn.com) · the map tiles for the part of the world in view
  • Esri (server.arcgisonline.com) · satellite imagery, only when you switch to the satellite view
  • Wikipedia and Wikidata (en.wikipedia.org, www.wikidata.org) · what you type in the place search, asked from your browser, when the configured or shared place search cannot answer. The place under your cursor or that you right-click is named from a built-in list, and nothing is sent for it
  • osirisai.live · the default shared place-search provider: typed place queries are sent from this server unless a separate geocoder or another shared search is configured
  • Google Fonts · the typefaces the site uses

Looking something up

The RECON tools answer by asking the public service that holds the answer, from our server. That service sees the email, domain, address or name you looked up, but not who you are. Two checks never leave our server at all: phone numbers are read with a library that runs here, and sanctions searches run against a copy of the published list we keep.
Which services, exactly
  • XposedOrNot · an email address, for breach checks
  • Hudson Rock · an email or domain, for infostealer checks
  • Shodan (InternetDB, or its API when configured), RIPE, RDAP, Google Public DNS, crt.sh · a host, address or domain, for infrastructure, ownership, DNS and certificate lookups
  • ip-api.com, Tor Project, AlienVault OTX · an IP address or indicator, for location and threat checks
  • CIRCL and MITRE · a CVE number, for vulnerability details
  • GitHub, and a dozen public profile sites · a username, to see where it is in use
  • maclookup.app · a hardware (MAC) address, for its maker
  • mempool.space, Blockscout, the public Solana network, CoinGecko · a wallet address, and prices to value it

Watching cameras and live alerts

Camera pictures and streams come straight from whoever runs each camera (a road authority, a harbour, a city) or from the video service it uses, such as YouTube, which may set its own cookies when a video plays. A few alerts carry photos that load from Telegram when you open them, and the Live Clouds layer loads its imagery from NOAA while it is switched on. In each case the service sees an ordinary request from your browser, as for any picture on the web.

Analysing camera pictures

AI Analyze detects objects in the browser using a model served by this site. Forecasts that use cameras run the detector on our server. If you choose Identify, cropped vehicle pictures and the camera label pass through our server to your selected vision-model provider using your own key.

Weather, transit and terrain

Wind data comes from NOAA through our server. Rain imagery loads in your browser from RainViewer. Transit positions come from operators’ feeds requested by our server for the map area. Terrain and cut-outs load public elevation and imagery tiles for the area you view.

Using NatusAI, on your own AI key

NatusAI runs on the AI provider and key you choose. When you start a prediction, talk to NatusAI Assist or check your key, your request goes from our server to that provider: your question and any data you add for a prediction, or the conversation and what is on the map for Assist. The provider sees our server’s address, not yours. Your key is used for that request and nothing else.

A prediction has its own link so it can be shared: anyone you give the link to can open it, and it is kept on our server for three hours after it finishes. The microphone in NatusAI Assist uses your browser’s own speech recognition (in Chrome and Edge, a Google or Microsoft service); we only ever receive the words.

Which services, exactly
  • The provider you choose · OpenAI, Anthropic, Google, OpenRouter, Groq, DeepSeek, xAI, Mistral or Alibaba Cloud: your key and your request
  • News publishers’ feeds, GDELT, Wikipedia · a few keywords from your question, to find the reporting and background a prediction reads; the articles found are then read from their publishers
  • Yahoo Finance · the ticker of a price your question is about, for its price history and its news
  • Polymarket and Manifold · a few keywords from your question, to find what prediction markets price it at; and, for the suggestions on the ask form, nothing about you at all
  • Wikipedia and Wikidata · a place name, when NatusAI Assist looks one up and the configured or shared place search cannot answer, asked from your browser

AI briefings and token scans

When the server’s Gemini key is configured, the briefing, analysis and overview buttons send the feed headlines they summarise to Google Gemini. A DonBot token scan opens DigitalDon’s scanner in a sealed frame, which receives the token you scan.

Self-hosted Umami analytics

This instance loads Umami from analytics.natusai.com to measure page visits. The service receives page paths, referrers and ordinary browser and device information. Only valid campaign labels in utm_source, utm_medium, utm_campaign and utm_content are included on the landing page view; other query parameters and fragments are removed. Referrer queries and fragments are also removed. The app respects Do Not Track and Global Privacy Control, and does not send custom investigation events, search text, AI keys or map coordinates to Umami.

Good to know

A lookup is a question to someone else

The service that answers a lookup sees what was asked. If what you are researching is sensitive, keep that in mind before you search.

Shared links are open

Anyone with a prediction’s link can open it while it is kept. Share it with the people you mean to.

AI is a starting point

Briefings and predictions are written by language models. NatusAI shows its sources so you can check them, and you should.

Scan only what you may

Scans are rate limited and kept away from private networks, but whether you may scan a system is between you and its owner.

Your choices

  • Clear everything by clearing this site’s data in your browser settings.
  • Keep your AI key to one session by leaving “Remember on this device” unticked; it is then forgotten when the tab closes.
  • Use only what you need: supported map layers start enabled. Turn off layers you do not need; opening camera streams or using AI can contact the services listed above.
  • Run your own copy: the underlying Osiris project is available under the MIT license, so you can host your own deployment.

Questions?

If something here is unclear, or you think we have missed something, tell us and we will put it right.

Last checked against the code on 15 November 2026. When a feature changes what it shares, this page changes with it.