Firebase Notifier helps users compose, send, save, and schedule Firebase Cloud Messaging notifications. Processed data depends on the features the user enables.
Account data
The app uses Google Sign-In to authenticate the user, restore sessions, and load available Firebase projects. Google identifiers are used to isolate user data.
App content
Drafts, templates, history, saved targets, and schedules may include notification titles, bodies, custom data, test tokens, and technical FCM responses.
Storage and sync
Data can be stored locally in the app. When sync is enabled, Firebase Notifier uses the private Google Drive appDataFolder, accessible only by the app.
Third-party services
The app may communicate with Google/Firebase for authentication, project listing, and FCM sending. RevenueCat may manage Pro and Max subscriptions. A scheduler backend may process schedules.
Secrets and security
Firebase server secrets must never be copied to Google Drive or exposed in exports. Server communication should use HTTPS in production.
Retention
Local data remains on the device until the user deletes it or the app performs cleanup. Synced data follows the connected Google account and appDataFolder behavior.
User choices
The user can sign out, disable Drive sync when available, delete templates, history, or schedules, and manage subscriptions through Apple and configured subscription services.
Contact
For data requests, use the support channel listed on the App Store page or inside the published app.