Isobark legal

Privacy Policy

Last updated: 15 August 2026

This policy explains how Isobark processes data when you use our website, web app or mobile app. Isobark provides forecast-based dog walking guidance; it does not provide veterinary, emergency or official severe-weather advice.

Data we process

Profile and preference data

Isobark can store the dog profile and settings you provide, including a dog’s name, size, age band, coat, rain preference, walk length, optional caution flags, units and an approximate saved location label. Until you choose cloud sync, this information remains in encrypted storage on your device. Your dog’s name is not sent in a forecast request.

Forecast requests

When you request a forecast, Isobark sends a selected town or postcode, or approximate coordinates you chose, together with the profile factors needed to produce cautious guidance. The Isobark forecast service sends only the location to its weather provider. We do not request or retain location history.

Optional account and cloud profile

Sign-in is optional. If you choose Google or Apple sign-in, Firebase Authentication processes the account identifier, provider identifier, email address where supplied, authentication events and technical security information needed to establish and protect your session. If you choose to copy a profile to your account, its cloud copy is held in Cloud Firestore. You can sign out, delete the cloud account and cloud profile, or separately delete the on-device profile in Settings.

Why we use the data

• To provide current conditions and the next 24 hours of forecast-based walking guidance.
• To save the preferences needed to personalise that guidance and any optional local reminder.
• To provide an optional account, protect it from misuse and, only when you choose it, synchronise a private profile between supported devices.
• To operate, secure and improve the service.

Where data is processed

Isobark’s forecast service runs on Google Cloud Run in London, United Kingdom. Optional cloud-profile data is stored in Google Cloud Firestore in London, United Kingdom (europe-west2). Firebase Authentication processes authentication data in the United States. This is an international transfer. Before native public release, Isobark will complete the applicable Google data-processing terms, transfer safeguard and transfer-risk assessment.

The forecast service uses WeatherAPI as its primary provider and Open-Meteo as a fallback. It retains a derived forecast result in memory for up to ten minutes and does not deliberately persist the original request body. Google Cloud, Cloudflare and weather providers may process ordinary technical data, such as IP address and request metadata, required to run their services under their own terms.

Retention and deletion

On-device profile data remains until you remove it in Settings. An optional cloud profile remains until you delete the cloud account and profile in the app. Deleting a cloud account does not automatically delete a separate local profile; you control that separately. Service-provider operational logs are retained according to the relevant provider’s configuration and terms. We will publish any material change to these arrangements on this page.

Your choices and rights

You can use a town or postcode rather than device location, change or remove a saved location, turn local reminders on or off, delete profile data from the device, and delete an optional cloud account and profile. Subject to applicable law, you may ask for access, correction, deletion, restriction or portability of personal data, or object to processing. You may also complain to the UK Information Commissioner’s Office.

Cookies and analytics

Isobark does not use advertising cookies or third-party behavioural analytics. The web app may use browser storage necessary to keep an optional signed-in session and your local app settings.

Contact