We collect information from three main sources: information you provide, information generated by your use of the app, and information provided by integrated services.
2.1 Information You Provide or Create in the App
- Habit and check-in data (for example: habits, records, check-in status, check-in notes, counters).
- Productivity and planning data (for example: tasks, wish list, redemption history, reminders).
- Card-related data (for example: collected cards, card notes).
- User profile data stored locally (for example: nickname, avatar URL, linked account status).
- App settings and preferences stored locally through mechanisms such as Room, DataStore, and SharedPreferences.
- Optional exported data when you export CSV files (saved to a location you select).
- Feedback content you send via your email app. The in-app feedback email template may prefill technical context such as Android version and app version information.
2.2 Account and Sign-In Information
If you use Google Sign-In / Firebase Authentication, we may process:
- Google/Firebase user ID (
uid).
- Display name.
- Profile photo URL.
These fields are used to update local account linkage fields such as openId, openNickname, and avatarUrl.
2.3 Cloud Backup Information
If you are logged in and eligible for cloud backup, and you choose to use backup features, ShineDay may back up selected app data to your Google Drive appDataFolder, including:
- Habits.
- Periods/contexts.
- Records.
- Cards.
2.4 Purchase and Subscription Information
For membership purchase and restoration, ShineDay uses Google Play Billing. We may process billing-related status information such as purchase state, product identifiers, and purchase tokens as provided by Google Play Billing APIs.
2.5 Technical and Usage Information from Service Providers
We integrate Firebase services (including Analytics, Crashlytics, Performance Monitoring, Remote Config). These services may process technical and usage data, including crash diagnostics, performance metrics, app instance/installation identifiers, and device/app metadata, according to their own privacy terms.
2.6 Network Requests
To load daily card content, ShineDay sends requests to our backend endpoint /v1/common/card with fields such as cardDate and request timestamp (gmtRequest).
2.7 Permissions
ShineDay currently requests:
INTERNET (network communication).
POST_NOTIFICATIONS (daily reminders and notification delivery).