Push notifications

Tools can deliver account notifications to the Android app or to a supported web browser.

Delivery priority

Push uses one account-level priority rule:

1. If one or more active Android app registrations exist, Tools sends push notifications to Android.
2. If no active Android registration exists, Tools sends to active web-browser registrations instead.
3. If neither transport is registered, no push delivery is attempted. Other configured notification channels such as email or SMS are unaffected.

Browser registrations remain stored as fallback while Android is active. You can disable individual registrations at any time.

Manage your registrations

Open My Profile -> Push notifications or visit /me/push while signed in.

The page shows:

• how many Android devices are active,
• how many browser registrations are active,
• which transport is currently preferred,
• all saved device/browser registrations and their last-seen state.

To enable browser push, select Enable or refresh browser push and grant the browser notification permission. Tools then registers that browser to your current account.

To disable browser push, use Disable this browser. You can also disable any active target from the registered-target list.

Android app

The Android app registers its Firebase Cloud Messaging token with the signed-in Tools account when push is enabled and the app has a valid Tools client token. Token rotation is handled automatically by the app.

If Android later becomes unavailable or its registration is revoked, an existing active browser registration becomes the fallback automatically.

Privacy and security

Push provider tokens are stored encrypted and are not displayed in full in the UI. The target list shows only a short fingerprint so registrations can be distinguished without exposing the provider token.