Privacy Policy
- Ball Sort Puzzle Challenger (Package Name: com.FeliceCasaTechnologyPTE.LTD.BallSortPro)
- Block Puzzle-Merge Games (Package Name: com.FeliceCasaTechnologyPTE.LTD.BlockPuzzleMaster)
- Water Sort – Color Puzzle (Package Name: com.FeliceCasaTechnologyPTE.LTD.WaterSortMaster)
- Any additional hyper-casual or puzzle games I release in the future that share similar data collection and usage practices
1. Collection of Personal Information
1.1 Information Collected Automatically
- Device Information:
- Android Advertising ID (adid)
- Google Install Referrer
- Firebase Installation ID
- App Instance ID (to track app usage, used by Firebase)
- Adjust Identifier
- Device-specific hashed IDs (for attribution, used by Adjust)
- Device and System Information:
- Device model (e.g., SM-G9910)
- Manufacturer (e.g., Samsung, Xiaomi)
- Operating system name and version (e.g., Android 13)
- Screen resolution and density (e.g., 1080×2400, 420dpi)
- CPU architecture (e.g., arm64-v8a)
- Available storage and memory (RAM and ROM)
- Language setting (e.g., en-US)
- Time zone and country/region (e.g., GMT+9, JP)
- Battery level and charging state
- Carrier or network operator name
- Wi-Fi and network connectivity status
- App version and package name
- Installation source (e.g., Google Play)
- IP address
- Application Usage Data:
- Number of app launches and session duration
- In-app events (e.g., level_start, level_complete, purchase, share_click)
- Button clicks and screen views
- Feature usage frequency and behavior patterns
- User engagement metrics (e.g., daily active users, retention)
- Crash logs, error stack traces, and exception reports
- App foreground/background state transitions
- Attribution and Advertising Data:
- Campaign ID, ad network, and creative ID
- Click-through and impression events
- Cost per install or event metrics
- Conversion events and user acquisition source
- Deferred deep linking and attribution parameters
- Payment and Purchase Data:
- Product ID and order ID
- Price, currency, and quantity
- Transaction timestamp and status
- Purchase validation data (sent securely via Google Play)
- Location Information (Approximate): I do not track or collect your precise location. However, the App may use or infer coarse, approximate location to tailor general content or ads.
The collected data will be transmitted to Adjust and Firebase, both of which are highly regarded third-party analytics platforms. All data will only be used for analytical purposes. We do not store any data, and all data will be processed by Adjust and Firebase with secure protocols (HTTPS / TLS).
1.2 Limited Scope of User Data
- Ad Delivery and Optimization: Data collected by Applovin MAX, Admob, and Adjust is used to deliver relevant ads, improve targeting accuracy, measure performance, and prevent fraud.
- Analytics and Performance Monitoring: Firebase Analytics and Adjust use this data to analyze user behavior, track key performance indicators (KPIs), and identify trends in user engagement and feature usage.
- Crash Reporting and Stability Improvement: Firebase Crashlytics collects crash stack traces and device context to help identify and resolve bugs, ensuring a better user experience.
- In-App Purchases: Unity IAP collects minimal purchase data to fulfill orders. No sensitive billing information, such as credit card details, is collected or stored.
1.3 Cookies and Similar Technologies
- Remember your login or other preferences;
- Analyze your interaction with the Website or App to improve features;
- Deliver more relevant content or ads (if applicable).
1.4 Third-Party SDKs and Services
- Adjust: Used for user attribution (installs, campaign tracking) and analytics to evaluate the effectiveness of marketing campaigns.
- Firebase (Analytics, Crashlytics, RemoteConfig): Collects in-app events and crash data to improve performance and user experience.
- AppLovin MAX and AdMob: Provide in-app advertisements and optimize ad performance, collecting data such as Google Advertising ID and approximate location to show relevant ads and measure ad effectiveness.
- Nice Vibration: Provides vibration feedback in gameplay without storing or transmitting any user data.
- Native Share: Provides system-level sharing feature without involving any user data or sensitive permissions.
1.5 User Permissions Declaration
The following permissions are requested by the app for specific purposes, ensuring the smooth operation of features and compliance with applicable privacy standards. Below is a detailed breakdown of each permission, its purpose, the SDKs that use it, and the data collected:
-
android.permission.ACCESS_ADSERVICES_AD_ID
Purpose: Accesses the Android Privacy Sandbox’s ad ID for privacy-preserving ad attribution and tracking on Android 13+.
Used by: Adjust (for ad attribution), Applovin MAX, Admob
Usage Scenario: Allows SDKs to access the new AdServices identifier securely when Android Advertising ID access is restricted or deprecated.
Data Collected: Anonymized ad ID (not tied to personal identity) -
com.google.android.gms.permission.AD_ID
Purpose: Accesses the Google Advertising ID (GAID) for attribution, targeting, and analytics.
Used by: Applovin MAX, Admob, Adjust, Firebase Analytics
Usage Scenario: Serves as the primary identifier for ad personalization, user acquisition tracking, and measurement.
Data Collected: Advertising ID (resettable by the user, not personally identifiable) -
android.permission.ACCESS_ADSERVICES_ATTRIBUTION
Purpose: Used to participate in Android 13+ attribution APIs under the Privacy Sandbox framework.
Used by: Adjust (for click/view attribution)
Usage Scenario: Triggered when attribution is handled using the Attribution Reporting API.
Data Collected: Attribution tokens and anonymous install interaction logs -
android.permission.ACCESS_ADSERVICES_TOPICS
Purpose: Enables participation in the Topics API for interest-based advertising without tracking individual users.
Used by: Applovin MAX, Admob (if Topics API is supported)
Usage Scenario: Used in ad personalization systems compliant with Android’s new Topics-based targeting.
Data Collected: Anonymous topic IDs generated by the system -
android.permission.ACCESS_NETWORK_STATE
Purpose: Checks if the device is connected to the network and whether it’s on Wi-Fi or mobile data.
Used by: Applovin MAX, Admob, Adjust, Firebase Analytics
Usage Scenario: SDKs verify network availability before serving ads or sending logs.
Data Collected: Network connection type (Wi-Fi/Mobile), no personal data -
android.permission.ACCESS_WIFI_STATE
Purpose: Provides additional Wi-Fi connection status details (e.g., signal strength, SSID).
Used by: Applovin MAX, Admob
Usage Scenario: Used internally by SDKs to assess network quality, not exposed to the app.
Data Collected: SSID/BSSID (in rare cases), but typically anonymized or not used directly -
android.permission.FOREGROUND_SERVICE
Purpose: Allows SDKs to run persistent foreground tasks without being killed by the system.
Used by: Firebase, Adjust, or internal components during analytics dispatch or background syncing
Usage Scenario: Ensures tasks like app startup, attribution tracking, or real-time config syncing are completed.
Data Collected: None directly, only enables persistent operation -
android.permission.INTERNET
Purpose: Grants access to internet resources.
Used by: Applovin MAX, Admob, Firebase, Adjust, Unity IAP
Usage Scenario: Required to serve ads, send crash logs, analytics events, perform remote config fetch, and complete purchases.
Data Collected: Enables all network-based data transmission, including analytics and crash data -
android.permission.VIBRATE
Purpose: Enables the app to trigger device vibration feedback.
Used by: Nice Vibration
Usage Scenario: Used for haptic feedback during game interactions (e.g., level completion, button taps).
Data Collected: None -
android.permission.WAKE_LOCK
Purpose: Keeps the device awake during long operations.
Used by: Firebase (for syncing config or logs), Adjust (for background task completion)
Usage Scenario: Used during data syncing or delayed attribution after app install.
Data Collected: None directly; used to control device state -
com.android.vending.BILLING
Purpose: Allows the app to make in-app purchases through Google Play.
Used by: Unity IAP
Usage Scenario: Triggered when a user initiates an in-app purchase.
Data Collected: Product ID, price, transaction status (no credit card or sensitive personal info) -
com.applovin.array.apphub.permission.BIND_APPHUB_SERVICE
Purpose: Internal Applovin permission to bind its SDK service for ad preloading and management.
Used by: Applovin MAX
Usage Scenario: Enables Applovin to preload ads efficiently and manage mediation logic.
Data Collected: None directly, but supports ad-related data delivery through other mechanisms -
com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE
Purpose: Enables SDKs to retrieve install referrer information via the Google Play Referrer API.
Used by: Adjust
Usage Scenario: Used immediately after app install to determine campaign source (e.g., which ad led to the install).
Data Collected: Install timestamp, referrer string (campaign parameters), does not identify the user directly -
[package name].DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION
Purpose: App-defined internal permission to restrict exported broadcasts or services for security.
Used by: App itself, not SDKs
Usage Scenario: Prevents unauthorized external apps from triggering internal components (e.g., receivers).
Data Collected: None
1.6 Information You Provide Voluntarily
2. Use of Information
2.1 Providing and Improving Services
2.2 Security and Risk Management
2.3 Personalization and Advertising
2.4 Communications
3. Information Sharing
3.1 Third-Party Service Providers
3.2 Legal and Security Requirements
3.3 With Your Consent or Authorization
4. Legal Basis for Data Processing
- Consent: Where you have agreed to specific uses of your personal information as described in this Privacy Policy.
- Contractual Necessity: Where processing is needed to perform or fulfill a contract or agreement between you and me, such as providing the functionalities of a game you downloaded.
- Legal Obligations: Where processing is required to comply with laws or regulations.
- Legitimate Interests: For purposes such as maintaining the security of the App or improving game services, provided these interests do not override your fundamental rights and freedoms.
5. Data Storage and Security
5.1 Storage
5.2 Retention and Deletion
6. Children’s Privacy
7. Your Rights
- Access/Rectify: Request access to or correct your personal information.
- Erase: Request the deletion of your personal information where permitted by law.
- Withdraw Consent: For processing based on consent, you can withdraw it at any time.
- Restrict/Object: In certain circumstances, object to or request the restriction of processing, especially regarding direct marketing.
- Data Portability (if applicable): Request that your data be provided in a portable format for transmission to another provider.
8. Policy Updates
9. Contact Information
- Developer Name: FeliceCasa
- Official Website: https://www.felicecasatech.com/
- Email: [email protected]