TrackCertify — Privacy Policy
This Privacy Policy applies to TrackCertify Lite, TrackCertify Pro, and TrackCertify Guard (collectively, the "apps"), formerly part of the RideTag product family. The apps are developed by TrailSD ("we", "us"). It explains what information the apps access, how that information is used, and when information may leave your device.
Summary
The apps are designed to process GPS tracks, photographs, and reports locally on your device. You do not need to create a TrackCertify account, and we do not operate a backend to receive or store your GPS tracks, photographs, or patrol reports automatically. Information may leave the device when you choose to share a report, use optional cloud storage where available, open a map link, or when the app requests third-party map tiles. Those activities are described below.
Differences between the applications
TrackCertify Lite
TrackCertify Lite uses the device's GPS location information and permitted access to photographs for the app's supported photo-location and reporting features. Processing takes place on your device. Any tagged copies, reports, and local files remain on the device unless you choose to share or remove them.
TrackCertify Pro
TrackCertify Pro provides additional photo-location and reporting features, including reports in supported formats. It can also offer optional Cloudflare R2 storage: if you configure credentials for an R2 account that you control, the app can upload reports directly to that account when you use the feature. We do not host those report files or have access to your R2 account credentials or bucket.
TrackCertify Guard
TrackCertify Guard records GPS locations during a security patrol shift, including when the screen is off or the app is in the background, subject to Android permissions and device conditions. When you take a photograph, Guard opens the device's camera application and saves the accepted photograph in private app storage. Guard combines recorded locations, photograph information, and shift start/end times to generate a local PDF security patrol report. Reports may include a route map, stationary-period analysis, and intervals with no recorded GPS positions. Guard does not upload your photographs or reports to Cloudflare R2.
Information the apps access and store
- Precise location (GPS): location coordinates and timestamps used for recording activities or security patrol shifts, matching photographs to locations, mapping routes, and preparing reports. GPS information is stored locally.
- Photographs and related details: images you select or capture, together with relevant capture times and available location metadata. Lite and Pro may read permitted photographs and create tagged copies; original photos are not intentionally overwritten as part of tagging. Guard stores newly accepted camera photographs in its private app storage rather than publishing them to the device's photo gallery.
- Shift and report records: Guard stores shift identifiers, start/end times, photograph associations, and report-related information locally so you can create and manage reports.
- Settings you choose: preferences such as report titles, footers, sharing text, and (where the R2 feature is available and enabled) Cloudflare R2 credentials. R2 credentials are protected on-device using the Android Keystore and used to communicate directly with the configured Cloudflare account.
Permissions and battery settings
The apps request Android permissions needed for the features you choose to use. Guard requires Precise Location, enabled device Location Services, and an exemption from battery optimization (often shown as Unrestricted Battery) before starting a new patrol shift. The battery setting helps reduce the risk of interrupted background GPS recording; it does not guarantee that GPS signals or location records will always be available. Android controls these permissions and settings, and you can change them in your device settings.
How information is used
GPS processing, photo matching, creation of tagged photo copies, and report generation occur on your device. Depending on the app edition, reports can be produced in the supported PDF, HTML, or Word formats; Guard generates PDF reports. We do not automatically transmit your raw GPS track, original photographs, or generated reports to a TrackCertify-operated storage server.
Third-party maps and external services
To display background maps in reports, the apps may request map tiles from an external mapping provider (currently Esri). Those requests can reveal network information, such as your IP address, and the geographic area of the map tiles requested. The apps do not send the photographs themselves as part of a map-tile request.
When you tap an Open in Google Maps link in a report, the link includes the relevant GPS coordinates, and Android, your browser, or Google Maps handles the request under that service's own privacy practices. The same applies to clickable map markers and report-table location links.
Where optional Cloudflare R2 storage is available and you configure it, reports are transferred directly to the Cloudflare storage account you control. Cloudflare's processing of those files is governed by its own terms and privacy practices.
Sharing
You can choose to share a report through the Android share sheet or another supported sharing action, including email or messaging apps. The receiving app or service handles the information you choose to share, which may include photographs, report text, GPS coordinates, and maps embedded in the report. Sharing or uploading a report is not required to complete a Guard shift, and canceling a share action does not delete the locally saved PDF.
Data retention and deletion
Local GPS records, tagged photos, Guard's private photographs, reports, and app settings are kept according to the app's storage and deletion functions, until you remove them or clear the app's data. When you delete a Guard report from Report History, the app also attempts to delete the original private photographs reliably associated with that report's shift; it does not delete photographs based on an uncertain association or erase the shared GPS track file simply because a report was deleted.
For backward compatibility, some Lite/Pro photo and report files may still be stored in folders with the older RideTag name, such as Pictures/RideTag or Download/RideTag. Files saved to shared device storage may remain even if you uninstall the app. Copies you already shared with other people or services cannot be deleted from their devices or accounts through TrackCertify. If you use your own Cloudflare R2 bucket, uploaded reports remain there until you remove them from that account.
Advertising and analytics
As of the date of this policy, the apps do not contain a third-party advertising SDK. If advertising or other third-party data collection is introduced in a future release, we will update this policy and any required app-store disclosures before that release.
Support communications
If you contact us for support, we receive the email address and information you choose to include in your message. We use it to respond to your request. Please avoid sending confidential GPS tracks or personal photographs unless necessary to describe your issue.
Children's privacy
The apps are not directed at children, and we do not knowingly collect personal information from children through the apps.
Changes to this policy
We may update this policy when app features or information practices change. The updated version will be posted at https://trackcertify.com/privacy, with a revised "Last updated" date.
Contact
For privacy questions, contact support@trackcertify.com.