The short version

Patchly works without an account, and Patchly operates no server that stores or processes your field history. Everything you record while prospecting, including GPS sessions, tracks, finds, pins, shapes, photos, detector history, search coverage and the Stash, is stored on your device and is never sent to Patchly. If you use backup and sync, a copy goes to your own iCloud Drive or Google Drive, or straight to your own computer, phone or tablet over your Wi-Fi, never to Patchly. The same holds for Patchly on a Windows, Mac or Linux computer: your records on it, and any change you make there, are stored on that computer and are never sent to Patchly. The app does use the network for infrastructure, such as downloading map tiles and layers, and this policy describes exactly what those requests involve.

Who is responsible

Patchly, on the App Store and Google Play and as a download for Windows, Mac and Linux computers from patchly.gold, is published by Patchly Labs Pty Ltd, an Australian company. For anything in this policy, contact contact@patchly.gold.

Data that stays under your control

The app's purpose is recording your prospecting work. That work is stored on your device, and in your own cloud storage if you use backup and sync, described below. It includes:

Patchly has no access to any of it. There is no Patchly account, no sync service run by Patchly, and no Patchly copy of your data.

When you add a licence from a photo or a scan, Patchly can read its text to fill in the fields for you. The reading happens on your device and opens no connection, so neither the photo nor the text read from it is sent anywhere to be read. On iPhone and iPad it uses Apple's own on-device text recognition. On Android it uses reading models the app downloads from Patchly's content delivery service the first time you open the vault or a licence, the same way a map layer downloads. The photo is kept with your other documents, so it leaves the device only through the backup, sync and exports described below.

Location

Patchly asks for location permission to show your position on the map and to record sessions, including in the background while a recording is running with the screen off. Location fixes are written to the recording on your device. They are not transmitted to Patchly, and reach your own cloud storage or your own computer only through backup and sync, described below. You can revoke location permission at any time in your device's system settings, which stops recording from working but leaves the rest of the app usable.

Patchly on a computer records no sessions. Its Locate button asks the computer's own location service for a single position, with the permission the system asks you for, to centre the map there. That position is not stored, and it is not sent to Patchly.

Backup, sync and exports you control

The app can back up your data to your own cloud storage, iCloud Drive on iPhone, iPad and Mac or Google Drive on Android, Windows, Mac and Linux, and can export a portable .patchly file you share or store wherever you choose. These copies go to storage under your control, in your own accounts. Patchly cannot read them, does not hold the keys to them, and never receives them.

The same backup keeps your own devices in step. Apple devices signed into the same iCloud account, or Android devices signed into the same Google account, catch up with each other through that storage, mainly when Patchly is opened on them. Patchly on a Mac can use the same iCloud Drive storage as your iPhone, and Patchly on a Windows, Mac or Linux computer can use the Google Drive backup a phone made, one of the two at a time. A computer joins a Google Drive backup a phone has already made and never starts one of its own. On a computer, taking in records from your other devices stays off until you turn Sync on. Your records travel only between your own devices and your own cloud storage, never through Patchly.

Signing in to Google on a computer happens in the computer's own web browser, on Google's page. Patchly asks only for access to the files the Patchly apps create in your Google Drive, not the rest of it. The sign-in Google returns is kept in the computer's system credential store, the Keychain on a Mac, Credential Manager on Windows or the desktop keyring on Linux, goes only to Google, and never reaches Patchly. Signing out forgets it on that computer.

Patchly on a computer linked to your phone can also sync with that phone directly over your local Wi-Fi, once you choose it on the phone and allow the phone on the computer. Your records then go straight from one of your devices to the other, over a connection only those two devices can read, through no cloud and no Patchly server. Wi-Fi sync carries your own records only, never map layers. While a phone is paired, or a code to pair one is waiting, the computer announces itself on your local network under a random identifier that names no person and no computer, so the phone can find it. Unpairing the two on either device stops it, and so does the computer's link to your phone ending.

Two of your phones or tablets can sync with each other directly over your local Wi-Fi in the same way, an iPhone or iPad with an Android device included. One device shows a pairing code, the other scans it, and the device that showed the code asks you to allow the other by name. No account, link or internet connection is involved. Your records and their photos, the same ones your backup holds, then go straight from one device to the other over the local network, over a connection only those two devices can read, never to a Patchly server or any other server. Map layers never travel this way. Stopping syncing on either device ends it, and everything already synced stays on both.

