Privacy Policy

Last updated: September 23, 2026

This policy covers the fieldlog.net mobile app (FieldLog), the fieldlog.net web app, and FurtherAfield: Spatial Audio Player. “We” and “us” refer to the independent developer of these services. The information handled depends on the app and features you use.

1. FieldLog mobile app

FieldLog stores your takes, notes, timestamps, tags, equipment details, settings, and attached photos on your device. With your permission, it uses your location to tag takes and retrieve weather information, and your camera or selected photos to document recording setups. Photos can contain embedded location and time information; importing that information lets you use it in a take.

The mobile apps do not require account registration or account sign-in. For optional synchronization, you supply a sync token generated in the fieldlog.net web app. The mobile app stores that token on your device and sends it to the sync service to authorize requests; it does not use your web account password. When you use sync, your recording metadata, attached locations, gear information, and photos are transmitted to and stored by the web service associated with that token. Using local features without sync does not upload your library to our servers. Weather and mapping features can still contact the services described below.

2. FieldLog web app

Accounts are managed in the web app. When you create a web account, we store your name, email address, account settings, and authentication information. Passwords are stored as hashes. If you choose Google sign-in, we receive your account identifier, name, and email information from Google to create or authenticate your account.

We store the takes, notes, equipment details, tags, locations, photos, and other content you enter, upload, or sync. We use this information to provide your library, search, editing, exports, and synchronization. We also retain account plan and subscription status where applicable.

The web app uses cookies for sign-in and security, and browser storage for interface preferences. Our servers process technical information such as IP addresses, browser or app details, requested pages and API endpoints, timestamps, response times, and errors. Server-side usage statistics may be associated with your account and use a hashed IP identifier. We use this information to understand usage, diagnose problems, prevent abuse, and operate the service.

3. FurtherAfield

FurtherAfield accesses audio files you select and processes audio on your device for binaural or supported head-tracked playback. It stores library information, playlists, playback settings, and progress locally. Your audio files and head-tracking information are not uploaded to us.

FurtherAfield does not require an app account. It does not record microphone audio or request access to your contacts or device location. Supported head tracking uses device or headphone motion capabilities to adjust playback. The Android beta includes Google advertising and purchase services, described below; these services can process technical information separately from your locally stored recordings.

If you select files from a cloud storage provider or export files to another service, that provider handles the transfer and storage under its own privacy policy.

4. Services used to provide features

Weather: FieldLog sends selected coordinates and the relevant recording date or time to Open-Meteo to retrieve conditions. Requests made directly from your device also expose its IP address to the provider. Open-Meteo can retain technical logs containing coordinates; see its privacy policy.

Maps and address lookup: FieldLog uses OpenStreetMap map tiles and platform location services. Map requests disclose the area being viewed and connection information to the provider. Where address lookup is enabled, take coordinates are sent to the configured Nominatim geocoding service. See the OpenStreetMap Foundation privacy policy.

Web resources and security: The web app loads fonts from Google Fonts and interface resources from jsDelivr and unpkg. These providers receive connection information, including IP addresses, when your browser requests their resources. Google sign-in and, where enabled, reCAPTCHA process information for authentication and abuse prevention under Google’s privacy policy. If IP-based country lookup is enabled, an IP address is sent to ipapi.co to estimate country-level usage.

Hosting and email providers process information needed to run the service and deliver account or support messages. If you contact us, we use the details you provide to respond. We do not sell your personal information. Information may also be disclosed when required by law or necessary to protect the security of the services.

5. FurtherAfield advertising and paid unlock

The FurtherAfield Android beta includes Google AdMob banner advertising and Google’s User Messaging Platform for privacy messages. The beta currently uses Google test advertisements rather than live commercial ads. Ad requests are configured as non-personalized. This disclosure applies to builds with advertising enabled; it does not mean that every platform or version includes ads.

Google’s advertising services may collect and share your IP address (which can indicate approximate location), device and advertising identifiers, ad interactions, and diagnostic information for ad delivery, reporting, analytics, and fraud prevention. Non-personalized ads can still use identifiers for reporting, frequency limits, and fraud prevention. We do not provide your recordings, playlists, or head-tracking information to advertisers. See Google’s privacy policy and how Google uses information from apps that use its services.

Where applicable, Google’s privacy messages present consent or opt-out choices before ads are requested. You can revisit available choices through About → Ad privacy choices; this entry appears when Google requires a privacy-options entry point for your region or consent status. You can also manage your advertising ID through Android settings. Rejecting personalized advertising does not necessarily prevent all advertising-related data processing.

The Android beta also includes an optional one-time Remove ads purchase through Google Play. Google processes payments under its own policies; we do not receive your card details. The app receives purchase status and signed purchase information, including a purchase token, and stores a receipt locally to verify and restore the unlock. Once the unlock is verified, the app stops displaying ads and making new ad requests. Restoring a purchase uses the Google Play account that owns it.

Removing ads does not delete information already processed by Google. Google retains advertising, consent, and transaction information according to its own policies and applicable requirements. Use Google’s privacy controls for that information, or contact us for help with a privacy request.

6. Retention, deletion, and your choices

Local app data remains on your device until you delete it, clear app storage, or uninstall the app. Device backups may retain copies according to your platform and backup settings. Original photos, recordings, and exported files stored outside an app remain until you delete them separately.

FieldLog account content is retained to provide your online library until you delete the content or your account. You can manage your information and delete your account in the web app’s account settings, or request help using the contact address below. Uninstalling the mobile app does not delete your web account or synced server data. Account deletion also does not erase independent exports, device copies, or backups.

Operational logs, backups, and support correspondence may remain for security, recovery, support, or legal needs. Retention depends on the purpose and applicable requirements; deletion from active account storage does not necessarily remove every backup immediately.

You can manage location, camera, photo, and motion permissions in your device settings and use available export tools. You can remove a sync token from the mobile app to disconnect it, or revoke the token in the web app to prevent further use. Disconnecting sync does not delete data already synchronized. Depending on your location, you may have rights to access, correct, delete, or obtain a copy of your personal information, or object to certain processing. Contact us to make a request.

7. Security and children’s privacy

We use access controls and encrypted connections to protect hosted information. No storage or transmission method is completely secure. These services are not directed at children under 13. If you believe a child has supplied personal information, contact us so we can investigate and remove it where appropriate.

8. Changes and contact

We will update this page and its date when our privacy practices change. Where required, we will provide additional notice or request consent before a change takes effect.

For privacy questions or requests, email houstin+privacy@fieldlog.com.