LogHog

Privacy policy

Last updated 11 November 2026

The short version

1. Who we are

LogHog is made and run by Louis Whyte, a sole trader in London (“we”, “us”). We are the data controller for the information described here, registered with the Information Commissioner’s Office (ICO) under registration number ZC261033. You can reach us at [email protected].

2. What LogHog keeps

Your account

Your email address and password (stored scrambled by our database provider, so nobody, including us, can read it), when you signed up, and the permissions you have given: the health information consent you tick when you create an account, and whether you have allowed Ask AI.

If you log in with Google or Apple, you have no LogHog password unless you add one. Instead we keep the email address Google or Apple gives us, the ID it uses for you, and, if Google sends them, your name and a link to your Google profile picture (LogHog does not show or use either). We never see your Google or Apple password. If the email is one you already use for LogHog, you log in to that same account. Apple lets you hide your real email address: if you do, Apple gives us a private address that passes our emails on to you, and that becomes your account’s email. When you delete an account you log in to with Apple, the iPhone app also tells Apple, so LogHog no longer has access to your Apple ID.

What you add

Everything you enter in the modules: bookings (with venues, guests, amounts, notes and attached files), balances, habits, trackers, checklists, recipes, intake, your watchlist, your reading list, your places (with where each one is, and any photos you keep of it), your workouts (exercises, routines and the sets you finish, with weights and reps), your countdowns and your tables (whatever rows and columns you choose to keep in them). This can include other people’s names, such as your guests or people who owe you money. We keep those only as part of your records and never contact them.

Things you share

If you share a list, the people you let in can see it, and change it if you allow that, and they see your email address. When you ask to join someone else’s, they see your email address before they decide whether to let you in. A shared list stays its owner’s: what the people on it add is kept with it, and if the owner stops sharing it or deletes it, it goes from everyone’s devices, along with anything they added. On a shared list, the owner and the people who can change it see who added each item: the name you give in Settings (Your name), or, to the owner only, your email address if you have not given one. People who can only view it do not see this. If the owner allows Ask AI on a shared list, the people on it can send it to Gemini when they use Ask AI (section 5). If you report something shared with you, we keep the report and your email address so we can look into it.

A Places list can be shared in the same way. The people on it see its places, with each place’s ratings and fields in that list. Notes belong to a list, so the notes you write in one list are never shown with another. The list’s owner chooses whether its notes, photos, Want to go or Been, and who recommended a place are shown too. Photos added to a shared list are kept with its owner’s account. When someone who can change a list you share searches Google for it, those searches and the places they pick count towards your own monthly Places allowance and your map’s limit, and LogHog keeps the positions of the list’s places up to date for everyone on it, for the 30 days Google allows (section 7).

If you turn on being told when someone asks to join, Apple gives LogHog a code for your iPhone, which we keep so our server can send that one kind of notification. It is deleted when you sign out.

Your settings

Your name, your dashboard, your module settings and the note LogHog’s AI keeps about your preferences, which you can read and edit in Settings. If you make a calendar feed (Settings, Bookings, Calendar), LogHog creates a private web link that calendar apps such as Google Calendar can subscribe to, and anyone who has that link can see your bookings. You can reset the link at any time, which stops the old one working. The feed is separate from LogHog’s Apple Calendar sync on iPhone (section 3), which happens on the phone itself and uses no link.

Your subscription

Whether you subscribe to LogHog Premium, and when it renews or ends. Card details go straight to the payment provider (Stripe on the website, Apple in the iPhone app). We never see them.

Messages you send us

Anything you email us, and any suggestion or problem report you send from the app, along with the app version and the kind of device it came from.

Diagnostics

When something goes wrong, the app records what failed, on which page, and your account ID, so the fault can be found. It does not record the contents of your records. The server also notes each call it makes to an outside service on your behalf: which service, when, how long it took and, for Ask AI, how large and how costly the request was. It does not note what you asked.