Backup is presented as a choice during onboarding, next to saving a manual .patchly export instead, and can be turned off at any time in the app's settings. Sync is a separate switch and starts off: once a second device backs up to the same cloud storage, Patchly asks once whether this device should take in the other devices' changes, and the switch stays in Settings, under Sync. Turning Backup off on a device stops that device syncing through your cloud storage and, after a confirmation, deletes the backup from your cloud storage. Deleting backups from your cloud storage is always available to you through that provider.

What does use the network

Patchly is a map app, and maps need infrastructure. These requests happen without any Patchly account attached:

Purchases

Patchly Pro subscriptions are sold and processed by Apple's App Store or Google Play. Patchly never sees your payment details, billing address or store identity.

To unlock Pro layers for download, the app sends the store's own proof of purchase to Patchly's token service, which confirms the subscription is current. On iPhone that proof is the signed receipt Apple issues for the transaction, and it is checked as the request arrives and never stored. On Android it is the product name and the purchase token Google issues, which are checked against Google and the answer kept briefly under a one-way hash of that token, never the token itself. Neither carries your name, your account or your payment details, and nothing you have recorded in the app is sent with them.

The token service also keeps a short record of each subscription, so that a renewal, refund or cancellation the store reports takes effect: the product, when the current period ends, whether it renews or was refunded, and when Patchly first saw it. It is filed under the store's own identifier for the subscription, which on Android is a one-way hash of the purchase token, and carries no name, account, email address or payment details. It is kept after the subscription ends, so Patchly can count the subscriptions it has had. To spot a subscription used on more devices than it allows, the service also notes which installs used it, under a one-way hash of the app integrity identifiers described above, made separately for each subscription, and that note expires 90 days after the subscription was last used.

Patchly downloaded for Windows, Mac or Linux from patchly.gold sells nothing and sends no proof of purchase of its own. It carries Pro from the phone it is linked to, as described below. The iPhone app installed on a Mac from the App Store confirms its own App Store purchase, as described above for iPhone.

Patchly on a computer

Patchly for Windows, Mac or Linux, downloaded from patchly.gold, works through Patchly on your phone, and this section describes that download. The computer shows a code, and the phone, beside it, scans the code and approves the computer. The link lasts 14 days from the last time the phone confirmed it in person, and ends sooner if either device unlinks it or the phone links a different computer. No account is involved.

The iPhone app installed on a Mac from the App Store is the phone app rather than this download. The sections for phones apply to it, including its own App Store purchase and the App Store label. It can also link to your phone, and Patchly's token service then keeps the same record of that link as described here.

The computer's key. When it is linked, the computer makes a key of its own and proves it holds that key every time it asks for map access. On a Mac with a Secure Enclave, the key is made inside the Secure Enclave and cannot be copied off the computer. On Windows, and on a Mac without one, it is a key file in the app's data folder that only your user account can read. On Linux, it is kept in the desktop keyring, or, where the computer has none, in a key file that only your user account can read. Patchly's token service keeps the link itself: which phone approved which computer's key, the computer's system, when the link was made, last used and last confirmed, and the phone's subscription status with the store's identifier for that purchase, so one subscription carries Pro to one computer. It keeps no name and no account with it. The subscription status and the store's identifier are deleted a day after the link's 14 days run out, and the time the computer last used the link 90 days after that use. The rest of the link is kept until either device unlinks it or the phone links a different computer in its place, and after a link ends any other way, until the computer is next opened. A computer the phone replaced with another is told so for 90 days, from a record holding only its key.

The Bluetooth check that carries Pro. While its code is on screen, a computer with Bluetooth broadcasts a short-lived random code. On a Mac or on Linux the broadcast goes out under the name Patchly. On Windows it carries the computer's own Bluetooth name instead, as Windows does for any Bluetooth service a nearby phone can find. The phone reads the code while scanning and sends it with its approval. The phone asks for any Bluetooth permission it needs at that moment, never before. Patchly's token service compares the two only to confirm the phone was beside the computer, and the computer carries the phone's Pro only while the last confirmation passed that check. The broadcast never names the phone and carries nothing you have recorded, and the code lasts only as long as the link code it belongs to.

What the computer sends. Like the phones, the computer sends nothing you record or edit on it to Patchly. Its records reach your other devices only through your own iCloud Drive or Google Drive, or directly over Wi-Fi, as described under Backup, sync and exports you control. Its map, layer, gold price and update requests are the ones described under What does use the network. It keeps a log of its own activity on the computer, holding counts, timings and states and never a position or anything you recorded, which Patchly never receives unless you attach it to an email yourself.

The station sign-on board

