Last updated 26 August 2026
Our apps tell us when they crash, and two of them also count how they are used, using Google’s crash-reporting and analytics libraries; none of them knows anything about who you are — no accounts, no name, no advertising ID, no precise location. Lumber Jack and Jill will play you a video advert in exchange for in-game money if you tap a button asking for one, and never otherwise; the other two have no adverts at all. Time in the Market never sends us the amounts, dates or companies you look up — those stay on your phone. This website collects the ordinary anonymous traffic statistics that almost every website collects. We do not sell data, and we have never had anything worth selling in the first place.
Blargh LLC (“Blargh Labs”, “we”, “us”) publishes this website and the mobile applications listed on it. You can reach us at support@blarghlabs.com.
We publish three: Lumber Jack and Jill, Lionfish Hunter and Time in the Market. None has accounts or sign-in. Lionfish Hunter and Time in the Market have no advertising at all. Lumber Jack and Jill has one kind, described below, and you have to ask for it.
Lionfish Hunter includes one Google library — Firebase Crashlytics — so that we are told when the game crashes rather than finding out from a one-star review. It has no analytics: we do not count how you play it. Until August 2026 it had nothing at all and this page said so in as many words, which is why we are saying the opposite here just as plainly rather than quietly editing that sentence away.
Lumber Jack and Jill includes two — Firebase Crashlytics and Google Analytics for Firebase — so that we can be told when it crashes and also see whether anyone is playing. Earlier versions had neither, and this page said so; that changed in August 2026 and this is us saying so plainly.
Time in the Market includes the same two — Firebase Crashlytics and Google Analytics for Firebase. It has no adverts and it does not request the advertising ID; the permission that would read it is stripped when the app is built, so that is a property of the binary rather than a promise.
It is a tool for looking up what an investment would have been worth, so it is worth being exact about one thing: what you put into it never reaches us. Not the amount, not the dates, not the companies you pick. The events we receive are bare names — that a company was added, that a screen was opened — with no detail attached to them at all. There is no code in the app that could attach one. Its market data is bundled inside the app when you install it, the same for everyone, so browsing it sends nothing anywhere.
Until September 2026 the iOS builds contained no analytics, no crash reporting and no third-party libraries of any kind, and this page said so plainly. That has changed. This paragraph replaces the old one rather than the old one quietly disappearing, because the previous version of this page promised exactly that.
Lumber Jack and Jill, and Lionfish Hunter, on iPhone and iPad now include Firebase Crashlytics and Google Analytics for Firebase — the same two libraries the Android builds have carried since August 2026, and for the same reason. Without them we learn the game is broken from a one-star review, which is too late for the person who wrote it. They send crash reports, which screens you open and how a session went, along with a random installation identifier, the device model, the OS version, and the country your device reports from its network address.
They do not collect the advertising identifier, and cannot. The analytics library is built in the configuration that leaves that capability out of the app entirely, rather than being asked politely not to use it. That is why these apps show no App Tracking Transparency prompt: there is nothing they would be asking you for. There are no adverts of any kind in either iOS build, and there is no cross-app or cross-site tracking.
Our App Store privacy labels change with this release. They used to read “Data Not Collected”; they now declare crash data, product interaction and a device identifier — none of it linked to your identity and none of it used to track you. The Google Play labels are unchanged. Time in the Market still has no iOS build; when it has one, this paragraph will say which of the two it behaves like rather than leaving you to guess.
Lumber Jack and Jill shows rewarded video only, and only when you ask for one. Two buttons offer it — one in camp, one after a tree has cost you money — and both trade a video for in-game coin. There are no banners, no full-screen ads between trees, nothing on a timer, and nothing that interrupts a cut. Ignore both buttons and you will never see an advert in this game.
Lionfish Hunter works the same way, and this page used to say it had no adverts at all. That stopped being true when its Android build gained rewarded video, and the sentence should have changed in the same release. It is rewarded video only and only when you ask — one button, at the dock — with no banners, nothing between dives and nothing on a timer.
When you do choose to watch one, the request goes to Google’s ad network carrying roughly what the analytics carry: a non-personalised identifier for the installation, and the same country-level location worked out from your IP. Unlike the analytics, that data reaches an advertising network rather than staying with Google as our processor, which is why our Play data-safety declaration lists it as shared.
In Lumber Jack and Jill the adverts are not personalised. That app does not request the Android advertising ID — the permission needed to read it is stripped at build time, and its absence is checked before every release — so what you are shown is not chosen from a profile of you. That earns us less money and we would rather have the simpler answer.
Lionfish Hunter does not yet do this, and we are saying so rather than implying otherwise. Its Android build still carries the advertising-ID permission, so the adverts it shows you can be chosen from a profile in a way Lumber Jack and Jill’s cannot. That is an inconsistency we intend to remove by stripping the permission there too, the same way and with the same check. Until a release says otherwise, treat Lionfish Hunter on Android as requesting the advertising identifier — which is what our Google Play data-safety declaration for it already says.
If you are in the EEA, the UK or Switzerland, Google will ask you about this once on first launch. Saying no is a complete answer: no advert is ever requested, and the two buttons simply never appear.
On a Fire tablet from the Amazon Appstore there are no adverts, because there is nothing for them to run on. Google’s ad network needs Google Play Services, which Fire OS does not have, and Fire OS has its own advertising identifier that we do not ask for. The advert buttons check whether anything loaded before they appear, so on a Fire tablet they do not. Crash reporting is in the Amazon builds and may or may not reach us there for the same reason; nothing else is collected, and there is still no account, no location and no advertising profile.
What those libraries send, and nothing beyond it — the analytics items are Lumber Jack only:
What they do not send, and what the build does not permit:
AD_ID permission is removed at build
time and its absence is checked before every release.
Lumber Jack and Jill now declares the Android INTERNET permission, which it did not
before, because sending the above requires it. Its other permissions are
VIBRATE for haptic feedback when the saw bites,
ACCESS_NETWORK_STATE and WAKE_LOCK, and several
advertising-service permissions that arrive with the Google libraries. Notably absent, and
deliberately so, is the one that would let it read your advertising ID.
We do not sell any of this and we do not share it with anyone. Google processes it on our behalf under Google’s privacy policy.
Your progress — logs cut, money, gear and clothing owned, and the trees you have felled — is written to a single file in the app’s own private storage on your phone. It never leaves the device and we cannot see it. Uninstalling the app deletes it, and we never had a copy to delete — your save is not what the analytics above are about, and it is never uploaded anywhere.
Our apps are not directed at children under 13. What they do collect is described above, and none of it identifies anyone, of any age.
Unlike the apps, blarghlabs.com is an ordinary website and behaves like one.
We use Google Analytics to count visits and see which pages people read. It sets cookies and records the usual things — pages viewed, approximate location derived from IP address, browser and device type, and how you arrived. We use it to know whether anyone is out there. We do not use it to identify you, and we do not combine it with anything else. Google’s handling of that data is covered by Google’s privacy policy. You can opt out entirely with Google’s browser add-on, or by blocking cookies for this site.
Some pages embed a Zendesk support widget. If you start a conversation in it, whatever you type — and any contact details you give us so we can reply — is processed by Zendesk on our behalf under their privacy notice. If you never open it, it collects nothing.
If you email us, we have your email and whatever you put in it, for as long as it takes to deal with it. That is the whole of it. We do not add you to a mailing list, because we do not have one.
Our web server keeps standard access logs — IP address, timestamp, requested URL, browser string — for security and diagnostics, and discards them on a rolling basis. Every web server does this and it is not practical to run one that does not.
Depending on where you live, you may have the right to ask what personal data we hold about you, to have it corrected, or to have it deleted.
To request deletion, email support@blarghlabs.com with the subject “Data deletion request”. Tell us which app and roughly when you last used it. We will confirm within 30 days. You do not need an account, because there are no accounts.
Two things you can do yourself, immediately and without asking us:
If we change this policy we will change the date at the top of it. If we ever start collecting something, we will say so plainly here before we do, not after.