Effective date: 19 April 2026
Last updated: 21 October 2026
Local Springs helps you discover springs and swimming places. This policy describes the current app, including its crash diagnostics. Contact: support@kpstudio.au.
The current app works without an account. Visited places, wishlists, custom names, and new places you add (including their descriptions, coordinates and selected photos) are saved locally on your device. These features do not upload that content to our servers or sync it between devices. Device backup services may separately back up app data according to your device settings. Older versions offered account and cloud features; updating does not automatically delete records previously supplied to those services. Contact support about historical data.
With your permission, the app uses foreground location to centre the map and show nearby places. We do not send your current coordinates to our own reporting backend. Map providers process map requests under their own policies. On Android, Google Maps processes network requests needed to display and interact with the map. Its SDK may also process device and SDK metadata, IP addresses, crash information, a pseudonymous SDK identifier and map interaction events. This does not mean map-provider requests stay on your device. The current app does not run background location monitoring or send proximity push notifications. Camera or photo-library access is used only when you choose to attach photos to a place saved on your device. You can change these permissions in your device settings.
When you submit an issue report, we receive the entry's identifier and displayed name, your description, the report category, platform and submission time. This is stored in Google Firebase and forwarded to our support inbox. No account is required. Please avoid including sensitive personal information in the description. Report delivery uses Resend; our support email uses Mailgun forwarding and Gmail.
If you choose to contact support by email, your mail app lets you review the message before sending it. The draft includes the name, email and message you enter, plus device model, operating-system version, app version and build number. You can edit or remove the device/app details. Your email service also provides its normal sender and message metadata.
Firebase Crashlytics automatically collects technical information about crashes and errors so we can investigate reliability problems. This includes stack traces and error information, device and operating-system information, app/build and update versions, and pseudonymous installation identifiers. These identifiers distinguish installations; they are not advertising identifiers or account names. Firebase dependencies also collect operational quality metrics to maintain and improve their services.
We add a short sequence of fixed action labels, such as app startup, opening a screen, changing a search or filter, using the map, changing a saved list, opening support, or submitting a report. The labels record that an action happened. They do not contain search terms, entry identifiers or names, coordinates, saved-list contents, report text, or support-message text. We do not set a user account identifier in Crashlytics. Automatically captured error information can contain details of the failing software operation; it is used for diagnosis, not advertising or cross-app tracking.
Crash diagnostics are collected automatically in the native app; there is currently no in-app switch for this collection. Google states that Crashlytics retains crash traces and associated installation identifiers for 90 days before beginning removal from live and backup systems. See Firebase privacy information.
On iOS, optional one-time tips use Apple in-app purchases. On Android versions that offer native tips, they use Google Play Billing. The relevant store processes payment; we do not receive your card details. The app handles product identifiers, transaction or purchase identifiers, purchase tokens where supplied by Google Play, and transaction status to check completed purchases, finish or consume tips, recover unfinished transactions and avoid processing the same transaction twice. The current implementation does not send this purchase information to our reporting backend. Tips do not create an account or unlock features, content or services. Apple and Google handle payment information under their own terms and privacy policies.
Expo Updates also sends a persistent, randomly generated installation identifier with update requests, along with platform and runtime information. If a previous update caused a fatal error, update requests can include that error information to support recovery. This identifier is not an advertising identifier; these requests help deliver and diagnose app updates.
We use Google Firebase (Firestore and Cloud Functions for issue reports, and Crashlytics for diagnostics), Apple Maps on iOS and Google Maps on Android, Expo for app updates, Apple and Google Play for optional store tips, and the email services described above. Network services receive connection information needed to operate, such as IP addresses.
Provider information: Google and Firebase, Apple, Google Maps, Expo, Resend, Mailgun.
We do not use advertising SDKs, sell personal information, or use these diagnostics to track you across other companies' apps or websites. Generic diagnostic action logs are used to investigate errors, not to build advertising profiles.
Local saved data remains on your device and any device backups. Issue reports and email correspondence are retained to investigate and resolve reported problems; they are not automatically deleted when you remove the app. Contact support to request access, correction or deletion of information you sent us. Crashlytics retention is described above. Service providers may process data outside Australia; this policy does not promise that diagnostics or email remain in one country.
The app uses encrypted network connections for its reporting services. Firebase rules restrict access to report records, and backend controls validate reports and limit duplicate email delivery. You can revoke location and photo permissions in device settings and review support emails before sending. To ask about data access, correction, deletion, or a privacy concern, email support@kpstudio.au. Applicable privacy rights depend on where you live. We may need enough information to locate the relevant report or correspondence.
Local Springs is not directed at children under 13. If you believe a child has sent us personal information, contact support so we can investigate and remove it where appropriate.
We update this policy when our practices change and revise the date above. Material changes may also be explained in the app or release information.
Kieran Savage, Melbourne, Australia. Email: support@kpstudio.au.