Last updated September 16, 2021.
When you start using Fancade you will be assigned a unique identifier that is stored on your device. It just looks like a bunch of random numbers and letters, and is not visible to other Fancade users, but serves to link any in-app purchases you make to your device so that they persist between play sessions.
If you choose to, you may connect an email and password to the identifier, creating a Fancade account that lets you sign in and access your purchases from your other devices. The email you provide is not visible to other Fancade users and will not be used to send you spam! However we may use it to contact you, e.g. to send a password reset link if you forgot your password.
Creating a Fancade account enables you to publish games you've made! The game, and the nick name you choose to publish as, will be visible to other users, so don't include any information that you do not wish to be public.
Fancade uses Google Firebase to provide these services and you can find more information here.
In order to improve Fancade we may collect usage statistics, such as the number of users, how often they play, and whether anyone actually buys anything. Fancade uses Google Analytics for Firebase to collect this analytics data and you can find more information here.
You may choose to play Fancade games for free, with ads. Your device has an Advertising Identifier and the ad provider uses this identifier, and information they have collected about you, to select content that is more likely to actually be of interest to you. Ads are entirely optional and you can opt out by using the mobile app's in-app purchases instead. Fancade uses Google AdMob and Google AdSense to provide ads and you can find more information here.
We do our best to find and fix software bugs before publishing new versions of the app. But, realistically, some bugs will slip through and may cause the Fancade app to crash. If this happens the app may send a crash log to help us find and fix the bug! Fancade uses Google Crashlytics to collect crash logs and you can find more information here.
Feel free to contact us at email@example.com if you have any questions!