Some pay-to-detect stations run a board at the office where campers put their name on the area they are heading to for the day, so the office knows everyone is back by dark. Where a station offers it, Patchly can carry that board, and it is the one optional feature that sends something about you to a server Patchly runs for the station. It is off unless you join it by collecting a single-use sign-on code from the office.

What it sends is your name as the office wrote it, the area you tapped, and when. It never sends your position, a coordinate or anything you have recorded in the app, and it is not an account: there is no email or password, and it is never linked to the identifier the app uses to fetch maps. Only that station's office can see the board. On your own phone you only ever see your own entry. The office removes your name when you leave, and the history behind it is deleted 90 days later.

The newsletter

This website lets you subscribe to an email when a new layer is added or a new version ships. It is separate from the app, and nothing you record in the app is connected to it. If you subscribe, Patchly stores your email address and when you signed up. So the form can turn away repeated signups from one place, it also notes the time of each signup with a keyed hash of your IP address, which cannot be turned back into the address without a secret key Patchly holds. Notes more than a day old are deleted each time someone signs up. All of it is held in a database Patchly runs on Cloudflare, with no outside newsletter service involved.

To keep out automated signups, the form uses Cloudflare Turnstile, a check that loads only once you start filling the form in. Patchly uses your address only to send you those emails, and never sells it or shares it for anyone else's marketing. To unsubscribe and have your address deleted, email contact@patchly.gold from that address.

No tracking, no ads, no sale of data

The app embeds no advertising software and nothing that tracks you across other apps or websites. Patchly does not sell, rent or trade any data, and holds no personal data from the app that could be sold. Outside the app, it holds the email address of anyone who subscribes to the website newsletter, described above, and never sells it. The app contains no analytics software: nothing in it watches what you do and reports it back. Because Patchly does not track visitors across websites, a browser's Do Not Track signal has nothing to change.

What Patchly does do is count its own service traffic, and it is worth being precise about it. When the app fetches a map layer it asks Patchly's servers for permission first, and those requests are counted so that Patchly knows roughly how many people use the app, which country, state or region and time zone they are in, which curated layers are popular, and which app versions are still in use. That counting is built only from requests the app already had to make, not from anything extra sent for the purpose.

It is kept deliberately coarse. The records hold no name, no account, no IP address, no town or city, and no map coordinate. Nothing you record in the app — your tracks, finds, pins, photos, notes or search coverage — is part of it, or reachable from it. Requests for individual map tiles, which are the ones that would show where you were looking, are not recorded at all. Each install is counted under a random identifier the app makes up on its own when you first open it. It is not your device's identity, is tied to no account, stays the same for as long as the app is installed, and disappears when you delete it. Where the app is used and which layers are popular are counted separately, under an identifier that changes every month, and Patchly never combines the two.

The mapping software described above is the exception worth stating plainly, because it is not Patchly's to switch off entirely. Mapbox, Google and Apple each collect some usage, performance and crash information about their own map components for their own analytics. Mapbox's reporting is switched off as described above. Google's and Apple's cannot be, and each applies only while that vendor's base map is selected. That is a statement about what those vendors do with their own software, and it is not tracking you across other apps. Crash reporting for the app itself relies on the platform's built-in, user-consented mechanisms operated by Apple and Google, not on a third-party crash service.

This website counts its own visits too, using Cloudflare Web Analytics. It records page views and where a visit arrived from, sets no cookie, and stores nothing that identifies a visitor or follows one between sites. It measures the website only, never the app.

The LiDAR coverage map on the website's Library pages is drawn by Mapbox and loads only when you tap it. From then on your browser fetches map tiles and place searches from Mapbox, which receives your IP address, the part of the map you look at, anything you search for, and a count of each map loaded tagged with a random identifier that Mapbox keeps in your browser's local storage and replaces every 24 hours, under the Mapbox privacy policy. The map's optional performance reporting to Mapbox is switched off. Patchly receives none of it.

What the store privacy labels say

The App Store and Google Play each require a data-safety label, and both of Patchly's list more than people expect. A label covers everything inside the app, including the mapping software built into it, so "collects nothing" is not an answer either store offers. The labels are accurate. They are also easy to misread, so here is what each line means.

Google Play shows two separate lists, and they are not the same list. One is headed "Data shared with third parties" and the other "Data collected". Patchly's shared list holds app interactions, crash logs, diagnostics, other app performance data, and device identifiers. Location is not on the shared list, and neither is purchase history. Those two appear under "Data collected" only, which on Google Play is the far broader bucket: anything the app sends off the device for any reason lands there, including a request to a server acting on Patchly's behalf.

