Captomatic Falcon for Android - Privacy Policy

Last updated: 16 October 2026

This policy covers the Captomatic Falcon Android app (com.captomatic.falcon).

1. Who we are

Captomatic SIA, registration No. 40203140085, Mūkusalas iela 29b, Rīga, Latvia ("Captomatic", "we"). Contact: [email protected]

2. Data and purposes

Falcon turns a business-operated Android device into a capture camera. The operator chooses the receiving endpoint: Captomatic's hosted service, an on-premises installation or another compatible system. The app has no user accounts.

Data sent to the registered endpoint	Purpose
Photos and videos from the device or a USB camera, with audio unless disabled	Capture and deliver media
Face and facial-feature positions, detection confidence and identifiers within a video, when face detection is enabled	Select capture moments
Device and registration identifiers	Authenticate the device
Device status, logs and live snapshots	Monitor and control the device

Face detection uses the built-in camera when enabled by the endpoint. It does not identify people; the metadata follows the retention rules for its video. Bluetooth is used for an optional trigger button.

3. Recipients and responsibility

Captured data is sent to the registered endpoint using TLS. Captomatic receives it when the device is registered with its hosted service. The business operating the device is responsible for lawful capture, notices and its choice of endpoint.

For hosted processing, Captomatic acts on the Customer's instructions under the Data Processing Agreement ("DPA"). Captomatic's own account, support and technical processing is described in the Privacy Policy. Direct requests about captured content to the business operating the device.

Registration can use Google's code scanner in Google Play services. It returns the code content to the app; Google may receive scanner usage and diagnostic data under Google's privacy policy.

For discovery before registration, the app broadcasts its device identifier, local IP address, device type and app version unencrypted on the local network.

4. Storage and deletion

Media is held in the app's local storage pending delivery. The endpoint selects:

• Full upload: files are deleted locally after confirmed upload.
• On-demand: requested files are deleted locally after confirmed upload; unrequested files expire after the period set by the endpoint.

If the endpoint is unreachable, media remains pending without automatic expiry. The operator can remove it using the app's storage cleanup function or by uninstalling the app. The operator controls physical access to the device.

Retention at the receiving endpoint follows the business's arrangements with that endpoint; hosted retention is described in the DPA.