Your data, clearly explained

Privacy policy

This page explains the data processed when you use the Đi Đâu app and website, why it is used and the choices available to you.

Updated November 17, 2026

1. Data you provide

  • Account: email, display name, avatar and authentication information handled by the authentication provider. With Google, the app receives the basic profile information you authorize. The app does not store your password.
  • In-app activity: your personal map, added or saved places, check-in photos, statuses, moods, reviews, likes, friendships, invitations and plans.
  • Support requests: your email address, message and files that you choose to send. Include only what is needed and redact unrelated private information.
  • Website account-deletion form: account email, optional message, confirmation, language, request reference, status and receipt time.

2. Device permissions

  • Location is used for the map, nearby places and directions when you use those features. Đi Đâu does not continuously track your location in the background.
  • Camera and photos are used to update your avatar, capture check-ins or scan QR codes. Uploaded images are reprocessed to remove source metadata, including EXIF/GPS.
  • Notifications are used for reminders and supported activity updates. Local network access is used to find nearby friends when you enable that feature. The app does not request access to your contacts.
  • You can change these permissions in iPhone Settings. Disabling a permission may prevent its related feature from working, but does not automatically delete saved data.

3. Why data is processed

  • To authenticate your account, synchronize data, show maps and content, connect friends, manage invitations, remind you about plans and provide the features you use.
  • To protect accounts, limit abuse, respond to support requests and fix technical problems. In-app data is not used for advertising tracking.
  • Sentry receives technical error reports filtered to limit identifying information. The current configuration does not enable session replay, UI screenshots or recording of user network activity content.

4. Who can see data

  • Each account has a personal map. Check-ins offer Only me or Friends visibility. Profile details, statuses and invitations are shown according to the feature and relationships in the app.
  • When a plan invitation is accepted, its places are added to the recipient’s map. Consider what you choose to share with friends.
  • Supabase provides authentication, the database and photo storage. Resend delivers authentication and account recovery emails through the SMTP configuration. Google supports sign-in and linked place information. Map components and sources include MapLibre, OpenFreeMap and OpenStreetMap; Sentry supports error diagnostics.
  • Providers may process necessary information such as IP addresses, request details and feature-related data on infrastructure in other countries. Third-party services apply their own policies.
  • Website deletion requests are stored in a Cloudflare D1 database through Sites infrastructure. The operator accesses a private queue to verify and process them; requests are not publicly listed.

5. Storage, protection and deletion

  • Account data and content are stored to provide the service until you delete the content or account, depending on the type of data. Device caches and sign-in sessions are managed per account.
  • Service connections use HTTPS, and in-app sessions are stored in Keychain. Data access is controlled by the backend. No safeguard can eliminate every security risk.
  • Account deletion removes your sign-in identity, private photos you own and related account data through the system’s deletion process. Some shared place information may remain after it is detached from the account.
  • Copies saved by others, security logs, support requests and provider backups may follow separate retention schedules or legal obligations. Contact us about specific data; this page does not promise one fixed deletion timeframe for every system.

6. Your choices and requests

  • You can edit your profile, change check-in visibility, delete supported content and delete your account in the app. See the Delete account page for instructions.
  • You can submit an account-deletion request through the website form. For access, correction or deletion of other data, contact vuongbachdoan@gmail.com. Ownership must be verified before deletion. Do not send passwords or OTP codes.

7. Website and policy changes

  • The website has an account-deletion request form, does not sign in to app accounts and does not include analytics or advertising trackers. Your language choice is saved locally when browser storage is available.
  • The form email and message are sent only when you select Send request. Entered content and request references are not saved to browser localStorage. Requests are kept in the private system for verification and processing; receipt does not mean the account has been deleted.
  • The form limits abuse using an HMAC-derived rate-limit identifier; the intake database does not store raw IP addresses. The hosting provider may still process separate technical logs to operate and protect the website.
  • Support email buttons open your email app; a message is sent only when you choose to send it. The current policy and update date are published here. Operator and privacy contact: vuongbachdoan@gmail.com.