Why location is on the collected list. Drawing a map means asking a tile server for the squares of the world currently on screen, and that request has to say which part of the map is being looked at. That is what puts location on the list. It is not your recording. Your tracks, finds, pins and search coverage are stored on your device and in your own backups, never on a Patchly server, as described above. Requests for individual map tiles are not recorded at all, and the service counting described above keeps the country and state or region only, never a coordinate.

Why purchase history is on the collected list. Confirming a Pro subscription means sending the store's own purchase receipt to a Patchly server, which answers whether the subscription is valid. On iPhone that receipt is checked as the request arrives, and on Android it is checked against Google, as described above. No card number, no billing address and no name is involved. Payment is handled entirely by the App Store or Google Play, and neither passes those details to Patchly.

Why a name can appear on the list. Nametag, the optional sign-on board for prospecting stations, is the only part of Patchly that sends a name. Today it runs at Palmerville Station. The station office writes your name on its board and gives you a code, and signing on with that code sends your moves and check-ins, with the area you chose, to the server Patchly runs for that station. If you never sign on to a station's board, Patchly sends no name at all.

What is actually shared, and with whom. The map components built into the app, from Mapbox and Google, report usage and performance information about their own software to their own analytics, and Google's map component also reports crash information. That is what the shared list describes. A store label covers what the software built into an app declares it is able to collect, not what it does on any given run, so the shared list still names the Mapbox reporting that Patchly switches off, as described above. Patchly embeds no advertising software, no analytics software and no crash reporter of its own.

The Windows, Mac and Linux download from patchly.gold comes from neither store, so it carries neither label. What it sends is set out above, under Patchly on a computer. The iPhone app installed on a Mac from the App Store carries the App Store label.

On the App Store, Patchly has no "Data Used to Track You" section at all. Apple asks a different question, whether data is linked to your identity rather than whether it is shared, and lists location and purchases under "Data Not Linked to You". Three entries are listed as linked to you, Name, Device ID and Other Data. Name is the optional Nametag sign-on board described above, linked because a name identifies a person on its own, and sent only if you sign on to a station's board. Device ID is linked because Google's map component declares it that way, even though the same App Store entry also covers the device identifier Mapbox uses for licence billing, described above. Other Data comes from Google alone.

Retention and deletion

Because your data lives on your devices and in your own cloud storage, retention is in your hands. Deleting a recording, find, pin or any other record in the app removes it from the device, and with sync on, from your other devices when they next catch up. Deleting the app from a phone or tablet removes everything it stored there. Removing it from a computer can leave its data folder in place, to be deleted as well. Backups you made to your own cloud storage are deleted through that provider, and the manual .patchly exports you created are files you manage yourself. Patchly holds no copy of your data, so there is nothing on a Patchly server to request deletion of. Transient infrastructure logs, such as IP addresses on tile requests, are kept only briefly for service operation and abuse protection. The service counts described above are aggregate totals rather than records about a person, so there is no individual record in them to identify, retrieve or delete. There are four exceptions, all described above. The token service keeps its record of each subscription after the subscription ends, as described under Purchases. The link between a computer and your phone is kept as described under Patchly on a computer. On a station sign-on board you have joined, the office removes your entry, and its history is deleted 90 days after that. A newsletter subscription is deleted when you ask at contact@patchly.gold, and the signup notes used to turn away repeated signups are deleted once they are more than a day old, the next time someone signs up. Patchly keeps backup copies of sign-on boards, newsletter signups and the records its services need to confirm purchases and keep the app working, for up to 30 days, so anything deleted also leaves those backups within 30 days. Those records carry no payment details and nothing recorded in the app.

Children

Patchly is a general-audience app for recreational prospectors and is not directed at children. Patchly does not knowingly collect personal information from children under 13. A parent who believes a child has given Patchly personal information, such as a newsletter signup or a station sign-on entry, can ask for it to be deleted at contact@patchly.gold.

Your rights and the law

Patchly Labs Pty Ltd handles personal information in line with the Australian Privacy Act 1988 and its Australian Privacy Principles, and, for users in New Zealand, the New Zealand Privacy Act 2020. Since Patchly holds no account data and no copy of your recorded data, most access and correction rights are exercised directly on your device. The newsletter list is the exception: to see, correct or delete the address you subscribed with, email contact@patchly.gold from it. For any privacy question, request or complaint, contact contact@patchly.gold. If you are not satisfied with the response, you can complain to the Office of the Australian Information Commissioner (oaic.gov.au) or, in New Zealand, the Office of the Privacy Commissioner (privacy.org.nz).

Changes to this policy

If Patchly's data practices change, this page will be updated and the effective date above revised. Material changes will be highlighted in the app's release notes.