Location Usage

When Location Is Used

No2Wait can request location after successful mobile sign-in or sign-up so location-powered pages can work consistently across the app. It also requests location when a user opens a feature that needs it, such as current-state suggestions, verifying a completed trip, showing the user's current point on a map, or estimating itinerary distance.

No2Wait does not show a custom Yes/No permission gate before requesting location. Device-level location permission is requested only through the operating system permission screen. If permission is denied, the app remains usable and later location features may ask again or direct users to device Settings.

The app does not need continuous background location tracking for the current MVP flow.

Google Maps Compliance

No2Wait uses map provider APIs for live display, markers, location context, and distance-related features. The app should not be used to copy, scrape, store, or redistribute provider map tiles, restricted map data, or protected imagery.

Static No2Wait-designed travel cards may use No2Wait-owned visuals and user trip information. Live map provider content is displayed in-app under the provider's applicable terms and may require an internet connection.

Visit Verification

When users verify a place, the backend checks whether their coordinates are near an eligible trip circuit target or event location.

Successful verification can sync a map pin, mark progress, and move the event toward completed status.

Control

Users can deny location permission, but location verification and current-state suggestions may not work until permission is granted.

Users can control No2Wait location access from their device permission settings. If location is denied or disabled, normal browsing, account access, and trip planning can continue, but current map pin, nearby suggestions, connected lines, and visit verification may not work.

Users can delete their account from the app or request data deletion from the web deletion page.