1. Who we are
Trips is developed and published by Pixelspore. We do not operate a Trips user-account backend. Banner ads are shown through Google AdMob (not a Pixelspore ad server).
Privacy questions and requests: trips@pixelspore.com
This policy: https://trips.pixelspore.com/privacy
2. Summary
- Trips is a navigation and trip-logging app. Core features require access to your device’s precise location, including while the app is in the background during recording or navigation.
- Routes, completed trips, waypoints, GPS track points, and app settings are stored locally on your device (not on Pixelspore servers).
- Pixelspore does not create user accounts and does not sell your data. Trips shows banner advertisements via Google AdMob on selected screens (main tabs, route detail, and trip detail). Ads are not shown during active navigation or recording.
- When you use maps, place search, route planning, road snapping, elevation, or turn-by-turn navigation, relevant location and route information is sent to Google Maps Platform / Navigation services so those features can work. That processing is governed by Google’s policies as well as this policy.
3. What the app does
Trips lets you:
- Plan routes with a start, destination, and optional stops (Places search / Directions).
- Record routes while driving, walking, or cycling (with optional snap-to-road for driving).
- Navigate a saved route with turn-by-turn guidance (Google Navigation SDK), including voice guidance if enabled.
- Log each navigation run as a trip with distance, timing, and a GPS track (coordinates, time, altitude, speed, bearing).
- View maps, traffic, ETA, elevation profiles, and compare trips.
- Use a subset of driving features on Android Auto.
- Export or import a route as a ZIP file you choose to share.
4. Information we access or process
Below is the information Trips accesses or processes. Categories align with Google Play’s Data safety disclosures.
4.1 Location (precise and approximate)
Trips requests Android location permissions, including
precise location (ACCESS_FINE_LOCATION),
approximate location
(ACCESS_COARSE_LOCATION), and
background location
(ACCESS_BACKGROUND_LOCATION) so recording and
navigation can continue when the screen is off or another app is
in the foreground.
Location is used to:
- Show your position on the map
- Record route and trip tracks
- Provide turn-by-turn navigation and progress
- Snap driving recordings to roads (when enabled)
- Support Android Auto navigation-related features
Location access is required for core features. You can deny or revoke permissions in Android settings; without them, recording and navigation will not work as intended.
4.2 App activity and trip content (stored on device)
The app stores the following locally in an on-device database and preferences store:
- Routes — name, description, travel mode (driving / walking / cycling), start and end labels and coordinates, waypoints (including optional Google Place IDs), encoded polylines, distance, and estimated duration
- Trips — status, start/end times, pause timing, distance traveled, last known position, optional description
- Track points — latitude, longitude, timestamp, and optional altitude, speed, and bearing
- Settings — for example whether voice guidance is enabled
You may also enter free-text names and descriptions. Do not put sensitive personal information in those fields if you do not want it stored with your routes or trips.
4.3 Network and device signals used for connectivity
Trips uses Internet access and may check network connectivity to call Google Maps Platform APIs. Those network requests involve standard technical data such as IP address as processed by Google and your network provider. Pixelspore does not operate a server that logs your Trips usage.
4.4 Notifications and foreground services
On Android versions that require it, Trips requests notification permission to show ongoing notifications while a location foreground service is running (recording or navigation). Those notifications are generated on your device so you can see that location is being used.
4.5 Information we do not collect
- No Trips user accounts, login, or passwords
- No collection by Pixelspore of your name, email, phone number, or contacts through the app
- No payment or financial information in the app
- No access to your contacts, SMS, call logs, camera, or microphone for recording audio/video
- No Pixelspore-operated crash reporting or analytics product that uploads your trip history to us
4.6 Advertising (Google AdMob)
Trips displays banner advertisements via Google AdMob on the main tabs and on route/trip detail screens. Ads are not shown during active navigation or recording. The Mobile Ads SDK may process the advertising ID and technical device/network signals to serve and measure ads, subject to Google’s policies and your device ad settings. See How Google uses information from sites or apps that use our services and the Google Privacy Policy.
5. How information is used
We use information only to provide app functionality:
- Plan, record, save, display, and compare routes and trips
- Provide in-app and Android Auto navigation
- Show maps, traffic, ETA, and elevation
- Remember your settings (such as voice guidance)
- Export or import routes when you choose to
Pixelspore does not use your trip data for advertising, selling data brokerage products, or building marketing profiles.
6. Sharing with third parties
6.1 Pixelspore
Pixelspore does not upload your routes, trips, or GPS tracks to Pixelspore servers. We do not sell or rent your personal data.
6.2 Google (maps, navigation, and ads)
Trips integrates Google services. When you use related features, data necessary for the request is transmitted to Google over an encrypted connection (HTTPS), for example:
- Navigation SDK / Maps — device location and routing context for turn-by-turn guidance, map display, and traffic
- Places API — search queries and place selections when planning stops
- Directions API — origin, destination, waypoints, and travel mode when calculating a planned route
- Roads API — GPS samples when snapping a driving recording to the road network
- Elevation API — coordinates when building an elevation profile
- AdMob / Mobile Ads SDK — advertising identifiers and technical signals used to request, show, and measure banner ads
Google’s processing of that data is subject to Google’s own terms and privacy disclosures for Google Maps Platform / Navigation, for example:
For Google Play Data safety purposes, location and related request data used by these SDKs/APIs may be considered shared with a third party (Google) for app functionality, even though Pixelspore does not receive a copy on our own servers.
6.3 Sharing you initiate
If you export a route ZIP (or share a file through Android’s share sheet / storage picker), that file leaves the app under your control. Recipients and cloud backups you choose are outside Pixelspore’s control.
6.4 Android system backups
If Android Backup / device transfer is enabled on your phone, the system may include Trips app data in backups according to your device and Google account settings. That is controlled by the platform, not by a Pixelspore cloud service.
7. Permissions (Android)
Depending on Android version and feature use, Trips may request:
- Location (precise / approximate / background) — recording and navigation
- Foreground service (location) — keep recording or navigation alive with a visible notification
- Notifications — show ongoing recording / navigation status
- Internet / network state — call Google Maps Platform APIs
- Wake lock / boot completed — support reliable background operation where applicable
- Android Auto / car app permissions — display navigation templates and surfaces in the car
You can review and revoke permissions in Android Settings → Apps → Trips → Permissions.
8. Security
- Local trip data stays on your device in the app’s private storage.
- Communication with Google APIs uses encrypted transport (HTTPS / TLS).
- Pixelspore does not maintain a Trips cloud database of your journeys, which limits our ability to access your trip history.
- No method of storage or transmission is perfectly secure. Protect your device with a screen lock and keep Android updated.
9. Retention and deletion
- Local route and trip data remains on your device until you delete it in the app or uninstall Trips.
- Uninstalling Trips removes the app’s local data from that installation, subject to normal Android behavior and any device backups you keep.
- Because we do not host your trip database, Pixelspore cannot remotely delete on-device data; deletion is performed by you on the device (or by clearing app storage / uninstalling).
- Data sent to Google for a live API request may be retained by Google according to Google’s policies; Pixelspore does not control Google’s retention periods.
There is no Trips account to delete. If you contact us about privacy, we will respond to emails we receive; we do not hold a separate profile of your trips.
10. Children’s privacy
Trips is not directed to children under 13 (or the minimum age required in your country). We do not knowingly collect personal information from children through a Pixelspore backend. If you believe a child has used the app in a way that concerns you, stop use on the device and contact trips@pixelspore.com.
11. International users
Trips may be used wherever Google Play and Google Maps Platform services are available. Location and routing requests to Google may be processed in countries where Google operates. Where applicable law provides rights of access, correction, or deletion for personal data we process (for example emails you send us), contact trips@pixelspore.com. For data processed by Google, use Google’s privacy tools and policies.
12. Changes to this policy
We may update this Privacy Policy when the app’s data practices or legal requirements change. The “Last updated” date at the top will change when we do. The current version will always be available at https://trips.pixelspore.com/privacy.
Material changes that affect how we handle personal data will be reflected here before or when the corresponding app version is distributed on Google Play.
13. Contact
Developer: Pixelspore
App: Trips (com.pixelspore.trips)
Email:
trips@pixelspore.com
Privacy Policy URL:
https://trips.pixelspore.com/privacy
14. Google Play Data safety alignment
This section is intended to help users and Play Console reviewers understand how Trips maps to common Data safety declarations. Always treat the live Play listing as authoritative if wording differs.
- Data collected / processed on device: precise location; approximate location; app activity / trip and route content you create
- Data shared: location and related routing / Places / Roads / Elevation request data with Google for app functionality; advertising identifiers / ad request data with Google AdMob for ads (not sold by Pixelspore)
- Data sold: no
- Contains ads: yes (banner / AdMob)
- Encryption in transit: yes (HTTPS to Google)
- Users can request deletion: delete in-app data or uninstall; no cloud account held by Pixelspore
- Optional vs required: location is required for core navigation and recording features