← Back to TAKIP

Privacy

Privacy, in plain words

TAKIP 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.

An account is optional

The map opens without one. An account keeps your email and sign-in details, and you can download or delete everything it holds from Account settings.

Usage data, to make TAKIP better

We count how long the map is open, which tools and layers get used and where it is used from, to improve TAKIP and build better tools. It stays on our server, with no analytics company involved. The free plans show a few Google ads, and Google sets its own cookies for them; Pro has none.

Your things stay with you

Your settings, history and keys are kept in your own browser, where you can see them and clear them. Not on our servers.

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.
  • We do not keep a record of what you search, look up or type. We do keep the address you use the map from, and the town it points to, to see where TAKIP is used.
  • We count map time, which tools and layers are in use and which actions people take (a search, a route), per account or per browser, to see what helps and improve it. What we measure below says exactly what.
  • If you report an issue, we keep your message, a snapshot of your map view and your browser’s details, tied to your account if you are signed in. Deleting the account deletes its reports.
  • The site reaches you through Cloudflare, which carries the connection between your browser and our server, as it does for much of the web.
  • The free plans show a few ads from Google, never on the map. Google may use cookies to choose and measure them. Pro shows none.

What stays on your device

These are kept in your browser’s own storage on this device. We receive one only when a feature needs it, like your AI key for a TI request, or the visitor id that goes with the map’s minute count. Clearing this site’s data in your browser settings removes them all.

Your AI key for TIKept for this browser tab only, and gone when you close it, unless you tick “Remember on this device”.
Your TI 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 TI 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, which layers are switched on, 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 you last waved off the ad blocker noteSo it asks at most once a day.
A random visitor idSent with the map’s once-a-minute usage count, and once when you open one of the public pages (see What we measure). It is a random number, not your name; clearing this site’s data replaces it with a new one.

What we measure, and why

We use this to see which tools people rely on and which go unused, so we can improve TAKIP and build better tools. It stays on our own server: it is not shared with the ad network or with any analytics company.

  • Map time. While the map is open and on screen, it tells our server once a minute. That minute counts toward the day’s map time, and is noted against the view (map, space, history or replay), the open panel, the data layers switched on and their sections (air, sea and so on), any open window such as a camera, and whether it is a phone. Not where you look on the map, what you search or what you type.
  • Reading the pages. Opening one of the public pages, such as a city, a layer or a guide, counts one view: which page, in which language, the site that sent you, and the random visitor id this browser keeps. It spends none of your map time. If you then open the map, the first page you read is noted as where you landed.
  • Actions. We count what people do by name: a search run, a route planned, a camera opened, a recon lookup by kind (email, domain…). Never the words, places, addresses or names themselves.
  • Signed out, those minutes are tied to the random visitor id this browser keeps, along with the browser’s name, the site that first sent you here, the page you landed on, and the address you connect from with the town and country it points to. Clearing this site’s data starts a new id.
  • Signed in, they are tied to your account, with the addresses you use the map from and where they point to, and the browser’s visitor id is linked to it. Each sign-in is recorded with its time, address and browser.
  • Your location, when you use it. If you use your location on the map (Your location in search, Use my location, or navigation), we note the position your browser gives, as precisely as it gives it, and the town it is in. While navigating that is at most one position a minute. We never ask for your location just to note it.
  • Where an address points to is looked up on our own server in a copy of DB-IP’s free database, so the address isn’t sent anywhere for it. It is a rough guess, usually the right country and a nearby town.
  • How long: all of this, sign-ins included, is kept for 90 days and then deleted. Counts of API requests, which plan limits rely on, are kept for up to 400 days (35 for visitors).
  • Yours to take or delete: your account’s download includes all of it, and deleting the account deletes it, with the browsers linked to it.

When we reach out to other services

TAKIP does not keep a database of intelligence of its own: it asks public services in real time. 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 used only to place the map (the place we keep for usage counts is looked up separately, see What we measure), 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
  • DB-IP (db-ip.com) · nothing is sent: a copy of its IP-to-town database on our server places the address the map is used from (IP geolocation by DB-IP, CC BY 4.0)
  • OpenFreeMap (tiles.openfreemap.org) · the map tiles, map symbols and label typefaces for the part of the world in view
  • CARTO (basemaps.cartocdn.com) · the map tiles instead, only if you pick CARTO as the base map
  • Esri (server.arcgisonline.com) · satellite imagery, only when you switch to the satellite view
  • Wikipedia · the name and position of a place you click on the map, asked from our server, so Wikipedia never sees you
  • 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, 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.

Using TI, on your own AI key

TI runs on the AI provider and key you choose. When you start a prediction, talk to TI 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 TI Assist uses your browser’s own speech recognition (in Chrome and Edge, a Google or Microsoft service); we only ever receive the words. Talking with TI live (OpenAI engines only) sends your voice straight from your browser to OpenAI on your own key: our server uses the key once to open a short session and keeps neither the key nor the audio.

Which services, exactly
  • The provider you choose · OpenAI, Anthropic, Google, OpenRouter, Groq, DeepSeek, xAI, Mistral or Alibaba Cloud: your key and your request. With local models, the request goes to a model server the site’s owner runs, and to no one else
  • 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
  • Photon and Nominatim (OpenStreetMap) · a place name, when you search for one or TI looks one up; and, to name the town of a location you used, a point rounded to about 10 km, asked from our server
  • OpenStreetMap Overpass · a point and a kind of place (dams, airports…), when TI looks up what is mapped near it
  • Open-Meteo · a point, when TI reads the weather there

Seeing ads, on the free plans

A small ad sits under some sidebar panels and in the docs; the map, TI and the tools you are working in never carry one, and Pro shows none at all. The ads come from Google AdSense: your browser loads them from Google, which sees your IP address and the page you are on. Google and its partners use cookies to show ads based on your visits to this and other sites, to cap how often you see one and to count clicks. Visitors in Europe and the UK are asked first, in Google's consent message, and can say no. If an ad blocker stops them, a note asks, at most once a day, whether you would let them through; nothing stops working either way.

How Google uses what it learns here: policies.google.com/technologies/partner-sites.

Which services, exactly
  • Google AdSense (googlesyndication.com, doubleclick.net) · your IP address, the page, and its own cookies, to choose, show and count ads

AI briefings and token scans

The briefing, analysis and overview buttons send the feed headlines they summarise to Google Gemini, on this site’s own key. A DonBot token scan opens DigitalDon’s scanner in a sealed frame, which receives the token you scan.

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. TI 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.
  • Delete your account from Account settings: choose Delete account, and we email you a link; opening it in a browser signed in to that account deletes the account and everything it holds, including sign-ins through Google, Facebook or GitHub.
  • Turn off personalised ads in Google's My Ad Center, or decline in the consent message; you then see ads that do not depend on your history.
  • 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: map layers, cameras and AI features reach out only when you switch them on or use them.
  • Run your own copy: TAKIP is open source, so you can host it yourself and decide who operates it.

Questions?

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

Open an issue on GitHub

Last checked against the code on October 19, 2026. When a feature changes what it shares, this page changes with it. Terms of use