Privacy is part
of the route.
We design LetsAdventure around consent-driven location sharing and access controlled by trip membership. This policy explains the current marketing website and the expected mobile app data flows.
1. Who operates this site
LetsAdventure is a founder-led, independently developed project based in Vietnam, currently pre-incorporation. Privacy questions or data requests can be sent to [email protected].
2. Data on this website
This marketing website does not provide account registration or collect GPS tracks, trip expenses or user-uploaded photos. If you contact us by email, we receive the email address and information you choose to share. Hosting and security providers may process technical connection data such as IP addresses and request logs to deliver and protect the site.
3. Intended mobile-app data
During development and future testing, the app may process account and login details, trip membership, group itineraries, GPS tracking points, expenses and settlements, images, video recaps, device/session identifiers, support messages and activity/audit records needed to operate the service.
We intend to collect trip location only when a participant grants device permissions and actively enables sharing for a trip. Depending on platform permissions, background tracking may continue while enabled and the device is locked. Trip location must only be visible to authorized participants according to membership and app permissions.
4. Uses and sharing
Trip information is used to coordinate groups, show agreed live locations, calculate shared expenses, store memories, generate requested recaps and secure accounts. We do not intend to sell personal location histories. Infrastructure and processing providers may handle data as needed for hosting, storage, maps, notifications and video generation, subject to applicable arrangements and permissions.
5. Retention and control
Live location display and trip history are different: stopping live sharing should stop fresh tracking, while previously recorded route history may remain available for a recap until deleted under app controls. The production retention schedule and any legal exceptions will be specified before wider availability. Users can request access, correction or deletion through the contact email.
6. Security and limitations
The codebase is designed with membership checks, authenticated API access and private media storage. No online system can guarantee absolute security. The mobile app has not completed all production-release acceptance tests; this page must be reviewed as the app, infrastructure and integrations change.
7. Contact and updates
For privacy requests, please email [email protected]. We will update this policy when live features, providers, retention periods or legal status materially change.