EOTECH Logo

TAK Stack for Android and iOS

Shared Privacy Policy

This page is the public privacy policy for the TAK Stack mobile applications on Google Play and the App Store. It explains the shared workflows and the platform-specific permissions and device features used by each app.

Effective May 14, 2026

Shared across both apps

Account, MFA, and file workflows

Both TAK Stack apps use first-party EOTAK services for registration, login, multi-factor authentication, profile management, server selection, and authenticated file operations.

Android specific

ATAK, Bluetooth, and file handoff

The current Android build requests Bluetooth, fine location, and media or storage permissions on startup to support ATAK interoperability, Bluetooth device workflows, user-selected file access, local downloads, and package handoff where a downloaded APK workflow is enabled.

iOS specific

Bluetooth, Files, and export workflows

The iOS app uses Bluetooth and background Bluetooth declarations, user-initiated document selection, local downloads, and Files or share-sheet export flows needed for its hardware and file-management workflows.

1. Scope and service model

This Privacy Policy applies only to the TAK Stack mobile applications for Android and iOS published by EOTAK, a product line of EOTECH, LLC. Both apps primarily communicate with the first-party EOTAK backend at https://dashboard.eotak.com.

This page is the public privacy policy URL for both store listings. It covers the shared behavior of both apps and the platform-specific differences that affect permissions, device features, or how information leaves the device.

2. Information the TAK Stack apps process

  • Account and profile information: first name, last name, email address, password, user type, selected server, profile updates, password changes, and account deletion requests.
  • Authentication and MFA information: sign-in identifier, password, MFA codes, temporary login tokens, remember-device choices, preferred MFA method, and optional device tokens used during login flows.
  • Files and file metadata: file lists, file download requests, user-selected uploads, file names, MIME types, categories, descriptions, and related server identifiers required to upload, retrieve, or delete files.
  • Role-based operational data: when your organization uses admin or enrollment workflows, the apps transmit user, group, server, role, and enrollment-token information through the same first-party service.
  • Local session state: the apps store authentication tokens and related sign-in state on your device so you can remain signed in between sessions.

3. How we use that information

  • To create and manage user accounts, authenticate users, and complete multi-factor authentication.
  • To retrieve and update profile information, user preferences, server assignments, and account settings.
  • To upload, list, download, share, and delete files that are part of TAK Stack workflows.
  • To support device-related features such as Bluetooth workflows, ATAK interoperability on Android, and file import or export flows on both platforms.
  • To support role-based administrative, server-management, and enrollment features when those features are available to your account.
  • To respond to support, privacy, and deletion requests.

4. Shared behavior and platform-specific differences

Shared

  • Account creation, login, MFA, and profile management flows.
  • Authenticated server and library file workflows, including uploads and downloads.
  • Role-based user, group, server, and enrollment operations when enabled by your organization.

Android

  • The Android app requests Bluetooth, fine location, and media or legacy storage permissions on startup, with the exact permission set varying by Android version.
  • Those permissions support Bluetooth discovery or device operations, user-selected uploads, local downloads, and file handoff to other installed apps or the system viewer.
  • The app includes ATAK interoperability checks and launch flows for the installed ATAK application.
  • The app also supports package-install handoff when a downloaded APK workflow is enabled.

iOS

  • The iOS app uses Bluetooth and background Bluetooth capabilities for supported device workflows.
  • The app supports user-initiated document selection, local downloads, export to Files, and share-sheet handoff for downloaded content.
  • iOS requests location authorization from Bluetooth-related workflows when the iOS permission model requires it for device discovery.
  • The iOS app does not request photo-library permission; file access is limited to the document picker and Files or share-sheet export flows.

5. Third-party analytics, advertising, and external services

No embedded mobile advertising or analytics SDKs

TAK Stack does not include embedded third-party advertising SDKs or third-party mobile analytics and crash-reporting SDKs.

We do not sell personal information.

  • First-party backend: both apps primarily send account, MFA, profile, server, and file requests to EOTAK infrastructure at dashboard.eotak.com.
  • Enrollment QR rendering: when an admin or enrollment user generates an enrollment QR code, the mobile app sends the enrollment URL, including the invite code embedded in that URL, to api.qrserver.com to render the QR image.
  • Downloads and hosted assets: downloadable content is delivered through the backend and, for certain files or packages, through EOTAK-selected external file hosts that provide the requested file or package.
  • Legal and security disclosures: we may disclose information when required by law or when reasonably necessary to protect rights, safety, security, or the integrity of the service.

6. Bluetooth, location-related permissions, and device workflows

Both TAK Stack apps include Bluetooth-related device workflows. The Android app requests Bluetooth, fine location, and media or storage permissions on startup, while iOS requests Bluetooth and location access from device workflows where the operating system requires those prompts for Bluetooth discovery, pairing, or related operations.

These permissions support device workflows, not advertising, analytics, or always-on consumer location tracking. This policy covers those permission-backed workflows and the information they process.

7. Retention, deletion, and your choices

We retain information for as long as needed to operate the service, support user accounts, maintain security, satisfy legal obligations, and handle support or administrative requests. Retention can vary by record type.

If you want to request account or data deletion, contact EOTAK support and identify the account email or organization associated with your request.

8. Security, children, and policy updates

We use administrative, technical, and organizational measures designed to protect personal information handled through these apps. No method of transmission or storage is completely secure, but we work to reduce unauthorized access, misuse, and disclosure.

TAK Stack is not directed to children under 13, and we do not knowingly collect personal information from children through these apps.

We may update this Privacy Policy from time to time. When we do, we will post the updated version at this URL and update the effective date shown on this page.

9. Contact us

For privacy questions, deletion requests, or support related to TAK Stack for Android or iOS, contact us at:

EOTECH, LLC. Attn: EOTAK Support [email protected] 110 Kapsia Way Clarksville, TN 37040 Use the public contact page