SpoturrLocation Data & Sharing

Location Data & Sharing

Effective date: August 12, 2026  ·  Spoturr LLC

This document supplements, and forms part of, the Privacy Policy of this Application. It describes in detail how location and related personal data is collected, retained, and shared within the Application. Where this document and the Privacy Policy address the same subject matter, read them together; this document provides the specific detail.

1. Location Data Shared With Other Users

The Application lets you share a vehicle with other people ("co-drivers"). Sharing a vehicle is what causes location data to be shared.

Every current member of a shared vehicle can see that vehicle's parked location, including its precise coordinates, the street block and side of the street it is parked on, and the time it was parked.

Members can also see parking-related activity for that vehicle, alarms shared with the vehicle, and the profile name and photo of other members. If you place a personal pin, that pin is visible only to you; pins are not shared with co-drivers.

2. Retained Location History

The Application does not retain only the current parked location. It keeps a rolling history of approximately 30 days of vehicle activity, which is shown to every member of the vehicle in the Activity feed.

Each entry in that history may include:

Entries older than approximately 30 days are no longer displayed in the Application.

3. Profile Name and Photo Visibility

Your profile photo and username are visible to other users you share a vehicle with.

A copy of your profile name and photo may remain visible to people you previously shared a vehicle with, in historical activity entries, after you or they have left that vehicle.

4. Vehicle Details Visible to Co-Drivers

Information you add to a shared vehicle — including the vehicle name, its photo, and the license plate, if you choose to enter one — is visible to every current member of that vehicle. The license plate field is optional.

5. Push Notifications

The Application sends push notifications for parking alarms and vehicle activity. These notifications are delivered through Apple's Push Notification service and Google's Firebase Cloud Messaging, and their contents pass through those services.

A notification may contain the location associated with the event, the street names of the block involved, the name of the vehicle, the name of the member who acted, and any custom message you have written on an alarm. Do not include information in an alarm message that you would not want transmitted through those services.

6. Invitation Links

When you share an invitation link or QR code to let someone join your vehicle, the link contains an identifier for the invitation and the display name of the person sharing it, so the recipient can see who invited them. Anyone who receives an active invitation link can use it to join that vehicle until the invitation expires or you revoke it in the Application.

7. Emails

If you enable email notifications for an alarm, the Application sends email through Mailgun, a third-party email provider based in the United States. Those emails contain the recipient's email address and the street intersection the alarm relates to. Mailgun processes this data on our behalf as described in the Privacy Policy.

8. Anonymous Usage Counts

The Application collects anonymous, aggregated counts of activity — for example, how many times a map tile has been viewed, or how many times a street block has been driven through or inspected, broken down by day of week and time of day.

These counts are not linked to any user account or device. No user identifier is stored with them, and each individual contribution is merged into a shared total at the moment it is recorded. They are used to understand which areas of a city are active, not to analyse the behaviour of any individual.

9. Your Choices