Privacy

On your device

Your progress, stars, coins, shop items, settings, chosen music, the nickname you type for Compete, and your challenge progress are saved in your browser's local storage. They don't leave your device, except for the Compete details and the anonymous play counts described below.

To work offline, the game also keeps a copy of its own files in your browser's cache.

To remove all of this, clear this site's data in your browser settings, or uninstall the app from your home screen.

Compete

Compete sends details to our server only when you use it. We store:

• the nickname you type (shown to the people you play against; please don't use your full name);
• a random player ID your device makes up. It isn't linked to your name, phone number, email or any account;
• the challenges you create or accept, your shots on each hole, and when you played.

Anyone with a challenge's link can see its scoreboard: nicknames, shots and whether someone is still playing.

This is kept in a database run by Upstash, in London (UK), and served through Vercel. Challenges are deleted automatically a year after they're created, and your win record a year after your last game.

Deleting your Compete data

In the game, open Settings and tap Delete my Compete data. That removes your scores, accepts and win record from our server and gives your device a new player ID. Challenges you created stay for the people who played them, with your nickname replaced by "Someone".

Anonymous play counts

So we can show how many people play, the game sends our server a short note when it opens, comes back into view or goes into the background. The note says only:

• whether this is the first time this device has opened the game, and the first time today, this week and this month;
• when you come back on a later day, how many days it has been since this device first opened the game (so we can see whether people come back);
• whether the game is running as an app installed on your home screen, the first time it does;
• how many shots you've taken and holes you've sunk since the last note.

It contains no player ID, nickname, progress or anything else that could tell your device apart from another. The server doesn't store the notes: it adds them to running totals (for example "1,204 players" or "57 active today"), which anyone can see on the About page. The totals are kept in the same Upstash database as Compete.

YouTube music

If you choose YouTube as your music, the game embeds YouTube's player (from youtube-nocookie.com) and uses the YouTube API Services to control it. YouTube and Google may then collect information under their own policies. By using the YouTube option you agree to the YouTube Terms of Service, and the Google Privacy Policy applies to what YouTube collects.

Holeshot doesn't sign you in to YouTube, can't see your YouTube account, and receives no data from YouTube. The link you paste is only saved on your device.

Other services

• Visitor statistics: we use Vercel Web Analytics to see how many people visit, which pages they open, which site sent them, and their country, browser and device type. It uses no cookies and stores nothing on your device. Vercel tells visits apart with a code made from your request that is thrown away after 24 hours, so visits can't be linked across days or to you.
• Hosting: the game is hosted by Vercel, which handles requests and keeps short-lived server logs (such as IP addresses) to run and protect the service. See Vercel's privacy policy.
• Fonts: the game's fonts load from Google Fonts, so Google receives a request from your browser when they load. See the Google Privacy Policy.
• Music tracks from Pixabay are served from our own site; Pixabay doesn't receive anything.

Children

Holeshot is suitable for all ages and has no ads, purchases with real money or chat. We don't knowingly collect personal information from children; nicknames should never be a real full name.

Questions and changes

If this policy changes, we'll update this page and the date at the top. For questions or requests, open an issue on the game's GitHub page.