Last updated 4 November 2026
StrikeKeeper is a bowling score-tracking app. This policy explains what it collects, what it does not, and what you can do about it. It is written to match what the app actually does.
Your games are stored on the device itself, and the app never contacts our server. We do not know you exist. The only thing that leaves the phone is the anonymous usage statistics and crash reports described below, and only until you switch them off.
Your account:
| What | Why |
|---|---|
| Your email address | It is how you sign in, and how you would recover your account |
| A display name | Shown in the app. If you do not choose one, we use the part of your email before the @ |
| Your password, hashed | So you can sign in. See “How your password is handled” below. There is none if you only use Sign in with Apple or Google |
| If you choose Sign in with Apple or Google: the account ID Apple or Google gives us for you, and the email address and name they share | So that provider can sign you in to the same account each time. We never see your Apple or Google password. If you use Apple’s “Hide My Email”, we only ever see the private relay address |
| The date you signed up | Ordinary account record-keeping |
Your games, for each game you have backed up:
| What | Why |
|---|---|
| When you bowled it | So your history is in order and your stats are right |
| Your score, and whether the game was finished | It is your score |
| Each roll: which frame, which ball, how many pins fell | This is what your scorecard and stats are made of |
| Which pins were left standing, when you used the pin diagram | Split and pin-leave stats. Blank when you used quick number entry |
| Game details, if you add them: the kind of game (league, practice, tournament, open), the bowling center, the ball, the lanes, the oil pattern, and your note | So your stats can be split by kind and by ball, and your history shows where and how you bowled |
| Whether a game was typed in as a final score only (a past game with no frames) | So it counts toward your average without pretending to have frames |
| A bowler's name, when you scored a game on your phone for somebody else | So their game is kept apart from yours and never counts toward your average |
That is the complete list. There is nothing else in our database. If you score games for other people, only type in what they are happy for you to keep — a first name is plenty.
We do not do this. StrikeKeeper does not track you across other companies' apps or websites, and does not share anything with data brokers or advertisers.
Whether or not you have an account, the app sends a handful of anonymous events to Google Analytics, so we can tell whether anyone is using StrikeKeeper and whether it is crashing:
| Event | What it carries |
|---|---|
| The app was opened | The app version |
| A game was finished | Its score, strikes and spares, how many rolls were entered on the pin diagram versus as numbers, the kind of game (if set), and whether it was scored for somebody else — never the center, the note, or any name |
| A scorecard was shared, or games were exported | That it happened, and how many games were exported |
| The app hit an error | The type of error, its first 100 characters, where in our code it happened, and the app version |
Each event carries a random number made up by the app when it was installed. It is not your account, your email, or any identifier from your phone, and we never connect it to them. Google receives your device's IP address as part of sending the event, as with any request on the internet; Google states that Google Analytics 4 does not log or store IP addresses.
From version 1.1.2 the app also uses Microsoft Clarity, a free usage-analytics service from Microsoft, to see which screens people open and which buttons they tap, so we can find the confusing parts and fix them. Clarity records taps, swipes and scrolling, the screens visited, how long a visit lasts, the app version, device model, operating system, screen size, a rough location (country or region, worked out from your IP address) and errors, and it can replay a visit as a short recording.
All text is hidden. We run Clarity in its strictest setting: every piece of text and every image on the screen, including your scores, names, centers and notes, is blanked out on your phone before the recording is sent. Clarity uses its own random identifier for your phone; we never give it your account, your email or your games, and it is not used for advertising. Microsoft processes this data under its own privacy statement: privacy.microsoft.com.
To switch it all off: Stats tab → Share anonymous usage. Off means off: the app then sends no counts, no crash reports and nothing to Clarity.
This policy also covers strikekeeper.com, the app's website with free bowling tools and guides. The score calculators and other tools run entirely in your browser: nothing you type into them is sent to us or to anyone else.
To see how many people visit and which pages help them, the website uses Google Analytics and Microsoft Clarity. They record the pages you visit, how you got here (for example a search engine), clicks and scrolling, your browser, device type and screen size, and a rough location worked out from your IP address. Clarity can replay a visit as a short recording. Both set cookies or use your browser's storage to recognise a returning visitor. This is a separate Google Analytics property from the app's, nothing on the website is linked to your StrikeKeeper account, and none of it is used for advertising.
You can block these with your browser's privacy or tracking-protection settings or a content blocker; the website works the same without them. Google's and Microsoft's own policies apply to what they receive: policies.google.com/privacy and privacy.microsoft.com.
If you have an account you can add friends. Nothing about this happens unless you use it, and it works like this:
For this, our server stores: your friend code, the list of people you have added, whether sharing is on, and — only while sharing is on — the pins of the game you are bowling, replaced after every roll and ignored fifteen minutes after the last one. Removing a friend removes the connection both ways. Deleting your account removes all of it.
When you share a scorecard or export your games to a spreadsheet, the app hands a picture or a file to your phone's own share sheet. It goes only where you send it; nothing passes through us.
When your phone talks to our server, our hosting provider receives your device's IP address as an ordinary part of how the internet works, and may record it in server logs.
We also count failed sign-in attempts against an IP address and an email address for fifteen minutes at a time. This is a security measure — it is what stops somebody guessing passwords — and those counts are held only in the server's memory, are never written to the database, and disappear when the server restarts.
Your password is hashed before it is stored, using bcrypt. Hashing is one-way: the stored value cannot be turned back into your password. We never store your password as you typed it, it is never included in anything the server sends back, and nobody working on StrikeKeeper can look it up or read it. If you forget it, it cannot be recovered — only replaced.
Nobody buys it, and nobody is given it to use for their own purposes. We do not sell, rent, or trade your information.
The only third parties involved are the services that make the app run:
These providers process data on our behalf so the app can work. Our server and database are hosted in the United States, so if you are elsewhere, your information is stored there.
We would only hand over information if we were legally required to.
Whether or not you have an account, the app keeps the following on the device itself:
Deleting the app removes all of it from your phone.
Your games and account stay until you delete them. There is no automatic expiry — a bowler's history is meant to last.
When you delete your account, it is removed from our database immediately, and every game and roll attached to it goes with it, along with your friend code, your friend connections and any live game. This is permanent and cannot be undone by us or by you.
Use the app without an account. Everything except the backup works, and nothing is sent to us.
Delete a game. Deleting a game in the app removes it from your phone and from our server.
Delete your account. In the app: Stats tab → Account → Delete account. It asks for your password to confirm (or, for an account made with Apple or Google, to sign in with it once more), then permanently deletes your account, your games, and your rolls from our server.
Your games stay on your phone when you delete your account. Deleting the account removes the backup, not your own history. If you want the games gone from the phone too, delete them in the app or remove the app.
If you no longer have the app, or cannot sign in to it, you can still have your account deleted. Email strikekeeper@citrusync.com from the email address you signed up with (for an account made with Apple or Google, the address that account uses) and ask for your account to be deleted. Writing from that address is how we know the request is really from you; if we cannot match it to an account, we will write back before deleting anything.
We delete exactly what the in-app option deletes: your account, every game and roll backed up to our server, your friend code, your friend connections and any live game. It is done within 30 days of your email, usually much sooner, and we reply to confirm. Like the in-app option, it is permanent. Games still on a phone are not touched.
Depending on where you live you may also have rights to ask for a copy of your information, to have it corrected, or to have it erased. Get in touch and we will help.
StrikeKeeper is not directed at children under 13, and we do not knowingly collect information from them. If you believe a child has given us their information, contact us and we will delete it.
If this policy changes, the date at the top will change with it, and the current version will always be at this address. If a change ever meaningfully affects what happens to your information, we will say so in the app rather than quietly editing this page.
Questions about this policy, or about your information: