Last updated: July 10, 2026
Cow Cow Technologies ("we", "us", or "our") builds a family of iOS and Android apps. This policy explains what data our apps work with, what stays on your device, and the limited data shared with third parties (advertising and analytics). Not every practice below applies to every app — an app only uses a capability if it offers the corresponding feature. Each app also requests system permissions (location, photos, tracking) in context, and you can decline or change them at any time in your device settings.
Our apps are designed to keep your content on your device. Depending on the app, this can include your travel history and places visited, photos and videos you choose to edit or import, activity and route files, and your in-app preferences. This data is stored locally and is not transmitted to servers we control. We have no account system and no backend that receives your personal content.
Some apps (for example, our travel and trip-tracking apps) use your location to record the places you visit or the routes you record. Location processing happens on your device; for travel history we keep only coarse information such as the country or city, not a precise coordinate trail, unless an app's feature explicitly records a route you asked it to. Location data is not sent to us.
Some apps read from your photo library — for example, to edit a photo or to discover past trips from the location tags already saved in your photos. This processing happens on your device. We do not upload, copy, or retain your photos.
Some apps (for example, our running-analysis and activity-file apps) can read workouts from Apple Health, with your permission, to analyze or export them. This happens on your device. We do not receive your Health data and do not store it on servers we control. You grant and revoke this access in the Health app or iOS Settings.
On Android, some apps (for example, our backyard-ultra timer) can write a finished run into Health Connect, with your permission. We write only the workout you just completed — the exercise session, the distance covered, and, if you recorded one, the GPS route of that run. Saving is opt-in and happens once per run, only when you ask for it; nothing is written automatically or in the background.
This access is write-only: our apps do not read your existing exercise, distance, route, or any other health data back out of Health Connect. The data is handed to Health Connect on your device and never sent to us, and we do not store it on servers we control. You grant and revoke this access in Health Connect or in Android Settings, and you can delete anything an app wrote from within Health Connect itself.
Where an app lets you connect an external service — for example, uploading an activity file to Strava — that transfer happens only when you initiate it and authorize the connection. The data goes directly from your device to that service under your own account, governed by that service's privacy policy. We do not store your credentials on our servers and we do not receive a copy of the uploaded data.
Where an app offers iCloud sync, your data is synced through your own private iCloud account using Apple's CloudKit. It is stored in your iCloud, governed by Apple's Privacy Policy, and is not accessible to us.
Some apps display ads through Google AdMob. To show ads, AdMob and its partners may use cookies, web beacons, your device's advertising identifier (Apple's IDFA on iOS, Google's Advertising ID on Android), and similar usage data. On iOS we present Apple's App Tracking Transparency prompt on first launch; on both platforms, where required by law, we present a consent form for personalized advertising. If you decline tracking or consent, ads are limited to non-personalized ads. You can change these choices in iOS Settings, in Android Settings under Privacy → Ads, and — where available — from a "Manage Privacy Choices" option inside the app. AdMob's handling of this data is described in Google's Privacy Policy.
Some apps use Google Firebase Analytics to understand aggregate, anonymized usage — for example, which features are used and how often — so we can improve the apps. These events carry counts and categories, not the contents of your trips, photos, routes, or other personal content. Analytics is provided by Google under Google's Privacy Policy.
Some apps use Google Firebase Remote Config to adjust feature settings without an app update. This uses a per-install Firebase Installation ID and carries no name, email, or other personal information. It is provided by Google under Google's Privacy Policy.
We want to be clear about what we don't take off your device. We have no account system and no backend that receives your personal content, so we do not collect:
The exceptions are spelled out above: the limited device identifiers and usage data shared with Google AdMob and Firebase, and any data you choose to send to a third-party service you connect yourself (such as a Strava upload). We do not sell your personal information.
Our apps rely on Google AdMob and Google Firebase, which have their own privacy policies linked above. If you connect an external service such as Strava, that service's own privacy policy also applies. We encourage you to review them.
We take reasonable measures to protect information. However, no method of electronic transmission or storage is 100% secure.
Our apps do not knowingly collect personal information from children under 13. If you believe we have collected such information, please contact us so we can delete it.
We may update this Privacy Policy from time to time. Any changes will be reflected on this page with an updated revision date.
If you have questions about this Privacy Policy, please contact us at privacy@cowcowtech.com.