GovCIO COMMANDLINK iOS Privacy Policy
Last Modified: July 28, 2026 Effective Date: July 28, 2026 Platform: iOS
Changelog
- 2026-07-28: Initial iOS policy version created from current Voyager legal policy language.
- 2026-07-28: Expanded with iOS app-specific disclosures (passkeys, Firebase, LiveKit, operational data categories, and international transfer notes).
Policy Scope
This policy applies to GovCIO COMMANDLINK for iOS and related supporting services.
GovCIO ("GovCIO," "GovCIO COMMANDLINK," "we," or "us") is committed to protecting the privacy of personally identifiable information collected through the service.
Shared Baseline
This platform-specific policy is based on the shared language in:
Unless otherwise stated below, shared sections govern:
- Core policy-change language
- Data retention and security baseline
- Core user-rights baseline
- Children's privacy baseline
- Regional disclosure baseline
Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect changes in practices, technology, legal requirements, or other factors.
If material changes are made, we will publish an updated policy and effective date.
1. Information We Collect
1.1 Account and Authentication Information
- Username and account identifiers.
- Authentication data needed to sign in.
- Multi-factor authentication data.
- Passkey-related data needed for WebAuthn/passkey sign-in and device registration.
1.2 Device and Technical Information
- Device identifiers used for registration and app functionality.
- iOS version, app version, and related technical metadata.
- Network and diagnostic metadata.
- Error and operational logs.
1.3 Location Information
- Precise location data when enabled by user permission and device settings.
- Location history and map-related updates used for tracking and operational workflows.
1.4 User-Generated and Operational Data
- Alerts, status updates, event reports, and related metadata.
- Map and unit-related data needed for app operation.
- App configuration preferences and settings stored locally on the device.
1.5 Push Notification Data
- Push tokens and notification metadata needed to deliver alerts and service messages.
1.6 Support Communications
- Information submitted in support requests, including message content and attachments.
2. How We Use Information
We use information to:
- Authenticate users and secure access to the app.
- Register and manage devices with backend services.
- Provide mapping, tracking, alerting, and related operational features.
- Deliver push notifications and in-app status updates.
- Support safety and monitoring capabilities.
- Troubleshoot issues, monitor stability, and improve reliability.
- Maintain security, detect misuse, and prevent unauthorized access.
- Respond to support requests and user feedback.
- Comply with legal obligations.
3. Legal Bases for Processing (Where Applicable)
Depending on jurisdiction, processing may be based on:
- Performance of a contract.
- Legitimate interests (for example, security, diagnostics, and reliability improvements).
- Consent (for example, location permissions and notifications).
- Legal obligations.
4. Sharing and Disclosure of Information
GovCIO does not sell personal information.
Information may be shared with:
- Service providers and infrastructure partners that host or process data on our behalf.
- Authentication, messaging, and notification providers needed for app functionality.
- Realtime communications providers (including LiveKit) and cloud-messaging providers (including Firebase) to support voice, presence, and notification features.
- Analytics, logging, or monitoring providers used for reliability and security.
- Legal authorities when required by law, regulation, subpoena, or legal process.
- Successors in connection with merger, acquisition, financing, or asset transfer.
We require service providers to protect information and use it only for authorized purposes.
5. Third-Party Services and Integrations
We use third-party providers to support core app features.
5.1 Firebase
- Purpose: Cloud messaging (FCM) for push notifications and crash reporting (Crashlytics).
- Data types: Push notification tokens, device and app metadata, message delivery metadata, and crash/diagnostic data.
- Privacy: https://policies.google.com/privacy and https://firebase.google.com/support/privacy-and-security/privacy
5.2 LiveKit
- Purpose: Real-time voice communication and channel presence features.
- Data types: Device and user identifiers, channel/room metadata, session and connectivity metadata, and voice transport metadata.
- Privacy: https://livekit.com/legal/privacy-policy
6. Data Retention
Refer to the shared baseline section:
- Data Retention
iOS-specific retention behavior may vary by enabled feature set and customer deployment context.
7. Data Security
Refer to the shared baseline section:
- Data Security
iOS-specific note:
- Device-level security controls and platform permissions are used to support protection of locally processed or stored data.
8. Your Choices
Users can:
- Disable location access in iOS Settings.
- Disable notifications in iOS Settings.
- Manage sign-in methods (including passkeys) where available.
- Manage app-specific preferences and settings where available.
Disabling certain permissions or settings may limit app functionality.
9. Your Privacy Rights
Refer to the shared baseline section:
- User Choices and Rights
10. Children's Privacy
Refer to the shared baseline section:
- Children's Privacy
11. U.S. State Privacy Disclosures
Refer to the shared baseline section:
- U.S. State Privacy Disclosures
Platform-specific details are provided where required by customer deployment context and legal review.
12. Contact
COMMANDLINK Support
- Email: CommandLinkSupport@GovCIO.com
- Phone: 1-877-857-1100