Location Permission Terms

When you choose to enable location features on Foody Finds, we request access to your device's geographic coordinates (latitude and longitude) via the W3C Geolocation API built into your browser. This is a standard web API supported by all modern browsers.

Specifically, we may receive the following data points depending on your device and browser:

• Latitude and longitude — your precise or approximate geographic position
• Accuracy radius — the estimated accuracy of the coordinates in metres
• Altitude — your elevation above sea level (if available on your device)
• Altitude accuracy — the estimated accuracy of the altitude reading (if available)
• Heading — the direction of travel in degrees (if your device is moving)
• Speed — your speed of travel in metres per second (if your device is moving)
• Timestamp — the time at which the position was recorded

In practice, Foody Finds uses only latitude, longitude, and accuracy to derive your approximate city. We do not actively use, process, or display altitude, heading, or speed data.

Your location data is used exclusively for the following purposes within Foody Finds:

• Deal filtering: We convert your coordinates to an approximate city name using a reverse-geocoding lookup, which is then used to filter and prioritise deals near you.
• AI recommendations: If you use the AI chat assistant, your city (derived from your coordinates) is included as context to generate more relevant deal suggestions.
• Location prompt personalisation: We remember whether you previously granted or denied location access so we don't repeatedly prompt you.

We do not use your location data for:

• Targeted advertising or tracking across websites
• Building behavioural profiles or movement history
• Sharing with restaurants, partners, or third-party advertisers
• Any purpose not explicitly described in this document

Your raw GPS coordinates are never stored in our database. The location pipeline works as follows:

1. Your browser provides coordinates to the Foody Finds front-end application running locally in your browser tab.
2. We perform a reverse-geocoding lookup to translate those coordinates into a human-readable city name (e.g. "Austin, TX").
3. Only the derived city name is passed to our backend services for deal filtering.
4. The raw coordinates are discarded immediately after the city name is resolved — they are never transmitted to or stored on our servers.

This means that even in the event of a data breach, your precise location history cannot be exposed because it was never stored.

Foody Finds requests location permission at the following moments:

• First visit: A prompt appears in the deal feed asking if you'd like to see deals near you.
• AI chat activation: If you open the AI assistant, it may request your location to enhance recommendations.
• Manual trigger: If you tap a "Use my location" button anywhere in the app.

Your browser will display its native permission dialog before any location data is shared with us. We receive no data until you explicitly click "Allow" in that dialog. We never attempt to infer your location from your IP address as a substitute.

Location access is entirely optional. Denying location access has no impact on your ability to use the core features of Foody Finds. You will simply see deals for all cities rather than filtered by your location.

You may revoke location permission at any time by:

• Chrome/Edge: Click the padlock icon in the address bar → Site settings → Location → Block
• Firefox: Click the padlock icon → Connection secure → More Information → Permissions → Access your location → Block
• Safari: Safari menu → Settings for this website → Location → Deny
• Mobile (iOS): Settings → Safari (or browser) → Location → Never
• Mobile (Android): Settings → Apps → Browser → Permissions → Location → Deny

Once revoked, Foody Finds will not be able to access your location until you manually re-enable it through your browser settings. We will not request permission again unless you manually trigger it.

Because we do not store your raw coordinates, there is no GPS history to delete. The only location-derived data we may retain is:

• City name preference: Stored in your browser's local storage to pre-populate location filters on your next visit. This is cleared when you clear your browser data.
• Permission state: Whether you dismissed the location prompt is stored in local storage. Clearing site data resets this.

You may clear all locally stored Foody Finds data via your browser's "Clear site data" feature at any time. We will treat this as a fresh session with no location preferences set.

To convert your coordinates into a city name, Foody Finds may use a third-party reverse-geocoding API. When this lookup is performed:

• Your approximate coordinates are sent to the geocoding provider over an encrypted HTTPS connection.
• The geocoding provider returns a city/region name and the raw coordinates are not retained by them beyond the immediate request (subject to the provider's own privacy policy).
• We do not pass any user identifiers (such as your email, user ID, or account details) to the geocoding provider alongside your coordinates.

Where possible, we perform geocoding entirely on the client side (in your browser) to avoid transmitting coordinates to any external service at all.

We process your location data on the following legal bases:

• Consent (GDPR Art. 6(1)(a)): You explicitly grant browser-level permission before any location data is accessed. You may withdraw this consent at any time without penalty.
• Legitimate interest (GDPR Art. 6(1)(f)): Providing geographically relevant content is a core feature of the service that users reasonably expect.

If you are located in the European Economic Area (EEA), United Kingdom, or California, you have additional rights under GDPR, UK GDPR, and CCPA respectively. These include the right to access, correct, or delete any personal data we hold. To exercise these rights, contact us at foodyfinds.app@gmail.com.

Foody Finds is not directed at children under the age of 13. We do not knowingly collect location data — or any personal data — from children under 13. If you believe a child has granted location access while using Foody Finds, please contact us immediately at foodyfinds.app@gmail.com and we will take appropriate action.

For users aged 13–17, we strongly recommend that a parent or guardian review and consent to location permissions before enabling them.

If we change how we collect, use, or retain location data in a material way, we will:

• Update the "Last updated" date at the top of this document
• Notify registered users by email at least 14 days before the change takes effect
• Re-request browser location permission where required under applicable law

Continued use of location features after the effective date of any change constitutes your acceptance of the revised terms.