Effective August 13, 2026
TrueNTP is built to collect as close to nothing as an app can. This policy describes what the app does with data, in plain language.
Nothing. TrueNTP has no accounts, no analytics, no advertising identifiers in use, no crash-reporting SDKs, and no tracking of any kind. We run no servers of our own and receive no data from your device. Your settings and sync history are stored only on your device and are deleted when you uninstall the app.
To measure time, the app sends small NTP packets (RFC 4330) to the time
servers you have configured, such as time.apple.com,
time.cloudflare.com, time.nist.gov, and the NTP
Pool. These packets contain only protocol timestamps — no personal
information. As with any internet traffic, the operators of those servers
can see your IP address; that is inherent to how networking works, and
those servers are operated by third parties under their own policies.
The optional GNSS reference feature reads the clock carried by GPS satellite signals, which Android only exposes to apps holding the precise location permission. TrueNTP uses that permission solely to read the satellite time signal. The app does not compute, store, or transmit your position — all processing happens on your device, and nothing leaves it. The feature is off by default; declining the permission simply leaves it off.
The sync-log export creates a CSV file containing timestamps, server hostnames, offsets, and round-trip times, and hands it to the share sheet. Where it goes from there is entirely your choice.
A future free tier is planned to show a single non-personalized banner ad served by Google AdMob, and a one-time purchase handled by Google Play or the App Store (with RevenueCat processing purchase receipts, not identities). When those features ship, this policy will be updated to describe exactly what those services process, and the effective date above will change.
TrueNTP is not directed at children under 13 and collects no data from anyone, of any age.
Any change to this policy will be posted at this address with a new effective date.
Questions about this policy: