OverviewLocationCamera dataStorage
Back to CamRadar

// LEGAL

Privacy Policy

Applies to CamRadar: Camera Map, published by Ngo Chi Thien

CamRadar: Camera Map

Last updated: August 3, 2026

01

Overview

This Privacy Policy applies to CamRadar: Camera Map ("CamRadar"), developed and published by Ngo Chi Thien. CamRadar is a community camera map for OpenStreetMap. This policy explains what location, camera, account and device data the app may access, why it is needed, where it is processed, and when it is shared with OpenStreetMap services.

02

Location Data

πŸ“

Foreground location

When you use Locate me, search an area, view nearby cameras or add a camera, CamRadar may access your precise or approximate device location. It uses this location to center the map, load nearby camera data, calculate distances and place a user-selected camera pin.

πŸ””

Optional background location

If you explicitly enable Background monitoring and grant the required system permission, CamRadar uses Android geofences to detect when you enter the alert radius of a known camera and send a local notification, including when the app is closed or not in use. Background monitoring can be disabled at any time in the app or system settings.

🌐

Map and camera requests

To load nearby camera data, CamRadar sends a map center and search radius to OpenStreetMap's Overpass API. Map tile requests may also reveal the approximate area being viewed to the tile provider. These requests are handled by the relevant OpenStreetMap services under their own policies.

03

Camera and OpenStreetMap Data

πŸ“·

Camera drafts

When you create a camera draft, CamRadar stores the camera name, type, coordinates, direction and sync status locally on your device so you can review and manage the draft before upload.

πŸ—ΊοΈ

User-approved contributions

If you sign in to OpenStreetMap and confirm a sync, the camera information you selected is sent to OpenStreetMap as a public map contribution. Public OSM data is governed by OpenStreetMap's own terms and privacy practices.

πŸ”

OpenStreetMap account

OpenStreetMap sign-in is optional. The OAuth access token and basic account identifier/name are stored on this device using platform secure storage and are used only to authenticate your requested OpenStreetMap sync.

04

Third-Party Services

CamRadar does not use advertising, analytics, Firebase or Supabase. It communicates with the following OpenStreetMap services to provide its core map and contribution features:

05

Local Storage, Security and Deletion

CamRadar stores camera cache, drafts, filters, alert preferences and notification state locally on your device. The OpenStreetMap OAuth token is stored using platform secure storage. CamRadar does not operate a backend that stores your personal profile or location history. You can remove local app data by clearing the app's storage or uninstalling the app. Camera contributions already uploaded to OpenStreetMap remain subject to OpenStreetMap's data and editing processes.

06

Children's Privacy

CamRadar is a general-audience map application and does not knowingly request personal information from children. Location and background monitoring permissions should only be enabled by a user who is authorized to grant them on the device. If you believe a child has provided personal information through CamRadar, please contact us.

07

Changes to This Policy

This policy applies to CamRadar: Camera Map. We may update it when CamRadar's data practices or legal requirements change. When we do, we will revise the "Last updated" date at the top of this page.

08

Contact

If you have any questions or concerns about this Privacy Policy, please get in touch:

thienngo.tech@gmail.com