LogHog

Privacy policy

Last updated 21 September 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. 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.

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 and your reading list. 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.

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, or anything else you choose to track. 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 and your booking files.
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: what you type in the venue box, straight from your device.
Google BooksBook search in Reading List: what you search for, through our server.
Google FontsThe website’s typefaces, loaded straight from your device.
StripePayments on the website.
AppleThe App Store, and payments in the iPhone app.
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.
Open Food FactsFood search and barcode look-ups in Intake and Checklists, straight from your device.
Movie of the NightFilm search and where to watch, through our server. Posters load straight from your device.
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.