BallFields and Your Data

I firmly believe in privacy and in the principle that your data, is your data. I have setup a premium model, where I charge for the services that you use, specifically so I do not have to monetize your data in any way. This is how your data are used.

A) Identifiable Data

What do I store and how do I store it?

When you create a BallFields account, either by signing in with Apple or by using an email/password account, I collect and store your name, email (or the relayed email if chosen with Apple Sign in) and store it on the Google Servers (Firestore). These servers are not used by anyone but BallFields users.  The Firestore server assigns you a unique ID that is always associated with your account and with most data that you create. This ID is stored with:

• • Ratings you make as a spectator or player.
• • Comments (hints) you make as a spectator or player.
• • The awards you have obtained, for example the number of comments you make, the number of fields you visit etc.

If you purchase the optional Scouting module, this gives you access to group messaging and group media sharing. Your unique ID is stored with:

• • Each Scouting Organization you create.
• • Each Scouting Organization you follow.
• • Each message you post.
• • Each BallRoll media you post. (Note: These media are deleted after 30 days).
• • When you “Call a meet”, your exact location is shared with the people who are in your organization, but only long enough for them to get a notification.

What do I do with your uploaded data?

I treat it with respect. Apart from what is needed to run Ballfields, I will never share your data with a third party and I will never sell your data.

How is your data shared with third parties so that I can run BallFields?

• • Your account data (as described above), your purchase history and activity within the app are store on third party servers I pay for to run BallFields.

• • If you contact support, using the options on the support page, your email address and the conversations we have are stored on my Helpdesk providers servers.

How is your data used within BallFields app?

• • If you email me with a problem, I may privately access your data as needed to try and solve the problem.
• • I may privately use your data, in an aggregated fashion - not an identified fashion - with everyone else’s data to help facilities improve their offerings (for example - parking is always bad at this facility, or toilets are disgusting at this facility). I will never give an individual users ratings or data to any facility in an identifiable way.

What data is shared with people in Scouting Organizations?

• • You are either invited to or create and invite people to scouting organizations. 
• • Members in the same organization can see your name and your avatar photo.
• • If you “Call a Meet”, they will see your location only at the time you call that meet.

If at any point you would like to delete all your un-aggregated data you can do so from the Settings Menu->Account Details->Delete your account. If you do this, anything which identifies you will be deleted. Aggregated data that you have submitted (e.g. ratings) will not be deleted.

B) Anonymous Data

Data Captured to improve BallFields

In addition to the specific data mentioned above, I do capture some anonymous data that I use to improve the App:

• • I do track examples of events through Firestore, for example “Someone created a rating for Montgomery Field” or “Someone made a comment on this playing surface”. No service gets access to this and it is not identified with you. I do it to track popularity of features and facilities where people are using the app.
• • I use a crash reporter called “Crashlytics” to track crashes. If the app crashes for you, the next time that you load the app, technical data about what was happening right before the crash are uploaded to my server. This information includes non-identifiable data including things like what phone you were using and where it happened. I use my own logs (which you would send to me) to correlate what happened with that crash data.