TacLink handles tactical data with minimal retention.

Information TacLink collects

• Account details such as email address, display name, and profile image.
• Authentication metadata required to keep you signed in securely.
• Team, invitation, game, and marker records that you create in TacLink.
• Subscription status, purchase records for one-time items (match credits, match pass, offline pack), and store-provider identifiers used for entitlement checks.
• A device identifier used to bind licences and to grant the welcome credits once per person.
• Event map images that organisers upload for a match.
• Player status during a match (for example hit, bleed-out, dead, respawn).
• Bluetooth mesh traffic between nearby phones during a match, described below.
• Session reports that keep counts, such as how many position updates were sent, and never coordinates.
• Operational telemetry such as crash reports, request errors, and low-cardinality diagnostics.

How TacLink uses the data

• To authenticate users and secure access to team and game data.
• To deliver core product features such as team membership, games, and map markers.
• To validate subscription access and restore purchases.
• To troubleshoot crashes, failed requests, and service abuse.

Location and realtime data

• Your location is shared only during an active match, with teammates on your side. Match staff (host, organizer, moderator) see all sides. The other side never sees your position or status.
• Sharing continues with the phone locked or another app open, until the match ends or you tap Stop sharing.
• Positions are treated as transient realtime data, and telemetry does not carry exact location payloads.
• Without signal, nearby phones exchange positions, markers, pins and status over Bluetooth Low Energy. These payloads are encrypted with a per-side key issued by the server. The Bluetooth link itself is not encrypted and carries no personal data in clear.

Data processors

• Vercel: hosting of the website and API. Vercel Blob stores event map images.
• Neon: Postgres database for application data.
• Ably: transient realtime delivery of positions and markers. Not stored.
• MapTiler: map tiles in the app, and geocoding to label a match location.
• Sentry: crash and error reports from the app and the API.
• RevenueCat, with the Apple App Store and Google Play: purchases and subscription status.
• Apple: Sign in with Apple. When device checks are enabled, DeviceCheck is used to grant the welcome credits once per device and to renew offline licences.
• Google: Google sign-in. When device checks are enabled, Play Integrity is used for the same device checks.

Retention and deletion

TacLink retains data only as long as needed to operate the service, comply with platform or financial obligations, and resolve disputes. You can request deletion from inside the app or via the public deletion page linked below. Event map images are deleted with the match or with your account.

One exception: the welcome-credit grant keeps a salted hash of your sign-in provider's subject id after account deletion, so a deleted account cannot claim the free credits again. This is for fraud prevention only.

User choices

• You can update basic profile fields inside the TacLink mobile app.
• You can manage or cancel store subscriptions in the store where you purchased them.
• You can request permanent account deletion from the public deletion page.

Children

TacLink is not directed at children under 16.

Your rights (GDPR)

• Access the personal data we hold about you.
• Correct data that is wrong.
• Erase your data (see deletion above).
• Receive your data in a portable format.
• Object to processing.
• Complain to the Croatian data protection authority (AZOP, azop.hr).

Contact

Controller: AV Solutions j.d.o.o., Croatia. Questions about privacy, your rights or deletion requests can be sent to support@tac-link.com.