Last updated:2026.8.31 · 简体中文
DevLocation is a GPS location simulation tool for development and testing provided by Weigan Technology (Shenzhen) Co., Ltd. (hereinafter referred to as "we" or "us"). It helps you simulate GPS locations on connected iOS devices to support app development and testing. This Privacy Policy applies to DevLocation on iOS, iPadOS, macOS, and visionOS.
We attach great importance to the protection of your personal information and privacy. We will provide appropriate security measures for your personal information in accordance with legal requirements and industry-standard security practices.
This Privacy Policy works together with our User Agreement for DevLocation.
The Mac app is the primary control surface. It connects to iPhones and other iOS devices over USB or the local network to send simulated locations. The iOS / iPadOS / visionOS companion app shows simulation status, map views, and remote stop controls. Simulated coordinates are processed mainly on your devices; saved places, routes, history, and runtime logs are processed mainly on macOS. We do not upload this data to our own cloud servers. The Service currently does not integrate third-party advertising SDKs and does not provide app accounts or cloud sync operated by us.
We use your personal information only where we have a lawful basis to do so. Depending on applicable law, we may rely on your consent, performance of a contract with you, compliance with legal obligations, or other lawful bases.
1.1 Core app features. To provide single-point simulation, route playback, device connection and management, favorites and history, GPX import/export, map picking, and address search, we process simulated coordinates, waypoints, speed settings, saved places, saved routes, visit history, device names and UDIDs (to identify connected devices), runtime state, and UI preferences on your devices. Device connection management, favorites and history, GPX import/export, and address search are mainly available on macOS; the companion app mainly displays synced simulation status. This data is used to perform location simulation and show status on your devices. We do not use it to identify you personally, and we do not upload a full database of your simulation data to our servers.
1.2 Local preferences and cross-device sync. We store certain settings locally, such as map style, simulation mode, tunnel/background agent state, and UI preferences. Between the macOS control app and the iOS / iPadOS / visionOS companion, simulation state summaries (for example, whether simulation is active, current coordinates, and device name) are synced mainly over the local network (Bonjour). Remote commands such as stop are also sent over that local connection. App Group storage is used for on-device state and commands within the same device (where applicable) and does not automatically sync across a Mac and an iPhone. This communication stays within your local network or on your devices and is not uploaded to our servers.
1.3 Maps and address search. When you use map display features, they are provided by Apple MapKit and related system map services. On macOS, when you use address search or place lookup, we may send search keywords or map region information to Apple to obtain search results and map tiles. Apple's handling of that data is governed by its policies.
1.4 Optional road routing (OSRM). On macOS, if you enable the optional road-routing feature, the app may send start and end coordinates to a public OSRM routing service (such as router.project-osrm.org) to obtain road-following waypoints. We send only the coordinates needed for the feature and do not send device identifiers, contacts, or unrelated information. That service is operated by a third party and is governed by its own policies.
1.5 Diagnostics and troubleshooting. On macOS, the app may generate local runtime logs or diagnostic summaries for device connection, tunneling, and simulation troubleshooting. You may view or copy these logs. By default, this information is not uploaded to our servers.
1.6 GPX and pairing files (where applicable). On macOS, when you import or export GPX route files, you choose the files yourself and they are stored locally on your device or in folders you select. In advanced/internal builds, you may also import developer pairing files. We do not proactively read or upload your other personal files.
1.7 What we do not do. The Service does not require you to register an in-app account with us. We currently do not integrate Firebase, Umeng, Pangle, AdMob, or similar third-party advertising or behavioral analytics SDKs. We do not read your photo library, contacts, SMS, call logs, or phone number in the background, and we do not request camera, microphone, or other sensitive permissions unrelated to core features (subject to the version you use).
1.8 Personal information inventory. To meet applicable privacy laws and app-store compliance requirements, we disclose below the categories of personal information that DevLocation may involve. The purpose, method, and scope described for each category apply only to the versions or scenarios noted. Categories marked as "not collected" mean that our app does not actively collect, read, or upload that type of information for the stated purpose.
This section describes third-party services that the Service may involve. Actual integrations may vary by platform.
The Service uses Apple MapKit for map display; on macOS, it is also used for place search. The Service uses Apple developer-service interfaces to communicate with connected iOS devices. Related data processing is governed by Apple policies.
Apple privacy policy: https://www.apple.com/legal/privacy/
When you enable the optional road-routing feature, the app may send start/end coordinates to a public OSRM instance (such as the Project OSRM demo service) to obtain route geometry. That service is operated by a third-party community or organization. We do not guarantee its availability, accuracy, or data-handling practices. You can disable the feature at any time to stop sending requests.
The Service mainly relies on operating-system capabilities for USB, local networking, location, file selection, and UI rendering. The macOS version may bundle or invoke open-source device-communication components (such as a pymobiledevice3-related runtime) to interact with your iOS devices locally. Except for map search and optional road routing that you actively enable, we do not upload your simulation database to our own cloud servers.
The Service is currently offered as a development tool and does not charge in-app subscriptions or one-time purchases, nor does it use app-store in-app purchases to unlock core features. If a future version introduces paid capabilities, we will update this Privacy Policy as required by law and obtain your consent where necessary.
The Service may request the permissions below while running. We ask for your consent in system permission dialogs. Denying a permission affects only the related feature. Details vary by platform.
Used to jump the map to your Mac's current location for faster point selection.
Used to discover and connect iOS devices with Developer Mode enabled over USB.
Used to discover devices over Wi-Fi, run tunnel services, and sync simulation state with the iOS companion through Bonjour.
Used for optional road routing through third-party OSRM services when you enable that feature, and for other network requests needed for device communication.
Used to import or export GPX route files.
Used to write coordinates or log excerpts to the system clipboard when you actively copy them.
Used to discover the Mac control app on your local network and sync simulation state.
The companion mainly displays simulated coordinates synced from the Mac and usually does not actively read your device's real location. If your version or system prompts involve location permission, the actual behavior is subject to your version.
You can manage app permissions at any time in system Settings or the app's permission settings.
If you have requests regarding your data-subject rights, or if you have questions, comments, or suggestions, contact us using the details in "How to Contact Us" below.
For information processed by Apple, OSRM, or other third parties, you may also exercise rights through those providers' settings or policies. You can remove locally stored simulation data and settings by deleting favorites/history, clearing app data, or uninstalling the app.
6.1 Simulated coordinates generated through the Service are processed and stored mainly on your devices. Saved places, routes, history, and runtime logs are processed and stored mainly on macOS. The current version does not provide cloud sync operated by us.
6.2 Map search and optional road-routing data may be stored and processed by Apple, OSRM, and other third parties on infrastructure that may be located outside your country or region, in accordance with their respective policies.
6.3 Unless otherwise required by law, we retain information only for as long as necessary to fulfill the processing purpose. After you uninstall the app or clear data, the corresponding local information is deleted.
You may contact us using the details below to exercise your rights. We will respond as soon as reasonably possible.
Email: weigantechnology@outlook.com
If you are not satisfied with our response, especially where you believe our processing has harmed your lawful rights and interests, you may seek resolution through a court with jurisdiction, an industry self-regulatory body, or a relevant government authority. You may also ask us about other complaint channels that may apply.