Location Data Policy
AALA Technologies LLC
This Location Data Policy supplements the Privacy Policy and describes feature-specific processing of precise, approximate, and background location information. Do not enable a location feature unless you understand its operation and risks.
1. Location Data We Process
Precise and approximate device coordinates, altitude, heading, speed, timestamp, and accuracy data made available by the device.
Background location while an enabled feature requires continued route recording, navigation, or live sharing.
Recorded tracks, GPX files, selected routes, waypoints, points of interest, route conditions, and map interactions.
Live location shared with a group or accepted contact, together with profile identifiers needed to display the share.
IP-derived approximate region and technical logs used for security, anti-spoofing, rate limiting, diagnostics, or consent evidence.
2. Why We Use It
We use location information to show position on a map; provide routing and offline navigation; record, import, export, and share routes; display nearby content, weather, and conditions; enable optional live sharing; prevent spoofing and misuse; troubleshoot reliability; respond to a user-directed safety request; and comply with law.
3. Consent and Controls
The device operating system controls location permission. We will present a prominent in-app explanation before requesting background location and request only the permission reasonably needed for the selected feature. Live sharing is optional, off by default, and requires an affirmative action. You choose the group or accepted contact and can stop sharing through the persistent in-app control.
You may revoke permission in device settings. Revocation may stop navigation, route recording, nearby results, or live sharing. The Company must keep separate, auditable records for acceptance of this Policy, device permission prompts where accessible, and live-sharing activation.
4. Visibility and Sharing
Do not share a home address, workplace, sensitive destination, confidential route, or another person's location without permission. Consider delaying publication of recorded routes and trimming start and end points.
5. Retention
6. Recipients and Transfers
Location information may be processed by infrastructure and mapping providers and disclosed to the users you select. Providers may include Mapbox, Google Maps, OpenStreetMap-related services, CARTO, ArcGIS, MapLibre-compatible sources, Open-Meteo, IP-geolocation providers, cloud infrastructure, and push-notification services, but the published list must match production. Cross-border processing is addressed in the Privacy Policy.
7. Safety Limits
TRIAKAMAP IS NOT AN EMERGENCY SERVICE, RESCUE DISPATCHER, OR SUBSTITUTE FOR OFFICIAL MAPS, TRAIL CLOSURES, WEATHER ALERTS, SIGNS, TRAINING, OR JUDGMENT. LOCATION MAY BE DELAYED, INACCURATE, UNAVAILABLE, OR WRONG BECAUSE OF DEVICE, SIGNAL, BATTERY, TERRAIN, WEATHER, MAP, PROVIDER, USER, OR NETWORK CONDITIONS. A SHARED POSITION DOES NOT CONFIRM THAT ANYONE IS MONITORING IT OR WILL RESPOND.
If an SOS or safety feature is included at launch, it must be separately documented and tested. Until then, no copy may represent the Service as contacting emergency responders or guaranteeing assistance. In an emergency, contact the appropriate local emergency service using a reliable channel.
8. Sensitive Places and Other People
Do not use the Service to track, stalk, harass, surveil, or infer attendance at sensitive locations. Do not attach location to a photo or message about another person without a lawful basis and permission. We may suspend sharing, preserve evidence, or disclose information when reasonably necessary to address credible threats, unlawful conduct, or valid process.
9. Rights and Contact
You may access, correct, delete, or export eligible location information and exercise jurisdiction-specific privacy rights as explained in the Privacy Policy. Contact privacy@triakamap.com.