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, and read-only Firebase scopes 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.

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, keep read-only account connection state visible, and send Slack test or alert messages when the user configures that feature. The first release is designed for safe inspection and setup. It does not perform destructive Firebase project changes.

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.

Sharing and third parties

Firebase Pulse sends data to Google Firebase APIs when the user connects Google access. 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.