Dashboard, public API, Deep Dive, and local Workspace need no identity.
Privacy, without guesswork.
IntelMap provides a public OSINT dashboard, API, and local Workspace without requiring an account. Optional IntelMap Plus provides a private profile secured by a generated sign-in key. IntelMap does not sell visitor data.
Watch zones and dashboard layouts stay in your browser.
Short-lived pseudonymous records power abuse controls and rankings.
Advertising and behavioral analytics are currently disabled.
What this notice covers
This notice covers intelmap.watch, its public API, signal dossiers, archive, dashboard, browser notification features, IntelMap Plus, synchronized workspaces, and billing controls. “IntelMap” means the operator of intelmap.watch. Contact: [email protected].
Data IntelMap receives
IP address, user agent, requested URL, referrer, time, and response details may appear in web-server and security logs. Used to deliver requests, diagnose failures, rate-limit abuse, and protect service.
Opening a signal records signal ID, time, and a salted pseudonymous signature derived from IP address and user agent. Used for duplicate suppression and “Most watched” rankings. Raw IP addresses are not stored in popularity database.
A report stores signal ID, report type, message, time, status, and salted reporter signature. Reports are private. Do not include sensitive personal information in message.
Account-free API calls receive same ordinary request logging and abuse controls as site traffic. API responses do not create a visitor profile.
If you enroll, IntelMap stores encrypted email address, keyed address hash, selected language, confirmation status, delivery timestamps, and unsubscribe status. Subscription requires CAPTCHA, explicit consent, and email confirmation.
CAPTCHA challenges are signed and short-lived. Hashed network and challenge records prevent replay, brute force, and confirmation-email abuse. CAPTCHA answer is not retained.
Optional accounts store an opaque account UUID, hashed account credential, hashed browser sessions, device class, state timestamps, security events, entitlement state, API-token metadata, and workspaces you explicitly save. Raw account, session, and API tokens are not stored.
Authenticated API calls store account and token IDs, time, method, endpoint path without query data, response status, duration, coarse client type, and a pseudonymous client signature. Raw IP addresses, user-agent strings, bearer tokens, request parameters, and response bodies are not stored in Plus API telemetry.
Saved boards, immutable revisions, mutation receipts, storage quota, and scoped API usage counters remain associated with opaque account UUID. Workspace content is never included in aggregate telemetry.
If enabled for your Plus profile, saved rules, revisions, source references, evaluation traces, triggers, acknowledgements, delivery settings, inbox items, and delivery outcomes stay linked to your account. Alert email is optional and requires separate address confirmation. Browser notices require browser permission.
When paid checkout opens, IntelMap stores encrypted PayPal subscription reference, plan, provider status, renewal time, and immutable entitlement history. PayPal receives and controls payer, payment-source, tax, dispute, and transaction records. IntelMap never receives raw card details.
- Legal name, display name, username, or recovery email for IntelMap Plus
- Email address unless you request daily briefing or separately confirm alert-email delivery
- Raw card, bank, or PayPal login credentials
- Contact list, microphone, camera, or browser geolocation
- Cross-site advertising profile
Cookies and local storage
IntelMap uses one first-party language cookie. Other interface preferences use browser storage. These values are not account-linked.
Theme, radar-motion preference, watch-zone names, center points, radii, dashboard layouts, saved Deep Dive views, and saved comparisons remain in browser local storage. JSON export leaves only through a download you start. Browser notifications require your permission. Daily email briefings are separate, optional, and require confirmed opt-in.
How long data remains
Short-lived records prevent repeated popularity counts.
Raw filter state and private export file remain until one-use download, expiry, or cleanup. Small exports stream directly and are not stored as export jobs.
Used to calculate recent reader-activity changes.
Removed after seven days without new activity.
Hashed abuse-control counters. *Expired entries clear during next rate-limit cleanup.
Retained for review, audit, recurring abuse detection, and dispute handling. *Eligible records clear during next report-storage maintenance.
Unconfirmed encrypted addresses expire after 24 hours. *Eligible rows clear during next subscription maintenance.
Encrypted address and delivery settings remain while briefing delivery is active.
Encrypted address is erased immediately. Keyed address hash remains to honor delivery stop and prevent accidental reactivation. Address is also erased after six consecutive delivery failures.
Retained while account exists. Owner can export and request permanent deletion. Account deletion immediately revokes credentials and sessions; background purge target is under 24 hours.
Saved rules and preferences remain until deleted or account deletion. Evaluations expire after 30 days; terminal delivery metadata after 90 days; triggers and activity after one year, subject to bounded maintenance and delivery references. Pending alert-email confirmations expire; delivery budgets clear after 45 days. Account deletion removes account-owned alert records.
Workspace retains at most 50 immutable revisions. Tombstones, idempotency receipts, and completed opaque deletion receipts expire after 30 days. Inactive service-limit counters expire after 48 hours.
Account-visible request records expire after 30 days and may expire sooner when account log volume reaches its safety cap.
Per-token endpoint counts, error counts, rate-limit counts, and timing totals remain for trend charts. Account deletion removes both detailed and aggregate API usage records.
IntelMap minimizes provider linkage after cancellation and deletion. PayPal retains transaction, tax, refund, dispute, and compliance records under its own legal obligations.
Rotated under infrastructure configuration. Retained only as needed for reliability, incident response, and security.
Public-source signals may remain in IntelMap archive for up to one year. This is intelligence-source retention, not visitor-tracking retention. Backups may preserve deleted records briefly until normal rotation completes.
External services
Your browser may connect to OpenFreeMap for map tiles and unpkg.com for map libraries. Standard connection data goes to those providers.
NASA GIBS is contacted by your browser only after Satellite mode is enabled.
Catalog metadata comes from IntelMap cache. Current still frames pass through restricted IntelMap cache. IntelMap does not record camera video or audio.
Opening a source, ATC, scanner, or radio link sends you to provider service. Provider receives ordinary browser connection data. Its privacy policy applies.
Hosting, network, DNS, and security providers may process request metadata required to deliver and protect service.
IntelMap translations run on operator-controlled infrastructure. Signal text is not sent to a consumer translation service.
Confirmed briefing delivery sends recipient address and message content to SMTP2GO. SMTP2GO processes delivery status and may retain operational delivery records under its privacy policy. IntelMap does not add tracking pixels; provider open and click tracking must remain disabled.
Paid IntelMap Plus checkout, when enabled, redirects to PayPal. PayPal processes payer identity and payment details under its own privacy notice. IntelMap receives subscription identifiers and status events, verifies them server-side, and stores encrypted provider references.
Use, disclosure, and legal basis
Operational data is used only to provide service, synchronize explicitly saved workspaces, enforce quotas, verify entitlements, measure current reader interest, prevent duplicate counts, respond to reports, diagnose faults, and protect infrastructure. Where law requires a legal basis, these uses rely on IntelMap’s legitimate interests in operating and securing service or performance of requested Plus service. Browser notifications and daily email delivery rely on explicit permission. Email delivery starts only after confirmation.
IntelMap does not sell visitor personal data. It does not disclose visitor data for cross-context behavioral advertising. Data may be disclosed to infrastructure processors, when required by valid law, or when reasonably necessary to protect users, service, or legal rights.
Safeguards
Controls include HTTPS, restrictive browser security headers, same-origin checks, request limits, private server-side storage, and salted pseudonymous identifiers. No system is risk-free. IntelMap limits collection and retention to reduce impact if controls fail.
Your choices and rights
- Clear language cookie and local storage through browser settings.
- Reset dashboard layout and remove watch zones in interface.
- Disable notifications through browser or operating-system settings.
- Unsubscribe instantly from link in every daily briefing.
- Export Plus account data and permanently delete Plus account from account controls.
- Revoke individual Plus sessions and scoped API tokens.
- Do not enable optional satellite layers or follow external links.
- Request access, correction, deletion, restriction, or objection where applicable law provides those rights.
IntelMap cannot recover a lost Plus sign-in key or connect a Plus profile to a person without an active session or sufficient context. IntelMap will still review substantiated requests. You may also contact your local data-protection authority where applicable.
Questions and requests
For signal-specific corrections, use “Report this signal” on dossier. For privacy requests, include relevant URL, request type, and enough context to investigate. Do not send passwords, government IDs, or unrelated sensitive data.
Version 3.1 adds account-visible Plus API request telemetry, quota reporting, and stated telemetry retention. Material future changes will appear here with new effective date.