Kubb Toss is a free single-player game made by me, James Hemson. There are no accounts or ads. From version 1.6 on the App Store, the game collects no analytics: it sends nothing about you or your games to me or anyone else. Earlier versions send gameplay analytics, and this page explains what they send and what you can ask me to do about it.
Which version are you using? You can check in the App Store, or in Settings, General, iPhone Storage, Kubb Toss. If you're still on version 1.5 or earlier, or on a TestFlight test build of 1.6 where you chose to share analytics, your copy sends gameplay analytics as described under earlier versions. Updating from the App Store stops that.
Version 1.6 and later on the App Store
The game has no analytics and no privacy settings to manage. Your saved match, personal records and settings stay on your iPhone.
When you update, the game deletes what older versions left on your iPhone: files from the old analytics library and, if you tested an early build of 1.6, the analytics choice and random identifier it saved. That clean-up only affects your phone. It doesn't delete anything older versions had already sent; see below for how to ask about that.
Apple gives me aggregated App Store statistics, such as downloads and, from people who agreed in their iPhone settings to share analytics with app developers, sessions and active devices. Apple collects that under its own privacy policy. The game doesn't send it, and it doesn't show me individual players.
What earlier versions send
Version 1.5 and earlier send gameplay analytics to PostHog without asking first. Their analytics library adds technical details such as device model, operating system, language, timezone and network context, and PostHog can add an approximate location worked out from the IP address. These versions keep sending until you update or delete the app.
Early test builds of 1.6, available only through TestFlight, ask first. If you chose to share, they send a small, fixed set of events until you update:
- App opens.
- Walkthrough starts and finishes, including whether it was replayed or skipped.
- Match starts, completions and abandonments.
- Opponent difficulty, who won, how the match ended, or which phase you left.
Events from both kinds of version include a timestamp, the app version and a random identifier created on your phone. That identifier connects events from the same installation, so this data is not completely anonymous, even though I never asked for your name or an account.
Who handles it
I'm responsible for the analytics earlier versions send, and I use it only to understand how the game is played and to improve it. It goes to PostHog's EU Cloud, hosted in Frankfurt, which receives these events on my behalf. Its infrastructure and service providers can also process data outside the EU; EU hosting does not mean every processing step happens only there. See PostHog's privacy information, service-provider list and data-processing terms.
Like any internet service receiving a request, PostHog receives the connection's IP address. This project's settings discard client IP addresses from stored events. The 1.6 test builds also ask PostHog not to add IP-derived location or create a person profile, and their checked events contain neither IP nor location properties. This is not a promise that network infrastructure never processes an IP address.
How long information stays
PostHog does not automatically delete this project's events based on their age. Its seven-year window limits how far back I can query events; it is not a deletion deadline, and events can remain stored beyond it. There is currently no scheduled age-based deletion. Updating to version 1.6 from the App Store stops future sharing; it does not delete information already sent.
Access and deletion requests
Contact james@coverd.cc to ask about access or deletion. There is no account or name attached to gameplay events, so an email address alone may not let me locate a particular installation's events. I will explain what can be identified and what options are available.
Where the relevant events can be identified, PostHog support can handle a deletion request even though this project does not create person profiles. PostHog says processing can take up to 30 days after a request has been approved and added to its deletion queue. Approval happens before that, so this is not a promise of deletion within 30 days of your email. Backup copies remain for a further 30 days after deletion from the live system. I will keep you informed about your request.
Depending on the applicable law and circumstances, you may also request correction, restriction or a portable copy of your data, or object to its use. You can raise a concern with me or complain to the UK's Information Commissioner's Office.
Contact and this website
If you email me, I receive your email address and whatever you include so I can respond. Please do not send sensitive information unless it is needed for your request. This website has no analytics scripts or advertising cookies. Its host, Railway, necessarily receives connection and request information to serve the pages; see Railway's privacy information.
Changes
If any of this changes, I'll update the date at the top and post the new version here.