GuardLinkCam
Privacy policy
What stays on your device, what goes to your chosen services, and how to remove data.
Who is responsible
Kotov Andrii develops GuardLinkCam. Contact for privacy and data questions: Andreikotov@ukr.net. This policy describes the planned 1.0.0 release for iPhone, iPad and Mac and this website.
The app has no GuardLinkCam registration, ads, tracking or usage analytics. The developer does not operate a video backend or route your camera streams through a developer server. This does not mean all processing stays on your device: the cameras, servers and providers you choose receive connection data.
Data on your device
- Keychain: passwords, secret stream URLs, cookies, session keys, tokens and other connection secrets.
- Application Support: camera names and identifiers, addresses without secrets, layouts, ordering, primary cameras, visibility and sensor mappings.
- Memory and temporary files: video, audio, frames and playback data needed for viewing.
- Local cache: snapshots and silent recordings you create. Exporting or sharing happens through system tools when you choose to do so. Copies at the recipient or selected storage are governed by their settings.
The app does not sync connection secrets between your devices. Export files from the cache for long-term storage.
Data sent when you connect
| Connection | Recipient and information |
|---|---|
| Xiaomi | The embedded sign-in page belongs to Xiaomi and may use cookies and CAPTCHA/2FA. The app obtains cookies and authorized session data to exchange with Xiaomi for camera lists, keys, live streams and microSD access. Xiaomi services receive requests, account/camera identifiers, session data and the network address. |
| Direct Ajax | Ajax receives your email, password hash, TOTP code if required, session information and a client UUID. The app receives the inventory, states and events your account can access for selected mappings. |
| Milestone / Husky | Your configured Mobile Server receives requests, login/session information, camera selections and requests for live video, archive, journal and available audio. |
| RTSP, HLS, ONVIF | The configured camera or server receives requests, the network address and authentication information needed to open streams and retrieve profiles. |
| Your optional Bridge | Only when configured by you: your chosen Bridge may receive your Ajax password, TOTP, session and mappings. With a separately configured APNs setup it also receives a push token and notification mappings. You or its operator control this server; the developer does not provide it. The standard release has no background push. |
Cameras and providers may use their own servers or relays and retain account, device, network log, video or event data under their own policies. Those policies govern such data, including the Xiaomi Account Privacy Policy and policies shown by your chosen service. Access does not constitute a promise of end-to-end encryption.
Retention and deletion
Local settings and secrets remain for future connections until you remove them. Use the app controls to disconnect accounts and delete local data. Do this before uninstalling: uninstalling the app may leave Keychain items. If you have already uninstalled, contact support for instructions for your platform.
Removing a GuardLinkCam integration does not delete the provider account, camera recordings, server archive, exported files or Bridge data. Remove those separately with their operator and revoke provider sessions when appropriate. Provider retention follows their policies.
Permissions and security
Local network access is used to reach cameras and servers on that network. The app uses system Keychain and the protections available in the selected protocol. Transport protection depends on the camera and service; local protocols may transfer data without encryption. Use a trusted network, a supported HTTPS/secure endpoint and a separate account with limited permissions.
Background event delivery is not enabled in the standard release. Sensor mapping, red borders and local sounds work while the app is active.
Support email and this website
If you email support, the developer and email provider receive your email address, message and files you choose to attach. They are used to respond and address the request and kept for as long as necessary for that purpose and applicable obligations. Do not send passwords, tokens, TOTP codes or unnecessary footage of people; redact secrets from screenshots.
The website uses no external fonts, analytics, advertising scripts, forms or developer-set cookies. Hosting and delivery infrastructure may receive IP addresses, date/time, URL and technical request information, and keep access logs to operate and protect the site. External links open websites governed by their own policies.
Requests and policy updates
For access, correction or deletion of data held by the developer, or other requests under applicable law, email Andreikotov@ukr.net. Describe your request without including access secrets. Available rights and exceptions depend on applicable law. Also contact the relevant operator for camera, provider or private Bridge data: the developer may have no access to it.
Updates are published here with a new date. Information about material processing changes will be updated before the change is applied. Fictional demonstration scenes are separate from real connections and contain no footage from your cameras.