The personal information that the app collects is your name and email address, our third party vendor might collect more, please read section n. 5 for that.
We collect information from you when you register on our app, so when you create a new account (Sign Up) or log in through Facebook. Our third party vendor might collect other different data in different times (app launch or on account registration) during the usage of our Services.
We do not use your information for any purpose at all, except to verify your data does match with what we collected from you and so to let you in. From time to time we might need to send some push notifications related to app specific new features to enrich your experience whilst playing to Wordtie.
In one of our particular feature of our app, we ask our users the permission to access their photo library should they want to, in order to use one of their picture as a player picture. That picture is not uploaded anywhere and it's in fact not stored anywhere and not persisted throughout an app session.
As a logged Facebook user, we offer our users (should they accept) the capability to share the Leaderboard results on their timeline, through the Share button, only available to Facebook logged in users. The Share on timeline feature gives permission to the app to upload a picture of the Leaderboard result on their timeline with an optional message to attach.
You can send us an email, stating that you want or might need information about what we collect, we can also help you understanding how you can opt-out of certain Services that our third party vendor collects.
The Studio does not have or use any personal databases, but the app relies on the usage of a few Services from Firebase. The Firebase Services that Wordtie use are: Cloud Firestore, Firebase Authentication, Firebase Crashlytics, Google Analytics. The above mentioned Services collect IP addresses, user names, email addresses, passwords (not for Facebook login), user agents, crash traces, device model, OS installed, minidump formatted data to process crashes.
On May 25th, 2018, the EU General Data Protection Regulation (GDPR) replaced the 1995 EU Data Protection Directive. On January 1, 2020, the California Consumer Privacy Act (CCPA) took effect. Google is committed to helping our customers succeed under these privacy regulations, whether they are large software companies or independent developers.
The GDPR imposes obligations on data controllers and data processors, and the CCPA imposes obligations on businesses and their service providers. Firebase customers typically act as the 'data controller' (GDPR) or 'business' (CCPA) for any personal data or information about their end-users they provide to Google in connection with their use of Firebase, and Google generally operates as a 'data processor' (GDPR) or 'service provider' (CCPA).
This means that data is under the customer's control. Customers are responsible for obligations like fulfilling an individual's rights with respect to their personal data or information.
Google Analytics uses the data to provide analytics and attribution information. Google Analytics retains certain advertising identifier associated data (e.g., Apple’s Identifier for Advertisers and Identifier for Vendors, Android’s Advertising ID) for 60 days, and retains aggregate reporting without automatic expiration. Retention of user-level data, including conversions, is fixed at up to 14 months. For all other event data, you may set the retention in your Analytics settings to 2 months or 14 months. Learn more.
The Facebook SDK collects the following information when you use Facebook Login: App Events: This covers generic App Events (e.g. App Install, app launch) and other standard logging for product metrics (e.g. SDK loading and SDK performance). Note that some of these events (e.g. App Installs, app launches etc.) are automatically logged as mentioned above. Developers can choose to disable automatic logging and log explicit events manually instead (instructions here for iOS and Android). Configuration data: After a user has logged in, the SDK makes periodic background requests to manage the lifetime of the access token automatically. Error information: The SDK captures error information, including during initialisation of the SDK, which may include a user ID of individuals who are logged in to Facebook. Short-term data: The SDK measures some user activity for purposes of managing fraud and abuse. This data is only retained for a very short period for those not logged in to Facebook. Use of this information about individuals with a Facebook account is governed by Facebook's Data Policy.
If you wish to delete any user data related to Wordtie, please follow these instructions. Go to Options Screen (top right button in the main game view), then at the bottom of the page you will notice the App version number and build number. Now tap on that number, in your pasteboard you have your unique user identifier now that you can send to us via email requesting a user data deletion to wordtie.app@gmail.com.
In max 3 working days then, your Wordtie user data will be deleted from Firebase.
These procedures are to guarantee the anonymity of the sender should you have decided to hide your email once signed up.
Firebase services encrypt data in transit using HTTPS and logically isolate customer data.
For any queries or information you may require, contact us at wordtie.app@gmail.com