3. What stays on your phone

4. Health information

Some of what you can log is health information: food and drink, alcohol, caffeine, weight, blood pressure, your workouts, or anything else you choose to track or keep in a table. LogHog only ever has what you add yourself. It reads nothing from Apple Health or any other app or device, so if you never log anything like this, it holds none. The law treats this as a special category of personal data, so we keep it only with your explicit consent, which you give when you create an account. We use it only to show it back to you. It is never used for anything else and never shared, apart from the providers in section 6 that store and carry it, and Gemini if you ask Ask AI about it.

You can take back that consent at any time by deleting the records concerned, or your whole account.

5. Ask AI

Ask AI is part of LogHog Premium. It asks your permission the first time you use it. When you send a message, LogHog sends your message, any photo you attach, the records it needs to answer (usually the ones in the module you are using) and your AI preferences note to Google’s Gemini service, through our server.

6. Who else handles your data

These companies do work for us, under contracts that only let them use your data to provide that work. “Straight from your device” means that service sees your device’s internet address, as any website you load does. “Through our server” means it sees our server’s address, not yours, and only what is needed for the request.

WhoWhat for
SupabaseStores your account, your records, your settings, your booking files and your photos of places.
CloudflareHosts the website, runs the LogHog server that passes requests to the other services, and receives email sent to loghog.co.uk.
Google GeminiAsk AI, only after you allow it (section 5), through our server.
Google MapsVenue search in Bookings, and the map in Places: what you type in Bookings, and the part of the map you look at, straight from your device. Place search in Places and in Import records: what you type, your position (or the middle of the map), and the place you pick, through our server. When you pick a place in Places, Google’s photo of it is loaded straight from Google to your device; it is shown once and not kept. Google’s map on the iPhone also sends Google information about how the map is used and how it performs, for Google’s own analysis. Google’s own privacy policy covers the map.
Google sign-inLogging in with Google, if you choose to. Google tells us your email address and the ID it uses for you, and may send your name and profile picture link. Google knows you have logged in to LogHog. Google’s own privacy policy covers your Google account.
GeoapifyThe address of a spot you drop a pin on in Places, from OpenStreetMap, through our server.
Google BooksBook search in Reading List: what you search for, through our server.
StripePayments on the website.
AppleThe App Store, payments in the iPhone app, Sign in with Apple in the iPhone app, and the notification telling you someone has asked to join something you share.
RevenueCatKeeps track of subscriptions bought in the iPhone app.
ResendSends account emails, such as confirming your address or resetting your password.
Google (Gmail)Email you send to [email protected], and a copy of any suggestion you send from the app, is received and answered from a Gmail account.
GitHubKeeps the weekly backup of the database, privately.
postcodes.ioA postcode you type in Places to measure distances from, straight from your device.
Open Food FactsFood search and barcode look-ups in Intake and Checklists, straight from your device.
OMDbFilm search and details, through our server. Posters load straight from your device, from Amazon's image servers.
TVmazeTV search and episode dates, through our server. Pictures load straight from your device.
Open LibraryBook covers, straight from your device.

Some of these companies process data outside the UK, including in the United States. Where they do, the transfer is covered by safeguards the UK recognises, such as the UK–US data bridge or the UK’s international data transfer addendum.

7. How long we keep it

8. Why we are allowed to

Under UK data protection law we rely on:

9. Your rights

You can:

10. Keeping it safe

Everything travels encrypted. The database lets each account read only its own records, booking files are private to their owner, and payment details never reach us. No system is perfectly secure, and if something went wrong that put your data at risk, we would tell you and the ICO as the law requires.

11. Children

LogHog is not meant for children under 13, and we do not knowingly keep their information. If you think a child has made an account, tell us and we will delete it.

12. Changes to this policy

The date at the top says when this policy last changed. If we change it in a way that matters, we will tell you in the app or by email before the change takes effect.