Firebase Pulse Privacy Policy

Information the app accesses

Firebase Pulse requests Google authorization only after the user chooses to connect an account. The app requests identity, email, Firebase project management and messaging permissions, plus read access to Storage, BigQuery exports, Cloud Monitoring, and Analytics so it can distinguish saved Google accounts and list the Firebase projects each account can access. The app may process a stable Google account identifier, the Google account email and display name returned by the authorization flow, granted OAuth scopes, Firebase project identifiers, project display names, project numbers, project state, and related project metadata returned by Firebase APIs. When a service is selected, the app may also process Storage object metadata, Firebase Authentication user identifiers and email addresses, account and provider status, Remote Config templates, aggregate Crashlytics reports, exported Performance trace samples, and aggregate Analytics reports.

The app also lets users enter Slack notification settings. If a user configures Slack, the app may store a Slack incoming webhook URL, channel name, bot display name, notification preferences, test status, and local logs of Slack notification attempts.

How information is used

Firebase Pulse uses this information to keep project data separated by Google account, let the user switch between saved accounts, show accessible Firebase projects, display monitoring and alert setup screens, show account connection and permission state, and send Slack test or alert messages when the user configures that feature. The app performs supported project changes and sends Cloud Messaging payloads only when the user requests and confirms the operation. Remote Config publishing requires a review step and protects against overwriting a newer template. Other administrative operations open Firebase Console.

Local storage

Firebase Pulse stores saved Google account identifiers, email addresses, display names, account-specific project summaries, alert rules, metric snapshots, incident records, Slack settings, and Slack notification logs in local app storage on the Android device. Google access tokens are used to call Firebase APIs during the active authorization flow; they are not stored in the account cache, sold, or used for advertising. Service responses and edited Remote Config templates remain in memory and are cleared when the user changes or disconnects the Google account.

Sharing and third parties

Firebase Pulse sends authenticated requests to Google Firebase, Google Cloud, and Google Analytics APIs when the user connects Google access and uses the corresponding service. User-approved Remote Config changes and Cloud Messaging payloads are sent to the selected Firebase project. If Slack notifications are configured, Firebase Pulse sends the user-configured notification payload to the Slack webhook URL provided by the user. The app does not sell personal or sensitive user data.

Security

Network requests use HTTPS. Users should treat Slack webhook URLs as secrets because anyone with a valid incoming webhook URL may be able to post to the connected Slack destination. Keep device screen locks, Google account security, and Slack workspace permissions configured appropriately.

Retention and deletion

Information stored by Firebase Pulse remains on the device until the user removes it through app controls where available, clears app storage, or uninstalls the app. Disconnecting an active Google account removes that account and its cached project summaries from the device without removing other saved accounts. Users can request privacy support by emailing privacy@created.link.

Children

Firebase Pulse is intended for developers, founders, and operations teams. It is not directed to children.

Changes to this policy

This policy may be updated as Firebase Pulse changes. Material changes will be reflected by updating this page and the "Last updated" date above.