Is Trailforks safe to use?

Trailforks integrates 24 third-party SDKs spanning infrastructure, analytics, and attribution. It does not collect data linked to your identity. It includes 1 advertising or attribution SDK. Whether this is acceptable depends on your personal privacy preferences.

What permissions does Trailforks need?

Trailforks requests 10 iOS permissions: Camera, Contacts, Photo Library, Location (When In Use), Location (Always), Location (Always & When In Use), Motion & Fitness, HealthKit (Read), HealthKit (Write), and Save to Photo Library.

What data does Trailforks collect?

According to its App Store privacy label, Trailforks collects Diagnostics not linked to your identity.

How many SDKs does Trailforks have?

Trailforks integrates 24 third-party SDKs. 1 for attribution, 8 for analytics, 1 for crash reporting, 11 for infrastructure, and 3 for other.

Does Trailforks use Google SDKs?

Yes. Trailforks includes 13 Google or Firebase SDKs: Firebase A/B Testing, Firebase Core, Firebase Performance, Firebase Remote Config, Firebase Remote Config Interop, Firebase Sessions, Google Data Transport, Firebase Crashlytics, Firebase Core Extension, Firebase Core Internal, Firebase Installations, Firebase Shared Swift, and Google Utilities. These are used for cloud infrastructure and services, not advertising.

Does Trailforks access your location?

Yes. Trailforks requests location access. The developer states: "Trailforks uses your location to display your position on the map and record your activities during use".

Does Trailforks access your camera?

Trailforks requests access to your camera. The developer says this is for "To take photos for attaching to trail reports. To scan QRCode from your friends". These permissions are only active when you grant them in iOS Settings.

Does Trailforks access your contacts?

Yes. Trailforks requests access to your contacts. The developer states: "We need access to your contacts to import your friends.".

Does Trailforks run in the background?

Yes. Trailforks registers 5 background modes, which means it can perform certain tasks when you're not actively using it.

What are some alternatives to Trailforks?

Other navigation apps include ABRP , 高德地图 , Shell , SpotAngels , Avenza Maps , and 10-4 by WEX . Each app takes a different approach to navigation and varies in its data collection and SDK usage.

Navigation · Privacy report

Trailforks: Offline Bike Maps

Free · ★4.7 · Pinkbike.com

Is Trailforks safe?

It leans heavily on third-party trackers.

Our take. Trailforks is built with more third-party tracking code than 82% of the navigation we have scanned, including an analytics SDK from Israel.

Privacy footprint · vs 89 navigationHeavy

Trackers from other companies8 · a lot

typical navigation: 3

Data the app links to you0 types · little

typical navigation: 4 · from its own privacy label

What it collects about you

It links almost nothing to you.

Trailforks's own App Store privacy label declares it links no data to your identity. That is rare, and it is a good sign.

Who else is inside

It carries trackers from 2 companies.

Third-party SDKs found in the app, matched to the company that publishes each. Present in the code; we do not observe what they transmit.

🇺🇸GoogleAnalytics

Firebase, AdMob and Google analytics SDKs, built to record how you use the app and serve ads.

SDKs

🇮🇱AppsFlyerAttribution · Israel

Marketing attribution and audience analytics.

SDK

How it compares

Where it sits among navigation.

Every one of these apps we have scanned, on the two measures above: third-party trackers it carries (across) and data it links to you on its own label (up). Toward the top right is more invasive.

Each dot is one navigation app. Trailforks sits to the right, carrying more third-party tracking than most.

Other signals

One more flag.

Each is a fact read straight from the app. The same checks run on every app we scan. Only the ones that apply here are shown.

It sends analytics to a company in Israel

AppsFlyer is a Israel company. Its analytics SDK is built into the app.

The evidence

What it's built from.

All 24 SDKs in the app, grouped by what they are for. 8 are third-party trackers.

1attribution

7analytics

1crash reporting

1push & messaging

14standard libraries

8 of the 24 are third-party trackers. One is a push-notification SDK that delivers notifications, rather than tracking you across apps. The rest are the app's own code and standard open-source building blocks.

Show the full SDK list

GoogleAnalytics · USA

Firebase A/B Testing · Firebase Core · Firebase Performance · Firebase Remote Config · Firebase Remote Config Interop · Firebase Sessions · Google Data Transport

AppsFlyerAttribution · Israel

AppsFlyer

Push & messaging1 · notifications

OneSignal

Standard libraries14 · on-device

The app's own code plus open-source interface, storage and networking libraries.

How we know this

Counterspy downloads the app from the App Store and statically analyzes its compiled binary. Embedded SDKs are matched against a signature database and resolved to the company that operates each. We also read the developer's App Store privacy label, which lists the data the app says it collects and links to you. We do not run the app or intercept its traffic, so we report capabilities present in the code and the developer's own disclosures, not proven transmission. We assess privacy and data collection, not malware, security flaws, or developer intent. Reports are automated and never edited for payment. Scan v2026.2.3, 2026-04-03.

Third-party trackers are advertising, analytics and attribution SDKs detected by static signature matching. Presence shows a capability is compiled in, not that it ran or transmitted data.
"Data the app links to you" is the count of data categories the developer declares as Data Linked To You in its App Store privacy label. Labels are self-reported and not verified by Apple.
Comparison across the 89 navigation in our corpus. Trackers: median 3. Data linked to you: median 4.