Location Data Disclosure

2v2 uses location information in two distinct ways: (1) your approximate area to find nearby challenges in the discovery feed, and (2) the venue location you enter when creating a challenge. This disclosure covers what is collected, where it is stored, how long it is retained, and what other users can see.

For the complete list of all data categories the app collects, see our Data Inventory.

You can set your discovery area using GPS or by choosing an area manually.

GPS mode: The app requests permission to access your device location. Your approximate coordinates are stored on your device and sent to our server as search parameters when you load the discovery feed. The server uses these coordinates to compute which challenges fall within your chosen radius. Coordinates are not stored server-side as a user location record — they are used only as query input and discarded after the query runs. The app reverse geocodes your coordinates to a city name for display. Only the city or neighborhood name is shown to other users as your home area.

Manual mode: You choose an area by name. No coordinates are stored on your device or sent to our server.

Location permission is requested the first time you choose GPS mode. 2v2 requests foreground location access only — we do not request background location permission.

You can change or revoke this permission at any time in your device settings under Privacy & Security > Location Services. Revoking permission switches you to manual area mode.

2v2 requests location at balanced accuracy, not high precision. This uses a combination of GPS, Wi-Fi, and cellular signals to produce an approximate position suitable for city-level discovery.

Before your GPS coordinates are saved on your device or used to search for nearby challenges, they are rounded to 3 decimal places (approximately 110 meters at typical latitudes). The raw sensor value is not retained.

Challenge venue coordinates from geocoding are stored at 5 decimal places (approximately 1 meter), which is sufficient for map directions without storing excess precision. Location snapshots in reports use the same 5-decimal-place precision.

Coordinates are not transmitted to our server as a persistent user location record.

When you create a challenge, you enter a location name, neighborhood, and city. The app geocodes this text to coordinates using your device's geocoding service. These venue coordinates — which represent the challenge venue, not your device GPS position — are stored server-side in the challenges table. Venue coordinates are used to power the distance filter in the discovery feed and to generate map directions links for joined participants.

What other users can see about a challenge location depends on whether they have joined:

• Not joined: Neighborhood and city only. The exact venue name is hidden until joined.
• Joined participant or host: Full venue name, neighborhood, and city.

Venue coordinates are never shown directly to users. They are used only for distance calculations and to generate directions links for joined participants.

When a user reports a challenge for a location concern, a snapshot of the venue location — including location name, neighborhood, city, and coordinates — is stored in our reports database for moderator review. This snapshot is retained as part of the moderation record.

• Your GPS coordinates (discovery): Stored on-device. Cleared when you switch to manual mode or uninstall the app.
• Challenge venue coordinates: Stored server-side. Retained while the challenge record exists. After account deletion, retained for dispute resolution and legal obligations, then deleted per our standard data retention schedule.
• Location snapshots in reports: Stored server-side. Retained for the lifetime of the report.

For questions about location data or your personal information, contact support@2-v2.com.