72 separates system notices from offer and chat activity. The system-notification tab is reserved for 72 announcements, support, and operational messages; offer and chat activity belongs to its relevant surface.
01Notification types
External FCM/APNs pushes can announce an offer, acceptance, new chat, message, support response, security event, or service notice. In-app banners and sounds operate while the app is active.
02Controls
Global external and in-app controls are available in Settings. A permanent chat can separately mute that person's external or in-app notifications.
03Badges and delivery
Badges represent unseen items on the relevant tab and clear when the item is viewed according to product rules. Delivery can be delayed or suppressed by device, OS, network, permission, privacy, mute, or safety state.
04Notification preview
Message previews are privacy-first. Message previews may be off/private by default. When previews are off, push notifications may use generic wording and may not show message text or sender profile photo. When previews are enabled, sender name, profile photo, and message content may appear on the lock screen or in the notification center.
05Silent or data notifications
Where platforms allow it, some notifications may be data-only, badge, token-refresh, navigation, or sync related and may not show a visible alert. Behavior may vary by device, operating system, Firebase/FCM, Apple/Google platform rules, and app state.
06Notification permissions
Notification permission is controlled by the device operating system. 72 may request permission or show permission state in the app, but final permission depends on device settings and platform rules.
- Users can disable system notification permission in device settings.
- 72 may provide in-app preferences such as introduction notifications, general notifications, and message previews.
- If device permission is off, push notifications may not arrive even if in-app preferences are on.
07Notification privacy
Notifications can contain sensitive information. If message previews are enabled, content may appear on the lock screen, connected devices, or operating-system notification history. Users should keep previews off when they need more privacy.
08Device behavior
Offline, reconnect, retry, failed delivery, and expired notification behavior may vary because of network, device, operating system, Firebase/FCM, Apple/Google services, app state, and backend state. A notification may be delayed, never arrive, expire, or point to content that is no longer accessible when opened.
09Notification safety
Notifications may be limited to protect safety and privacy. 72 may use open-only or generic notification text for media, voice, private media, location, or sensitive content. Some notifications may not be sent because of safety, abuse, block, mute, report, moderation, or legal reasons.
10User controls
Users may control device notification permission, introduction notifications, general notifications, message preview, chat mute/unmute, block/report, permanent chat end/delete/clear, and account deletion. Some controls are managed in the app, while others are managed in device settings.
11What 72 does not guarantee
72 does not guarantee that notifications will always arrive, arrive on time, appear on the correct device, complete every action successfully, apply preview settings identically in every operating-system context, or prevent external recording of media. 72 does not present notification generation as an AI decision system and does not claim E2EE, screenshot prevention, or absolute media protection.